{"version":"2.1.271","anchor":"turn-scoped-tracking-for-plugin-originated-prompt-submission","canonical_anchor":"turn-scoped-tracking-for-plugin-originated-prompt-submission","heading":"Turn tracking for plugin prompt submissions now uses the real turn id","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/turn-scoped-tracking-for-plugin-originated-prompt-submission","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Turn tracking for plugin prompt submissions now uses the real turn id\n\nPlugin-submitted prompts are tagged to the current turn, and turn-complete reporting now uses the real turn id instead of a freshly generated one\n\n**What**\n\n- New turn-lifecycle bookkeeping marks prompt UUIDs against `turn.start`\/`turn.complete` events and prunes stale entries. The plugin API for submitting a prompt now uses this bookkeeping when submitting, tagging the submission to the current turn only if its origin is undefined or `session.start`.\n\n- The handler that reports a completed agent turn to telemetry\/session state now forwards the actual `turnId` from the event, rather than generating a new id at report time.\n\n**Why**\n\nThis makes turn tracking for plugin-submitted prompts, and the turn id used in turn-complete reporting, more accurate and consistent instead of relying on freshly generated ids.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}