Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>LetThemBuildNew to Visual Studio Code? Get it now.
LetThemBuild

LetThemBuild

GPULogy AI

|
5 installs
| (0) | Free
Claude, ChatGPT, Gemini and Grok review each other's work in your checkout — and run the commands to prove it.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

LetThemBuild for VS Code and Cursor

Claude, ChatGPT, Gemini and Grok review each other's work in the checkout you already have open — and run the commands to prove what they claim.

One of them leads. The others review what it did, and each reviewer runs its own commands rather than taking the lead's word: the build, the tests, whatever settles the question. Every verdict carries the commands it ran and whether they passed.

What it does

Command What it asks the room
Review my uncommitted changes your working tree, for real defects
Review this file the file you are in
Review the selection the lines you highlighted
Ask the room… anything, in your own words

Findings that name a real file and line become squiggles in the editor, attributed to the seat that raised them. Everything else stays in the panel — the markers are an addition to the transcript, never a replacement.

Installing

Search for LetThemBuild in the Extensions view — in VS Code it comes from the Marketplace, in Cursor from Cursor's marketplace. One build serves both, and a review started in either is the same review.

Requirements

The LetThemBuild desktop app — for macOS, Windows or Linux — and its command line installed:

LetThemBuild → Settings → Workspace → Command line → Install the command…

The extension runs that command. It does not reimplement the room, hold its own API keys, or talk to any model directly — the seats, keys, models and subscriptions are the ones you already configured in the app. A review started from the editor is the same review as one started from the app.

Where it looks: on a Mac, /opt/homebrew/bin and /usr/local/bin (the app's installer or brew install --cask gpulogyai/tap/ltb); on Linux, /usr/bin (the deb and rpm put ltb there) and ~/.local/bin; on Windows, %LOCALAPPDATA%\Microsoft\WindowsApps, where the app installs ltb.cmd. Then your PATH. If the command lives somewhere unusual, set letthembuild.cliPath — on Windows it may point at ltb.cmd or straight at LetThemBuild.exe.

Settings

Setting Default What it does
letthembuild.permission plan What the room may do. plan reads and reports without changing anything — the safe default for a review you started with a keystroke. edits, auto and bypass let it write.
letthembuild.rounds 0 Rounds of review. 0 means until the reviewers agree.
letthembuild.cliPath (empty) Where ltb is, if it is not somewhere obvious (on Windows, ltb.cmd or LetThemBuild.exe).

What it deliberately does not do

The full transcript, the diff pane, the artifacts and the browser and simulator panes live in the app. This shows you the run and puts the findings where you are working; Open the full transcript in the app is one command away when you want the rest — it opens a letthembuild:// link, which the app registers on macOS, Windows and Linux alike.

Nothing is sent anywhere the app would not send it.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft