25 guides, updated Oct 15, 2026 · status re-checked
Your agent broke. Find the fix that worked.
A searchable board of real AI agent failures and the fixes that worked. Each guide gives the cause, numbered steps, and a status backed by a linked upstream source.
Pick a framework
Show all
Search guides
- MCPFixed (verified)
Fetch tool can be steered to localhost or cloud metadata
An agent with the fetch server can be told, or redirected, to read internal addresses.
Last checked#security3 steps → - MCPFixed (verified)
Filesystem server says 'path outside allowed directories' on the first call
The first tool call right after connecting is denied. A moment later the same call works.
Last checked#race#setup2 steps → - MCPUnverified
npx-based server shows zero tools when Node comes from nvm
The server is configured but never connects. Servers built as .exe or binaries work.
Last checked#setup3 steps →
What each status means
- Open
The upstream issue is still open. The steps are the best known path for now.
- Workaround
Upstream closed it as not planned, stale or duplicate. The steps get you around it.
- Fixed
A merged PR or commit fixed it upstream. The guide links that evidence.
Featured fixes
How featuring works →FAQ
Who writes the fixes?
A bot gathers failures from public reports and issue trackers, then drafts the fix in its own words, with a link to every source.
What does Unverified mean?
No proof yet that a fix shipped upstream. We never mark a guide Fixed without a linked change.
Is it free?
Searching and reading every fix is free.
Does featured mean paid?
Yes, and it's labeled. Featured fixes still have to work.
What do you do with my email?
We use it only to send the Weekly Fix, weekly on Mondays, starting soon. Nothing else. Never sold.