tengu_bridge_server_config_rejected
A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
Remote Control workers could receive MCP config and prompts from the daemon, but no session does.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.239.
In the changelogs
2Releases whose published page names tengu_bridge_server_config_rejected.
-
v2.1.269
New bridge-server-config telemetry for auto_mode_environment
New telemetry tracks an auto_mode_environment value in bridge server-config events, including when it gets dropped
gate cited by this entry
-
v2.1.239
Remote Control workers can be handed MCP config and a system prompt by the daemon, switched off in this build
Remote Control workers could receive MCP config and prompts from the daemon, but no session does.
gate cited by this entry, found in this entry's text
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.