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
ghis 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
ghin 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.
Names in the bundleCLAUDE_CODE_REMOTE
Documented inclaude-code/cloud-environments
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear what sets the session identifier that selects the per-session setup.