Repository navigation
fix: start a fresh demo session on page refresh - #36
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Kinfe123
marked this pull request as ready for review
October 23, 2026 06:10
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
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.
Refreshing the demo currently reopens the session saved in its cookie and URL. Each full page reload now starts a fresh session, including reloads of
?session=...URLs, and updates the displayed ID, browser URL, and terminal command together.The browser creates one random capability per document and shares its bootstrap request across effect remounts. Retries reuse that capability; reconnects fetch configuration for the selected session. Opening a session link and selecting a sidebar thread still resume existing conversations. Earlier threads, terminal attachments, connected folders, creation limits, and the explicit shared-demo mode remain intact. The page and demo documentation explain these behaviors.
Validation:
No production deployment or live provider-account verification was performed. Refreshes consume the existing session-creation allowance.