{"version":"2.1.309","anchor":"ccr-worker-holds-the-first-idle-report-while-inbound-work-is","canonical_anchor":"ccr-worker-holds-the-first-idle-report-while-inbound-work-is","heading":"Remote sessions wait before first reporting idle while work is queued","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/ccr-worker-holds-the-first-idle-report-while-inbound-work-is","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote sessions wait before first reporting idle while work is queued\n\nIn remote sessions, the first \"idle\" status can now wait, up to a time limit, while incoming messages are still queued\n\n**What**\n\nIn a remote session, Claude Code reports to the server whether it is busy or idle. When a setting is turned on and incoming messages are waiting, the first \"idle\" report is now held back and is sent after a time limit. Other changes:\n\n- Session details that fail to send are queued to be sent again.\n\n- Self-hosted runners have a new environment variable, `CLAUDE_RUNNER_DISABLE_TURN_BEGAN_BEFORE_INIT`.\n\n- In one mode, the runner removes setting sources from the arguments it starts Claude Code with.\n\n**Why**\n\nThis stops a remote session from reporting idle too early, when there is still work waiting for it.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}