Skip to main content
When a tool or decision needs your input, Mains shows a request in the conversation. Review what the agent wants to do, then allow, deny, or answer it.

​
Request types

Permission choices depend on the provider and tool. Some requests let you remember a decision for the session. Forms with fields need a fresh answer. A previous approval does not silently submit new form values.

​
Where to answer

Use the chat for every request type. On macOS, supported simple requests can also be answered from a notification or the menu bar:
  • Allow or deny a tool request.
  • Choose an option for a single-choice question.
  • Reply to an open text question.
Plans, multi-select questions, forms, and sensitive input open the conversation for review. You can also answer supported requests from the iPhone companion.

​
Permissions and modes

Code exposes provider-specific permission or sandbox controls. Work and Chat apply their mode policies, so those controls are hidden. Codex Full Access asks you to confirm what it enables before activating. Review the scope before accepting it. Approving a request allows that operation within the provider’s constraints. It does not convert a Chat run into a writable run.

​
A run waiting in the background

The menu bar groups runs that need you and lets you open or stop them. Enable it under Settings → General → Menu Bar Icon. Configure completion and approval notifications in Settings → Notifications. If a run looks stuck, check for a pending request before stopping it.