{"version":"2.1.287","anchor":"self-hosted-runner-accepts-startupcommandphases","canonical_anchor":"self-hosted-runner-accepts-startupcommandphases","heading":"Self-hosted runner passes startup command phases to its first session","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/self-hosted-runner-accepts-startupcommandphases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Self-hosted runner passes startup command phases to its first session\n\nThe self-hosted runner now reads its startup command phases once and hands them to the first session it starts\n\n**Unclear.** It is not clear what the startup command phases do, or how a user would set them.\n\n**What**\n\nA self-hosted runner is a copy of Claude Code that you run on your own machine to carry out sessions, where a session is one continuous piece of work with Claude. The runner now reads a set of startup command phases from its configuration a single time and passes them to the first session it starts. Later sessions do not receive them again.\n\n**Why**\n\nThis is internal to the runner. In practice, any startup command phases apply only to the first session a runner starts.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}