{"version":"2.1.247","anchor":"programmatic-prompt-submission-gains-origin-and-wait-which-h","canonical_anchor":"programmatic-prompt-submission-gains-origin-and-wait-which-h","heading":"Programmatic prompt submission gains origin and wait, which hooks cannot forge","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/programmatic-prompt-submission-gains-origin-and-wait-which-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Programmatic prompt submission gains origin and wait, which hooks cannot forge\n\nHooks can see where a prompt came from and whether it queues, and cannot fake either.\n\n**What**\n\nPlugin hooks that see a prompt submission now receive two extra fields: `origin`, saying where the prompt came from, and `wait`, saying whether it queues behind the turn in progress. New rules reject any hook answer that invents an origin the engine did not set, changes the one it was given, or sets or changes `wait`. This whole surface exists only when the JavaScript plugin hooks rollout is enabled, and its in-build fallback is off.\n\n**Details**\n\n- The existing rule against a hook rewriting the prompt text still applies alongside the two new ones.\n- Controlled by `tengu_plugin_hooks_modules`, which falls back to false in this build, so it is off unless server configuration turns it on.\n\n**Evidence**\n\n`a wait the engine did not set (whether the prompt waits its turn is the user's; a hook carries it as received)`\n\n- Area: Hooks\n- Names: `origin`, `wait`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}