ProductPlan & share

Collaboration

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.

Get startedRead the docs
feat/retry-budget
CodeGraphAtlasTasksJobs
AS
2
ToolsPS
1
2
3⌄
4
5
6
7
8
9⌄
10⌄
11
12
13⌄
14
15
16
17
18
19
20⌄
21
22
23
24
25
26
27
28
29⌄
30
31
package checkout
​
import (
"context"
"math/rand/v2"
"time"
)
​
func (b Budget) Wait(ctx context.Context, attempt int) error {
if attempt >= b.Attempts {
return ErrBudgetSpent
}
if err := ctx.Err(); err != nil {
return err
}
base := b.Base
delay := base * time.Duration(attempt)
t := time.NewTimer(delay)
defer t.Stop()
select {
case <-ctx.Done():
return ctx.Err()
case <-t.C:
return nil
}
}
​
// jitter spreads retries so callers do not stampede.
func jitter(d time.Duration, frac float64) time.Duration {
return d - time.Duration(rand.Float64()*frac*float64(d))
}
services/checkout/retry.goLSP✦ AICollab2utf-8Code toolsFormat
Terminal 1×
^CClear
~/checkout (feat/retry-budget) $ rbs build //services/checkout:server
✅ Successfully built //services/checkout:server
~/checkout (feat/retry-budget) $
RBSReadyUTF-8GO✦ Completions On◇ Show AIHide Activity Bar◀ Hide Explorer⫿ Split🔍 Search● ⎇ Git (1)Hide Terminal

How you use it

Collaboration, step by step.

  1. 01Collaboration

    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.

  2. 02Collaboration

    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.

  3. 03Collaboration

    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.

  4. 04Collaboration

    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.

Coming soon: meeting recording and transcription · chat across branches and in the hub

The full reference lives in the docs.

Works with

EditorCoding agentsHosted git

Open a branch and try it.

Boots in seconds. Your team joins with a link.

Get startedTalk to us