Use it now
Useful4 Signal3
Five more environment variables, including stream and byte watchdogs, can be set in settings.json.
What's wrong with this entry?
Anonymous. No account, no email.
CLAUDE_ENABLE_STREAM_WATCHDOGCLAUDE_ENABLE_BYTE_WATCHDOGCLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCKMCP_CONNECTION_NONBLOCKINGCLAUDE_CODE_TEAM_TEARDOWN_PARK_TIMEOUT_MS
What
The allowlist that decides which env keys in a settings file are applied to the process gains CLAUDE_CODE_TEAM_TEARDOWN_PARK_TIMEOUT_MS, MCP_CONNECTION_NONBLOCKING, CLAUDE_ENABLE_BYTE_WATCHDOG, CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK and CLAUDE_ENABLE_STREAM_WATCHDOG. Previously these could only be set in your shell before launching. Set them once in settings instead, for example { "env": { "CLAUDE_ENABLE_STREAM_WATCHDOG": "1" } }.
Details
- The same allowlist decides whether a settings file is flagged as carrying unrecognised env keys, so these five no longer trigger that warning.
- All five are already read elsewhere in the build; the change is only that settings can now supply them.
- The byte watchdog, which aborts a response whose byte stream stalls, checks its variable first and otherwise falls back to a server-side default that is on, so leaving it unset keeps the current behaviour.
Evidence
CLAUDE_CODE_TEAM_TEARDOWN_PARK_TIMEOUT_MS, CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK
Strings lifted out of the shipped bundle, so the claim above can be checked against them.