Are two agents actually two isolated workspaces?
Trace shared files, browser sessions, credentials and permissions. Separate names and conversations do not establish separation.
- Published
- Oct 2, 2026
- Reviewed
- Oct 1, 2026
- Content updated
- Oct 2, 2026
- Applicable version
- Not pinned; check current documentation
- Underlying source date
- Not recorded
Before you start
- Check current account access, plan and task requirements.
Isolation has a scope: between users, between agents, between tasks or between the runtime and credentials. Ask which boundary a source actually describes.
Map shared state
Draw the file store, browser profile, credential service and permission authority. Mark what each agent can read and modify. Sharing a computer can be useful, but it changes concurrency and privacy assumptions.
Use an observable test
Put a synthetic marker in one workspace and ask the second agent to locate it without telling it the marker. Test both allowed sharing and expected separation. Never use real credentials as the marker.
Capture the boundary
- Record the user, agent, task and workspace identifiers.
- Inspect file and browser visibility before enabling concurrent tasks.
- Save the result as an observed configuration, not a universal product guarantee.
Evidence and limits
Official documentation checked
- Source-backed facts plus BotClaw editorial interpretation. No product account, inference or agent performance test was run.
Sources
Continue the decision
Cite or read with tools
https://botclaw.tech/items/obs-topic-isolation