Workspaces and worktrees

A workspace groups a task's branch, working files, and conversations. Its worktree is the folder where those files live. Separate workspaces let you work on separate branches of the same repository without repeatedly switching one checkout.

All chats inside one workspace see the same working files. Two agents can edit the same file, so give each a clear responsibility when they work concurrently. Worktrees separate checkouts; they are not a security boundary or a replacement for provider permissions.

For example, one workspace can hold a settings fix while another holds a documentation change. Two chats reviewing that settings fix belong in the same workspace, where they can inspect the same diff.

Renaming a chat changes its tab title. Renaming a workspace changes its branch name without moving its folder. A tracked pull request can supply the displayed workspace title.

Review and save the work you need before archiving. Archive retains the conversation history and branch; restoration prepares a working checkout again. It is not a general backup for uncommitted files or build output. Read any archive confirmation before proceeding.

You have the right arrangement when independent tasks have separate workspaces and collaborating chats have explicit ownership. Next: Conversations and agent controls.