Add persistent MCP artifact views - #41
Merged
Merged
Conversation
nicosuave
added this pull request to stack #43
October 4, 2026 03:13
nicosuave
marked this pull request as ready for review
October 4, 2026 03:16
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.
Adds persistent library and thread views, authenticated revision deep links, permission-filtered mentions, and an editor for owned artifact files. Selected model context, host capability checks, explicit tool visibility, and optional preview suppression preserve compatible working state across supported MCP hosts.
The thread view restores its explicitly attached artifact through fresh server authorization. File saves use host-managed opaque resources and ETag conflicts; ordinary TSX remains with the host viewer.