Quox Dev Suite · Triage
The pile, worked.
Triage is the agent that owns that backlog properly: evaluates each item with evidence, proposes fixes that ask before applying, and leaves receipts for everything it touches.
Worksthe whole inboxProposesnever just appliesApprovalsHITL, witnessedOutputfixes with receiptsIn plain words
What it is, where it lives, when to reach for it
- What is it
- A method for clearing a bug backlog with an agent that proposes fixes and asks first.
- Where do I use it
- In a terminal session on a dev server today. A dashboard window per server is planned.
- When would I use it
- When bug reports pile up faster than anyone can read, reproduce, or close them.
- How do I use it
- Not yet invocable. There is no quox triage verb and no packaged agent; today it is a way of working.
The model
Sweep, evaluate, propose. A human keeps the yes.
Every codebase has a backlog nobody owns: the gripes, the flaky tests, the bugs too small to schedule and too real to ignore. Handing that pile to an unwatched agent just converts it into a second pile of unreviewed changes.
Pick up everything
Triage starts where humans stop: the pile. Gripes, filed bugs, failing checks, stale reports, it sweeps the whole org inbox, dedupes what is really one issue wearing five hats, and ranks by evidence, not by who shouted loudest.
Evidence before theory
Each item gets the discipline: reproduce it, read the actual error, name the hypothesis with the evidence behind it. No fix is proposed from a guess. Items that will not reproduce are closed with the trace that says so, which is also an answer.
A fix that asks first
Triage proposes: a diff, the failing test that proves the bug, the passing run that proves the fix. Applying it is an approval in your inbox, witnessed on the evidence chain. The agent does the work; a human keeps the yes.
A window per dev server
Where it goes next: Triage as a packaged agent on every enrolled dev server, with a dashboard window showing the queue, what it is working, what awaits your yes, and the receipts of everything it closed. The fleet’s bug backlog, worked while you sleep.
Honest state
What is real today, what is planned
- The triage workflow, run against our own fleet inbox: real bugs picked up, evaluated, fixed
- Evidence-first discipline enforced (reproduce, hypothesis, one change at a time)
- HITL checkpoints through the real approval inbox, witnessed on the chain
- Triage as a packaged agent delivered with the dev server kit
- The dashboard window per dev server: queue, in-flight, awaiting-approval, closed-with-receipts
- The Gripe handoff: gripes stream in as the inbox it works
- Scheduling: nightly sweeps, budget caps, per-org policy
Evidence
The pile, on screen
How you get it
An agent in daily use, a listing you can hold
Real, on our fleet
Triage works our own inbox today as a terminal workflow, behind the real approval inbox, with witnessed receipts. The dashboard window per dev server is the planned half, listed in the open above.
On its own
Triage has its own store row at $19, and it ships inside the Dev Suite bundle at $169 alongside the Gripe stream it works. The row is priced and launch-gated: checkout opens on launch day, through Stripe, with the licence key delivered by email.
There is no dashboard plugin manifest for Triage yet, so what launch delivers is the licence key, not the packaged agent and its dashboard window, which stay in the planned column above.
Triage
A backlog with an owner
Part of the Quox Dev Suite. The fixes come with receipts.