{"version":"2.1.288","anchor":"gh-stand-in-shim-supports-any-host","canonical_anchor":"gh-stand-in-shim-supports-any-host","heading":"Environment info now covers the GitHub CLI and its stand-in","tier":"internal","area":"Sessions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/gh-stand-in-shim-supports-any-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Environment info now covers the GitHub CLI and its stand-in\n\nClaude's environment details gain a `githubCli` entry, the model is told when built-in gh goes away, and the gh stand-in can reach any GitHub host\n\n**Unclear.** It is not clear what sets `ghesHosts` to \"any\".\n\n**What**\n\nClaude Code gives the model a short description of the environment it runs in, such as the platform, shell and operating system. That description now has room for the GitHub command-line tool, `gh`.\n\n- `githubCli` is a new optional field in the environment description and in the session-environment schema, next to `scratchpadDirectory`.\n\n- When `gh` was announced to the model earlier and is missing from a later snapshot, the model is now told that it changed. This is tracked through `toldOfBuiltinGh`.\n\n- A new `ghStandin` slot holds a generated `gh` stand-in script. It can now be given `--any-host` when `ghesHosts` is \"any\". It then talks to github.com or to the GitHub Enterprise host a command names. Before, it accepted only an explicit `--hosts=` list.\n\n- Separately, the check for placeholders that count as pasted text now also matches `[` followed by a new marker.\n\n**Why**\n\nIn practice the model can now be told whether `gh` is available and be told again if it disappears, instead of assuming a tool that is gone. Sessions that rely on the stand-in are no longer limited to a fixed list of GitHub hosts.\n\n- Area: Sessions\n- Names: `ghesHosts`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}