glorp

Git Loop fOr Robot Patchers

Focus on problems.
Let the robots solve them.

glorp is a daemon that watches your GitHub issues. You describe a problem — a bug, a proposal, a thing that should exist — and it puts a robot on it.

The queue is your issue list. The scheduling rules are labels and dependencies. The progress report is the thread. Nothing new to learn, nowhere new to look.

Install glorp glorp watch owner/repo
owner/repo·Issues•••
Open opened by you · assigned to you

Load balance new issues across both agents #142

Repeating --agent should split work evenly instead of always taking the first one. Blocked until #139 lands.

enhancement agents
glorpwaiting on #139

Dependency closed. Does anyone have this? /glorp:8f21a

glorp2 minutes later

Starting work on this issue.

glorp18 minutes later

Opened #143 — round-robin dispatch across the listed agents, with tests for uneven queues.

All checks have passed#143 merged

The loop

It keeps going after you stop looking

A webhook delivery — or a poll, if you would rather skip the tunnel — surfaces the issue in seconds. glorp claims it with a signed comment so no two instances take the same ticket, then starts the agent.

When a pull request closes, it sweeps for #123 mentions and picks up whatever that unblocked. Sessions persist in .glorp.json, so a restart resumes instead of repeating.

Would rather skip the tunnel entirely? glorp watch --browser reads GitHub through a headless Chrome it drives itself — no ngrok, no API rate limit to ration. It always polls, every twenty seconds, on a browser profile of its own. Point it at another Chromium build with --browser-binary, or another profile directory with --browser-profile.

That profile starts signed out, so anything private looks like a 404 until it has a session. glorp auth opens a real browser window on the same profile, waits while you sign in, and closes it again — once, and the session sticks across restarts. glorp auth --status says who it is signed in as.

01You describe itAn issue, opened and assigned to yourself
02glorp claims itSigned comment, then a two minute wait
03An agent buildsInvestigates, ships a branch, proves it
04The thread reportsMerged, and the next issue unblocks
glorp watch

Git Loop fOr Robot Patchers

glorp dashboard v0.9.2

live
jobs: 1 idle 2 active 14 total
quota: codex: 71% left
webhook (ngrok)
targets: owner/repo (3 issues)
#142 Load balance new issues across agents
checkout: /tmp/glorp-142-9fa1
session: 01JC4K2M8ZQ
agent: codex/gpt-5.6:high
clone: /tmp/glorp-142-9fa1
reading dispatch.go
added round-robin selector
running go test ./...
ok  github.com/lsegal/glorp/internal
#145 Reaper leaves ngrok running on SIGKILL
checkout: /tmp/glorp-145-4c07
session: 01JC4K3T1YB
agent: claude/opus:medium
clone: /tmp/glorp-145-4c07
reproduced on darwin
holding pipe to parent
verifying process groups
Logs
webhook delivery: issues.opened #147 → queued
claim posted on #147, waiting 2m for other instances
dispatching claude/opus:medium for #147▏

The dashboard

Watch it work, or don’t

A localhost-only browser dashboard shows every agent card, its output viewport, job counts, quota, delivery mode and target status. glorp ui finds a running instance and opens it without you hunting for the port.

Prefer the terminal? --ui tui gives the same view in your shell, and --ui none just writes timestamped lines to stdout.

Two focused skills

Hand work to the right robot.

Both ship with the installer and register globally for every agent glorp knows about.

/gh-fixIssue to merged fixInvestigate, ship, prove, and close the loop. Dispatched for every issue that clears its dependencies. /gh-discussOne useful answerRead the thread, research the repo, reply only when certain. Read-only, and silent when it isn’t sure.

Install

The script downloads the release for your OS and architecture, installs the binary, and registers the bundled skills through skills.sh.

macOS or Linux

curl -fsSL https://github.com/lsegal/glorp/releases/latest/download/install.sh | bash

Windows PowerShell

irm https://github.com/lsegal/glorp/releases/latest/download/install.ps1 | iex

Already installed? glorp upgrade re-runs the installer for your platform.

Prerequisites

  • GitHub CLI (gh)Authenticated with access to every repository glorp watches. Project targets need the read:project and project scopes.
  • Node.js and npxThe installer uses npx to install the bundled gh-fix and gh-discuss skills through skills.sh.
  • ngrokFor the default webhook mode; installing it is optional, since glorp falls back to npx ngrok. Configure its auth before starting. Not required with --poll.
  • Chrome, Chromium or EdgeOnly for --browser mode, which needs no ngrok tunnel and no extra token. Safari has no DevTools Protocol and cannot be used.
  • A coding agentAt least one of Codex CLI (codex), Claude Code (claude), Gemini CLI (gemini), Meta Muse Code (muse), opencode (opencode), or Cline (cline) on your PATH. Any other CLI can be added with an agent definition.

Note. glorp launches agents non-interactively. Agent sandbox and permission controls remain enabled by default. --yolo disables those protections; use it only with repositories and issues whose contents you trust.