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

Claude Code v2.1.288 ·

How remote sessions set up their stand-in gh command

In remote sessions, the stand-in gh command now gets its own folder per session, is skipped in some cases and cleans itself up

Under the hood Internal Changes
JSON All of v2.1.288
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.288,
Internal ChangesSection of the release
What

In remote sessions (with CLAUDE_CODE_REMOTE set and the agent proxy turned on), Claude Code can put in place a stand-in gh command, a small program that takes the place of the GitHub command-line tool. This is set up differently now:

  • Each session gets its own folder under sessions/, instead of all sharing one folder.
  • In selective relay mode, where GitHub requests are not sent through the session's proxy, no stand-in is created if gh is not already installed.
  • If an outer session already set up its own stand-in, Claude Code leaves it alone.
  • The stand-in file is deleted by a cleanup step when it is no longer needed.
  • When the gh in use is not the stand-in, the note Claude reads says it is the machine's own GitHub CLI.
Why

This changes how gh behaves inside remote sessions, and Claude is told more accurately which gh it is using.

Read from
Names in the bundleCLAUDE_CODE_REMOTE
What the documentation says
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 the session identifier that selects the per-session setup.

See this entry in the whole of v2.1.288 →

Feedback