{"version":"2.1.242","anchor":"plugins-can-queue-a-prompt-into-the-conversation","canonical_anchor":"plugins-can-queue-a-prompt-into-the-conversation","heading":"Plugins can queue a prompt into the conversation","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plugins-can-queue-a-prompt-into-the-conversation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Plugins can queue a prompt into the conversation\n\nPlugins can drop a prompt into your conversation, labelled as theirs and rate-limited.\n\n**What**\n\n`$.prompt.submit` lets a plugin put a prompt into the running conversation, tagged as coming from that plugin rather than from you. Text starting with `\/` is refused so a plugin cannot fire a slash command in your name, and attachments are refused. Each plugin has a per-session submission count and a minimum gap between its prompts.\n\n**Details**\n\n- Requires an interactive session attached to the process. Headless `-p` runs and the SDK reject the call.\n- The submitted prompt is marked with the plugin's name as its origin.\n\n**Evidence**\n\n`$.prompt.submit submits a prompt to the model; a text beginning with \/ would run a command as the user`\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}