8ae8e526d9
3 phases, 6 plans, 16 requirements. Archives copied to milestones/. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
100 lines
5.4 KiB
Markdown
100 lines
5.4 KiB
Markdown
# Roadmap: v1.4 Hermes Default Provider
|
|
|
|
**Milestone:** v1.4
|
|
**Status:** Active
|
|
**Phases:** 27-29 (3 phases)
|
|
**Granularity:** Coarse
|
|
**Coverage:** 16/16 requirements mapped
|
|
|
|
---
|
|
|
|
## Phases
|
|
|
|
- [x] **Phase 27: Hermes Adapter** — Install and enable the Hermes adapter, expose it in the Add Agent dialog, and deliver working heartbeat execution with session persistence (completed 2026-04-02)
|
|
- [x] **Phase 28: Ollama Integration & Agent Surface** — Detect Ollama, list and recommend models, expose skill/cost/dashboard data for Hermes agents (completed 2026-04-02)
|
|
- [x] **Phase 29: Default Provider & End-to-End** — Onboarding fallback to Hermes, agent template compatibility, GSD workflow validation, full end-to-end smoke test (completed 2026-04-02)
|
|
|
|
---
|
|
|
|
## Phase Details
|
|
|
|
### Phase 27: Hermes Adapter
|
|
**Goal**: Users can create a Hermes agent in Nexus, configure it, and have it execute heartbeats that spawn `hermes chat -q`, return a result, and persist the session across runs
|
|
**Depends on**: Nothing (first phase of v1.4; depends on v1.3 milestone being shipped)
|
|
**Requirements**: HERM-01, HERM-02, HERM-03, HERM-04
|
|
**Success Criteria** (what must be TRUE):
|
|
1. "Hermes" appears in the "Add Agent" dropdown and can be selected to create a new agent
|
|
2. When creating a Hermes agent, the user can pick a model and toggle tool permissions; the agent is saved and appears in the agent list
|
|
3. When a heartbeat fires for a Hermes agent, Nexus spawns `hermes chat -q` with the task, the process completes, and the result is written back as a task update
|
|
4. A second heartbeat on the same Hermes agent resumes the prior session via `--resume`; context from the previous run is accessible
|
|
**Plans:** 1/1 plans complete
|
|
Plans:
|
|
- [x] 27-01-PLAN.md — Close four integration gaps: SESSIONED_LOCAL_ADAPTERS, create-mode toolsets bug, duplicate constant, session codec test
|
|
|
|
### Phase 28: Ollama Integration & Agent Surface
|
|
**Goal**: Users can see which Ollama models are available, get a recommendation for their hardware, configure any Hermes agent to use a local model, and see Hermes-specific runtime data in the dashboard and agent config
|
|
**Depends on**: Phase 27
|
|
**Requirements**: OLLA-01, OLLA-02, OLLA-03, OLLA-04, OLLA-05, HERM-05, HERM-06, HERM-07
|
|
**Success Criteria** (what must be TRUE):
|
|
1. When Ollama is installed, a status indicator in the Hermes agent config shows "Ollama detected" with the version; when Ollama is absent, the config shows installation instructions with a link
|
|
2. A Hermes agent's model selector lists all locally available Ollama models pulled from `ollama list`
|
|
3. User can save a Hermes agent with any Ollama model from the list; heartbeats use the selected model
|
|
4. The model selector shows a recommended model (highlighted) based on detected RAM/VRAM, derived from a shipped catalog
|
|
5. The agent config page shows Nexus-managed skills alongside Hermes native skills in a single unified list
|
|
6. The dashboard agent card for a Hermes agent shows model name, memory usage, and native skill count
|
|
7. Token usage and estimated model cost are recorded per heartbeat and surfaced in the cost tracking view
|
|
**Plans:** 3/3 plans complete
|
|
Plans:
|
|
- [x] 28-01-PLAN.md — Ollama service, routes, model catalog, and unit tests
|
|
- [x] 28-02-PLAN.md — UI model selector dropdown, install callout, Hermes skill badge
|
|
- [x] 28-03-PLAN.md — Hermes stateJson runtime data and dashboard HermesRuntimeCard
|
|
**UI hint**: yes
|
|
|
|
### Phase 29: Default Provider & End-to-End
|
|
**Goal**: A fresh Nexus install with only Hermes and Ollama works end-to-end — onboarding offers Hermes as the default, PM and Engineer templates run correctly on the Hermes runtime, and GSD workflow tasks complete successfully
|
|
**Depends on**: Phase 28
|
|
**Requirements**: DFLT-01, DFLT-02, DFLT-03, DFLT-04
|
|
**Success Criteria** (what must be TRUE):
|
|
1. During onboarding, if no cloud provider API key is detected, the setup flow offers "Use Hermes (local, free)" as the default provider with a one-click path to configure it
|
|
2. Creating a PM agent or Engineer agent from the predefined templates and assigning it to a Hermes runtime produces a working agent — heartbeats execute and return meaningful results
|
|
3. Running a full GSD workflow task (create issue, assign to Engineer, execute heartbeat, mark complete) with Hermes as the sole runtime completes without errors
|
|
4. A machine with only Nexus, Hermes, and Ollama installed (no Anthropic/OpenAI key) can complete the entire onboarding-to-first-task flow with no paywalls or missing-key errors
|
|
**Plans:** 2/2 plans complete
|
|
Plans:
|
|
- [x] 29-01-PLAN.md — Adapter probe route, onboarding wizard Hermes fallback, adapter-neutral templates
|
|
- [x] 29-02-PLAN.md — Hermes skill injection via promptTemplate, integration tests
|
|
|
|
---
|
|
|
|
## Coverage Validation
|
|
|
|
All 16 v1 requirements are mapped to exactly one phase. No orphans.
|
|
|
|
| Requirement | Phase |
|
|
|-------------|-------|
|
|
| HERM-01 | 27 |
|
|
| HERM-02 | 27 |
|
|
| HERM-03 | 27 |
|
|
| HERM-04 | 27 |
|
|
| HERM-05 | 28 |
|
|
| HERM-06 | 28 |
|
|
| HERM-07 | 28 |
|
|
| OLLA-01 | 28 |
|
|
| OLLA-02 | 28 |
|
|
| OLLA-03 | 28 |
|
|
| OLLA-04 | 28 |
|
|
| OLLA-05 | 28 |
|
|
| DFLT-01 | 29 |
|
|
| DFLT-02 | 29 |
|
|
| DFLT-03 | 29 |
|
|
| DFLT-04 | 29 |
|
|
|
|
---
|
|
|
|
## Progress
|
|
|
|
| Phase | Milestone | Plans Complete | Status | Completed |
|
|
|-------|-----------|----------------|--------|-----------|
|
|
| 27. Hermes Adapter | v1.4 | 1/1 | Complete | 2026-04-02 |
|
|
| 28. Ollama Integration & Agent Surface | v1.4 | 3/3 | Complete | 2026-04-02 |
|
|
| 29. Default Provider & End-to-End | v1.4 | 2/2 | Complete | 2026-04-02 |
|