{"version":"2.1.296","anchor":"self-hosted-runner-error-hint-for-lock-to-account-id","canonical_anchor":"self-hosted-runner-error-hint-for-lock-to-account-id","heading":"Clearer hint for self-hosted runner account lock errors","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/self-hosted-runner-error-hint-for-lock-to-account-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Clearer hint for self-hosted runner account lock errors\n\nSelf-hosted runner errors about lock_to_account_id now point to --lock-to-account and say the value must be an organization member\n\n**What**\n\nA self-hosted runner is a machine you run yourself to host work for Claude Code. Errors that mention `lock_to_account_id` now come with a hint that this value is set with `--lock-to-account` or `SELF_HOSTED_RUNNER_LOCK_TO_ACCOUNT`. For errors about membership, the hint adds that the value must be the user_ or email address of a member of the organization that owns the environment.\n\n**Why**\n\nIf you run a self-hosted runner, the error now tells you which setting to fix and what kind of value it expects.\n\n- Area: Self-Hosted Runner\n- Names: `SELF_HOSTED_RUNNER_LOCK_TO_ACCOUNT`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}