{"version":"2.1.281","anchor":"startup-now-passes-the-thinking-display-flag-early-remote-l","canonical_anchor":"startup-now-passes-the-thinking-display-flag-early-remote-l","heading":"Startup now passes the thinking-display flag, early remote link and headless cloud print mode downstream","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/startup-now-passes-the-thinking-display-flag-early-remote-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Startup now passes the thinking-display flag, early remote link and headless cloud print mode downstream\n\nStartup now hands more options to the session it prepares, and the --thinking-display value is read even when thinking is turned off\n\n**Unclear.** The finding does not say what `earlyRemoteLink` or `headlessCloudPrint` do for someone using Claude Code.\n\n**What**\n\nWhen Claude Code starts, it builds an internal record of the session it is about to run and passes that record on to the rest of the program. That record now carries four more values:\n\n- `thinkingDisplayFlag`, the value given to `--thinking-display`\n\n- `earlyRemoteLink`\n\n- `headlessCloudPrint`\n\n- `allowDangerouslySkipPermissions`\n\nThe `--thinking-display` value is also now worked out even when thinking is disabled, where before it was skipped in that case. A check on dynamic MCP configuration (MCP servers are outside programs that give Claude extra tools) now also accepts one more condition, but that condition is fixed to false in this build, so it never applies.\n\n**Why**\n\nIn practice, a `--thinking-display` value you pass is no longer dropped just because thinking is off at startup. The other new values are now available to later parts of the program instead of being lost after startup.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}