Choose a mode before running
- Open a Code session and check its harness.
- Open the composer’s permission-mode control.
- Read the available modes and select one appropriate to the work. Ask is a useful starting point when offered.
- Send the request and respond to approval or question cards as they appear.
- Inspect the requested action, affected files or command, and explanation before approving it.
Accept edits, Auto, Plan, and Bypass are not universal capabilities. Bypass is separately gated. Cursor presents its own Agent, Plan, Debug, Multitask, and Ask choices; Muse does not expose a functioning Ask approval channel in this build.
During a run
Some harnesses support live changes for a subset of permission modes. Others disable the control until the run ends. Plan is not a general mid-run toggle, and a disabled choice should not be read as a UI failure. Grok Build and Muse lack the same live permission channel as Claude Code or Codex.
An approval card is different from a question requesting a decision. Answer the actual question rather than granting broad permission as a substitute. If a task appears stalled, inspect pending cards and the activity state before sending another request.
After a provider continuation
Claude Code/Codex linked continuation resets the destination to Ask. Review the destination’s permissions and working folder before sending the next message. Prior approvals are not a blanket authorization for a new provider’s actions.
Use run and queue controls for execution states and agent browser tools for browser-specific action approval boundaries.