Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.271 ·

Self-hosted runner session start now probes the session config dir before proceeding

Self-hosted runner sessions now check the config directory's health before starting, flagging stuck NFS/CSI mounts

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

When a self-hosted runner starts a new session, it now runs an explicit check to see if the session's config directory is reachable, logging [runner:stuck] session config dir check ... (check NFS/CSI mount health) if something's wrong. This check happens before the runner sets up the rest of the session's internal state. If the check hits an unrecoverable error, a new failure flag is set that causes later cleanup steps to be skipped.

Why

This helps diagnose sessions that hang because of a broken or slow network filesystem mount (NFS or CSI), pointing operators at the mount as the likely cause instead of leaving the session silently stuck.

See this entry in the whole of v2.1.271 →

Feedback