{"version":"2.1.295","anchor":"home-settings-seed-gate-now-admits-runner-children-and-keeps","canonical_anchor":"home-settings-seed-gate-now-admits-runner-children-and-keeps","heading":"Home settings can now be seeded in self-hosted runner sessions","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/home-settings-seed-gate-now-admits-runner-children-and-keeps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Home settings can now be seeded in self-hosted runner sessions\n\nSeeding of home settings now also runs for runner child sessions that declare an absolute `CLAUDE_CONFIG_DIR`, not only managed cloud workers\n\n**Unclear.** How a session comes to be treated as a runner child is not stated.\n\n**What**\n\nClaude Code has a worker that seeds your home settings, meaning it fills in settings files in the session's configuration folder. Before, it started only on a managed cloud worker, and any `CLAUDE_CONFIG_DIR` (the environment variable that moves Claude Code's configuration folder) stopped it.\n\nIt now starts for two kinds of session:\n\n- Managed sessions, which replace files in that folder that did not come from the seeding\n\n- Runner child sessions, which keep those files\n\nA runner child session must set `CLAUDE_CONFIG_DIR` to an absolute path, meaning a full path starting from the top of the file system. If the session is neither kind, or the variable is missing or not absolute, the worker does not start. The environment variable `CLAUDE_CODE_DISABLE_HOME_SETTINGS_SEED` controls switching the seeding off.\n\n**Why**\n\nSessions started by a self-hosted runner can now get seeded home settings, and files already in their configuration folder are left alone.\n\n- Area: Self-Hosted Runners\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}