{"version":"2.1.236","anchor":"plugin-eval-reference-corrected-a-prompt-is-always-required","canonical_anchor":"plugin-eval-reference-corrected-a-prompt-is-always-required","heading":"Plugin eval reference corrected: a prompt is always required","tier":"notice","area":"Documentation","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/plugin-eval-reference-corrected-a-prompt-is-always-required","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Plugin eval reference corrected: a prompt is always required\n\nThe plugin eval docs now correctly say a prompt is always required.\n\n**What**\n\nThe bundled plugin eval reference previously said a case was valid with either a prompt or a session history file. It now states a prompt is always required, and that with a history file the prompt is the resumed session's next user turn. The rest of the document is unchanged.\n\n**Details**\n\n- The same document still notes that `plugin eval` is in early access.\n\n**Evidence**\n\n`` `execution.prompt` (or a `prompt.md` body) is always required ``\n\n- Area: Documentation\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}