Repository navigation
Conversation
An LLM chat client in Octane (chat-stream/octane/App.tsrx): a sidebar of conversations, a message list and a composer, with replies streamed a few tokens at a time and rendered as memoized Markdown. It commits like the Octane fixture of the chat-stream benchmark in the Octane repository: event handlers only set state, which the steps commit through window.__benchFlush, and each streamed chunk commits with flushSync. The corpus, Markdown parser, network stub and stylesheet are in shared/, and the build is in dist/octane.
✅ Deploy Preview for webkit-speedometer-preview ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
StreamReply1, StreamReply2 and StreamReply3 become a single StreamReplies step that sends the three prompts in turn in the first conversation, streaming each reply to completion before sending the next. Also fix the README's reference to chatStreamHelpers, which is named chatStreamTests.
Contributor
|
We have 2 very fast steps on my m4: => StreamReplies and TypePrompt should probably be bumped by 2x |
Build the Markdown views the way a design-system component catalog is built, as AssistantChat-Octane's catalog is: the app root provides theme, locale and layout contexts, each message a message context, and each reply streaming, typography and density contexts. Every block renders through a memoized chain (MarkdownBlock, the block's own component, Frame, Part), and each of them, the list items, inline spans and code lines reads the contexts it depends on. That exercises Octane's context dependency tracking across long chains of memoized ancestors, where AssistantChat-Octane's streaming steps spend much of their time. The streaming cursor's selector moves one level down, into the block frame.
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.
An LLM chat client in Octane (chat-stream/octane/App.tsrx): a sidebar of conversations, a message list and a composer, with replies streamed a few tokens at a time and rendered as memoized Markdown. It commits like the Octane fixture of the chat-stream benchmark in the Octane repository: event handlers only set state, which the steps commit through window.__benchFlush, and each streamed chunk commits with flushSync.
The corpus, Markdown parser, network stub and stylesheet are in shared/, and the build is in dist/octane.