Repository navigation
feat: dogfood React Chat Interrupts in the native example - #1259
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The canonical Chat Interrupt Panel example now offers a native React preview. A user can request a demo flight booking, review the saved approval, and confirm or cancel it using the existing React chat components and Python graph.
The example owns a fresh conversation and validates saved transcript, tool, interrupt, and checkpoint evidence before enabling a fixed decision. Changed or ambiguous evidence blocks further commands; stopping or replacing a conversation revokes its approval. These checks protect observed state but do not provide an atomic checkpoint precondition against another client. The title-generation model is marked non-streaming so its metadata cannot enter the conversation transcript.
The preview includes Docs, Code, and Run integration, generated public guidance, and private fixtures executing the actual compiled graph with deterministic providers and real checkpoints. Private fixtures and proof routes are excluded from assembled deployment assets. Packages remain private source-built candidates.
Validation: fresh scoped tests and strict types; 23 native unit suites (1,155 tests); 23 installed native browser suites; 291 production website browser tests with four expected skips; all 64 frontend builds assembled with HTTP checks for all 23 native routes; isolated package-consumer checks; desktop and mobile visual inspection. The new native example covers both scalar decisions, repeated approvals, saved-state conflicts, failed requests, and stop/reset behavior.