The ltb command line
Ships with the desktop app, under the names ltb and letthembuild. Four verbs:
| Command | What it does |
|---|---|
ltb review "…" | The room reviews this checkout |
ltb run "…" | The room does it, in this checkout |
ltb chat "…" | The room answers. No folder, nothing changed |
ltb rc | Makes this machine claimable from your phone |
--rounds N (0 means until they agree), --permission plan|manual|edits|auto|bypass, --cwd PATH, --json, --quiet.
It exits 0 when the reviewers agreed, 1 when they did not, and 2 when the run failed — so it is usable as a gate in a script or in CI.
It drives the desktop app headless, which means it uses the seats, keys and CLI subscriptions you already configured. It holds no keys of its own.
The editor extension
One extension, published to the Visual Studio Marketplace and to Open VSX, which is where Cursor looks. There is no JetBrains plugin.
It gives you: review my uncommitted changes, review this file, review the selection, ask the room, and stop the run. Findings come back as inline diagnostics on the lines they are about. It is a thin wrapper over ltb — it holds no keys and talks to no model directly.
Hooks
Run your own command at points in a discussion's life — when a session starts, when it ends, before or after a write. For the things every team does differently: your formatter, your notifier, your audit trail.
MCP
The app is an MCP server as well as an MCP client. Other tools can ask your room a question and read its agreed answer; your room can use the MCP servers you have configured. See the the developer reference.
Schedules
A discussion can be set to run on a schedule — a nightly check, a weekly review of what changed. It runs where you told it to run, and tells you what it found.
The HTTP API
Everything the apps do goes through a documented API, with OAuth for third-party clients. The full route list is on the the developer reference.