Separate Workspaces for Agent Execution
Shell, filesystem, and browser tools run in an agent workspace instead of the runtime that holds platform credentials. Sessions use separate working directories within a shared team workspace.
Session Working Directories
Sessions have their own working directories in a shared team workspace. These directories are not a security boundary between sessions.
checkout-api session
- RepositoryRead and write
- CI logsRead
- Developer laptops
- Production keys
Platform Credentials Stay Out
The workspace environment filter removes model credentials and platform keys before commands run.
Coordinator keeps
- Model keys
- Platform keys
Keys filtered out
Workspace receives
- Repo clone
- Task env values
Access You Choose
Choose repository context and a named environment-variable profile for the work. These settings are not permission boundaries.
- DATABASE_URLpostgres://••••
- STRIPE_KEYsk_test_••••
Common Questions
Is it safe to let agents run unattended?
Workspace separation limits access to runtime credentials, but it does not make arbitrary commands safe. Use least-privilege credentials and review consequential changes.
What can an agent's workspace access?
Provided repositories, environment values, and connected services. Outbound network access is open by default. The environment filter removes platform credentials, not credentials you intentionally supply for the task.
Do sessions share a workspace?
Yes. Sessions use separate working directories within a team workspace. Delegated agents can work on the same files as their parent session.
Does isolation replace least-privilege access?
No. Use scoped test accounts, narrow provider permissions, and non-production data where possible.
Learn more about Security docs, Self-hosting.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.