Claude Code v2.1.216 · 20 Jul 2026
CCR Agent Proxy: Selective Relay Mode
Entry Kind: in v2.1.216, 20 Jul 26
Improvements Section of the release
What
New environment variables give fine-grained control over which hosts the CCR agent proxy relays to, allowing direct dial for selected hosts while tunnelling everything else.
Evidence
Selective relay log messages (search for "[agent-proxy] selective relay:" or "CCR_AGENT_PROXY_RELAY_MODE=selective but include-host").
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.216 →
Names in this entry
env CCR_AGENT_PROXY_RELAY_MODE On self-hosted runners, Claude Code can route all session traffic through a proxy you run, and refuses to start if it cannot
env CCR_AGENT_PROXY_INCLUDE_HOSTS Read by the agent proxy setup in a remote session (CLAUDE_CODE_REMOTE truthy and CCR_AGENT_PROXY_ENABLED set), which removes it from the environment before those checks. With CCR_AGENT_PROXY_RELAY_MODE=selective and no AGENT_PROXY_URL, it is a comma-separated host list: those hosts go through the proxy relay and unlisted hosts use normal networking. An empty or unparsable list logs a warning and falls back to tunnelling all traffic.
env CLAUDE_CODE_AGENT_PROXY_GH_SHIM The agent/tool proxy can now add extra git config includes and prepend a directory to PATH
env CLAUDE_CODE_AGENT_PROXY_GIT_CONFIG Turns on governed git routing in Claude Code's agent proxy; Claude Code sets it to 1 in a remote session's environment when that session's tool config enables gitConfig. When truthy and the agent proxy starts (a remote session with CCR_AGENT_PROXY_ENABLED), it appends a marked governed-git block to the git config file named by GIT_CONFIG_GLOBAL (skipped with a warning if that is unset), routing HTTPS git traffic for the governed hosts (CLAUDE_CODE_AGENT_PROXY_GIT_HOSTS, default github.com) through the local proxy with its CA bundle and git credential prompts disabled. Like CLAUDE_CODE_AGENT_PROXY_GH_SHIM, it also puts the proxy in its tool-scoped mode, and a settings file's env block cannot set it.
Is this right?
0 0 Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 13 of 15
Context Over-Limit Warning Improved
In v2.1.216 Improvements release-page order
Next → · 15 of 15
