Skip to content

docs: a host doesn't ask to go on after a step that waits for the user #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snakajima merged 1 commit into from
Sep 28, 2026
Merged

docs: a host doesn't ask to go on after a step that waits for the user #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/plugin-development-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading