test: name the cause when the sandbox MCP session cannot be opened #126
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/test-sandbox-mcp-diagnosis"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #125 after its first real run on the website sandbox, where 11 of 12 checks passed and the mcp check failed with a message naming three possible causes at once. When no SSE endpoint event arrives, the probe now requests the status line alone and reports what it got: 000 means the wraptool server is not running on the host or the pinhole is gone, 401 a stale bearer token in the harness config, 403 a missing sandbox-scoped network rule, 200 a stream that sent no event. Each message names the command that fixes it. Dry-run against a fake sbx for the 000 path. 🤖 Generated with Claude Code