docs
From a branch to a first build. Then the reference.
Everything below is what the tools do today, in the branch a workspace gives you. The full reference is at docs.reasonos.com.
Quickstart
Open a branch
Every branch runs on its own server with rbs already on it. Nothing to install: the editor, the terminal and the build are in the browser.
reasonos://acme/checkout · new branch feat/first-buildBuild in the branch terminal
No configuration to start: rbs detects Go modules, Node and Vite apps, Python packages and more, and generates what it needs.
rbs build //...Keep the generated config
Writes the same files rbs just used, byte for byte, so nothing changes when you commit them.
rbs adoptTest with a floor
Declare a coverage floor on a test target and the build fails below it.
rbs test //services/api:testHand a task to an agent
The agent works in the same branch with the same tools, and ends in a change request that passes the same gates.
rbs agent "add a regression test for the retry ceiling"load("@rbs//go/rules.rbs", "go_binary", "go_test")
go_binary(
name = "server",
srcs = glob(["*.go"]),
deps = ["//libs/money"],
)
go_test(
name = "test",
srcs = glob(["*_test.go"]),
min_line_coverage = 80,
)the reference
Where things are.
Build
CI, infra and deploy
Agents and editor
rbs --help
The command line.
One binary, twenty-five commands. Each has its own --help.
Every command above exists in the current release; this list is regenerated from the binary.