ProductCode & review

Editor

One workspace. People and agents, side by side.

The editor opens onto a running branch: the code, the language servers, the terminal, the services, your teammates and the agent, all on one server. Nothing is on your laptop.

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

Editor, step by step.

  1. 01Editor

    Open the branch; the workspace is already running

    A branch is a server with rbs on it. The editor connects to that server: the terminal is its terminal, the files are its files, and a service you run there is reachable to everyone in the branch through the browser panel. Close the tab and it keeps running.

  2. 02Editor

    Real language servers, one per app

    gopls, the TypeScript server, deno, clangd, jdtls, the Kotlin server and pylsp, each started by the branch and keyed to its app’s root, so a monorepo runs isolated servers per app. Hover, go to definition, references, signature help, formatting and diagnostics are the real thing, and a server that cannot answer says so instead of failing quietly.

    CodeMirror underneath, with split groups, quick open, project search and semantic search.

  3. 03Editor

    The agent’s loop: in the same window

    The agent panel is part of the editor. Give it a task and watch the tool calls stream: the graph asked, files read, a change made, tests run. Permission prompts and plan cards appear in the panel, checkpoints are one click to revert, and sessions run in tabs so several tasks can be in flight.

  4. 04Editor

    Everything the branch knows, one panel away

    The Atlas view maps the symbol graph and answers questions as a flow of the files involved. The workspace graph shows targets and dependencies. Git status, the stack, jobs and the environment panel sit beside them; a secret in the environment panel shows as a digest, so two environments can be compared without a secret ever reaching a browser.

  5. 05Editor

    Two kinds of teammates, one file

    Presence shows who is in the branch and which file they are in. Edits merge with operational transforms; when two collide, the editor names who you collided with. A person’s cursor and an agent’s cursor are drawn the same way, because they are doing the same job.

Coming soon: a debugger · notebooks in the editor

The full reference lives in the docs.

Works with

Coding agentsCollaborationAtlas

Open a branch and try it.

Boots in seconds. Your team joins with a link.

Get startedTalk to us