# Start here

One coding agent in one chat is one mind and one pass. Loopgate runs the pattern across the coding agents your team already has: plan, build, check, review, fix, pull request. Every loop has a bound, a command decides pass or fail, a person decides what matters, and every word is visible. It runs on your own box. Your team drives it from Slack, and anyone on it can open a run and steer it. It never holds your code, your credentials or your agents' sign-ins.

**Try it on your laptop, five minutes.** With Node, run `npx loopgate ui` and give it a first task on your own code: [Try Loopgate on your laptop](laptop.md). Then [Use](#use) says what it can do.

**Set it up for your team, thirty minutes.** One line from the portal on a server of yours, then the browser for everything else, and Slack when you want it: [Set it up for your team](team.md).

## What your team gains

- **The right engine at each step.** Each step picks its tool, model and thinking level: [Several agents on several harnesses](harnesses.md).
- **Two harnesses on one problem.** Two models plan or investigate on their own, and a lead writes one answer: [The patterns](patterns.md).
- **A task said in Slack, a pull request back.** The thread is the record: [Slack as the workbench](slack-workbench.md).
- **One run the whole team can open and steer.** Every member reads the same words and can reply: [Work on a run together](together.md).
- **Nothing of the code leaves your box.** What goes where: [What leaves your box](words.md#what-leaves-your-box).

## What is yours

- **The server.** Loopgate runs on your infrastructure: a Linux machine with Docker in your cloud account or your own data centre. Stop it, move it or delete it whenever you like.
- **The code.** Your repository, the agents' changes, what they are told and what they say back never leave that machine. The pull request goes from it to your GitHub.
- **The AI.** The agents think with the ChatGPT or Claude plan you already have, signed in with your own account. No API key to buy, none to give us.
- **Slack and GitHub.** The Slack app is yours, in your workspace; the GitHub token is yours, on your server.
- **The switch.** Revoke a runner from the portal and within a minute nobody can reach it.

What Loopgate's servers receive: a heartbeat, your team's member list, and a short record of each finished run, who ran it, when, how it ended and what it cost. Never code, diffs, prompts, transcripts or the task.

## Use

What the app can do, one page each: [Your first workflow](first-workflow.md), [The patterns](patterns.md), [Build a workflow of your own](build.md), [Several agents on several harnesses](harnesses.md), [Steer a run](steer.md), [Work on a run together](together.md), [Slack as the workbench](slack-workbench.md).

## Run it for your team

[Set it up for your team](team.md) is the path. Each cloud has its page ([AWS](aws.md), [Azure](azure.md), [Google Cloud](gcp.md), [a VPS](vps.md)), then [Any Linux computer with Docker](any-box.md), [Engines, GitHub and your repository](sign-in.md), [Connect Slack](slack.md), and a permanent address with [Cloudflare Tunnel](address-cloudflare.md) or [Tailscale](address-tailscale.md).

## Reference

[By hand](by-hand.md) is every file and line. [Update, back up, fix](care.md) keeps a runner running. [The words we use](words.md) explains each new word. The kit's files are in the list on the left.