Repository navigation
feat(mcp): add an in-chat page editor - #249
Open
massimoalbarello wants to merge 1 commit into
Open
massimoalbarello wants to merge 1 commit into
massimoalbarello wants to merge 1 commit into
Conversation
This branch has not been 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.
Why
Context Use already stores versioned knowledge pages through MCP, but users cannot inspect or manage those pages in the conversation where they were captured. Saving useful conversation context should leave a page people can see and maintain.
How
Attach a self-contained MCP Apps view to the existing page tools. Users can browse, read, create, edit, and archive pages through the host's authenticated bridge, with revision conflicts, public-page confirmation, and archive blockers preserved.
The app uses Markdown with a rendered preview; attachments appear as labels. Page snapshots travel in UI-only result metadata, while existing tool text and structured outputs stay compact.