From d2695919f6c57dd00bb52e175e2af44a9064052b Mon Sep 17 00:00:00 2001 From: snakajima Date: Mon, 28 Sep 2026 20:00:22 +0900 Subject: [PATCH] docs: a host doesn't ask to go on after a step that waits for the user The sequences section said the host asks the model to go on mid-sequence without the waitsForUser exception (CodeRabbit found the same sentence in receptron/MulmoChat#234). Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/plugin-development-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/plugin-development-guide.md b/docs/plugin-development-guide.md index 28d535d..84bcda2 100644 --- a/docs/plugin-development-guide.md +++ b/docs/plugin-development-guide.md @@ -172,8 +172,8 @@ interface ToolContext { A tool that shows a sequence one step per call, such as slides or a story's panels, returns `sequence` on each result: where the sequence is and the call for the next step. A host that supports sequences asks the model once to go on when it ends a reply mid-sequence, which models -do. Set `sequence: null` for a step that wasn't shown, and leave it out on results that aren't -steps. A step that waits for the user sets `waitsForUser`, and the plugin holds a later step until +do, but not after a step that waits for the user (`waitsForUser`). Set `sequence: null` for a +step that wasn't shown, and leave it out on results that aren't steps. A step that waits for the user sets `waitsForUser`, and the plugin holds a later step until `context.userSpokeAt` is after the waiting step appeared. ```typescript