Skip to content

Roadmap overhaul: milestone-aligned plans with voice-first P0 and 9 new plan documents#710

Open
kovtcharov wants to merge 16 commits intomainfrom
kalin/roadmap-plans-2026-04
Open

Roadmap overhaul: milestone-aligned plans with voice-first P0 and 9 new plan documents#710
kovtcharov wants to merge 16 commits intomainfrom
kalin/roadmap-plans-2026-04

Conversation

@kovtcharov
Copy link
Copy Markdown
Collaborator

Summary

Key Decisions Captured

New Plan Documents

Document Lines Covers
security-model.md 805 Threat model, guardrails, audit trail, credential vault, messaging security
setup-wizard.md 670 First-run onboarding, system scanner, model download
email-calendar-integration.md 549 Email triage, calendar, Outlook, meeting notes with diarization
skill-format.md 738 SKILL.md spec, permission model, security tiers, OpenClaw compatibility
autonomy-engine.md 367 Heartbeat scheduler, event hooks, system tray, background service
messaging-integrations-plan.md 363 Signal, Discord, Slack, Telegram adapter architecture
oem-bundling.md 153 Hardware SKU pre-config, model packages, distribution

Updated Documents

Document Change
roadmap.mdx Complete rewrite — v0.1.0 through v0.25.0 with timeline, issue refs, shipped history
agent-ui.md Comprehensive plan (Phases A-D) with all new decisions
agent-ui.mdx Summary page updated for docs site
agent-hub.mdx ChatAgent → GaiaAgent
docs.json plans/chat-ui → plans/agent-ui

Test plan

…e-first P0

Rewrite roadmap.mdx to reflect current milestone structure (v0.17.2 through v0.25.0)
with shipped release history (v0.1.0 through v0.16.0) and timeline diagram.

New plan documents:
- agent-ui.md: Comprehensive Agent UI plan (Phases A-D) with GaiaAgent rename,
  configuration + observability dashboards, personality recipes, dynamic tool loading,
  no-compaction memory design, and MCP-first email/calendar
- security-model.md: Unified security architecture across all milestones
- autonomy-engine.md: Heartbeat scheduler, event hooks, system tray, background service
- setup-wizard.md: First-run onboarding, system scanner, model download
- messaging-integrations-plan.md: Signal/Discord/Slack/Telegram adapter architecture
- email-calendar-integration.md: Email triage, calendar, Outlook, meeting notes with
  speaker diarization, MCP-first approach
- oem-bundling.md: Hardware SKU pre-configuration for OEM partners
- skill-format.md: SKILL.md specification with permission model and security tiers

Updated existing:
- agent-ui.mdx: Summary page for docs site reflecting all decisions
- agent-hub.mdx: ChatAgent -> GaiaAgent rename
- docs.json: plans/chat-ui -> plans/agent-ui

