Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Reading a new release v2.1.323 Downloading and diffing · 2/6 0 findings $0.00 so far
HomeReleasesv2.1.281entry #196

Claude Code v2.1.281 ·

Self-hosted runner: gh routing by path, staged files as args, subagent prompt inlining

The self-hosted runner now routes GitHub calls by path, passes staged files as arguments and can inline subagent prompts

You'll notice Improvements
JSON All of v2.1.281
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release

Unclear The finding does not say how a reader starts the self-hosted runner or what inlining the subagent prompt changes in a session.

What

The self-hosted runner, which starts Claude Code sessions as child processes, changed how it sets each one up:

  • ghRoutePath and ghRouteBasePath replace the old ghShimDir folder for sending GitHub requests along a set route.
  • stagedFileArgs holds files the server provides (agent_files and claude_code_args), which are added to the child's command line.
  • subagentPromptInline is passed to the child session. A subagent is a helper Claude that the main session starts for a side task.

The runner now prints a warning, "governed git: the session's PATH changed after the GitHub API route was set up", when the session's PATH (the list of folders the system searches for programs) changes after that route is in place. The "represent_failed" telemetry now uses the renamed route objects.

Why

If you run sessions through the self-hosted runner, the new warning tells you when a later PATH change may stop GitHub requests from going through the route that was set up.

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 doubtThe finding does not say how a reader starts the self-hosted runner or what inlining the subagent prompt changes in a session.

See this entry in the whole of v2.1.281 →

Feedback