The permission mode decides what an agent may do without asking you. Everything else shows up as an approval card above the message box.
Change the mode
Use the mode icon in the message box, press ⇧⇥ to cycle, or type /permissions. ⇧⇥ cycles through the everyday modes and skips the one that never asks, Bypass permissions or Full access. You choose that mode from the menu, and BeyDock asks you to confirm it first.
Modes differ by provider:
- Claude: Ask for approval, Accept edits, Plan mode, Auto and Bypass permissions. Auto approves safe actions on its own.
- Codex: Auto, Ask for approval, Read only and Full access. Auto works inside the session's folder and asks before going outside it. Full access also removes the sandbox. Codex has no plan mode.
- Antigravity: Accept edits, Read only, Plan mode and Full access.
- OpenCode: Ask for approval, Accept edits, Plan mode and Full access.
Antigravity can't ask for approval in the middle of a turn. Its mode decides everything: an action that needs approval is skipped and shown as denied. If you want it to run commands, choose a more permissive mode before you send the message.
Mode and model are remembered per provider for your next session. A session started by another agent through Delegation has a fixed mode.
Read the approval card
An approval card shows everything you are about to allow:
- A command appears exactly as the agent reported it.
- A file change shows a diff. If one approval covers several files, the card says "Make edits to 3 files?" and lists every file with its own diff.
Buttons and shortcuts:
- Deny, or esc.
- Allow, or ⌘↵.
- Always allow, or ⌘⇧↵. This appears only when the provider can suggest a lasting rule. The card spells out the rule, for example a command pattern "in this project" or file edits "in this session". Always allow means exactly that rule and nothing more.
Other cards
- Questions from the agent appear as a card with options you can pick. Skip declines them.
- Plan approval asks "Ready to code?". Choose Approve, Approve and Accept Edits, or Keep Planning and type what to change.
- Start an agent appears when a session wants to hand work to another account or provider. It shows the full task, the target, whether it can edit, and where it works.
- Apply agent changes appears when an agent wants to bring a sub-agent's changes into your folder.
While a session waits for you, the Needs you item in the menu bar appears, if you have it turned on. See Menu bar, widgets and Control Center.
Production devices
When you add an SSH host, you can mark it Development, Staging or Production. On a production device, BeyDock doesn't carry a risky mode (such as accepting edits automatically, Bypass permissions or Full access) into a new session: it falls back to the provider's cautious mode. Stopping a process or container on the device always asks first.
Tips
- Use Plan mode or Read only when you want to see an approach before anything changes.
- Use Accept edits for work you can review afterward in the Changes panel (⌥⌘D).
- Keep Bypass permissions and Full access for folders you can throw away, ideally in a worktree.