One action.
Allow the current request when you want to decide again next time.
Permissions
More autonomy. Deliberate boundaries.
A useful agent needs tools. You need to know what it can read, change and execute. Permission scopes make those decisions visible instead of hiding them behind a single switch.
Effective access depends on the tool, active mode, project settings and approval history. Permission controls do not replace review of commands or external services.
Choose the scope, not just “yes”.
This session.
Use a session-scoped decision for work that belongs to the current run.
A deliberate exception.
Project and persistent approvals can cover repeated work. Inspect their exact scope and revoke decisions you no longer need.
Keep decisions visible
A saved approval should not become a forgotten one.
/permissions lists permission sources, scopes and effects. Review the entries and revoke a selected decision when the task or project changes.
Start by looking at the effective setup.
Inspect permissions and available tools before granting broader access. Clearing project approvals is a separate state-changing action, not a routine inspection command.
- Inspect permissions in chat
/permissions - Inspect tool availability
/tools desc
Permissions and privacy protect different boundaries.
Tool controls concern what the agent can do. GDPR, ZDR and no-training concern model processing. Keep both in view when choosing a mode and approving an action.
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
Are approvals always permanent?
No. Available decisions include one-time, session and scoped persistent approvals. Read the scope of the particular request before allowing it.
Can I inspect and revoke approvals?
Yes. /permissions displays permission sources, scopes and entries and provides revocation options. Project-level clearing is separate from inspection.
Do permissions guarantee that every command is safe?
No. Review commands, file scope and external destinations. Tool permission controls are not a replacement for your project quality and security process.
Permissions
Give the agent the access the task needs.
Start with the current permissions, choose a narrow scope and keep the resulting work under review.
Effective access depends on the tool, active mode, project settings and approval history. Permission controls do not replace review of commands or external services.
Want to start with your team? Talk to us.