When you don't answer
What Pushary does when you leave an approval unanswered on your phone. The wait ladder for each mode, keyboard bypass, the wait action, how long a question stays open and what each device shows once it closes.
Updated
Every approval Pushary holds ends one of four ways: you approve it, you deny it, the agent's own prompt takes over, or Pushary keeps holding for your phone (with a wait rule). Which one happens, and when, is the wait ladder. Your policy for that tool decides it, and the hook enforces exactly what the policy says.
See your own ladder for every tool:
npx pushary@latest wait statusSilence never approves anything, unless you chose auto-approve as a rule's timeout action.
The ladder for each approval mode
| Mode | While you're away | If you don't answer |
|---|---|---|
push_first (When away) | Asks your phone for pushFirstSeconds | Hands back to the agent's own prompt. An agent with no prompt of its own is handled like Always instead (details). A Codex call Pushary asked about before it ran (PreToolUse) waits for the rule's timeout instead, at most about 170 seconds, and is then refused. With no device connected, Codex decides at once |
push_only (Always, where a new workspace starts) | Blocks and waits for your phone for up to timeoutSeconds | Applies the timeout action: auto-approve, auto-deny, ask in the terminal, or wait. A Codex call Pushary asked about before it ran (PreToolUse) is refused, unless the action is auto-approve and the timeout is at most about 170 seconds |
terminal_only (In agent) | Sends no approval alert | The agent's own prompt decides |
notify_only (Alert only) | Sends an alert that approval is needed, with no approve or deny on the phone | The agent's own prompt decides. A host with no prompt of its own refuses the action (details) |
Change how long your phone is asked first
In push_first (When away), your phone buzzes when you are away. If you don't tap within the window, the agent's own prompt takes over. A Codex call Pushary asked about before it ran (PreToolUse) waits for the rule's timeout instead, at most about 170 seconds, then is refused. With no device connected, Codex decides at once, unless Codex is in full access or the call is an edit outside a scope you agreed. Set the window from the CLI, from 0 to 300 seconds:
# Ask the phone for 45s before the terminal takes over (a new site starts at 20s)
npx pushary@latest wait 45
# Reset the window to 20 seconds
npx pushary@latest wait clearpushary wait <seconds> sets the window on the * catch-all rule, which every tool without its own rule inherits. Set a window for one tool in the dashboard under Agent > Policies.
Keyboard bypass: decide at your desk
When you are typing in the terminal, a phone buzz is noise. In push_first, Pushary detects that you are at the terminal, skips the phone push and shows the agent's own prompt right away, with no wait and no notification. On a Mac running the Pushary app, the decision stays on the Mac while you are there, however long it waits, and moves to your phone when you leave. This is automatic, with nothing to turn on.
Some agents have no prompt of their own to show at the keyboard. When their hook comes from the pushary CLI or the Cursor plugin, When away works like Always for them. Your phone is asked about every gated call, even while you are at the keyboard, and it waits up to timeoutSeconds instead of pushFirstSeconds. This covers Cursor file edits and sessions started from your phone (pushary 1.9.13 or later), Antigravity CLI (1.9.14 or later), a Codex edit outside a scope you agreed (1.9.15 or later), and Codex set to never ask for approval, which is full access (1.9.17 or later). In full access, Codex refuses a call nobody answers with "No response within timeout". For every agent on this list, a call nobody answers under When away is refused, even when the rule approves on timeout (pushary 1.9.24 or later, Cursor plugin 0.2.6 or later).
To keep every decision in the terminal for a while, whatever your policy says, set a mode override:
npx pushary@latest mode terminal_only --for 1h
# Check the override, or remove it
npx pushary@latest mode status
npx pushary@latest mode clearThe mode command needs a full-access key: create a new key with Create Key at pushary.com/dashboard/agent/settings. With a key Pushary created when you set up your computer, change the mode in the Pushary app instead: tap Questions & approvals at the top of your inbox. Picking a mode there also ends a temporary mode early. You can change your rules' mode at pushary.com/dashboard/agent/policies, but that does not end a temporary mode.
Hold for your phone: the wait action
Set a push_only rule's timeout action to wait and the hook holds for your phone instead of deciding on its own. At the end of the window it hands the decision to the agent's own prompt. It never auto-denies, except for a Codex call Pushary asked about before it ran (PreToolUse), which is refused. Use it for a rule like "production deploy: I'll approve from my phone."
How long wait can hold depends on the agent's hook budget: about 590s for Claude Code, 170s for Codex and Gemini CLI, 110s for OpenCode, and 45s for Cursor and VS Code. After that the agent's own prompt takes over. A longer hold is on the roadmap. Today wait means "use the whole window for the phone, and never auto-deny", apart from that Codex exception.
How long a question stays open
The ladder above is for approvals a hook holds. A question an agent asks with ask_user has its own lifetime, set by how the agent connects:
| How the agent connects | For example | The question stays open |
|---|---|---|
| An API key: CLI setup, the Mac app, or a key from Settings | Claude Code set up with Pushary, Codex, Cursor, VS Code, Gemini CLI, OpenCode, Hermes, Windsurf, Lovable | Until you answer it or the agent cancels it. Under Always or When away, your phone gets one reminder after 10 minutes |
| A connector: signing in to Pushary, or a connector key or link | Claude Chat, Cowork and claude.ai, ChatGPT, Grok Bot, Cline when signed in, Claude Code through the Pushary for Claude plugin | 10 minutes after it is sent |
| A hook approving one tool call | A command or file change the hook gates | Up to 10 minutes. Once the hook stops waiting, the ladder above decides, even if the question can still be answered |
A question inside a notification (context.askQuestion, kept for older agents) | Any agent | 10 minutes after it is sent |
| A Partner decision | create_decision and the decisions API | 1 hour by default, from 60 seconds to 24 hours |
A question an agent asked that closes without an answer is never a yes. If the agent is still waiting on it, it is told the question closed, does not take the step it asked about, and can ask you in its own chat instead. A chat reply that already ended is not reopened: the question just closes. An answer that arrives after a question closed is not delivered to the agent.
What you see when a question has closed
| Where you answer | Someone answered first | The question closed |
|---|---|---|
| Pushary app | "Already answered on another device" | "This question expired". The card leaves your list on the next refresh |
| Lock screen | The notification is withdrawn | The notification is withdrawn. If you tap an action on one that already closed, neither phone tells you: the action is dropped, or Pushary shows your inbox or the session the next time you open it |
| Mac notch | The card leaves and names where it was answered | The card leaves with Expired or Withdrawn. If your click lands as it closes, it says Timed out |
| Decision page in a browser | "Already answered", with where and when | "Question expired", or "Question cancelled" when the agent withdrew it first |
| Browser inbox | The card leaves | "This question closed before your answer arrived." A question Pushary can no longer find is removed without a message |
| Dashboard | "Already answered" | "Question expired" |
| Slack | The message changes to Answered | The message changes to Expired, or Withdrawn when the agent cancelled it |
After you answer a question that already closed, the Pushary app and the dashboard say it expired and the Mac notch says Timed out, even when the agent cancelled it.
What if Pushary cannot reach you?
The ladder always falls back to the safest approver left: you, in the agent's own prompt.
- No device connected: the hook withdraws the question without waiting and hands the decision to the agent's own prompt. The response warns you to connect a phone under Settings > Connections.
- Pushary unreachable: the hook returns no opinion, so the agent's own prompt decides. An offline agent cannot reach your phone anyway.
- The window is longer than the hook can safely wait: the hook hands the decision to the agent's own prompt. It does not apply a timeout action for a window it could not fully serve.
A host with no prompt of its own, such as a Cursor file hook, refuses the action in these cases instead. A Codex call Pushary asked about before it ran (PreToolUse) is refused too, with two exceptions. Under When away with no device connected, Codex decides, unless Codex is in full access or the call is an edit outside a scope you agreed. And if the hook itself fails, for example because it cannot load your policy, it steps aside and Codex decides, as the Codex guide says.
Check your ladder with doctor
npx pushary@latest doctorDoctor prints a Wait Ladder section with your default window, any active mode override and every per-tool rule. It reads the same policy the hooks fetch. This needs @pushary/agent-hooks 0.95.7 or later.
Next steps
Set your permission policies
Pick the approval mode, timeout and timeout action for each tool.
Handle unanswered questions in your own agent
Follow handoffAction, then nextAction, when ask_user returns without an answer.