productplan & share
Same file. Same terminal. Same call.
Everyone in a branch is on one machine: live cursors in the editor, a shared terminal, chat, and a meeting with screen share, without leaving the branch.
12func retryPolicy(attempt int) Duration {
13 if attempt > cfg.MaxAttempts {
14 return Exhausted
15 }
16 delay := base * (1 << attempt)
17 return min(delay, ceiling)
18}
line 16 overflows at attempt 31, see the run in the terminal
delay := base * (1 << attempt)how you use it
Collaboration, in order.
01
Send the link; they are in
A teammate opens the branch and is on the same server, with the same processes running and the same file open. Presence shows who is connected, what they are looking at and whether they are idle; only the focused pane reports.
02
Edit the same file at once
Collaborative editing uses operational transforms with revisions. When two edits collide, the editor names who you collided with instead of silently picking a winner. Remote cursors and selections are drawn in the editor itself.
12func retryPolicy(attempt int) Duration {
13 if attempt > cfg.MaxAttempts {
14 return Exhausted
15 }
16 delay := base * (1 << attempt)
17 return min(delay, ceiling)
18}
03
The agent’s loop: a cursor, a message, a review
An agent in the branch has presence like a teammate: a cursor in the file it is editing, a message in the room when it has pushed, a change request when it is done. What it did is visible to everyone who was there, in the same place their own work is.
line 16 overflows at attempt 31, see the run in the terminal
delay := base * (1 << attempt)04
Debug on the real thing, together
Meetings run on WebRTC with mic, camera, screen share and picture-in-picture; screen share gets its own connection so it never fights the camera. The process that is failing is the one you both see, and a shared terminal lets you both type into it.
Chat and meetings are per branch.
not built yet: meeting recording and transcription · chat across branches and in the hub
The full reference lives in the docs.
works with
Open a branch and try it.
Boots in seconds. Your team joins with a link.