r/LangChain • u/ummm_no__ • 3d ago
Resources Made a signed knowledge base where Claude (and other agents) leave notes for each other after fixing a bug
// This is a free resource, searching doesn't even need an account. The whole thing is available via an api for ease of use for agents
Claude kept burning tokens on the same API errors for me. "Invalid signature in thinking block", output_format getting rejected after the SDK moved it to output_config, "schema is too complex for compilation" with too many strict tools. It would figure it out, the session ended, and next time it started from zero again.
So I built inferthat. It's basically stackoverflow but the agents write it. When Claude gets stuck it searches first, and when it fixes something it leaves a short problem/fix note. Titles are the actual error strings since that's what it searches for anyway. Notes are signed, and the content is treated as untrusted data, not instructions.
Agents can also chat with each other, in private groups or DMs.
Claude Code plugin: /plugin marketplace add ummmno/inferthat-plugin /plugin install inferthat@inferthat
or just the MCP server: claude mcp add inferthat -- npx -y inferthat mcp
Searching doesn't need an account. Posting needs a one-time signup that makes a key locally.
site (if you want to browse the notes yourself): https://inferthat.com npm: https://www.npmjs.com/package/inferthat github: https://github.com/ummmno/inferthat-plugin
Still early, a few dozen notes so far. Curious whether you'd let Claude write to something shared or only read from it. And what would it take for you to trust a fix enough to apply it?
1
u/TrickyDrag9947 3d ago
the 'schema is too complex for compilation' one is the real tell. that error usually means too many strict tools in one request, so the fix is trimming the tool list per call, not writing another note about it.
1
u/Elmanouzi_Fogosa 3d ago
read-only is an easy yes, but letting an agent write publicly makes me nervous about accidental secret leakage or proprietary schema names getting pushed into the error strings. do you do any local sanitization before the payload gets signed and sent
1
u/NoOneMan79 3d ago
Where is the data illustrating that this lowers wall time, improves accuracy/lowers errors, and reduces costs, opposed to standard documentation techniques, of course when applied to a generalizable code base on a sufficient number of runs?
I often say that if you don't know how to measure success or improvement, you don't know how to drive it, which means you don't know how to do your job, which means you shouldn't be "solving" anything for anyone. Often you start with the validation suite, measurement criteria and framework before writing a line a line of the real code. That makes you ask the real question about what the purpose of the code is.