{"version":"2.1.311","anchor":"self-hosted-runner-skips-context-repos-that-stay-rate-limite","canonical_anchor":"self-hosted-runner-skips-context-repos-that-stay-rate-limite","heading":"Self-hosted sessions now start without a context repository that stays rate-limited","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/self-hosted-runner-skips-context-repos-that-stay-rate-limite","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Self-hosted sessions now start without a context repository that stays rate-limited\n\nA self-hosted session no longer fails when an extra context repository keeps asking it to wait; it starts without that repository and warns\n\n**What**\n\nA self-hosted runner, which runs Claude Code sessions on your own machines, can pull in extra repositories as background material for a session. If one of these keeps telling it to try again later after several attempts, the runner now skips it with a warning and starts the session without it. Before, the whole setup failed. The skipped repository is tried again the next time the session starts.\n\nIf every such repository is rate-limited, setup still fails, with the rate-limit error as the reason.\n\n**Why**\n\nOne busy extra repository no longer stops a self-hosted session from starting.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}