Drive 2.0.1 can apply connection-level chaos, but reproducing an OpenCode TUI location-sync regression required a small loopback proxy to return HTTP 500 for only GET /api/agent while GET /api/location and SSE remain healthy. The same setup needs to heal that route and click Retry without restarting the instance.
A scoped HTTP fault override in the network fixture would make this repeatable without a Bun preload/proxy. Expected: select a method/path, return a deterministic status/body, inspect matching request counts, and remove the override. Current workaround: preload a loopback proxy for the script-owned TUI only, forward other requests, and toggle the selected response from the isolated fixture. OpenCode base tested: d9c85d8d95. This is a Drive fixture capability request, not the OpenCode bug itself.
Drive 2.0.1 can apply connection-level chaos, but reproducing an OpenCode TUI location-sync regression required a small loopback proxy to return HTTP 500 for only GET /api/agent while GET /api/location and SSE remain healthy. The same setup needs to heal that route and click Retry without restarting the instance.
A scoped HTTP fault override in the network fixture would make this repeatable without a Bun preload/proxy. Expected: select a method/path, return a deterministic status/body, inspect matching request counts, and remove the override. Current workaround: preload a loopback proxy for the script-owned TUI only, forward other requests, and toggle the selected response from the isolated fixture. OpenCode base tested: d9c85d8d95. This is a Drive fixture capability request, not the OpenCode bug itself.