{"version":"2.1.295","anchor":"git-fetch-gets-a-server-progress-stall-cap-env-var","canonical_anchor":"git-fetch-gets-a-server-progress-stall-cap-env-var","heading":"New setting caps how long a runner's git fetch waits on server progress","tier":"use","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/git-fetch-gets-a-server-progress-stall-cap-env-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New setting caps how long a runner's git fetch waits on server progress\n\n`CLAUDE_RUNNER_FETCH_SERVER_PROGRESS_CAP_MS` sets a time cap on server-side progress when a runner fetches a repository\n\n**Unclear.** It is not stated what happens when the cap is reached, or what the default cap is.\n\n**What**\n\nA runner is the process that prepares a repository for a session that does not run on your own machine. It uses git fetch to download the repository's history. A new environment variable, `CLAUDE_RUNNER_FETCH_SERVER_PROGRESS_CAP_MS`, sets a time cap on the server-side part of that fetch. An environment variable is a named value you set before starting a program. It accepts:\n\n- a positive whole number of milliseconds, kept between two minutes and thirty minutes\n\n- `0` or `off`, to turn the cap off\n\nAny other value is ignored and the default is used. Claude Code also now reads the \"remote: Enumerating objects: N\" lines the server prints while preparing a fetch.\n\n**Why**\n\nThis matters for cloud and self-hosted runners cloning slow or very large repositories. You can now change or remove the cap if a fetch needs more time.\n\n- Area: Self-Hosted Runners\n- Names: `CLAUDE_RUNNER_FETCH_SERVER_PROGRESS_CAP_MS`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}