Customize display and add chat orchestration - #1
Merged
Conversation
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.
What changed
chat_*MCP tools so T3 chats can spawn, inspect, prompt, wait for, and manage other T3 chatsWhy
These changes make the app feel cleaner and more personal while bringing T3 chats closer to the orchestration workflow available with subagents. Prompt queueing also prevents follow-up messages from steering an active generation by default.
User impact
Users can customize the app's appearance, manage persistent visible chats through MCP tools, and safely queue follow-up prompts without interrupting the current response.
Validation
vp fmton every changed filevp lint --report-unused-disable-directivespassedCannot read properties of undefined (reading 'config')/Vitest failed to find the current suite); no test body failures occurred