CoincideFeature
Full access, approvals and questions
Each thread has an access setting. With Full access, agents run commands and edit files without asking. With Ask for approval, every command and file change waits for you, and the request appears right above the composer.
Choosing the access mode
The access button in the composer shows the thread’s mode. Change it there, with Thread › Access… (⇧⌘A), or with Choose Access… in the command palette.
- Full access: “Agents run commands and edit files without asking.” This is the default for new threads.
- Ask for approval: “Agents ask before running commands or editing files.”
Settings › General › New Threads › Access sets what new threads start with, and a project’s Project Defaults… can set its own. Changing the access of one thread also makes it the default for the next new thread.
When you move a thread from Full access to Ask for approval, Coincide ends the agent sessions that might still hold full access: idle ones at once, a running one when its turn ends. The next message resumes them under approval, so an agent can’t keep working unasked in the background.
Answering an approval
An approval request shows above the composer with what the agent wants to do, such as a command approval with the exact command, a file change approval, or a web access approval, and the agent’s own choices as buttons. Common choices:
- Allow once, or Deny, which lets the agent try something else;
- Deny and stop, which also ends the turn;
- a session-wide choice such as “Always allow this session” (Claude Code) or “Allow for this session” (Codex), and for Codex sometimes “Always allow” a specific command or host.
Some requests have a text field for a note to send with your choice. If you type a new message while an approval is waiting, sending it declines the request and steers the agent with your message instead. The Dock icon’s badge counts approvals waiting in all threads, and with Coincide in the background a notification tells you; see Notifications.
What each mode means for each agent
Coincide maps the two modes onto each agent’s own permission system, so the agent enforces them.
| Agent | Full access | Ask for approval |
|---|---|---|
| Claude Code | bypassPermissions. If your Claude Code settings don’t allow it, Coincide falls back to auto mode, then to asking. | Claude Code’s default mode. “Always allow” is limited to this session and never switches Claude into a mode that skips more than file-edit prompts. |
| Codex | Never asks, and runs without a sandbox. | A read-only sandbox; Codex asks before commands it doesn’t trust and before any change. |
| Cursor | Runs cursor-agent with --force. | Cursor’s own options for each request, plus Cancel. |
| Grok Build | Grok’s always-approve mode. | Grok’s default permission mode: Approve, Allow all edits this session, Decline or Cancel. |
| OpenCode | Allows everything. | Asks before shell commands, edits and work outside the project folder. |
| Antigravity | Antigravity’s yolo mode. | Allow once, Allow for this thread, Deny or Cancel, with Google’s security note. |
For Grok Build and Antigravity, reading and searching files never needs approval, in either mode. Changing the access mode of a Cursor or Grok Build thread restarts the agent process, which then reloads the conversation.
Questions from the agent
Agents sometimes stop to ask you something, such as Claude Code’s AskUserQuestion, Codex’s input requests, Cursor’s and Grok Build’s questions, Antigravity’s interactions and OpenCode’s forms. Coincide shows them one at a time above the composer: pick an option or type an answer, then go on to the next with Next or Back. Answers to secret questions use a password field and aren’t saved in the transcript. In the work log the question reads “Answer below” until you do, then lists your answers.
Claude Code and Codex can also show forms from their MCP servers. OpenCode forms with links, hidden or conditional fields are declined with a note to the agent, since Coincide can’t show them faithfully.
Choosing wisely
- Full access is fast but trusts the agent with your shell and files. Run it in a worktree, keep checkpoints on, and review the diff.
- Ask for approval suits unfamiliar repositories, production credentials, or prompt-based plan mode.
- Schedules an agent creates for itself have their own approval: by default you allow them from a card in the thread (Settings › General › “Approve schedules agents create”). See Scheduled tasks.