docs(spec): unified agent panel 2c implementation plan#207
Merged
Conversation
BunsDev
marked this pull request as ready for review
July 18, 2026 13:21
Contributor
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Description
Docs-only. The 2c implementation plan for the unified agent panel —
specs/castcodes-unified-agent-panel/PLAN-2c.md. Continues the Phase 2 design (#204); builds on 2a (#205) + 2b (#206).2c scope: route the panel composer by conversation backend — CLI → terminal PTY (2b), Coven daemon →
cast_agentstream_agent_eventsstreamed into the same transcript — and populate the list with live daemon sessions.Two Phase-1/2 unknowns resolved by code survey and recorded in the plan:
launch_daemon_sessioncarries the prompt in thePOST /api/v1/sessionslaunch body withlaunchMode:"stream"; no stdin user-frame needed. Each submit is one launch (session-per-turn); multi-turn context continuity is out of scope.bind_livehas no production caller (CLI auto-binds on first event); daemon conversations get a newConversationBinding::LiveDaemonand a directChatModel::append_entrypath (daemon events aren'tCLIAgentEvents).6 TDD tasks; the async stream consumer explicitly mirrors the shipped
ai_assistantpanel rather than inventing a warpui async primitive.Linked Issue
Continues the reconciliation roadmap (design #204; 2a #205; 2b #206; Phase 1 #201). No separate tracking issue, per the #204 precedent.
Testing
./script/check_ai_attribution+./script/check_rebrandpass../script/run(n/a — plan document).Agent Mode