Dream
DocumentationDownload
Chats

Agent permissions

Choose Ask, Accept edits, or Full access, respond to agent requests, and delegate tasks.

Each chat has a Permissions control beneath its message box. New chats inherit Settings → General → Models → Default permissions, which starts at Full access. Changing the default does not change existing chats.

Choose permissions#

  1. Open the shield control beneath the message box. Its tooltip is Permissions.
  2. Select Ask, Accept edits, or Full access.
  3. Review your task and submit it.
PermissionIntended behavior
AskRequest approval for actions that require permission under the provider's configuration
Accept editsAllow file edits automatically while retaining approval handling for other actions
Full accessGive the agent broader access to act without approval prompts

The selected provider determines the exact permission behavior. Ask does not mean every read or tool call prompts, and Accept edits does not approve every command.

Dream no longer has separate Build and Plan controls. To plan first, ask the agent to investigate and propose an approach before making changes. That instruction is not a read-only filesystem boundary; choose permissions appropriate to the task as well.

The shield and Full access label identify this chat's permission control.

Respond to questions and approvals#

An agent may ask you to clarify a requirement, choose an option, or approve an action. Read the request in the conversation and respond using the controls it provides. A project tab can indicate that an agent is waiting for your answer. Open that project and return to the conversation to read the request.

If the request requires changing the task, give the agent the revised instruction in that chat. Use the stop control to interrupt a response when necessary. Stopping does not roll back edits or commands that already completed; inspect Changes afterward, or use the reply's checkpoint to restore files it changed.

For parallel tasks that need separate files, use worktrees. Permission settings do not give two chats in the same folder independent checkouts.

Delegated tasks#

Agents can hand part of a task to another agent provider in the same project. For example, a Claude Code chat can ask Codex to review a change, then read the result in a later turn. Ask for this in your message, such as “Have another agent write the tests for this module and report back.”

RuleDetail
Providers that can delegateCodex, Claude Code, OpenCode, and Grok Build. Cursor Agent can receive delegated tasks but cannot start them
Available providersThe other provider's CLI must be installed and signed in on the project's host
PermissionsA delegated task cannot have more access than the chat that started it
FilesDelegated tasks work in the same project files; give each one a separate part of the work to avoid conflicts
StoppingStopping the chat also stops the tasks it delegated

Delegated tasks run on the host and keep their results, so the agent can check on them in a later turn or after Dream restarts. Open the tool details in the reply to see which tasks the agent started.