How Permissions Are Resolved

All conversations share three execution presets; execution locations supply the initial working directory and writable roots.

Plain, project, workspace, friend, and scheduled conversations share one execution permission system. Conversation types supply initial directories and permission defaults rather than adding another filesystem sandbox. Each conversation keeps its own selected policy. A change during a run applies at the next tool call and survives session reconstruction.

Plan mode is a separate conversation mode, not a fourth permission preset. Accepting a plan still leaves individual actions subject to the selected execution policy.

Default directories

  • A plain conversation uses its own working directory as its default writable root.
  • A project conversation uses the project directory.
  • A workspace conversation includes every directory saved in that workspace, with the first as its working directory.
  • A friend conversation starts with that friendship's own shared subdirectory and adds the selected project, workspace, and additional writable directories.
  • Scheduled tasks initialize plain, project, and workspace locations by the same rules.

These roots determine which ordinary writes can run directly. They are not an absolute boundary for every read. Ordinary read-only actions may read files elsewhere; explicit rules, tool checks, and operating-system permissions still apply.

Three permission presets

  • Ask for approval: ordinary edits and sandboxed commands within writable roots run directly. Writes outside those roots, elevated operations, and network access enter the approval flow. Sensitive files and actions explicitly requiring review can still need confirmation.
  • Approve for me: keeps the current sandbox and writable roots, and sends actions requiring approval to an independent reviewer. It can approve, decline, or refer an action to you.
  • Full access: removes the ordinary filesystem sandbox and ordinary approval prompts. It has the same meaning in friend and scheduled conversations, without an additional directory ceiling. It does not grant permissions the operating system has withheld, and explicit deny rules still apply.

An allowed action must still execute successfully. Missing files, operating-system denials, missing application authorization, and invalid tool arguments are separate failures.

Initialization and later changes

The execution preset in friend settings seeds a new friend conversation. Task admission decides whether to accept the request and is separate from approval of individual tool actions. Computer Use application authorization is managed independently.

A scheduled task saves its execution location and permission preset. Each run creates an ordinary execution conversation initialized from those saved choices; older tasks retain their previous full-access default. Ask for approval waits for your response in the run's conversation, and Approve for me uses the same reviewer as other conversations. Running in the background does not promote a task to full access. Changing the run's conversation affects that run; the saved task form determines subsequent runs.