I gave Space Bunny a coding-agent tracing task in OpenCode. The goal was to capture model calls without storing every unrelated request the CLI sent through the proxy. The request filter ended up being the most important part of the implementation to review. The first version identified model calls by checking whether a POST endpoint ended in /messages. That was too broad: an unrelated tool could send a request to a path such as /tools/messages and still be recorded as a model call. The revised filter checks the configured endpoint path as well as the request body. A request is stored only when it contains a nonempty model name and either the expected messages list or an input field. Requests that do not meet those conditions still pass through the proxy; they are simply excluded from the saved trace. The regression test makes that distinction explicit. It sends an unrelated tool request containing a recognizable marker, confirms that the request reaches the upstream server, and then verifies that the marker does not appear in the trace. The test failed with the original suffix-based filter and passed after the fix. It is worth keeping because it protects both sides of the intended behavior: unrelated requests must continue to work, but their contents must not be recorded. A later review found a separate protocol mismatch in prompt-export mode. A prefixed Messages endpoint was receiving a Responses-format reply. The patch now handles that endpoint correctly for both regular JSON responses and SSE streams. The integration was still under review when this test was run. The live HTTP/SSE trace in the pull request verifies the setup with one configured provider. Other providers, as well as WebSocket-based configurations, have less coverage and still need their own end-to-end tests.   submitted by   /u/Greney_Yunan [link]   [comments]