Approval ticket

Definition

An approval ticket is the record created for one request an AI agent makes, which waits for a decision, then follows the work it starts and holds the result for the agent to collect.

Also called: ticket, agent request ticket.

A ticket separates asking from doing. The agent gets an id straight away and carries on (or waits on it); a person, or a rule they set, decides; and the ticket keeps what was asked, who decided and what came back. That makes agent actions auditable, and lets an agent collect a slow result later instead of blocking.

A ticket's life

1. Created when the agent asks, with the full request.
2. Allowed by a rule, approved, declined, refused by a guardrail, or expired.
3. Running, then done, failed or stopped.
4. The result is collected by the agent, or delivered to it.

In Pairbar

Every agent request in Pairbar gets a ticket (such as t_1a2b3c4d5e) at once. When the kind is Ask me, it waits on an approval sheet at the top of the chat list, with Approve and Decline there, on the notification and in ⌘K. A ticket nobody answers expires after an hour; one still waiting survives quitting Pairbar. The chat collects the result with wait (up to 8 tickets) or get_result, or Pairbar pushes it into the chat (push delivery). Tickets are kept in ~/.config/pairbar/agent-runs.json, readable only by you (the last 300 finished), and every decision is listed in Agent activity.