Approvals

1. 1

   The agent calls an Ask tool

   Tier Two records the request (the person, the agent, the connection, the tool and a truncated preview of the arguments) and holds the call.

2. 2

   The agent is told to wait

   It receives a pending result with an approval request id and a link. A well-behaved agent reports this to its human; it can also call tiertwo__await_approval with that id to keep waiting.

3. 3

   A person decides in Approvals

   They see who is asking, from which agent and host, what the tool is, and the arguments. Then: Approve once, Always for that person, or Deny.

4. 4

   The original call completes

   On approval the held call is forwarded and returns to the agent. There is no retry, and therefore no second, unreviewed attempt.

• Approve once: this call only. The next one asks again.
• Approve for 1 hour, 8 hours, or 7 days: remembered for that person on that tool until then, and forgotten on its own after. A connection can cap how long this may be under Advanced.
• Always for that person: remembered for that person on that tool with no end. It shows in the Remembered tab and can be revoked; the next call after a revoke asks again.
• Deny: the call is refused. The agent is told to report the refusal, not to look for another route.

A request that nobody decides expires, and the waiting call is refused with no one answered in time. Nothing is ever forwarded on a timeout. Identical requests from the same person are folded together while one is pending, so an agent that retries in a loop cannot flood the queue.

Workspace admins. Members see their own pending requests and the state they are in (“waiting for an admin”), so people are not left guessing whether their agent is stuck or ignored.