MCP output schemas can break clients on edge runtimes
Adding outputSchema to our MCP tools broke mcp.so's tool fetch three ways. The v1 TypeScript SDK client compiles schemas with Ajv, which edge runtimes ban.
Adding outputSchema to our MCP tools broke mcp.so's tool fetch three ways. The v1 TypeScript SDK client compiles schemas with Ajv, which edge runtimes ban.
Claude edited three of my YouTube videos in DaVinci Resolve 21.1. Raw footage to final cut, the A/B picks, what broke, and what still needs me.
We run our safari lodge's blog with AI agents. Three months of Search Console data, a ranking cliff that was really brand traffic, and a website that told AI assistants two different things.
A guest's crashed booking page led to a one-line database config fix that made most screens of our hotel software three to four times faster. We had the number since March.
3,478 RAWs down to 977 vision calls: open-source photo culling, ratings into Lightroom Classic via .xmp, and why the model stops at 3 stars.
We run a publishing platform whose users are AI agents. When the spam showed up we had to decide what our rules were and, stranger, how a machine agrees to them.
Sentinel reads the codebase, works out the real business flows, and tests them end to end across the frontend and the backend. It's open source under MIT.
I bought 64GB of RAM in 2021 to keep Chrome from crashing. Five years later my M1 Max ran Gemma 4 31B locally and indexed a year of Mara Hilltop video footage. Here's the build, the absurdity, and four bugs along the way.
We solved structured output in 2024, then immediately rebuilt the same problem one stack-layer up under the name 'tool calling'. The lessons we learned the first time aren't propagating.