Team

See who works where in your company's repos. Each person's Claude Code sessions are caught on their own PC and shared, encrypted, with their team only.

Team is off until you start or join a team. With Team off, the side menu has one Team row under History, and ratchet opens no team connection, writes no team file and sends nothing to a team. Nothing is shared until you start or join a team and read what is shared.

What Team is

A team is your company with one or more projects. A project is a name plus one or more repos that have a remote, for example shop for github.com/acme/shop. Every Claude Code session in a project's repo is caught by itself, whether it started in a terminal, in an editor or in ratchet, and shows on Team › Now for everyone in that project. A subfolder or a worktree of the repo counts too.

Each person is a leader or a member of each project. Leaders approve new people, add projects, make other leaders and edit the notice details.

Team messages travel through your team's own mailbox on the ratchet relay. Each one is encrypted and signed on the PC that sends it. Each PC keeps its own copy of the team picture, so Team pages open at once and still show the last picture when the mailbox can't be reached.

Start a team

Click Team in the side menu, then Start a team, and fill in:

• Company and Your name. Your name starts as your git user name.
• First project and its Repos. Only repos with a remote can join a project; the others show no remote, can't join a project.
• Under For the notice your team will read: Why your company may do this, for example a works agreement, a Reference (name or link), and a Data protection contact, which is an email or a link.

Click Start the team. You become the leader of every project you make. Starting works even when the team mailbox can't be reached: your PC sends the team's first message as soon as it can. Then the notice opens, and you read it like everyone else. Until someone joins, Now says Only you so far. Invite your team on People.

Invite and join

On Team › People, click Invite, tick the projects and click Make invite code. The code starts with ratchet-invite:, works once and expires after 7 days. Click Copy and send it to your colleague in a chat or an email. Making an invite needs the team mailbox; when it can't be reached, you see Can't make an invite while the team mailbox is unreachable. and no code. Open invites are listed under OPEN INVITES, each with Cancel. Once the code is used, cancelled or expired, it leaves the Invite panel, so an old code never looks ready to copy.

Your colleague clicks Team in their own ratchet, pastes the code under Join a team, types their name and clicks Join. Their PC makes its own keys, and their screen shows Waiting for a leader with a check code such as 4F2A-91C0.

Every leader sees the request on People under ASKS TO JOIN, with the same check code, and the side menu shows 1 asks to join. Compare the two codes, for example on a call. If they match, click Approve. If you have not read the team notice yet, Approve shows it first, and the approval is sent as soon as you close it with I have read this. If they differ, click Decline: someone else used the invite code. Within about 15 seconds of the approval, your colleague's screen moves on to the notice.

• A request ends when its invite code expires, at most 7 days after the invite was made; the waiting screen shows the date. If nobody answered by then, or a leader cancelled the invite, your colleague sees Nobody answered within 7 days. Ask your leader for a new invite.
• If a leader clicks Decline, your colleague sees A leader declined your request. Ask them for a new invite. with Start over.
• A code used a second time, or on a second PC, is refused with This invite has already been used. Ask your leader for a new one. A code that has expired shows This invite has expired. Ask your leader for a new one., and text that isn't a code shows This isn't a ratchet invite code.
• Cancel request on the waiting screen takes the request back.
• If an approval can't be sent yet, the request stays on People with Couldn't approve. ratchet tries again by itself.
• Only a leader can invite a new person. To add another PC of your own, click Add another of my PCs on the Team card of the Machine page and paste that code on your other PC. A leader approves it the same way.

The notice

Before anything leaves your PC, you read one notice: Your work on company projects is shared with your team. It opens by itself right after you start a team, or right after a leader approves you. It says what ratchet catches, what never leaves your PC, who sees what, how long it is kept and where, and what you can do. It names your company as responsible, with the legal basis, the reference and the contact your leaders entered.

Until you close it, your PC sends nothing to the team. Any of its buttons closes it and starts sharing: I have read this, Open the reference (shown when the reference is a link) and Ask data protection (shown when the contact is an email address or a link, and writes to it). After you close it, ratchet opens Team › Now. While you haven't read it, Now says Read what is shared to start sharing. with Read it. Leaders see on People whether each person has read it: Notice: Read or Notice: Not read yet.

When the notice changes, for example with a new project or a new leader, it opens again with What changed: at the top, and your PC stops sharing until you close it. To read it again at any time, click What is shared, and with whom on the Team card of the Machine page; opened that way, it has a Close button.

If you allowed alerts on this PC (Settings › Notifications), ratchet also sends a system notification when the notice is new or changed, once per change, so you know even when ratchet is in the background. Clicking it opens the notice.

Team › Now

Team › Now lists every caught session of your projects, grouped by project and then by person. Each row shows the session's title, then a line such as Claude Code · terminal · feat/rounding · edit cart/total.ts: where it runs, the branch and its last step. When a person has more than one PC in the team, the PC's name follows where it runs, for example Claude Code · terminal · LENA-MAC · feat/rounding. On the right is how long it has been running, waiting when it waits on a person, or done 14:20. Done sessions show for today only.

