{"version":"2.1.274","anchor":"self-hosted-runner-inaccessible-context-source-repos-are-sk","canonical_anchor":"self-hosted-runner-inaccessible-context-source-repos-are-sk","heading":"Self-hosted runner: inaccessible context-source repos are skipped instead of failing the whole clone","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/self-hosted-runner-inaccessible-context-source-repos-are-sk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Self-hosted runner: inaccessible context-source repos are skipped instead of failing the whole clone\n\nSelf-hosted runner now skips context-source repos it can't access instead of failing the whole clone\n\n**What**\n\nWhen a self-hosted runner (the `claude runner` binary used to run hosted or CI-style pools of sessions) prepares context sources for a session, it used to fail the whole clone if one repo couldn't be reached. Now, if a repo that isn't a work repo (it has no `push_targets` entry) can't be accessed through the git mount or proxy because of an authentication or permission problem, the runner logs a warning, records the skip as `context_source_access_denied`, and shows a step message telling the user to check their GitHub connection or ask an admin to check org access.\n\n**Why**\n\nThis keeps one inaccessible repo from blocking an entire session's setup, and it gives users a clear next step (check GitHub access, or ask an admin) instead of an opaque failure.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}