{"version":"2.1.287","anchor":"remote-agent-proxy-gh-stand-in-shim-when-no-gh-on-path","canonical_anchor":"remote-agent-proxy-gh-stand-in-shim-when-no-gh-on-path","heading":"gh works in governed remote sessions even when it is not installed","tier":"notice","area":"GitHub","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-agent-proxy-gh-stand-in-shim-when-no-gh-on-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### `gh` works in governed remote sessions even when it is not installed\n\nRemote sessions with governed git now get a stand-in for the GitHub `gh` command when `gh` is not installed\n\n**What**\n\n`gh` is GitHub's command-line tool. In remote sessions where git access goes through a governing proxy, Claude Code already wrapped an installed `gh`. It now also writes a stand-in for `gh` when none is installed, so the command still exists. It also keeps track of enterprise GitHub hosts.\n\nThis applies only when `CLAUDE_CODE_REMOTE` is set.\n\n**Why**\n\n`gh` commands now work in governed remote sessions whose machine does not have `gh` installed.\n\n- Area: GitHub\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}