The inbox and what each status means
One list of every session on every box, with whatever is waiting on you at the top. Here is how it sorts and exactly what each word on it means.
WatchOn this page
How the inbox sorts #
The inbox has one row for every live session, and one for every environment that has gone quiet. It is sorted by how much each needs you:
- Needs input sessions, longest wait first.
- Failed sessions, most recent first.
- Environments that are Down, then Stale, longest first.
- Sessions that are Working, then Idle, most recent activity first.
Ended sessions are not in the inbox. They are on their environment's page for as long as your plan keeps history.
You can filter by machine, by environment and by status. The filter changes what you see, not what alerts.
Session statuses #
A session's status is the last thing it said about itself.
| Status | It means | What moves it on |
|---|---|---|
| Working | A turn is running. | The turn ends, fails, or stops to ask you something. |
| Idle | The last turn finished, moments ago. | A new prompt makes it working. A minute with no reply makes it needs input. |
| Needs input | It is blocked on you. | You answer in the vendor's app and it goes back to working. |
| Failed | The last turn ended in an error. | A new prompt. |
| Ended | The session is over. | Nothing. A late message never brings it back. |
Needs input has three causes, and the row says which:
- Permission. The agent wants to do something its settings do not allow without asking, and the prompt has gone unanswered.
- Input. The agent finished its turn and nobody has replied for about a minute. An agent that stopped to ask you a question is here, and so is one that simply finished.
- A form. A tool the agent is using has opened a form or asked you to visit an address.
Watch knows which of the three it is. It never knows what the agent asked: the question is content, and content stays on the box.
Failed carries a short fixed word for the kind of error, such as rate_limit or authentication_failed. It is never the error's message. A session that fails does not alert; it waits in the inbox, second from the top.
Each session row also shows the names of its repos, its branch, and how long it has been in its current status.
Machine and environment statuses #
A machine's status comes from its heartbeats, and so does the status of each agent server on it.
| Status | It means |
|---|---|
| Online | Heartbeats are arriving on time. |
| Stale | A few have been missed. It may be a blip. |
| Down | The silence has gone on long enough to act on. |
| Pending | The machine has been added and has never reported. |
Deadlines gives the exact timing. Only a new heartbeat brings a machine back to online.
Two last-seen times, never one #
An environment's page shows two times side by side:
- Machine last seen: when Watch last received a heartbeat from the box.
- Agent server last seen: when a heartbeat last said this environment's agent server was running.
They are separate facts and Watch never merges them. A box can be perfectly healthy while one login's agent server has crashed, and that is a different problem from the box losing power:
| Machine | Agent server | What happened | Where to look |
|---|---|---|---|
| Online | Online | Nothing. | |
| Online | Down | The agent server stopped. The box is fine. | On the box: is the login still signed in, is its unit running? |
| Down | Down | The box is dark, or cannot reach the internet. | Power, network, then the box itself. |
An environment's own status is the worse of the two.
The page also shows the machine's health from its latest heartbeat: how full the disk is, the load, how long it has been up, and memory pressure.
The link out #
Each environment can carry one link to your agent vendor's own app. It is the only thing in Watch that goes anywhere, and it goes away from Watch. There are no buttons that approve a prompt, stop a session or restart a server, because Watch has no way to do any of those. See why.
When a row looks wrong #
The environment page has a list of the last few hundred messages Watch received for it, each marked with what Watch did with it: applied it, set it aside because a newer one had already arrived, or ignored it because the session had ended. It shows the same fields the box sent and nothing more. Troubleshooting uses it for the cases where a session's status does not match what you see on the box.