{"version":"2.1.229","anchor":"injected-stream-json-user-messages-no-longer-count-as-human-","canonical_anchor":"injected-stream-json-user-messages-no-longer-count-as-human-","heading":"Injected stream-json user messages no longer count as human turns","tier":"notice","area":"Stream JSON","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/injected-stream-json-user-messages-no-longer-count-as-human-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Injected stream-json user messages no longer count as human turns\n\nProgrammatically injected messages are no longer counted as coming from a real person.\n\n**What**\n\nMessages pushed into a session programmatically are now marked and skipped by both the content transform and the check that stamps a turn as coming from a verified human relay, so an injected line cannot be attributed to a person. The injected line is also no longer given a trailing newline before it is parsed.\n\n**Evidence**\n\n`verifiedSlackHumanTurn`\n\n- Area: Stream JSON\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}