# Loopgate

> Loopgate runs multi-step coding workflows — plan, build, check, review, fix, pull request — on the coding agents a developer already uses: Claude Code, Codex and pi. Every step is a conversation you can steer, every loop stops at its limit, and every gate waits for a person.

Website: https://loopgate.dev/. Loopgate is not released yet; the page shows a working copy of the desktop app on example data and takes signups for the waitlist. Nothing on the page runs a real task.

## What it does

- A workflow is a graph of steps: agents, checks (commands the repository declares, whose exit code routes the run), gates where a person chooses, approves or locks a document, joins, merges and a pull request.
- Each agent step picks its own harness, model and thinking level, and carries its own permissions: read only, workspace access, or full access switched on for that step alone.
- Loops are bounded: a review that asks for changes sends the work back to a fixer for at most the rounds the workflow allows, then asks the person what happens next.
- The work happens on the developer's machine; in a Git repository, in a worktree and branch made for the run, so their own checkout stays as they left it. The agents talk to their own providers as they do today; Loopgate holds no model key and puts no server in between.
- Eight workflows ship built in, including plan-build-review, build-fix, per-module-builders, reviewer-panel, security-audit and architect-build-test. A builder draws and edits them; a copilot can draft changes on the canvas.
- There is a desktop app and a command line (`loopgate run`, `loopgate decide`) sharing one local daemon.
- For teams, workflows can be published to an organisation and policy set once (allowed engines, banned commands, whether full access is allowed). The team portal receives run metadata only — never code, diffs, prompts, transcripts or the task.

## What it never does

- Edit code itself; the agents do.
- Hold a model key.
- Grant full access by default.
- Resolve a merge conflict on its own.
- Write outside `.loopgate/` without the person's review.
- Send code to the team portal.

## Waitlist

- [Join the waitlist](https://loopgate.dev/#join): one email when the invite is ready; no newsletter.