Repository navigation
docs(agents): log where the CLI confuses agents - #33
Merged
Merged
Conversation
Ask agents to record each error they work around, each tool they use beside voltage, and each slow discovery of why a task cannot be done. Records go in git-ignored per-issue directories under docs/issues/, with provenance, the status on unmerged branches, and a Nix reproduction. Agents delete them once the issue is fixed.
This was referenced Oct 14, 2026
gkrizek
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Agents that use
voltageoften hit errors, work around the CLI withpythonor shell loops, or need many calls to learn why a task cannot be done. Nobody records these cases, so nobody fixes them.Change
AGENTS.mdgets an Agent friction log section. It tells agents to:voltagecommand errors and the agent works around itvoltageor reads the source to make progressrepro.shagainstmasterand delete the records it fixedEach record is a directory,
docs/issues/<date>-<slug>/, with:README.md: what happened, why it confused the agent, provenance, and status on unmerged branchesrepro.shthat runs in the Nix dev shellRecords must be generic: placeholders only, and no personal or account data.
.gitignoreignores/docs/issues/, so each record stays in the agent's own checkout.Validation
The first six records, from a staging session, are opened as GitHub issues: #34, #35, #36, #37, #38, #39. I ran their three offline reproductions on this branch, so on
master's code. All three still fail.Docs only; no code changes.