T3 panels are connected before the first prompt - #733
Open
Anton-Horn wants to merge 1 commit into
Open
Anton-Horn wants to merge 1 commit into
Anton-Horn wants to merge 1 commit into
Conversation
Main now owns one orchestration.subscribeShell stream per running T3 harness and pushes full thread snapshots to every window, replacing the script that was injected into the guest page. Activity, titles and "connected" are known without a mounted T3 page. Prompts to a bound thread go through T3's orchestration API (startTurn), so cate agent send works with no page mounted. A connected fresh chat counts as able to take a prompt; its first prompt goes through the page composer, which creates the thread. T3 panels are named after the provider running the thread.
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.
Stacked on #732.
T3 panels now know they're connected before the first prompt. Main keeps one thread-shell stream per running T3 server and pushes snapshots to every window, replacing the script we injected into the T3 page.
Sending to a bound T3 thread goes through T3's API (startTurn), so no page has to be mounted. A fresh chat counts as ready and its first prompt goes through the composer, which creates the thread.
T3 panels are named after the provider running the thread. The e2e spec checks data-agent-connected instead of page globals.