Engines, GitHub and a repository

Time

10 minutes, 15 with Codex or Claude Code.

You need

• The runner from Any Linux box, opened from the portal's Devices page
• To be an owner or admin of your org, for every step here
• A ChatGPT or Claude subscription
• A GitHub account with access to your repository

Set this up with your agent

Copy this to a coding agent on your laptop. It runs the commands 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.
Walk me through Loopgate's docs page "Engines, GitHub and a repository": https://loopgate.dev/docs/sign-in.md. The pages it links to are beside it, each ending in .md.
Run its commands yourself, on my laptop or on my box over SSH as the page says, one step at a time, and check each "You should see" line before the next step.
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, Slack, GitHub), pressing Add a runner, every token and password, my AI subscription's device code, and making the Slack app.
If I paste you the portal's install line, run it on the box: its token works once, for an hour.

Steps

1. In the workbench, open Settings → Engines and press Sign in with ChatGPT on pi's row (or Sign in with Claude). Loopgate's image comes with pi.

2. Open the address the page shows on your laptop and enter the code it shows. With Claude, sign in, then paste the code Claude shows (or the address your browser ends on) into the page's box.

   You should see: pi's row says Ready. Signed in with ChatGPT, the copilot thinks on pi's GPT-6 Luna.

3. For Codex or Claude Code, press Install Codex or Install Claude Code on its row, then Sign in. Open the address the page shows and enter its code, or paste back the code you are given when the page says Finish signing in.

   You should see: its row says Ready.

4. Open Settings → GitHub and press Make a token in GitHub. In GitHub, give the token access to your repositories, set Contents and Pull requests to Read and write under Repository permissions, and copy it.

5. Paste the token on the page and press Save. Check the name and email the runner's commits carry, and press Save identity if you change them.

   You should see: Signed in as <the GitHub user>.

6. On Tasks, choose Add a workspace, paste your repository's address and press Clone. Or type a name and press Create for an empty folder.

   You should see: Cloning <repo>… with git's progress, then the workspace in the sidebar.

7. Type a task on Tasks and press Run.

   You should see: the copilot's proposal, with who works it and each step's engine.

Good to know

• Codex and Claude Code are optional. They install at the version Loopgate tested and survive restarts and updates.
• The token lets the runner clone private repositories, push and open pull requests. A token for a separate "bot" GitHub user keeps the runner's work easy to tell apart.
• A box several people share runs every task on whoever signed in there. A subscription per person is not built yet; many teams sign in with a team account.
• To pay per use instead, put an API key in runner.env, such as OPENAI_API_KEY=… or ANTHROPIC_API_KEY=…, then run docker compose up -d runner.
• By hand signs in to engines from the terminal and puts the GitHub token in runner.env.

If something is off

• The page says Ask an owner or admin of your org to … on this runner. Signing in engines, saving GitHub and adding workspaces on a runner are theirs to do.
• GitHub refused the token. Make it again with the two permissions in step 4.
• An engine's row says Sign in needed. Press Sign in on its row again.

Next

• Connect Slack
• A permanent address with Cloudflare Tunnel