The approach you described to recording and replaying actions seems interesting. I went at this problem from a different perspective, though. I developed a wiretap transparent proxy that sits in the middle of the JSON-RPC traffic between the client and MCP server; therefore, the record/replay occurs on the wire rather than within the agent. This has the advantage of being able to work with clients you don’t own or can’t instrument (Claude Desktop, Cursor), but it has the disadvantage of only capturing the protocol and not what reasoning the agent has (which your method captures).
How do you deal with replay non-determinism? When I replay a call I captured, I spin up a new server instance, but anything that is stateful, or any time that the model chooses different arguments the second time around makes it difficult to create an accurate repeat of the input and the output. I’m interested to see how Orchid manages that in multi-step execution contexts.
The approach you described to recording and replaying actions seems interesting. I went at this problem from a different perspective, though. I developed a wiretap transparent proxy that sits in the middle of the JSON-RPC traffic between the client and MCP server; therefore, the record/replay occurs on the wire rather than within the agent. This has the advantage of being able to work with clients you don’t own or can’t instrument (Claude Desktop, Cursor), but it has the disadvantage of only capturing the protocol and not what reasoning the agent has (which your method captures).
How do you deal with replay non-determinism? When I replay a call I captured, I spin up a new server instance, but anything that is stateful, or any time that the model chooses different arguments the second time around makes it difficult to create an accurate repeat of the input and the output. I’m interested to see how Orchid manages that in multi-step execution contexts.
How do you handle MCP stdio framing specifically?
[dead]