Help
How the apps work, and what to do when something goes wrong. Can’t find it? The support page says how to reach a person.
Getting started
- What a discussion is, and how the room reaches agreement
One question, several AIs, a lead, reviewers, rounds, and an agreed answer.
- Depth: choosing how hard the room works
Quick, Compare, Consensus and Deep set how many seats take part and for how many rounds.
- Signing in, and keeping the Mac, web and iPhone in sync
Continue with Apple, Google or Microsoft; one account across the three apps; what syncs and what never does.
- Keyboard shortcuts on the Mac
The keys the desktop app answers to.
Seats, models and keys
- The four seats: Leader and Reviewer
Claude, ChatGPT, Gemini and Grok each have a chair, and each chair has a lead model and a reviewing model.
- Putting any model in a seat
The catalogue, custom endpoints, and how a chair takes another vendor's model.
- "Runs on": Our Keys, BYOK, Custom Endpoint
Each seat chooses how it is powered, separately from the account's default.
- Our Keys vs your own keys, and what credit is
What credit is, how it is spent, and when you would rather bring a key.
- CLI seats: Claude Code, Codex and Gemini CLI on the Mac
A seat powered by the vendor's own command-line agent, on the subscription you already have.
Running on your Mac
- "Run on my Mac" from the web or the phone
Send a discussion to your Mac, where the seats, the keys and the checkout are.
- Co-drive: letting teammates steer a run on your Mac
The owner's switch that lets teammates send turns to the Mac running a shared discussion.
- "Test the answer after the AIs agree"
The replay of proven checks on the final code, and why only tests that have caught a mistake are used.
- The VS Code and Cursor extension
Review your working tree, a file or a selection from the editor; findings become squiggles.
Tickets and teams
- Every discussion is a ticket
Keys like LTB-12, stages on the board, types, priorities and labels.
- Projects, comments, the inbox and releases
How the ticket layer is organised, who is told what, and how work is grouped into releases.
- The Team plan: seats, shared workspaces, and what happens when it lapses
Inviting teammates, what sharing means, roles, and a lapsed plan making shared work read-only.
- Team controls: every discussion a ticket, spend by project, ceilings and alerts
The four controls that tie AI spend to work: tickets only, cost by project and release, a ceiling per discussion, and budget alerts.
- Slack: asking the room from a channel
Mention the bot and a discussion starts; the thread is its mirror and the answer comes back as a reply.
Billing
- Plans: Free, Pro and Team
What each plan includes and costs, and how to change or cancel.
- Included credit, top-ups and auto-reload
How the monthly allowance works, how to add credit, and how to keep it to one bill.
Settings
- Pinning an answer
Keep the answer that mattered at the top of the discussion, on every device.
- Sending feedback or reporting a bug
Where the feedback door is on each app, what the report contains, and where it goes.
Troubleshooting
- "OAuth session expired and could not be refreshed"
A CLI seat's sign-in could not be renewed. Sign in to the CLI again from a terminal.
- A CLI seat says it is not installed, or ltb hangs
Detection re-run with Test; the app and the command line share one store.
Privacy
- Meeting your own AI duties with LetThemBuild
What the room decides on its own, where you stay in control, what to log and export for an auditor, and which team settings to turn on.
- What passes through our servers, and what does not
Keys encrypted at rest; prompts through our servers only on Our Keys, or on the web; the Mac's own paths stay on the Mac.
- How to reach support
The help centre's Messages tab, email, what to include, and where security reports go.
LetThemBuild and LetThemChat are made by GPULogy AI LLC.