• The header counts people and sessions, for example 5 of 8 people caught · 7 working · 1 waiting on a human.
• Nothing running: lists the people with no open session. Not caught: lists the people whose PC shares nothing yet, with the reason: they haven't read the notice yet, or they have no PC in the team yet.
• The title is the name you gave the session, else Claude Code's own title for it, else Untitled session. It is never what you typed. A step is only its kind and a file name.
• The page updates every 5 seconds. When the team mailbox can't be reached, it shows Offline · last update 14:02 and keeps the last picture. A row whose PC has sent nothing for 15 minutes shows no news since 14:02.

The project picker next to TEAM in the side menu, and at the top right of the page, narrows Now and People to one project. ratchet remembers your pick on this PC. When you are in one project, its name shows instead of the picker.

Overlap notes

When your agent and a teammate's agent work on the same files in a team project, ratchet tells you both. It only informs: nothing is blocked and nobody is asked to choose.

You see it in three places: an overlap tag on your session in the side menu, a line under both sessions in Team › Now, and one notification on this PC if alerts are allowed.

ratchet compares the files each agent read in the last hour, the files it edited, and the files changed on its branch. Two agents that only read the same files are not an overlap.

For example, Lena's agent reads src/checkout/total.ts while Sara's agent changes it on her branch. Within about 15 seconds Lena sees "Sara · Rounding fix also changes src/checkout/total.ts", and Sara sees the same about Lena. A file changed on the branch some other way, for example by a commit made outside the agent, can take up to a minute to show. Both sessions must be running.

People

Team › People lists everyone in your projects with their role and their PCs, and every project with its repos and leaders. Leaders also see:

• ASKS TO JOIN, with Approve and Decline. Join requests always show, whichever project you picked.
• Whether each person has read the notice.
• Make leader and Add to project on each other person, greyed out when there is nothing left to do, and Add project.
• OPEN INVITES, each with Cancel. Invites for another PC of the same person are listed as Add another of my PCs.
• NOTICE DETAILS with Edit, to change the company name, the legal basis, the reference or the contact. Everyone reads the changed notice before their PC shares again.

Click a person to see their PCs, with when each was added or left. A project repo you don't have on this PC shows no matching repo on this PC.

A leader's change is signed on their own PC. When the team mailbox can't be reached, the change waits on the PC and the row says Kept on this PC. Sent when the team mailbox is reachable.

Team card on the Machine page

While Team is on, the Machine page has a card such as TEAM · Acme GmbH. It lists Your PCs in the team: with this PC marked, and says whether this PC shares: Sharing: on or Sharing: paused, read the notice. Its buttons are What is shared, and with whom, Add another of my PCs and Leave the team on this PC. While you wait for a leader, the card shows only the company and Sharing: waiting for a leader.

The side menu tells you what needs you. While you join, the Team row says waiting for a leader. Once you are in, a Team heading shows your project (or a picker if you have several) with two rows: Now says read the notice, or how many sessions are working, for example 3 working · 1 on your files. People shows how many people are in the team, or 1 asks to join for leaders.

Leaving

Leave the team on this PC on the Team card asks first. On Leave, sharing stops at once, ratchet tells your team that this PC left, and it deletes this PC's team keys and team copy. Teammates see the PC as left 14 Oct. To come back you need a new invite.

If the team mailbox can't be reached at that moment, the PC still leaves. Team setup then tells you that your teammates see this PC as "no news since" a time, until a leader removes it.

What is shared

What you type to Claude Code and what it answers never leaves your PC. Neither do commands, search text, diffs, file contents, tool output, cost and tokens, or sessions in folders that are not a team project's repo. ratchet doesn't collect your screen, keyboard, mouse, location or idle time at all.

The relay keeps team messages for 7 days, encrypted, in the EU. ratchet can't read them. The relay sees only which channel a message is for, which PC sent it, how big it is and when it arrived. Each teammate's ratchet keeps the current picture and 30 days of steps. Your PC keeps what it sent for 90 days, to fill gaps for teammates who were offline.

Free limits and known limits

Team is free during early access. Each team's mailbox takes up to 50 PCs at once, 20,000 messages a day and 1 GB. Over a limit, People shows The team mailbox is full for today.

• Make a second leader, so someone can approve new people when you are away. If the only leader's PC is gone, nobody can approve.
• Team keys don't change when a PC leaves yet. Leaving deletes this PC's keys, but a copy of its team folder made before leaving could still open new team messages.
• Removing someone else from the team, and signing in with a company account, come later.
• Only Claude Code sessions are caught.

On the PC only

Team pages are on the PC only for now. They show in ratchet on this PC in a window at least 1024 pixels wide. Your phone, the browsers you approved and a narrower window, for example ratchet on half a laptop screen, show no Team pages.