Working as a team
Share visibility and review across an Organization, follow a teammate's Workspace live, and see file collisions before they become merge conflicts.
An Organization is a team of authenticated Members. It owns the shared Repositories and Workspaces and is the boundary of visibility: a Member sees their Organization's work and nothing else. While your Organization is only you, the client sends nothing to the sync backend; the Chat, the diff, and the Checks stay on your machine, because there is no one to share them with. Sync begins when a teammate joins.
Owner, and everyone else
Every Workspace has one Owner: the Member on whose machine it runs, where its worktree, agent, terminal, and files live. Execution-bound actions (prompting the agent, the Editor, the Terminal) are the Owner's alone. Review actions (Notes, Todos, merge) are open to any Member. Sharing a Workspace means shared visibility and review, not shared execution.
Remote Workspaces
A teammate's Workspace appears in your client as a Remote Workspace, mirrored read-only: its Chat and Diff stream in live, so you can watch the agent work and review the Changeset as it forms, while execution stays on the Owner's machine. Only the conversation and the changeset diff sync; the worktree itself never leaves the Owner.
Overview
Overview is the Organization-scoped command center, entered from the TitleBar. Where a Workspace shows one task, Overview shows the many: an org header with the Members and their pulse, and a Team & workspaces panel listing the Organization's Workspaces grouped by Member, including teammates' Remote Workspaces, each with its agent and state. It is the audit surface for who runs what, on which agent, in what state, live. Beside it sit three consoles:
- Branches: a full git branch console for the Repository (checkout, create, delete, merge, rebase, push, pull, fetch).
- Contributions: the GitHub contribution graph, per Member.
- Runs: repo-wide GitHub Actions workflow runs, distinct from a Workspace's own Checks.
Collisions
A Collision is two in-flight Workspaces whose Changesets touch the same file: a merge conflict that does not exist yet but will. Because Cohalen owns every worktree and mirrors each Changeset's file list, it detects the overlap live, across your own Workspaces and across Members. Collisions show as markers in the Diff pane and in Overview. They are indicative, never enforcing: Cohalen warns, it does not lock files or block a launch. What you do with the warning (re-scope a task, sequence the merges, talk to the teammate) stays your call.
Getting started walks the whole loop end to end.