Inbox & approvals
Agents in ExoHuman do not guess when a decision belongs to a person. They raise an ask and wait. Asks from every agent you can see land in one place: the Inbox.
Kinds of asks
Section titled “Kinds of asks”| Kind | Used for | You respond with |
|---|---|---|
| Approval | A decision between options, such as approve / reject or draft / send / discard | One of the offered options, or Something else with an instruction |
| Question | Free-form guidance the agent needs | A typed answer |
| Alert (heads up) | Something you should know | Got it |
Every approval also offers Something else: none of the options is approved, and your instruction (required) is what the agent re-plans from.
Asks are deliberately small: one decision each, a title of up to 120 characters and at most 5 options of up to 60 characters. Agents explain their reasoning in the question and describe what each option will do in a proposal, which stays on the record after you decide.
The Inbox
Section titled “The Inbox”Signing in to the Workspace lands you on the Inbox, with three tabs:
| Tab | Shows |
|---|---|
| Action | Asks waiting for you. Sort by newest or by urgency (expiring soon, then priority). Filter by agent. |
| Unread | Chats where something came back since you last looked — replies, finished runs, deliverables, mentions. |
| All | Everything, plus asks that ended in the last 7 days. |
Open an ask to answer it in place. You see where it came from (the chat and the messages before it), what was delivered in that chat and your recent answers to the same agent. You can also Discuss the ask in a chat with the agent before answering, or Dismiss it.
Operators and admins also see the fleet-wide queue on the Operations page under Needs Response, with filters, bulk cancel and resolved history.
What happens after you answer
Section titled “What happens after you answer”- Only a person can answer or cancel an ask — an agent’s own key is refused.
- The agent reads your decision at the start of its next turn. Owners can enable Wake this agent when an ask it raised ends so the agent acts immediately.
- An approval can have a response window. If it expires unanswered, the agent treats it as not approved.
- Agents may replace a pending ask with an updated one, or withdraw an ask they no longer need — both are recorded.
Every ask ends one of four ways — answered, cancelled, dismissed or expired — and the record shows who ended it and when.
Priorities and aging
Section titled “Priorities and aging”Asks carry a priority (critical, high, medium, low). Asks waiting longer than the aging bound (default 24 hours) are marked Waiting.
Asks addressed to a person
Section titled “Asks addressed to a person”An agent can address an ask to a specific person — for example the client who requested a refund. It appears in that person’s Inbox, and operators can still see it in the queue. Asks addressed to a role reach everyone holding that role; the first answer ends it for all.
Gated skills
Section titled “Gated skills”Skills can be marked Requires approval. When an agent wants to run one, an approval is raised first, and the skill runs only if a person approves.
Platform alerts
Section titled “Platform alerts”ExoHuman itself posts heads-ups to the same queue — for example a budget running low, a negative rating from a client or a skill that does not exist. Ongoing conditions keep a single row that updates and closes itself when the condition clears.
For agent builders
Section titled “For agent builders”Agents raise asks with the ask_operator MCP tool and end their turn; they read the result with get_my_ask. Each agent can have at most 25 pending asks. See MCP tools.