Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Environment info now covers the GitHub CLI and its stand-in

Claude'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

Group of 5 Use it now Notable No documentation found Improvements
JSON All of v2.1.288
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
GitHub CLIArea: what it touches
ImprovementsKind: in v2.1.288,
What probably matters to youSection of the release

What

Claude 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.

  • githubCli is a new optional field in the environment description and in the session-environment schema, next to scratchpadDirectory.
  • 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.
  • 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.
  • Separately, the check for placeholders that count as pasted text now also matches [ followed by a new marker.

Why

In 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.

Read from
Names in the bundleghesHosts
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what sets `ghesHosts` to "any".

See this entry in the whole of v2.1.288 →

Feedback