← Back to all guides

Set it up for your team

MarkdownOpen in ClaudeOpen in ChatGPT

Your team says a task in Slack, sees what will run and what it may cost, presses Start, and gets a pull request back. The agents work on your own servers, in your cloud account or your data centre, signed in to the AI subscriptions you already pay for.

Set this up with your agent

Copy this to a coding agent on your laptop. It runs the commands on your server and checks each step with you; what you sign in to, press or paste stays yours.

This is for a coding agent that can run commands on my laptop (Claude Code, Codex, Cursor), not a chat website.
Help me set up Loopgate's runner, one step at a time, following https://loopgate.dev/runner/guides/team.md and the guides it links to, each beside it ending in .md.
Ask me which Linux server with Docker it runs on: one of mine, or a new one on AWS, Azure, Google Cloud or a VPS, whose guide you walk me through.
Over SSH, check that the box answers `docker compose version`.
I press Add a runner on the portal's Devices page and paste you its line; its token works once, for an hour. Run it on the box over SSH.
Then read `cd ~/loopgate && docker compose logs runner` and tell me when it says `Registered as` and `Runner ready at`.
Then walk me through the runner's page: engines, GitHub and a workspace (sign-in.md), then Slack (slack.md).
These are mine: tell me when it is my turn, wait for me, and never ask me to type them into this chat. Signing in to anything (the portal, a cloud console, the runner's page, Slack, GitHub), pressing Add a runner, every token and password, my AI subscription's device code, and making the Slack app.

What is yours

  • The server. Loopgate runs on your infrastructure: a Linux machine with Docker in your cloud account or your own data centre. A small one is enough, and renting one is about the price of a lunch a month. Stop it, move it or delete it whenever you like; nothing of yours is kept anywhere else.
  • The code. Your repository, the changes the agents make, what they are told and what they say back never leave that box. The pull request goes from your box to your GitHub.
  • The AI. The agents think with the ChatGPT or Claude plan you already have, signed in on the box with your own account. There is no API key to buy and none to give us.
  • Slack and GitHub. The Slack app is yours, in your workspace, and talks only to your box. The GitHub token is yours, kept on your box.
  • The switch. Revoke the runner from the portal and within a minute nobody can reach it; remove a teammate and their access ends at their next sign-in.

What Loopgate's servers receive: a heartbeat from the runner, 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; a policy you set decides whether step summaries come with it.

The setup, in five steps

Time: 30 minutes in one sitting. You need your Loopgate sign-in as an owner or admin, a Slack admin, a GitHub account with access to your repository, and an AI subscription you already pay for, such as ChatGPT or Claude. New words are in The words we use.

  1. Sign in to the portal at app.loopgate.dev.
  2. Pick a Linux server with Docker, one of yours, or a new one on AWS, Azure, Google Cloud or a VPS (cheapest, fewest screens).
  3. Paste the portal's line on it: Any Linux computer with Docker. One line installs the runner, signs it in to your org and gives it an address; nothing else to fill in.
  4. Open the runner from the portal's Devices page, and on its page sign in to your AI subscription, set GitHub and add a workspace: Engines, GitHub and your repository.
  5. Connect Slack on the same page: Connect Slack.

The runner's first address ends trycloudflare.com and changes when the box restarts; the portal's Open always uses the current one. When you want an address that stays: Cloudflare Tunnel, open from anywhere, or Tailscale, open only to your team's laptops.

Later, Update, back up, fix keeps it running.

Doing it by hand

By hand is every file and line, for whoever wants to see or change each piece. The result is the same.