{"version":"2.1.317","anchor":"cowork-cloud-init-frames-gain-client-thinking-and-flag-resta","canonical_anchor":"cowork-cloud-init-frames-gain-client-thinking-and-flag-resta","heading":"Cowork cloud workers report thinking settings when a session starts","tier":"internal","area":"Cowork","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/cowork-cloud-init-frames-gain-client-thinking-and-flag-resta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Cowork cloud workers report thinking settings when a session starts\n\nThe opening message in stream-json output gains client_thinking and flag_restate_noop fields for Cowork cloud workers, plus two new refusal reasons\n\n**What**\n\nWhen Claude Code runs with stream-json output, it starts by printing an opening message describing the session for the program that controls it. That message can now carry two more optional fields, both used only by Cowork cloud workers:\n\n- `client_thinking`, holding `max_thinking_tokens` and `thinking_display`\n\n- `flag_restate_noop`\n\nThe reasons a cloud session can give for not being served also gain two values: `computer_too_old` and `session_too_old`.\n\n**Why**\n\nProgrammers who build tools on top of Claude Code have new fields to read in that opening message, and two more refusal reasons to handle when a cloud session will not run.\n\n- Area: Cowork\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}