A library author and the same issue, again
Solo buildersMaintainer of a small TypeScript library, alone
Every few weeks someone opened an issue asking why the library breaks in Jest with CommonJS. Each time we asked an agent to look into it, it re-traced the package exports map and the build config, about 20k tokens.
How do I stop re-investigating the same duplicate GitHub issue on my library every few weeks?
With ArcRoom, the first investigation ends with complete_task: the cause and the workaround, stored with the git hashes of package.json and the build config it relied on. The next duplicate issue goes through find_task and gets the saved answer. When those files change in a new release, the answer is stale and redone. The playbook is the maintainer's: contributors' agents don't see it unless they join the team.
Also asked as: The same Jest and CommonJS issue keeps getting opened on my library. How do I save the answer? · How do I reuse an AI agent's investigation for duplicate issues? · Can an AI agent tell when a saved answer about my build config is out of date?
The first investigation ends with complete_task: the cause and the workaround.
- Reused answer
- Saved answer
- Freshness check
find_task → match: reuse (0.86), saved 5 weeks ago
Step by step
- The first investigation ends with complete_task: the cause and the workaround.
- The answer stores the git hashes of package.json and the build config it relied on.
- The next duplicate issue goes through find_task and gets the saved answer.
- When the exports map changes in a new release, the answer is stale and redone.
What the agent sees
find_task → match: reuse (0.86), saved 5 weeks ago
"Jest + CJS: exports map has no 'require' entry since 3.0. Workaround: transformIgnorePatterns. Fix planned in 3.2."
files unchanged since savedCompared with today's tools
A pinned FAQ issue or GitHub Discussions
Write the answer once in a pinned issue and link duplicates to it.
- Setup
- 20 min
- Ongoing
- update the FAQ after each release, ~10 min
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
The public FAQ is better because users read it themselves; ArcRoom adds that the agent knows when the answer went stale.
Where it stops
The playbook is the maintainer's, not public. Contributors' agents don't see it unless they join the team.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.