Skip to content

A job queue for coding agents

Your GitHub issues, worked on your machines.

hopper takes the issues you choose, runs each one on a computer you trust, and keeps you in the loop.

Install it on Linux, or on Windows inside WSL, with one line:

curl -fsSL https://henningfutrell.github.io/hopper/install.sh | bash

Recommended: the published image with Podman. The install guide takes you from nothing to a first finished job.

Read the install guide Source on GitHub

How it works

Three steps, and you only do two.

  1. Label an issue

    Give a GitHub issue the hopper label: it is a job now.

  2. It runs on your machine

    A coding agent works on it, on a machine of yours, inside its usage budget.

  3. Review the pull request

    The work comes back as a pull request. A question it cannot answer comes to you.

A look around

One daemon, one database, and a UI that works from your phone.

Everything the hopper keeps is in its Postgres database, and every setting is edited in the UI. No config files, and secrets only from its environment.

  • The hopper overview: nine lanes on four machines running jobs at once, the lane timeline, and the waiting queue with held jobs.

    The queue and its lanes

    Every job waiting, held or running, in the order the hopper takes them. Each lane shows what a machine is doing now.

  • The lane timeline: finished and failed runs on each lane over the last hour, jobs running now, and a hovered job waiting on its answer.

    Follow every job as it works

    The lane timeline shows what each lane ran, how each run ended, and where a job waited on a question.

  • A question from a job, escalated past both escalation levels to its owner, with an answer typed in the answer box.

    Questions come to you

    A job's question climbs the escalation levels. Only the ones nothing else can answer wait for you, on any screen, your phone too.

  • The Machines view: four online machines, each with its lanes and live usage of the session and the week.

    Your machines, inside their budgets

    Add the computers jobs run on. Live usage shows how much of each budget is left, and the hopper keeps every machine inside it.

  • The Sources view: a connected GitHub account with four of its repositories chosen for jobs.

    You choose what becomes a job

    Sign in with GitHub, tick the repositories, and label an issue hopper. Nothing else can give the hopper work.

  • Settings → Routing: the router, the queue sorter and three routing rules.

    Every part is a plugin

    Routing rules, job rules and plugins, all edited in the UI. Install more from the plugin store.

Read more