{"version":"2.1.246","anchor":"headless-startup-logs-which-turn-loop-it-is-running","canonical_anchor":"headless-startup-logs-which-turn-loop-it-is-running","heading":"Headless startup logs which turn loop it is running","tier":"internal","area":"Headless Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/headless-startup-logs-which-turn-loop-it-is-running","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Headless startup logs which turn loop it is running\n\nHeadless runs log which turn loop they're using, making non-interactive problems easier to diagnose.\n\n**What**\n\nOn starting a print\/headless run, Claude Code now writes a debug line naming which of its two turn loops is active, which makes headless behaviour easier to triage.\n\n**Details**\n\n- Selected by the environment variable `CLAUDE_CODE_PRINT_ENGINE_LOOP`; the accessor returns its value when set and false otherwise, so the legacy per-turn path is the default.\n\n**Evidence**\n\n`[print] turns run on the engine session (createHeadlessSession)`\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}