Key decisions captured:
- Voice-first is P0 enabling technology (#702)
- Home Assistant integration is P0 (#705)
- No context compaction — memory + RAG handles long conversations
- ChatAgent renamed to GaiaAgent in v0.20.0 (#696)
- Signal is Phase 1 messaging priority (privacy-first, #693)
- MCP servers primary for email/calendar (not browser automation)
- Two Agent UI dashboards: configuration + observability
- Small business on Strix Halo as target demographic (#708)
@github-actions github-actions bot added the documentation Documentation changes label Apr 1, 2026
- Convert 7 plan .md files to .mdx with Mintlify frontmatter
- Remove .md duplicates (keep .mdx only)
- Organize plans in docs.json into 4 groups: Agent UI, Ecosystem,
  Infrastructure, Agents
- Add "Roadmap & Plans" section to CLAUDE.md with plan index and
  key architectural decisions
- Update README.md: add Agent UI and Roadmap to capabilities/docs
- Update cpp/README.md: add roadmap and Agent UI plan references
- Update copyright to 2024-2026
@github-actions github-actions bot added devops DevOps/infrastructure changes cpp labels Apr 1, 2026
### Competitive Positioning

- **GAIA Installer Plan** - Lightweight installer system (one-liner install, winget, `gaia update`, etc.)
| Feature | ChatGPT Desktop | Ollama + Open WebUI | GAIA |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this intentional to name other services?

- Remove competitive positioning, market analysis, and strategic context
  from security-model, email-calendar, skill-format, agent-hub, agent-ui
- Replace "strategic priority" with technical priority levels
- Replace "value proposition" with "key features"
- Remove OpenClaw stats and competitor references (keep technical
  compatibility references only)
- Remove marketing budget and competition prize references from agent-hub
- Rewrite agent-hub.mdx from 682 to 425 lines — removed competitions,
  prizes, budgets, marketing goals, talent pipeline, strategic framing
- Keep: agent registry, Arena architecture, manifest format, CLI, quality
  gates, developer profiles, CI/CD pipeline, seed agents, implementation phases
- Clean remaining "strategic" references in email-calendar and oem-bundling
- Zero business/marketing jargon remaining across all plan documents
…ments

- Remove "strategy", "value proposition", "Strategy doc requirement"
- Fix all .md → .mdx cross-references (20 instances across 6 files)
- Fix broken section reference (security-model Section 4.4 → Section 7)
- Zero business/marketing jargon remaining
- Zero broken cross-references remaining
…ments

- Signal is now Phase 1 (first adapter built), not Telegram
- Email/calendar provider tables: MCP is Primary column, Browser is Fallback
- Remove duplicate Phase 1.5 section from email-calendar plan
- Fix orphaned code fence in skill-format.mdx that broke rendering
The SKILL.md full schema example had an unclosed yaml code fence
followed by markdown body content that was meant to be part of the
example but rendered as actual markdown. Trimmed the example to
close the fence properly. Fence count now even (44).
…pyright

- Replace 6 ChatSDK references with AgentSDK in messaging plan (v0.23.0
  is post-v0.20.0 rename)
- Add Signal adapter to architecture diagram as P0 priority
- Update copyright year from 2024-2025 to 2024-2026 in skill-format example
…inks

- Replace `<8 GB` with `&lt;8 GB` in setup-wizard.mdx:142 to fix MDX
  JSX parse error caught by `mintlify validate`
- Remove undeployed `https://amd-gaia.ai/roadmap` links from README.md
  and cpp/README.md that caused HTTP 404 in the doc link checker
…eferences

- Replace Qwen3-Coder-30B with Qwen3.5-35B across 7 plan files
- Fix Lemonade health-check port 8399 → 8000 in setup-wizard.mdx
- Remove stale source line numbers from security-model.mdx
- Annotate historical ChatSDK reference in roadmap.mdx
- Update CUA target date to v0.21.0 milestone
- Add issue cross-refs #691/#692 to skill-format.mdx
- Add Section 14 with #635/#693 cross-refs to messaging-integrations-plan.mdx
- Replace all SDK.md references with correct .mdx paths (llm-client, api-agent,
  database-mixin, file-change-handler, test-utilities, mcp-agent, vlm-client)
- Fix docs/talk.md → docs/guides/talk.mdx in talk-sdk.mdx
- Fix "Chat SDK" → "Agent SDK" docstring in orchestrator.mdx
- Update plugin-registry.mdx Last Updated date to April 2026
- Fix docker-containers.mdx port table: 8000=Lemonade, 8080=GAIA API
- Remove conflicting --port 8080 flag from lemonade-server command
…tron spec

- Add GaiaAgent rename notice (v0.20.0, #696) to chat-agent.mdx
- Update Last Updated dates from December 2025 to April 2026 in agent-base.mdx
  and component-status.mdx
- Fix mcpPort default 8080 → 8765 in electron-integration.mdx (matches
  src/gaia/electron/src/services/mcp-client.js:17)
- Rename 'Chat SDK' → 'Agent SDK' links in llm.mdx, rag.mdx, dev.mdx
- Fix 'Qwen3-Coder' → 'Qwen3.5-35B' in docker.mdx troubleshooting text
@github-actions github-actions bot added mcp MCP integration changes llm LLM backend changes labels Apr 1, 2026
…n specs

- api-server.mdx: Change custom port example 8000 → 9090 (avoids Lemonade collision)
- chat-agent.mdx: Add missing mixins FileIOToolsMixin, VLMToolsMixin,
  ScreenshotToolsMixin, SDToolsMixin, MCPClientMixin to Inherits and class def
- file-change-handler.mdx: Update 'Extract from ChatAgent' section to reflect
  that extraction to src/gaia/utils/file_watcher.py is already complete
@kovtcharov
Copy link
Copy Markdown
Collaborator Author

@claude review this PR for correctness, we may have missed a few recent milestones that were added.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 11, 2026

Claude finished @kovtcharov's task —— View job


PR Review: Roadmap Overhaul

  • Read pr-diff.txt and pr-files.txt for overview
  • Check roadmap.mdx against recent milestones
  • Verify milestone versions match actual releases
  • Check for any missing features/issues
  • Review new plan documents for correctness
  • Provide feedback summary

Summary

The roadmap overhaul looks comprehensive and well-organized. The new plan documents are thorough and cross-reference appropriately. However, I found missing milestone entries that should be added to the "Shipped" section.

🔴 Missing Milestones

The roadmap shows v0.16.0 as the most recent shipped release, but v0.16.1, v0.17.0, v0.17.1, and v0.17.2 have all shipped (tags exist, release notes exist in docs/releases/).

Current "Shipped" section ends at:

  • v0.16.0 (March 2026)

Missing from "Shipped" section:

Version Date Key Features
v0.17.2 April 2026 One-click desktop installers, Agent Registry with per-session agent selection, MCP tool visualization, RAG cache integrity verification
v0.17.1 April 2026 npm upgrade for OIDC trusted publishing
v0.17.0 April 2026 GAIA Agent UI — privacy-first web app, 78% smaller system prompt, ngrok tunnel, tool guardrails
v0.16.1 March 2026 C++ tool security (policies, confirmation, allowlisting), gaia init fixes, Lemonade v10.0.0, doc link checker

🟡 Timeline Diagram Issue

The Mermaid diagram at docs/roadmap.mdx:23-68 shows:

  • Shipped: v0.15.x, v0.16.0
  • Current (In Progress): v0.17.2

This is inconsistent with the reality that v0.17.2 has already shipped (tag exists at commit cd81adc, release notes at docs/releases/v0.17.2.mdx). The timeline should be updated to:

  • Move v0.16.1, v0.17.0, v0.17.1, v0.17.2 to "Shipped"
  • Update "Current" to reflect v0.18.x

🟢 Plan Documents Look Good

The 7 new plan documents are well-structured:

  • security-model.mdx — Comprehensive threat model, 10 security domains
  • setup-wizard.mdx — First-run onboarding with system scan
  • email-calendar-integration.mdx — MCP-first approach for Gmail/Calendar
  • skill-format.mdx — SKILL.md specification with security tiers
  • autonomy-engine.mdx — Background service architecture
  • messaging-integrations-plan.mdx — Signal-first adapter architecture
  • oem-bundling.mdx — Hardware SKU pre-configuration

Cross-references between plans are consistent, and issue numbers (#686-#708) are correctly cited.

Review Comment Response

Re: "OpenClaw" (itomek's comment): This appears to be an external skill format compatibility layer mentioned in skill-format.mdx. The term is used consistently across the PR.


Recommendation: Add the missing v0.16.1, v0.17.0, v0.17.1, and v0.17.2 entries to the "Shipped" section and update the Mermaid diagram before merging.

- Move v0.17.2 to Shipped section with release summary
- Add v0.17.3 as current release (RAG reliability, security, website)
- Update v0.18.x tables to reflect issue triage (moved 10 issues out of v0.17.3)
- Add v0.19.0 model fine-tuning deliverables (was missing from table)
- Add v0.22.0 App Consolidation section and Mermaid node (was missing)
- Remove duplicate #455 from v0.18.2 (addressed by PR #746 in v0.17.3)
- Add Detailed Plan links to v0.17.3
- Set sequential weekly deadlines: Apr 17 through Jun 16
- Update timestamp to April 13, 2026

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cpp devops DevOps/infrastructure changes documentation Documentation changes llm LLM backend changes mcp MCP integration changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants