{"version":"2.1.299","anchor":"self-hosted-runner-setup-guide-adds-git-https-credential-gui","canonical_anchor":"self-hosted-runner-setup-guide-adds-git-https-credential-gui","heading":"Self-hosted runner setup now explains git sign-in limits and how to recover","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/self-hosted-runner-setup-guide-adds-git-https-credential-gui","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Self-hosted runner setup now explains git sign-in limits and how to recover\n\nThe self-hosted runner setup guide now warns that repositories must clone over HTTPS without a sign-in prompt and explains how to recover\n\n**What**\n\nThe setup guide for a self-hosted runner (a machine you provide that runs Claude Code sessions) has a new step before it sends you to \/code. It explains that the runner copies your repository over HTTPS and cannot show a sign-in prompt, so an SSH key alone is not enough. The repository must be public or otherwise copyable without being asked to sign in.\n\nIt also gives a recovery procedure for when git fails with \"could not read Username\":\n\n- archive the failed session\n\n- wait for the pool of waiting work to empty\n\n- start the runner again\n\n**Why**\n\nWithout these steps, a failed session can keep being handed to each new runner, which then fails the same way. Following the recovery procedure breaks that loop.\n\n- Area: Self-Hosted Runner\n- Names: `\/code`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}