{"version":"2.1.286","anchor":"mid-turn-user-messages-lose-the-explanatory-suffix-plugin-m","canonical_anchor":"mid-turn-user-messages-lose-the-explanatory-suffix-plugin-m","heading":"Messages sent mid-turn, including some from plugins, are framed in one way","tier":"internal","area":"Message Queue","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mid-turn-user-messages-lose-the-explanatory-suffix-plugin-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Messages sent mid-turn, including some from plugins, are framed in one way\n\nMessages you send while Claude is working are now wrapped by one shared step, which plugin messages marked as yours also use\n\n**Unclear.** Whether the wording the model actually sees for mid-turn messages changed is not settled.\n\n**What**\n\nWhen you send a message while Claude is still working on a reply, Claude Code wraps it with extra text so the model knows it arrived mid-turn. That wrapping is now done by one shared step instead of a template written inline, for both your own messages and automatic continuation messages.\n\nMessages from a plugin that are marked as coming from the user now go through the same step, instead of being wrapped as plugin messages.\n\n**Why**\n\nThis changes how queued mid-turn messages are presented to the model, and makes plugin messages sent on your behalf look like your own.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}