The ltb command line
Ships with the desktop app, under the names ltb and letthembuild. The ones that start the room or reach this machine are below; the rest (discussions, tickets, seats, channels, automation, your account) are on the ltb pages linked below.
| Command | What it does |
|---|---|
ltb run "…" | The room does it, in this checkout, or in a new project folder when you are not in one |
ltb review "…" | The room reviews this checkout |
ltb ask "…" | The room answers. No folder, nothing changed |
ltb chat | A conversation in the terminal; type follow-ups |
ltb continue GPU-12 "…" | A follow-up in a discussion the app has |
ltb rc | Makes this machine claimable from your phone |
ltb acp | The room as an agent inside an editor that speaks the Agent Client Protocol |
ltb doctor | Says what on this machine would stop the room working |
--rounds N (0 means until they agree), --permission plan|manual|edits|smart|auto|bypass (default auto), --staged and --branch NAME for review, --cwd PATH, --new [NAME], --json, --quiet, and for one run only --model, --effort, --dollars, --attach, --add-dir, --append-prompt, --schema, --allow, --deny, --verbose. All of it is on the page The ltb command.
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
Your account is an MCP server: other tools can ask your room a question and read its agreed answer through letthemchat.com, signed in with OAuth. On the Mac the room is also an MCP client: the lead (never a reviewer, and not a lead running through its own CLI) can use the MCP servers you set up under Plugins. See 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 developer reference.