# Working as a team

Source: https://cohalen.com/docs/teams



On a team the review is shared and the execution isn't. You see every workspace in
your organization, including the ones your teammates are running.

While your organization is only you, the client sends nothing. The chat, the diff,
and the checks stay on your machine, because there's nobody to share them with.
Sync starts when a teammate joins.

## The owner, and everyone else [#the-owner-and-everyone-else]

Only a workspace's owner can run things in it: prompting the agent, the Editor, the
Terminal. Anyone on the team can review: notes, todos, merge. Sending those back
from a teammate's client is in build rather than shipped.

## Remote workspaces [#remote-workspaces]

A teammate's workspace shows up in your client as a remote workspace, mirrored
read-only. Its chat and its diff stream in live, so you can watch the agent work
and read the changeset as it forms. Those two are all that sync outward; your
notes, todos, and merge actions will travel back the same way. The worktree
stays where the owner runs it: their machine, or a [box](/docs/cloud) in their
own vendor account.

<Mermaid
  chart="`flowchart LR
accTitle: What syncs between an owner and a teammate
accDescr {
  The workspace, its worktree, agent, and terminal all stay on the owner's
  side, their machine or their own cloud account. Its chat and changeset diff
  travel through a sync backend to a read-only mirror in the teammate's
  client. Notes, todos, and merge actions travel back the same way.
}
subgraph O [&#x22;Owner's machine or box&#x22;]
  W[&#x22;Workspace<br/>worktree · agent · terminal&#x22;]
end
subgraph M [Teammate's client]
  R[&#x22;Remote workspace<br/>read-only mirror&#x22;]
end
W -- &#x22;chat + changeset diff&#x22; --> S[(Sync backend)] --> R
R -- &#x22;notes · todos · merge&#x22; --> S --> W`"
/>

## Overview [#overview]

**Overview** is where you see the whole organization at once, opened from the title
bar. A workspace shows you one task. Overview shows you all of them.

A **Team and workspaces** panel lists the organization's workspaces grouped by
member, teammates' remote ones included, each with its agent and its state. That's
how you see who's running what, 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, which are a different thing
  from a workspace's own checks.

## Collisions [#collisions]

A collision is two workspaces in flight whose changesets touch the same file. It's
a merge conflict that hasn't happened yet, but will.

Because Cohalen owns every worktree and mirrors each changeset's file list, it
spots the overlap live, across your own workspaces and across the team. Collisions
show as markers in the diff and in **Overview**.

A collision is a warning and nothing more. Cohalen doesn't lock the file or stop
you launching. Re-scope one of the tasks, merge them in an order that works, or go
talk to your teammate. You pick.