{"version":"2.1.317","anchor":"plugin-prompt-display-field-in-session-events","canonical_anchor":"plugin-prompt-display-field-in-session-events","heading":"Session messages sent by a plugin can carry the plugin's name and prompt","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-prompt-display-field-in-session-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Session messages sent by a plugin can carry the plugin's name and prompt\n\nMessages a plugin sends can now carry a plugin_prompt field with the plugin's name and text, so apps can show them under the plugin\n\n**Unclear.** It is unclear whether any plugin currently causes this field to be sent.\n\n**What**\n\nSome programs embed Claude Code and show its conversation in their own window. For a message that a plugin sent, these programs can now receive a `plugin_prompt` field. It holds the plugin's name and the text of its prompt or command, so the program can show that message under the plugin's name. A plugin is an add-on that extends Claude Code.\n\n**Why**\n\nPrograms built on Claude Code can show prompts that plugins send more cleanly, labelled with the plugin they came from.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}