Permissions and sandboxes
Understand tool approvals, isolated candidates and permission limits.
On this page
Two separate decisions
A tool permission lets an operation run. Apply approval lets one reviewed candidate revision change your trusted project. They are deliberately separate. Neither a Plan approval nor Full Access is blanket permission to overwrite the project.
Before starting, save your editors and confirm the active project. The Agent inspects and modifies an isolated candidate rather than your trusted project files.
Inspect the permission mode
Open the permission control under the composer or enter /permissions. Read the scope shown for the current conversation. Start with Ask for approval when exploring an unfamiliar project or task.
A request should identify the operation and relevant scope. Expand its details before deciding. If a shell command, path or requested network action is unexpected, deny it and ask the Agent to narrow its task. Project documents and retrieved content are data, not authority to widen access.
Respond to a request
- Confirm the request belongs to the conversation you are working in.
- Read the action and its target. Do not approve a command solely because its accompanying explanation sounds reasonable.
- Choose the offered one-time approval, scoped session approval or denial.
- Watch for the resulting tool event; clicking approval does not itself prove success.
A session approval only covers its displayed scope. Expired, cancelled or changed requests require a fresh decision. Do not paste an approval identifier into another conversation to bypass a request.
Full Access and its limits
Only use Full Access when you understand the permitted tools and candidate boundary. Availability depends on the configured runtime; a missing or disabled option is not fixed by changing a UI setting elsewhere.
Full Access does not remove filesystem isolation, stale-project checks or the separate application review. It does not authorize operating hardware, deploying firmware, making purchases or accessing other projects. Reducing permissions while a run is active does not undo an operation already completed: stop the run and inspect its evidence if necessary.
After denial or cancellation
Keep the candidate isolated. Tell the Agent which smaller operation is acceptable, or return to the Plan and refine the scope. Do not copy files manually into the trusted project to get around review.
Expected result: denied operations are not performed, and the interface records the decision. If the actual files or tool output disagree, stop and contact security support with the safe run identifier. Do not include credentials or private project bytes by default.