Cues & auto-accept

Agents don't need you hovering — they need you occasionally. Two tools close that gap: Cues queue up prompts that fire when the agent is ready for them, and auto-accept answers its routine confirmations so a permission dialog at 2am doesn't stall the whole run.

Cues — prompts that wait for the right moment

A Cue is a prompt with a trigger. Instead of interrupting an agent mid-turn (or sitting there waiting for it to finish), you queue the instruction and Termary delivers it the moment the agent goes idle — never interleaved with something you're typing.

• When idle — "next, run the test suite" lands as soon as the current turn ends.
• At a time — "at 7am, summarize what you did overnight."
• On a loop — a recurring nudge, e.g. "keep going through the TODO list" every 20 minutes.
• From anywhere — create Cues on the Mac, or from the phone: agent → ⋯ → Cues…

Auto-accept — run unattended

Flip Auto-accept on an agent and Termary answers its routine confirmation prompts for it, so the run keeps moving while you're away. It's per-agent and always an explicit choice — nothing ever turns it on for you.

1. On the phone: open the agent → ⋯ menu → toggle Auto-accept (run unattended).
2. Watch the state from the widget or Live Activity — you still get pinged for anything it can't answer.
3. Kill it anytime with the same toggle — from the phone, even mid-run.

Use auto-accept for agents you trust on tasks you've scoped. Real questions — the ones that need a human decision — still come to your phone as "needs you" pings; auto-accept only clears the routine yes/no gates.

Steering agents from the phone — including Cues and the auto-accept toggle — is a Termary Pro feature.