Workspaces and Threads
Organize Threads and choose where each one runs.
Workspace
A Workspace groups Threads and their members. It is not tied to one folder, repository, or execution location.
Choose Local or Cloud when starting a Thread. The same Workspace can contain both.
Thread
A Thread is one durable AI session inside a Workspace. People in the Workspace can follow the same conversation, see messages attributed to the sender, and continue with the same agent context.
Concurrent work
For Local execution, choose a folder and either Default or New worktree. Default uses the selected folder directly; a Git worktree provides a separate checkout and branch.
Each Cloud Thread has its own sandbox. Select the repositories it may use; the agent clones them when needed and can work across multiple repositories.
Git worktrees isolate files; they do not magically resolve semantic conflicts. If two branches change the same code, Git still reports a merge conflict when the work is combined. Worktree keeps that conflict explicit so a person or agent can review it instead of silently overwriting work.
Visibility
- Local Threads are private until their host enables sharing.
- Shared Local history remains readable while the host is offline. Execution requires the host computer to be awake with Worktree open.
- Cloud history remains readable while its sandbox sleeps. Sending a message wakes the environment.
- Workspace membership controls collaboration; Cloud execution also requires the appropriate paid access.
