The answer queue

Every agent waiting for a confirmation, in one list you clear with single keystrokes — approve, reject, or approve and remember so the same question never comes back.

Ten agents working means ten agents that eventually stop and ask something. The Waiting for answers tab collects all of them, across every project and every CLI, into one list you clear in seconds.

When it is empty it says so: Queue empty — no agent is waiting for confirmation.

Clearing it with the keyboard

The queue is built for keystrokes, not clicks:

Whatever you pick, OFM sends exactly one thing to the agent: a keystroke — the same thing a human would type. There is no side channel and no hidden API.

See the terminal before deciding

Selecting a question shows that session’s live CLI on the right. You approve with the real output in view, not a stripped-down summary. When the entry has no live terminal, the panel says so rather than showing a blank frame.

The deny-list banner

A question matching the hard deny-list — rm -rf, git push, fork bombs and friends — appears with a red banner: Sensitive action (deny-list) — review before approving.

The banner does not block you. It removes the possibility of approving something destructive on autopilot while clearing a queue at speed. The deny-list itself is built into the engine, cannot be deleted, and always wins over your rules — see Guardrails.

Options: how much to remember

Options opens the precise version of “remember”:

The distinction that matters is prefix versus exact. Approving npm install as a family also approves npm run build and every other npm command — convenient, and broader than most people intend on the first click. When in doubt, choose the exact command; you can widen it later from the Rules tab.

Where answered questions go

Every answer — yours or automatic — is written to the audit log, with the source that decided it. That is how you find out later which rule let an agent do something you did not expect.