Skip to content
LoopCodeDocs

Get started

Quickstart

Install LoopCode, sign in, and finish your first task — with the change reviewed and the checks passing — in about five minutes.

1. Install

Pick the interface you want to start with. You can add the others later; they share one account.

Terminal — macOS and Linux
curl -fsSL https://loopcode.heksync.in/cli.sh | sh
Terminal — Windows (PowerShell)
irm https://loopcode.heksync.in/cli.ps1 | iex
Desktop app — macOS
curl -fsSL https://loopcode.heksync.in/mac.sh | sh
Desktop app — Windows
irm https://loopcode.heksync.in/win.ps1 | iex

The CLI needs nothing installed first: it uses your Node.js when it is 22.18 or newer and otherwise brings its own. Linux desktop packages, VS Code and the requirements are on Install LoopCode.

2. Sign in

The first time you run loopcode (or open the app) it asks you to sign in. Your browser opens; approve the code it shows, and you are in. There is no API key to paste.

bash
loopcode login

A free account works straight away. See Plans and usage for what each plan includes.

3. Open your project

bash
cd ~/code/my-app
loopcode

In the desktop app, choose File → Open Project… (⌘ O) and pick the folder.

4. Ask for something real

Start with a question, then a change. Say what done looks like:

Explain how a request reaches the orders API, from the router to the database.
Quantities below 1 reach the database when an order is created. Reject them
with a 400 and a clear message, add a regression test, and run the API tests.

LoopCode reads the files it needs, makes the change, and runs the tests. You see each step as it happens.

5. Review and approve

By default LoopCode runs in Auto-review mode: routine edits and checks go ahead, and a reviewer model stops anything risky to ask you first. When it asks, you can allow the action once, for the session, or always. Press shift tab in the terminal to switch modes — for example to Plan mode, where LoopCode only proposes a plan for you to approve. See Permissions and safety.

When the work is done, look at the result:

  • In the terminal, /diff shows every change, /review asks LoopCode to review it, and /rewind undoes the file changes of recent turns.
  • In the desktop app, open Review Changes (⌘ ⇧ D) to read the diff file by file, undo the turn, or commit.

6. Ship it

/pr

/pr commits the work on a branch, pushes it, and opens a pull request with a title and description written from the changes. With the GitHub CLI (gh) signed in it opens the pull request itself; without it, it pushes and opens GitHub's page for you to finish.

Next steps