Session Watch

Session Watch gives you one place to see every Zide Assist session running across all of your open projects, and to jump straight to the one that needs you. It solves two problems that come up when you run several agents at once: finding a specific session that lives in a project you are not currently viewing, and noticing when a background session has changed state (started waiting for your approval, finished, or paused) while you were looking elsewhere.

Session Watch covers Zide Assist sessions and is available on every plan that includes AI access.

Open Session Watch

There are two ways to summon it:

Click the grid button in the footer, just right of the version number.
Press Ctrl+Shift+A.

Press Esc, click outside the panel, or use the button or hotkey again to close it.

The attention badge

The footer button changes color to signal what is happening across all your projects, no matter which one you are currently viewing:

Amber when one or more sessions are waiting on you (a tool approval or a pause), so you know to open Session Watch even when the waiting session is in another project.
Green when one or more replies are ready and unread (a turn finished while you were elsewhere) and nothing is waiting on you. Amber takes priority: if any session is waiting, the button stays amber.
Gray (the normal footer color) when there is nothing new to act on.

Reading the tiles

Session Watch shows one tile per session. Each tile is labeled with its project and shows the session’s latest message:

While a turn is in progress, the tile shows the message you sent, so you can tell what the agent is working on.
Once a turn is complete, the tile shows Zide’s reply.

If you use Relay to reach your sessions from another device, a tile also carries a small radio-tower mark in its top corner: lit while a remote client is watching that session right now, and slashed while the session is muted from the mirror. The same mark appears in the session’s own tab header, where you can also open a small popover to see who is watching and to stop or resume mirroring that one session. See the tab header for the controls; the tile mark is a read-only echo of that state.

Priority order

Tiles are grouped into four priority tiers, ordered so the sessions you can act on come first. The order is fixed when you open Session Watch and does not reshuffle while you are scanning. Within each tier, the most recently active session comes first.

Waiting for you (amber, glowing). The agent is blocked on a tool approval or is paused and needs your input. These tiles show your message plus a short banner saying the session is waiting. They are never dimmed, no matter how long ago they were last active.
Zide replied (green). The turn is complete and recent; it is your move. This tier has two shades: a reply you have not looked at yet (the turn finished while you were elsewhere) shows a green “Zide replied” label with a green outline and sorts to the top of the tier, while a reply you have already seen settles into a calmer gray. Opening the session, or watching the turn finish, marks it seen.
Working (blue, with a spinner). The agent is still processing your message. There is nothing for you to do yet.
Cold (dimmed). A completed session that has been untouched for a while, or a session that was restored from your last launch and has not been opened yet.

Jump to a session

Click any tile to jump to that session: Zide activates the owning project and switches to the session’s tab. This works for every tile, including a session that was restored from your last launch but not opened yet; clicking it opens the session for the first time.

Reaching your sessions from a browser (Relay)

Relay mirrors this desktop’s live sessions so you can watch — and, if you allow it, drive — them from a browser at account.zide.dev. Turn it on under Settings → Relay. Signing into the portal with your email is not enough on its own: each browser has to be paired with each desktop before it can see anything. This keeps a stolen or shared login from silently reaching your machine.

Pairing a browser

In the portal, pick this desktop and request access — Observe (watch only) or Interact (watch and send input).
Zide pops up a pairing request on this desktop showing the browser, its approximate location, and the access it asked for. Nothing is approved automatically. The same request also appears under Settings → Relay → Remote clients.
Choose Deny, Approve observe, or Approve interaction. (Approving interaction also needs Allow remote interaction turned on in Relay settings; while that is off, the button stays visible but disabled.) You can approve at the level asked for, or grant less — you can never grant more than was requested.
On approval, Zide shows an 8-digit code (for example, 1234 5678) with a five-minute countdown. Type it into the portal to finish pairing. The code is shown once, here only; Zide never sends it anywhere for you, and it never appears in logs or notifications. If it expires or you lose it, start a new request from the portal.

Pairing happens once per browser and desktop, not on every reconnect. A different browser (or the same one after you revoke it) pairs separately.

Managing paired browsers

Every paired browser is a row under Settings → Relay → Remote clients, shown whether it is currently online or offline:

Observe / Interact — change what a browser can do at any time. Interaction also requires the global Allow remote interaction switch.
Revoke — end a browser’s access. It loses its live connection and must pair again from the portal to return.

Turning Relay off immediately disconnects every browser and makes the desktop unreachable, but preserves valid pairings so they can reconnect when Relay is enabled again. Use Revoke to remove one pairing, or sign out everywhere to revoke them all. A browser’s access also ends on its own if its portal sign-in expires. While a desktop is offline, remote actions to it simply fail — nothing is queued to run later.