One inbox for every agent that needs you

The agent already has a tool call. You should not have to keep four chats open to find the question it is stuck on.

Updated October 25, 2026

People who use more than one coding agent end up with the same problem, scattered. Claude is blocked on a worksheet. Codex is blocked on a deploy approval. Cursor is blocked on a form the agent invented for a config it does not understand. Each wait lives inside the client that asked, which means the only way to clear it is to remember which window you left open.

Invoke Human is the other end of those waits. It is one inbox, on iPhone, iPad, and Mac, for tasks an agent spawned that need a person. The clients do not each grow a new inbox. They call one remote MCP server, https://invokehumantool.com/mcp, on one account.

What lands there

What shows up is a handoff:

• Questions. The agent is missing a fact only you know. A customer name, a preference, a “which of these three”.
• Approvals. The agent can describe what it is about to do, and should not invent the yes. More on that on agent approvals.
• Worksheets. Something you mark up and send back. The landing page is this, in miniature: a factoring problem, answered in pencil, returned with attribution.
• Generative UI forms. The agent builds a form for the specific task instead of asking you to parse a paragraph. send_ui_handoff delivers it. validate_ui checks the document before it is sent.
• HTML. A page the person answers by tapping or typing. send_html_handoff delivers it.

send_handoff sends a handoff to the signed-in person, or to other people. send_ui_handoff sends a structured form the person answers on a device or a signed link. send_html_handoff sends an HTML handoff the person answers by tapping or typing. validate_ui checks a UI document before it is sent. share_handoff invites more people to a handoff, or forwards it. delegate_handoff forwards a handoff to new recipients. get_handoff_status reads the type, title, and status of one handoff. get_handoff_result fetches the answer, or the current status if it is not finished. wait_for_handoff waits until the person finishes that handoff. send_handoff returns before the person answers. wait_for_handoff holds the call until they finish or the wait times out. get_handoff_status and get_handoff_result are the check in between. Parameter names come from the tool list the server returns after OAuth. The guides are how each client is pointed at the server. The short install is on Support.

What comes back

The answer returns to the agent that asked, with attribution: who answered, and how. The landing page’s example is answered_by and via. The agent does not have to guess whether a human actually replied, or which human. The privacy policy covers where the handoff and the answer are stored (Cloudflare D1) and the deletion path. They are not used to train models.

You sign in with an email address or an Apple ID. The OAuth scope is handoffs. Connecting a client authorizes that client to send handoffs to your account and to receive the answers you return. That sentence is also in the terms, because it is the actual permission, not a slogan.

What it is not

It is not a second conversation with the model. The model keeps its context in the client. You see the task, not the whole transcript, unless the agent put the transcript in the handoff.

It is not the client’s own permission dialog. Cursor, Claude Code, and Codex can already ask “may I run this tool?” on the machine where they are running. Leave that in place. The inbox is for the decision the local dialog does not know how to ask. The human-in-the-loop page separates those two.

It is not a browsable web app with every open task. Support documents a signed page for the handoff you were given. The list of what is waiting is the app. iPhone and iPad need iOS 17 or later. The iOS app is in TestFlight. The list is on the home page.

It is not a shared team queue with seats and review templates. share_handoff and delegate_handoff can invite or forward a single handoff. If you need review templates and webhooks, read the gotoHuman comparison before assuming this is that product.

Several agents on the same account is the normal case, and it is the point. That flow is multi-agent handoffs.