Self-hosted sessions now start without a context repository that stays rate-limited

A 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.

If every such repository is rate-limited, setup still fails, with the rate-limit error as the reason.