doodlebyte

I completely agree. That observation is actually what led us to build StateGuard. We expected model failures to dominate, but after reproducing a few dozen real-world issues, most of them turned out to be contract mismatches between APIs, providers, schemas, tool outputs, and application logic.

We're trying to understand which of those failures developers would actually want repaired automatically versus simply surfaced through observability.

This is a really interesting class of failure. It feels like we're going to see more cases where the "human view" and the "LLM view" of the same data diverge. Have you run into similar issues outside of MCP as well, or is this mostly specific to terminal-based tool interactions?

Interesting idea. Have you found reviewers actually use the generated reasoning, or does it mostly help the original author organize their thoughts?

Nice work. I'm curious what made you choose this approach over the more conventional alternatives. Was there a specific pain point that pushed you in this direction?