Developer workflow Beta
Runner
Runner connects an approved GitHub Project task to local coding agents, carrying the plan, implementation and review evidence through to a pull request.
A real change on this website
The first FlowStack page came through Runner.
The task was to add FlowStack to the portfolio and create an accurate page in English and Danish. Here is a summary of that brief, the changes and the agent’s review.
This walkthrough follows the released v0.7.11 GitHub Project workflow. The repository’s main branch also contains replacement-coordinator work; use documentation matching the version you install.
An approved task
Describe the company, my role and the bilingual journey from the portfolio to the detail page.
A reviewable change
Implementation produced the page, navigation and localization changes in an assigned checkout.
Evidence before a decision
Agent QA accepted a specific commit. The pull request records that review, and GitHub separately records its later merge.
This example is from November 2026. The website repository is private, so the task, change and review are summarized here. The current page has been revised since.
What would make this task complete?
“Add FlowStack” needed a clear definition of success. The task made the company relationship and the visitor’s journey part of acceptance.
- Say the right thing
- The page needed the platform description and my active co-founder/CTO role, without implying that I built FlowStack alone or that Techbase owns it.
- Make the journey work
- A visitor needed to reach the corresponding English or Danish page from the portfolio, change language and return to the work. The native page metadata and discovery entries had to agree too.
- Check the delivered candidate
- The retained results covered the bilingual journeys, narrow layouts, native metadata and the required frontend and Go checks. The reviewer assessed that evidence against a specific commit.
An accepted change has an identity.
The review named the commit below. That matters because a later change can affect the result: evidence for one candidate does not automatically establish that another candidate is ready.
Commit accepted by agent QA
9d4e431ef20dd0f029a8862b18ff3282e2a1a269The report also says which evidence was reused and what was unverified. Its browser coverage was Chromium viewport emulation; physical devices and Safari were outside that check.
Review, merge and release answer different questions.
Agent review
Does this candidate meet the task, given the source and evidence inspected?
Merge decision
Should this change enter the project’s base branch? GitHub records the later merge separately from the agent’s acceptance.
Deployment
Which commit reached the server, and does the public journey work there? This needs its own release result and live observation.
That separation is a large part of why I work on Runner. I want a result I can inspect, with the reasons and limits alongside it, and a clear place to make the next decision.
Why I’m building it.
I want the coding task and the reasons for accepting its result to stay together, so I can follow the work and understand the decision.
I work on the architecture and agent orchestration, the GitHub integration and the checks around AI-generated changes. I want to be able to follow the work and see what supports a decision to merge.
For trusted or maintainer-approved work, Runner coordinates planning, implementation in an assigned worktree and agent review. A resulting pull request waits for a human decision by default. Passing checks and agent review inform that decision; someone still needs to judge whether the change fits the task.
Run it with your own tools.
The public beta uses your existing GitHub CLI login and configured AI tools. You run it locally, without a hosted control plane, inbound server or required GitHub Actions workflow. The repository explains setup and operation.
Runner can create Project fields and cards, branches, worktrees and pull requests. An agent with host access can reach files and credentials available to your operating-system account. Start with the documented sandbox settings and automatic merge disabled.
This page follows the released GitHub Project beta. The source repository also contains a replacement coordinator under development. The released v0.7.11 documentation linked above matches the workflow described here; development-branch features have their own qualification and release process.
Ask me about Runner →