Self-hosted runners on Windows now require you to set a base directory instead of failing oddly.
What's wrong with this entry?
Starting a self-hosted runner on Windows without a base directory now fails with an explanatory error instead of silently falling back to a POSIX container path that does not exist there. Set --base-dir or the SELF_HOSTED_RUNNER_BASE_DIR environment variable to the directory repositories should be checked out under. The runner also now passes CLAUDE_RUNNER_CLIENT_PLATFORM into spawned runner environments, parsed as client_platform.
- Passing
--base-dirrecords where the value came from.
claude ... --base-dir C:\runner\repos--base-dir (or SELF_HOSTED_RUNNER_BASE_DIR) is required on Windows: the built-in default is a POSIX container path that does not apply there. Pass the directory that repositories should be checked out under.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
Self-hosted runner checks its base directory before starting work
Both mention base self hosted runner
-
v2.1.224
Runner management tools require a first-party login and say so
Both mention base self hosted runner
-
v2.1.248
--client-labelflag on the runner commandBoth mention self hosted runner client