This is a Fictional demo showing how Local Agent Workbench can turn a vague issue report into a structured maintainer handoff.
No real user data, credentials, logs, or private project details are included.
A small CLI tool has a bug: when a user runs demo-tool audit --json, the command exits successfully but prints non-JSON warning text before the JSON object. This breaks downstream scripts that expect clean JSON.
The files model a 9-pane Codex CLI session:
question.mdcontains the issue report.pane-roles.mdassigns one job to each pane.pane-1-reproduction.mdthroughpane-6-maintainer-response.mdshow sample agent outputs.final-triage.mdshows the maintainer-ready synthesis.handoff-summary.mdshows the output a maintainer could generate withscripts/close_workflow.sh.
The important pattern is not that nine agents all agree. The value is that each pane checks a different part of the maintenance decision:
- reproduction
- likely code path
- minimal fix
- tests
- risk
- maintainer reply
That makes the final triage memo easier to trust and act on.