{"version":"2.1.323","anchor":"runner-setup-script-step-and-batched-deferred-events","canonical_anchor":"runner-setup-script-step-and-batched-deferred-events","heading":"Self-hosted runners can run a setup script sent by the server","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/runner-setup-script-step-and-batched-deferred-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Self-hosted runners can run a setup script sent by the server\n\nSelf-hosted runners now run a setup script sent by the server and report it as its own step, except during code reviews\n\n**What**\n\nA self-hosted runner is a machine you run that does Claude Code work on the server's behalf. It now runs a setup script when the server sends one, and lists it as a setup step alongside provisioning, cloning and starting Claude Code. A code review does not run the script, and the runner warns that it was ignored. Delayed step events can now also be sent together in batches.\n\n**Why**\n\nSelf-hosted runners gain a way to prepare the machine before work starts.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}