Inbox
One feed for everything your employees produced or need from you. Three kinds of item land here:
Three ways to read it
- Topics — grouped by conversation and group chat, for catching up on a thread
- Timeline — everything, newest first, when you want the raw chronology
- Notifications — only what is asking something of you
A job you can actually follow
Open a job and you get its runs, the employee's comments as it worked, and the output. A run that stops mid-way shows why — most often needs_input, which renders as a small form: answer it and the run resumes where it stopped.
That is the difference between an agent that "failed" and one that asked a question. Only the second one is useful.
Nudges
An employee sends a nudge instead of guessing. Answering takes a status and, optionally, a written reply that is delivered back into the session the employee raised it from:
Statuses: acted_on (handled) and dismissed (no action). acknowledged is still accepted and folded into acted_on — it named the same outcome twice.
starred is independent of status on purpose: flagging a request for later must not file it away.
Approvals
An approval is a run that stops until you answer. The employee raises it mid-run, the run pauses, and your answer resumes it — see the task's open approvals on GET /api/jobs/:id.
Group chats
Several people and one employee in the same thread, with roles per member. Useful when a client or a teammate should see the employee's answers without getting the rest of your workspace — see Channels.
Live updates
The Inbox refreshes on its own. GET /api/nudges/live is a server-sent event stream that fires whenever a job or nudge changes; the client refetches when it hears something. Use it if you are building your own view.