Push delivery

Definition

Push delivery is sending the result of work an AI agent asked for back into that agent's chat as a new message, once the chat can take one, instead of waiting for the agent to collect it.

Also called: result delivery, pushed results.

An agent that starts slow work (a review, a helper chat, a workflow run) can wait for it, poll for it, or end its turn. Waiting and polling keep the chat busy; ending the turn means the result has to reach it some other way. Push delivery is that other way: the result arrives as a message, and the agent picks up from there.

The hard part is timing. A message sent into a chat mid-turn can interrupt it, so a good push waits until the chat is idle, or goes into a queue the app works through when it's free.

In Pairbar

Deliver results into the chat that asked is on to start with (Settings → Integrations → Agent actions). A finished helper's, follow-up's or workflow run's result that the chat didn't collect with wait or get_result is sent into it:

• not before 90 seconds after it finished, so a chat calling wait gets it that way instead;
• Codex: submitted through codex queue; a receipt confirms queue submission, not that the desktop has started processing it;
• Claude: only while Claude Code's own record says the chat is idle, never mid-turn or while it waits for you; a chat busy for 30 minutes gets nothing pushed;
• held while agent actions are paused or Pairbar is locked, tried up to three times, and kept across a quit.

The message says which request it answers, then the result framed as another chat's information, not instructions. Agent activity shows a delivered row. See Results.