docs: resolve Hermes integration decisions (both UIs, report-only, eagle-eye)
UI: trial hermes-ui + hermes-workspace in parallel, keep winner (new Task 9). Curator stays report-only. eagle-eye trial confirmed (only direct skill-router in the ecosystem; llmtrim noted as complementary). camofox minimal 2-tool skill. All phases now ungated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
ginnoir
co-authored by
Claude Opus 4.8
Claude Opus 4.8
parent
98c4a2a02b
commit
3cd843072d
@@ -21,13 +21,14 @@ also installed), and triaged them into adopt / trial / decide / skip.
|
||||
| **1** | `hermes-curator-evolver` | **ADOPT (dry-run first)** | Closes Hermes' self-improvement loop; read-only by default; aligns with your curation habit. |
|
||||
| **2** | `camofox-browser` | **ADOPT (new homelab stack)** | Gives the local agent real web browsing; clean Docker/Caddy fit; independent of Hermes internals. |
|
||||
| **2** | `eagle-eye` | **TRIAL / DEFER** | Solves the exact tool-overload pain you already hit — but very early (5★, 1 commit) and carries a required Chinese-tokenizer dep. Trial behind a flag; don't depend on it. |
|
||||
| **3** | `hermes-ui` | **TRIAL (low-cost UI upgrade)** | Single-HTML + stdlib proxy; trivial to stand up next to the bundled webui. |
|
||||
| **3** | `hermes-workspace` | **DECISION** | The full "command center," but a real React build + a swarm model your single P100 can't actually parallelize. |
|
||||
| **3** | `mission-control` | **SKIP / DEFER** | Not Hermes-native (built for OpenClaw/CrewAI/LangGraph/AutoGen). Redundant with the two Hermes UIs unless you want a framework-agnostic ops plane. |
|
||||
| **3** | `hermes-ui` | **ADOPT (trial)** | Single-HTML + stdlib proxy; stood up next to the bundled webui to evaluate. |
|
||||
| **3** | `hermes-workspace` | **ADOPT (trial)** | Full command center; stood up in parallel to compare head-to-head, then keep one. Swarm Mode won't parallelize on one P100 — value is the workspace/observability features. |
|
||||
| **3** | `mission-control` | **SKIP** | Not Hermes-native (built for OpenClaw/CrewAI/LangGraph/AutoGen). Redundant with the two Hermes UIs. |
|
||||
|
||||
**Decisions I need from you (Section 6):** (1) which UI, if any; (2) whether curator-evolver may
|
||||
ever run in `--approve` mode or stays report-only; (3) whether to trial eagle-eye at all given its
|
||||
maturity/dependency profile.
|
||||
**Decisions — RESOLVED 2026-06-27 (see Section 6):** (1) trial **both** UIs, keep the winner;
|
||||
(2) curator-evolver stays **report-only** for now; (3) **trial eagle-eye** — it's the only direct
|
||||
skill-router in the ecosystem, no more-mature equivalent exists; (4) wire camofox as a **minimal
|
||||
2-tool skill**.
|
||||
|
||||
---
|
||||
|
||||
@@ -230,17 +231,24 @@ Each phase is independently shippable and independently reversible. Stop after a
|
||||
|
||||
---
|
||||
|
||||
## 6. OPEN DECISIONS — please answer in the morning
|
||||
## 6. DECISIONS — RESOLVED 2026-06-27
|
||||
|
||||
1. **UI direction.** (a) Stay on bundled webui; (b) trial `hermes-ui` first *(my rec)*; (c) go
|
||||
straight to `hermes-workspace` as a stack; (d) something else. → gates Phase 3.
|
||||
2. **Curator autonomy.** Keep `hermes-curator-evolver` **report-only forever**, or allow eventual
|
||||
`--approve` auto-edits after a trust period? *(My rec: report-only first, revisit.)*
|
||||
3. **eagle-eye.** Trial it despite 1-commit maturity + the `jieba` dependency, or skip until it
|
||||
matures? *(My rec: short A/B trial, keep only if measurably better.)*
|
||||
4. **camofox wiring.** MCP shim vs. a Hermes skill that curls the REST API? *(My rec: minimal
|
||||
2-tool skill to respect the tool budget.)*
|
||||
5. **Scope confirmation.** Happy with the Phase 1 → 3 ordering, or want to cut/reorder anything?
|
||||
1. **UI direction → trial BOTH.** Stand up `hermes-ui` *and* `hermes-workspace` in parallel,
|
||||
evaluate head-to-head against the bundled webui, then keep the winner and remove the other.
|
||||
(Phase 3 now builds both.)
|
||||
2. **Curator autonomy → report-only for now.** `hermes-curator-evolver` runs dry-run/report only;
|
||||
no `--approve` / `--apply-low-risk` / `--approve-auto-apply`. Revisit after a trust period.
|
||||
3. **eagle-eye → trial it.** Rationale (ginnoir): wants a large skill library available without
|
||||
weighting every turn — which is exactly eagle-eye's pre-LLM skill-selection job. **Research
|
||||
result:** eagle-eye is the *only* direct skill-router in the Hermes ecosystem (per
|
||||
`awesome-hermes-agent` / Hermes Atlas); the nominal "alternatives" do different jobs —
|
||||
`llmtrim` (compresses tool schemas + MCP output; **complementary**, worth a later look for the
|
||||
tool side), `rtk-hermes` (shell-output compression), `hermes-snow-search` (faster session
|
||||
search), `hermes-motif` (mines traces into micro-skills; a curator-evolver *rival*, not a
|
||||
router). So eagle-eye stands, with the trial caveat (1-commit maturity, `jieba` dep): keep only
|
||||
if it measurably improves selection; run L1+L2 only (no P100 embeddings).
|
||||
4. **camofox wiring → minimal.** A small 2-tool Hermes skill (`browse`, `search`) over the REST
|
||||
API, not the full surface or an MCP shim — protects the curated tool budget.
|
||||
|
||||
The implementation plan that follows this spec details **Phase 1** concretely (it's unambiguous and
|
||||
safe), with Phase 2/3 sketched pending your answers above.
|
||||
All four resolved ⇒ **Phases 1, 2, and 3 are all actionable.** The implementation plan that
|
||||
follows details every phase.
|
||||
|
||||
Reference in New Issue
Block a user