> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_22/prd_phase_22.md). # PRD Phase 22: Non-Hermes Multi-Agent Detection And Home Surfaces **Status**: Complete **Sessions**: 3 (initial estimate) **Estimated Duration**: 4-6 days **Source Code Roots**: `V23/` = `/home/aiwithapex/projects/claudeos/claude-os-v2.3/`; `AIOS/` = `/home/aiwithapex/projects/aios/`; diff reference = `/home/aiwithapex/projects/claudeos/diff-v1-v2.3/`. **Progress**: 3/3 sessions (100%) *** ## Overview Phase 22 completes the non-Hermes v2.3 multi-agent detection and home-dashboard surfaces after the usage-accuracy foundation. It adds Antigravity as a real dual-surface local agent signal, wires its usage into existing usage/ROI surfaces, exposes Hermes in the setup wizard, and adds the home `DreamSourcesStrip` that shows which Dream input streams are live. This phase preserves workstream B and the Antigravity-dependent A6/A7 details from `docs/ongoing-projects/v2_3-port-remaining.md`. Phase 21 preserves the global source legend and already-done audit. Phase 23 preserves the remaining route, polish, housekeeping, no-action, and closeout details. *** ## Progress Tracker | Session | Name | Status | Est. Tasks | Validated | | ------- | ------------------------------------ | -------- | ---------- | ---------- | | 01 | Antigravity Detection Data Contract | Complete | \~18-24 | 2026-06-02 | | 02 | Antigravity Usage Consumers | Complete | \~14-20 | 2026-06-02 | | 03 | Setup Wizard And Dream Sources Strip | Complete | \~18-24 | 2026-06-02 | *** ## Completed Sessions * Session 01: Antigravity Detection Data Contract * Session 02: Antigravity Usage Consumers * Session 03: Setup Wizard And Dream Sources Strip *** ## Upcoming Sessions * None *** ## Objectives 1. Extend local app detection so Antigravity reports independent IDE and CLI surfaces plus conversation usage and saved-equivalent value. 2. Wire Antigravity usage into the usage panel and home ROI strip only after the data contract exists. 3. Add the Hermes Agent setup wizard card using existing aios Hermes detection. 4. Port the `DreamSourcesStrip` as a small aios component and selector layer that reads existing host/local data contracts. *** ## Prerequisites * Phase 21 Sessions 01-02 complete for stable usage/ROI base contracts. * Phase 22 Session 01 complete before Session 02 consumes Antigravity data. * Hermes detection already exists in aios app detection. * Hermes Phase 16-20 data may improve the Hermes tile, but the strip must degrade safely if Hermes data is not yet live. *** ## Technical Considerations ### Architecture Antigravity detection belongs in `AIOS/scripts/lib/app-detection.ts`, with typed browser-safe output in `AIOS/src/lib/live-data-types.ts` and `AIOS/src/lib/validate-live-data.ts`. UI consumers should be split into small components/selectors instead of growing `src/routes/index.tsx` further. ### Session Source Map **Session 01: B1** * Source types and detection body: [V23/scripts/aggregate.ts:769](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/scripts/aggregate.ts:769) through `:790`, and [V23/scripts/aggregate.ts:807](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/scripts/aggregate.ts:807) through `:905`. * Target `.app`-only boolean: [AIOS/scripts/lib/app-detection.ts:207](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/scripts/lib/app-detection.ts:207) through `:210`. * Required output: `surfaces.{ide,cli}`, conversation count, last-active, and `usage.savedEquivalent`, scanned from `~/.gemini/antigravity/conversations/*.pb` and `*.json`. **Session 02: A6 and A7** * A6 usage-panel source row and logo map: [V23/src/components/usage-panel.tsx:143](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/usage-panel.tsx:143) through `:179`, and [V23/src/components/usage-panel.tsx:301](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/usage-panel.tsx:301) through `:305`. * A6 target service list: [AIOS/src/components/usage-panel.tsx:23](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/usage-panel.tsx:23), currently `Claude | ChatGPT | Codex | OpenRouter`. * A7 source ROI chip: [V23/src/routes/index.tsx:16560](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/index.tsx:16560) through `:16600`. * A7 target: `AIOS/src/routes/index.tsx` and `AIOS/src/lib/home-transforms.ts`. **Session 03: B2 and B3** * B2 Hermes setup wizard source: [V23/src/routes/setup.tsx:198](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/setup.tsx:198) through `:207`, with wiring at `:102`, `:265`, and `:326`. * B2 target: `AIOS/src/components/setup/constants.ts` and `AIOS/src/routes/setup.tsx`; aios app detection already exposes Hermes at [AIOS/scripts/lib/app-detection.ts:63](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/scripts/lib/app-detection.ts:63). * B3 source: [V23/src/routes/index.tsx:16278](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/index.tsx:16278) through `:16542` for `DreamSourcesStrip` and `DreamSourceTile`, mounted at [V23/src/routes/index.tsx:16241](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/index.tsx:16241). * B3 target: own aios component file plus a `home-transforms` selector reading `detection.apps` and `hermes` blocks. ### Relevant Considerations * \[P08] Local agent privacy/readiness boundary: expose only counts, statuses, timestamps, and safe labels. Do not expose raw conversation paths, prompts, transcripts, or auth payloads. * \[P09] Provider-neutral helpers should remain the single UI projection layer: prefer shared selectors for home and usage surfaces. * \[P02] Typed degradation over throws: missing Antigravity data or missing Hermes data must show optional/missing states rather than breaking the home dashboard. *** ## Success Criteria Phase complete when: * [x] All three sessions completed and validated. * [x] Antigravity reports IDE and CLI surfaces independently, with bounded conversation usage and saved-equivalent value. * [x] `detection.apps.antigravity.usage` is typed, validated, and represented in example/demo data. * [x] Usage panel shows an Antigravity row only from validated data and keeps Codex split from ChatGPT. * [x] Home ROI includes Antigravity saved-equivalent value with a gated attribution chip. * [x] Setup wizard includes a Hermes Agent card backed by existing detection. * [x] `DreamSourcesStrip` renders live/optional/missing state for Claude Code, Antigravity, Memory, Skills, Integrations, Automations, and Hermes. *** ## Dependencies ### Depends On * Phase 21: Non-Hermes v2.3 Usage Accuracy ### Enables * Phase 23: Non-Hermes Routes, Polish And Closeout --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_22/prd_phase_22.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.