Working the queue at Runner since August 2026
Triaged watches your issue tracker. Each new bug is diagnosed in an isolated copy of your code, fixed, tested, screenshotted, and challenged by an independent reviewer. Clean fixes ship. Real decisions come to you, once, with a recommendation.
How it works
The shape of every run, with a made-up bug.
Someone files “Investor status chip doesn’t update until refresh.”
Triaged sees the queue change, waits for the reporter to stop typing, and starts a run.
It checks out an isolated copy of the code, reproduces the bug, and writes the fix and a test.
Tests, lint and typecheck pass. It takes a screenshot from the reporter’s point of view.
A second, independent reviewer tries to break the fix and checks every human comment on the issue against the change.
Verdict: clean. The fix lands as a normal commit with the issue number. The issue moves to In Review with a plain-English note and the picture.
You read the note over coffee. If it was a judgment call instead, one question is waiting with a recommendation and lettered options. Answer it and it ships.
What comes back
A clean fix: tests green, reviewer passed, no open human comments, inside your shipping hours. Committed as you, referencing the issue.
A product or engineering decision. One question in your tracker, marked as the bot, with a recommendation and lettered options. Ships when you answer.
Anything the reviewer could not clear waits on the dashboard with the patch, the test result, the screenshot and the findings. Accept, reject, or send it back with notes.
Issues that share a root cause are reconciled into one patch and one question first, so nobody gets three bot questions about one policy. The question names the decider, states the options, says which one it would pick and why, and ships within the hour of the answer.
Guardrails
Every one of these is a switch or a mechanism on the dashboard, not a promise in a slide.
Beyond the queue
Fixes are the core loop. The rest of keeping a system healthy runs under the same guardrails.
A check that goes stale, an on-chain heartbeat, a dead endpoint — monitors file their own ticket before anyone notices, and it gets worked like any other.
Work outside the repository — a vendor console, a DNS record, something that needs hands — becomes a drafted bounty for a vetted human. You approve it before it posts, and payment clears only after the fix has soaked.
Scoped, policy-gated capabilities: set an environment variable, add a DNS record, run an operator-approved command. Each grant is yours to give; every act is journaled.
In production
Runner builds fund-formation software for private markets: a Rails and React codebase, regulated data, one engineer. Triaged has worked its Linear queue since 19 August 2026.
Counts of unique issues from the Triaged ledger, as of 5 September 2026.
Setup
Who decides, which hours it may ship, which model and how hard it thinks, the monthly budget, and one hard stop. The person who owns the repository owns the settings.
About
Triaged is built by Zack Skolnik, founding engineer at Runner, previously Compound, MakerDAO and co-founder of Fission Labs. MIT Computer Science.
Get in
Triaged is in private use. Tell me about your queue and I’ll be in touch within a day.