{"version":"2.1.288","anchor":"agent-proxy-ca-watch-ca-order-tolerance-gh-shim-per-sessio","canonical_anchor":"agent-proxy-ca-watch-ca-order-tolerance-gh-shim-per-sessio","heading":"Remote sessions handle proxy certificates and the gh command per session","tier":"internal","area":"Sessions","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/agent-proxy-ca-watch-ca-order-tolerance-gh-shim-per-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote sessions handle proxy certificates and the gh command per session\n\nIn remote sessions using the agent proxy, certificate checks accept swapped order and the gh stand-in now lives in each session's own folder\n\n**Unclear.** What `CCR_AGENT_PROXY_CA_WATCH_ENABLED` turns on is not shown.\n\n**What**\n\nSome remote sessions send their network traffic through an agent proxy (a go-between that sits in front of the internet). This only applies when `CLAUDE_CODE_REMOTE` and `CCR_AGENT_PROXY_ENABLED` are set. These sessions changed in several ways:\n\n- `CCR_AGENT_PROXY_CA_WATCH_ENABLED` is a new environment variable that Claude Code now reads.\n\n- Two sets of certificates (the files that prove a secure connection is trusted) now count as the same when they contain the same two certificates in the other order. Before, they had to match byte for byte.\n\n- Installing the proxy's certificate into the system's trusted list now reports whether it worked, and a retry is marked as incomplete.\n\n- The `gh` shim (a small stand-in for the GitHub command-line tool) now lives in its own folder for each session, under `sessions\/<id>\/bin`, instead of one shared folder. That folder is added to the command search path.\n\n- Setting up the shim now checks whether one was inherited from elsewhere, checks whether `jq` is available, and skips some relaying.\n\n- Claude's instructions now say that when the shim is not a stand-in, `gh` in Bash is the machine's own GitHub command-line tool.\n\n**Why**\n\nThis affects how remote sessions decide which secure connections to trust and which `gh` command Claude actually runs. Keeping the shim per session stops one session's setup from affecting another's.\n\n- Area: Sessions\n- Names: `CCR_AGENT_PROXY_CA_WATCH_ENABLED`, `CCR_AGENT_PROXY_ENABLED`, `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}