{"version":"2.1.310","anchor":"runner-reports-capabilities-at-registration-context-repos-p","canonical_anchor":"runner-reports-capabilities-at-registration-context-repos-p","heading":"Self-hosted runners report what they can do, and prepare repositories in parallel","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/runner-reports-capabilities-at-registration-context-repos-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Self-hosted runners report what they can do, and prepare repositories in parallel\n\nSelf-hosted runners now send and log a list of capabilities when they register, and can prepare repositories at the same time\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. Two changes:\n\n- When a runner registers with the server, it now sends a list of its capabilities and logs it as '[runner] capabilities reported to the server:'. The list only has entries when the runner is started with `--capacity 1` and no debug token folder is set.\n\n- Repositories a session needs for context can now be prepared at the same time instead of one after another.\n\n**Why**\n\nThis changes how self-hosted runners register and how quickly they can get repositories ready.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}