{"version":"2.1.310","anchor":"runner-prep-git-and-hook-repo-preparation-scheduled-with-pe","canonical_anchor":"runner-prep-git-and-hook-repo-preparation-scheduled-with-pe","heading":"Self-hosted runners prepare session repositories through a scheduler","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/runner-prep-git-and-hook-repo-preparation-scheduled-with-pe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Self-hosted runners prepare session repositories through a scheduler\n\nSelf-hosted runners now prepare repositories through a scheduler with separate hook and git slots, replacing a simple one-after-another loop\n\n**Unclear.** Whether more than one repository is actually prepared at the same time in practice.\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. When it sets up the repositories (code projects) for a session, it used to prepare them one after another. It now uses a scheduler with separate slots for two kinds of work:\n\n- hook work: 2 slots by default (a hook is a script set up to run at a certain point)\n\n- git work: 1 slot by default\n\nPreparing each repository is now split into steps for starting, claiming a slot and finishing. Clone progress messages are shown one at a time.\n\n**Why**\n\nStarting a session with several repositories on a self-hosted runner may get faster.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}