posit-dev / posit-dev/shinychat
Support multiple markdown streams inside a single assistant message
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 28
- Avg merge
- 23h 44m
- Merged PRs (30d)
- 50
Description
There are key moments in the chat lifecycle where we know for certain that future streams will no longer update the previous content. For example, during the tool call loop, when we receive a tool request, or a tool result, we could stop the current stream and start a new stream.
The advantage of this approach is that it would provide a light-weight way to prevent stream updates — e.g. in messages after a tool request/result — from causing previous content from re-rendering in the browser. This is particularly important with #52.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the chat lifecycle and tool-call loop described here, then read issue #52 for the browser re-rendering problem this should address. Done means one assistant message can contain separate markdown streams, with later tool-request or tool-result streams no longer updating or re-rendering earlier content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100