{"version":"2.1.281","anchor":"remote-session-humanturn-marker-skips-messages-matching-a-ne","canonical_anchor":"remote-session-humanturn-marker-skips-messages-matching-a-ne","heading":"Messages made only of wrapped blocks no longer count as human turns","tier":"internal","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-session-humanturn-marker-skips-messages-matching-a-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Messages made only of wrapped blocks no longer count as human turns\n\nThe humanTurn marker is no longer added to messages whose text consists entirely of wrapped blocks\n\n**Unclear.** The finding does not say what text the new check matches or what the `humanTurn` marker is used for.\n\n**What**\n\nClaude Code can mark a message it sends with `humanTurn: true`, which flags the message as a real turn typed by a person. This applies to prompt messages from certain origins, such as remote sessions. The marker is now withheld when the message text consists entirely of wrapped blocks. The text is checked after joining it and trimming leading whitespace.\n\nThe existing on\/off check still has to pass as well. That check sits behind the `tengu_parsed_willow` flag and can be overridden with the `CLAUDE_CODE_PARSED_WILLOW` environment variable. Its built-in fallback applies the check. Nothing has been read about this flag yet.\n\n**Why**\n\nMessages that carry only wrapped, automatically added content stop being counted as turns a person actually took. This can affect how a session tells your own messages apart from generated ones.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}