CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK
Updated by Alex Sorokoletov
CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK is a Claude Code environment variable: Enable the byte watchdog on Bedrock connections. The watchdog fires when a connection opens but produces no bytes within a window — catching silent stalls that don't produce a connection error. Added between v2.1.138 and v2.1.143 and still present in v2.1.294. It is listed in the official reference.
| Status | Present in v2.1.294 |
|---|---|
| Added | Added between v2.1.138 and v2.1.143 |
| Category | Cloud providers |
| Official docs | Listed |
How to set it
For one session, export it in the shell that starts Claude Code:
export CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK=<value>
claudeTo apply it to every session, add it to the env object of a settings file:
// ~/.claude/settings.json
{
"env": {
"CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK": "<value>"
}
}Release notes that mention it
Related variables
ENABLE_PROMPT_CACHING_1H_BEDROCK: Enable 1-hour prompt caching on Bedrock.ANTHROPIC_BEDROCK_BASE_URL: Alternative Bedrock endpoint (alias).ANTHROPIC_BEDROCK_MANTLE_BASE_URLANTHROPIC_BEDROCK_REGION_PREFIXANTHROPIC_BEDROCK_SERVICE_TIERAWS_BEARER_TOKEN_BEDROCK: Bearer token for Bedrock authentication.CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULTCLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_GUARD
Frequently asked questions
What does CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK do?
Enable the byte watchdog on Bedrock connections. The watchdog fires when a connection opens but produces no bytes within a window — catching silent stalls that don't produce a connection error.
Which Claude Code version has CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK?
Added between v2.1.138 and v2.1.143 and still present in v2.1.294.
How do I set CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK?
Export it before starting Claude Code (export CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK=value), or add it to the "env" object in ~/.claude/settings.json to apply it to every session.
All variables, searchable: Claude Code environment variables.