# Resumed Claude request held open after a gateway 429

Environment: Linux web dev client, Chromium 1280x800, light theme, Claude Code 2.1.325. Each commit has a separate installed worktree and fresh `.t3` created with `T3CODE_DEV_SEED=0`; no copied database. Base 4860a730695762331cc482253ba60beda7875c40; head 6eea8212c8eeee28e9b6c6e4266a6dd991885a03. No product source or T3 timeout was modified.

1. Run the accompanying `gateway.py` (Python standard library), which defaults to returning the report's CLIProxyAPI-shaped 429 with a long retry-after. Its only upstream is local; it never contacts a model.
2. Create an isolated Claude config directory. Put this in its settings.json:
   {"env":{"ANTHROPIC_BASE_URL":"http://127.0.0.1:18778","ANTHROPIC_API_KEY":"synthetic-gateway-key","ANTHROPIC_AUTH_TOKEN":"synthetic-gateway-key","API_TIMEOUT_MS":"3600000"}}
3. Configure the test server's providerInstances.claudeAgent as {"driver":"claudeAgent","config":{"homePath":"<isolated Claude config directory>"},"environment":[{"name":"API_TIMEOUT_MS","value":"3600000","sensitive":false},{"name":"API_FORCE_IDLE_TIMEOUT","value":"false","sensitive":false},{"name":"CLAUDE_BYTE_STREAM_IDLE_TIMEOUT_MS","value":"1800000","sensitive":false},{"name":"CLAUDE_STREAM_IDLE_TIMEOUT_MS","value":"1800000","sensitive":false}]}. Ordinary environment overrides alone are insufficient if the default Claude settings supply their own endpoint.
4. In each worktree, run `T3CODE_DEV_SEED=0 vp run dev`, retain its session, and use its startup pairing URL to open the web client. Use a fresh synthetic git repository and `node apps/server/src/bin.ts project add <repository> --title 'Gateway silence' --base-dir .t3`.
5. Start a Claude Fable 5.2 thread through the real server CLI:
   `node apps/server/src/bin.ts thread start <repository> 'Say hello in one word.' --title 'Resumed Claude silence' --provider claudeAgent --model claude-fable-5-2 --base-dir .t3 --json`
6. Open that thread's environment/thread URL in each web client. Confirm the 429 message and Usage limit reached / reset UI.
7. Start a browser recording on each side. Write `hang` into the gateway's sibling `mode` file. For POST /v1/messages the gateway now accepts the request and sends no response at all. The explicit process environment extends the CLI timeouts identically on both sides to keep its per-attempt timeout from preempting T3’s ten-minute deadline. This models the report’s 16+ minute silent request without altering T3 Code.
8. In each client's composer, type `start again` and press Enter. Do not press Stop, reload, restart the server, or advance the clock. Observe for more than ten real minutes.
9. Capture both apps at the same elapsed point after the head has reached its deadline. Stop the recordings. Record what each app actually displays; the expected fixed behavior is a settled turn with a visible explanation of the unanswered request.

The browser's environment label was replaced with `Test environment` for privacy on both sides before recording; no conversation, status, timing, or error text was changed. Early setup-validation threads are visible in the sidebar but the captured reproduction is the thread titled `Resumed Claude silence`.

Observed: both providers remained silent after requesting. Head interrupted and closed its query at 20:18:53 UTC, ten minutes after requesting, and showed the unanswered-request error. Base still showed Working/Thinking at +10m10s. The gateway later received SIGTERM; base first emitted api_retry at 20:19:26 UTC (+10m31s) and eventually failed with connection refused. The paired clips are the first 615 seconds of the original recordings, ending before this tooling interruption; full recordings and protocol transcripts preserve what happened afterward. A sixteen-minute silent base interval is not claimed.
