2 posts tagged with "Agents"

More teams are moving AI agents from demos into real systems. Agents are reviewing payments, answering support questions, querying internal data, calling MCP servers, creating tickets, summarizing incidents, and producing work that downstream systems depend on.

That changes the architecture. If an agent consumes information, calls tools, writes data, or produces artifacts, it needs to be visible in the same place as the rest of your system.

EventCatalog 3.41.0 adds first-class agent documentation. You can now document agents alongside your domains, services, events, commands, data stores, tools, and flows.

I've been using Claude Code and Cursor every day to work on EventCatalog, and I kept running into the same frustrating thing — the agent would confidently spit out frontmatter that didn't exist, point at folders we'd renamed months ago, or call an API that changed two releases back. I'd read the diff, sigh, and fix it by hand. Every time.

It's not really the agent's fault. It's working from a snapshot of the web that's months (or years) out of date, and EventCatalog moves fast. So I kept asking myself: why are we making agents guess what our API looks like when the answer is already sitting in node_modules?

That's what shipped in 3.35.1. The full EventCatalog docs are now bundled inside the npm package, version-matched to whatever you have installed. No more guessing. No more stale snippets. The agent reads the same docs you do.