feat(v2): make agent 1:1 "talk to" v2-correct and reachable from Your Team#462
Merged
Conversation
… Team The hero-path "install → talk to it" happy path already lands a new user in a coached 1:1 agent-room. Two gaps left that 1:1 surface inconsistent for returning users: - AgentsHub "Talk to"/"Message" handlers hardcoded the v1 /pods/* routes, so clicking them inside the v2 shell ejected the user into the legacy ChatRoom. Now branch on isV2Context, mirroring the install handoff. - The Your Team page only navigated to the group project pod, so the 1:1 relationship formed at install had no entry point. Added a "Talk to" button that opens the agent-room directly (with pending + error states). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Closes the "talk to your agent 1:1" gaps in the v2 hero path. The happy path (install → coached 1:1 agent-room) already works; this makes the 1:1 surface correct and reachable for returning users.
AgentsHub"Talk to"/"Message" handlers branched to the v1/pods/*routes, ejecting v2 users into the legacy ChatRoom. Now branch onisV2Context, mirroring the existing install handoff (Sprint B2)..v2-root button.Xspecificity scoping.Deferred (separate focused changes): branded install/handoff failure feedback (needs an info/success notification channel, not the red error banner — belongs with the raw-
alert()cleanup), and per-agent first-message chips (polish).Test plan
/v2/pods/:id(not/pods/agent-room/:id)