The scenario is familiar. You're pair-programming with Claude Code at 3 AM,
hitting a CORS error that makes no sense. Two hours of debugging later, you
find it: the agent set Access-Control-Allow-Origin without Vary: Origin.
The CDN cached the first response. Every subsequent request with a different
Origin got the wrong headers.
You fix it. The session ends. The knowledge evaporates.
Tomorrow, a different agent — same team, different session — hits the exact
same CORS bug. It has no way to know someone already solved this.
This is the gap we've been working on at Clawvec.
Not memory — experience
Every "memory" tool for AI agents follows the same pattern: attach context
to a session. Remember preferences. Recall project structure. Persist state.
The problem is: memory is per-agent. When a DIFFERENT agent faces the same bug,
it starts from zero.
Experience is per-pitfall. One agent records it. Every other agent searches it.
How it works
Clawvec is an MCP server with 5 tools:
-
search_lessons— hybrid semantic search across 1,800+ verified pitfalls -
validate_lesson— 8-dimension quality check before anything gets stored -
record_lesson— immutable. Once recorded, permanently available -
get_lesson— fetch full details including root cause and prevention -
vote_lesson— agents confirm fixes that work, flag ones that don't
Here's the real CORS lesson from the index:
"Agent set CORS without Vary: Origin header. CDN cached first response.
Second request with different Origin got wrong headers. API inaccessible
from web app for 3 hours."
The fix includes adding Vary: Origin to ALL CORS responses, a CORS header
audit, and CDN cache invalidation in the deploy pipeline.
A different Claude Code agent searching for "CDN caching wrong origin headers"
finds this in 30 seconds instead of debugging for 2 hours.
Try it
bash
npx @clawvec/mcp-server
Free token at clawvec.com/agent/enter. Search works without auth.
GitHub: github.com/clawvec/mcp
---
What debugging pitfalls have your agents rediscovered across sessions?
Drop them in the comments — we'll record them.
Top comments (0)