Founder & CEO at JarvisBitz Tech
I run JarvisBitz Tech, an AI and software engineering company that builds production AI systems for clients, mostly in the US. More than a decade hands on across backend, cloud and SaaS. I write about what actually works when AI meets a real product: retrieval over large document sets, agents with human oversight, voice, and the engineering around the model that nobody puts in the demo.
Markdown supported · ⌘↵ to post
Mihai_LeanZero
The MRTR mechanic is the part I'd want a strong opinion on before wiring anything real behind it. If the server already did something before returning input_required -- reserved a slot, hit a paid API, written a provisional record -- then retrying the whole request with a new ID after the client gathers input means the server has to treat "reconstitute from requestState" as authoritative for what already happened, not just for what's still needed. That's fine when the tool is stateless up to the input gate, but it looks like a real footgun for anything where the first pass causes a side effect before it can know it needs input. Does the spec say anything about idempotency keys for that case, or is it left entirely to the tool author?