How workspaces are isolated

A workspace is everything of yours on one machine: the files your sessions work on, the transcript of everything that was said, and the Claude login they run on. Every session you open belongs to one workspace, and everything a session writes stays there.

You can have several, one per machine you connect. They do not share files, and nothing moves between them on its own.

• A hosted workspace runs on our machines. One click and it exists. No instance to size, nothing to maintain.
• Your own machine runs on a Linux server you connected. Files, transcripts and the Claude login never leave it. How to connect one.

The client shows both the same way. Moving from one kind to the other later costs nothing. What is in a workspace stays where it is until you move it yourself.

Workspaces of different accounts never meet: separate files, separate transcripts, separate Claude logins. Nothing is pooled or shared, including when several people are on one subscription.

Sessions inside one workspace share its files. This is deliberate. It is what lets you open a second session on the same project and have it see what the first one wrote.

So the unit of isolation is the workspace, not the session. Two pieces of work that must not touch each other belong on two machines, not in two sessions on one machine.

• On your own machine: the files, the work and the Claude login are on your hardware. What passes through us is the traffic between your client and that machine. It is forwarded, not stored.
• In a hosted workspace: it runs on a machine we operate, so our operators can technically reach that machine. We do not read what is on it, but that is a policy, not a technical barrier. If you need the barrier, use your own machine.
• Self-hosted: even the forwarding runs inside your own network. What that involves.

A session on your own server is a real shell running as the user that installed it. It can read and change whatever that user can. That is intended: it is your machine, and the work needs your files.

• Idle sessions are put away. Everything said and written is kept. A new message brings the session back where it was.
• Losing the network or closing the client changes nothing in the workspace. The machine keeps it, and you come back to it.
• Cancelling stops new sessions, not your files. Nothing in the workspace is touched. Subscribe again and continue where you left off.