{"version":"2.1.239","anchor":"remote-workers-can-start-up-reporting-a-pending-permission-i","canonical_anchor":"remote-workers-can-start-up-reporting-a-pending-permission-i","heading":"Remote workers can start up reporting a pending permission, if three env vars are set","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-workers-can-start-up-reporting-a-pending-permission-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote workers can start up reporting a pending permission, if three env vars are set\n\nRemote workers can start up reporting a pending permission if you set three environment variables.\n\n**What**\n\nA remote worker's startup can report that it needs action, with details drawn from its stored state, instead of the usual idle status. It turns on only when `CLAUDE_CODE_HOLD_REPORT_PARK_AT_INIT`, `CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION` and `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` are all set.\n\n**Details**\n\n- The first of those three is read at the point the worker client is built and nowhere else in the build, and does not exist at all in 2.1.238, so it can only be turned on from outside the process.\n- The other two are written elsewhere in the product.\n- With the option off, startup reports `worker_status: \"idle\"` as before.\n\n**Evidence**\n\n`CLAUDE_CODE_HOLD_REPORT_PARK_AT_INIT`\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_HOLD_REPORT_PARK_AT_INIT`, `CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION`, `CLAUDE_CODE_RESUME_INTERRUPTED_TURN`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 4\/5"}