Mission Control settings

Choose who answers your agents' questions — globally or per project — plus dangerous-action blocking, activity detection tuning, notifications, hotkeys and the emergency stop.

These settings decide what the app may approve on its own, and what must always go through you. Nothing here is irreversible: change it whenever you like, and the emergency stop cuts everything at once.

Who answers the agents’ questions

The autonomy level, described in full in Guardrails:

Even at the broadest level, three things stay on: the dangerous-action handling, the audit log, and the emergency stop.

Per-project override

Every project follows the global level by default, and any project can be forced to a different one. The pattern this exists for: broad autonomy on your own repository where a mistake costs nothing, and strict manual approval on a client’s production codebase — on the same machine, at the same time.

Safeguards & detection

Automatically reject dangerous actions. On, risky actions (deleting files, pushing code) are blocked without asking. Off, they are shown to you with a red banner so you decide. The hard deny-list is separate and always active.

Delay before an agent is considered “at rest” (milliseconds). OFM infers state from the agent’s rendered screen; this is how long it must stay quiet before being marked idle. Shorter reacts faster; longer avoids false “at rest”. 800 ms suits most cases — the setting exists for slow remote sessions and unusually chatty CLIs.

Notifications

• System notification on each new question — an OS notification when an agent starts waiting.
• Badge showing the number of pending questions — a running count on the app.

With ten agents running, the badge is usually the better signal: it tells you how much is waiting without a notification per event.

Ergonomics

• Shortcut to show/hide the Dashboard — the fastest way to jump between one agent and all of them.
• Shortcut to close the agent tab.
• Language — switches the interface immediately without killing running sessions.

Full list: Keyboard shortcuts.

Emergency stop

One switch that immediately cuts all automatic replies. Everything reverts to manual validation.

Use it the moment something feels wrong — a rule you regret, an agent doing something surprising, a batch behaving oddly. It stops the automation without killing the agents, so nothing in progress is lost while you look at the audit log.