snapshot: preserve central wiki state 2026-08-15 (7 modified + 1 new file)
This commit is contained in:
Tony0410
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Decisions
|
||||
type: collection
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
confidence: high
|
||||
tags: [decisions]
|
||||
---
|
||||
|
||||
# Decisions
|
||||
|
||||
Stable strategic and config decisions, with evidence and status.
|
||||
|
||||
## Current decisions
|
||||
|
||||
- [[decisions/keep-openrouter-as-fallback]]
|
||||
- [[decisions/persistent-shell-enabled]]
|
||||
- [[decisions/rollback-steel-to-camofox]]
|
||||
|
||||
## History
|
||||
- **Verified:** Decision pages initialized during wiki setup on 2026-07-22
|
||||
- **Inferred:** Config version 33 and multiple named backups imply iterative changes in vision, browser, and model routing
|
||||
- **Unknown:** Exact date each listed decision was made; exact alternatives considered
|
||||
|
||||
## Related
|
||||
- [[current-state]]
|
||||
- [[model-routing]]
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: Keep OpenRouter as fallback
|
||||
type: decision
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
review_after: 2026-08-22 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when
|
||||
confidence: high
|
||||
tags: [routing, provider, decision]
|
||||
sources: []
|
||||
---
|
||||
# Keep OpenRouter as fallback
|
||||
|
||||
## Decision
|
||||
OpenRouter must remain available as a fallback provider, even if a self-hosted router becomes primary.
|
||||
|
||||
## Reasons
|
||||
- Free models are important.
|
||||
- Broad model coverage.
|
||||
- Previous migrations disrupted provider availability.
|
||||
- A fallback reduces the chance of Hermes becoming unusable.
|
||||
|
||||
## Alternatives considered
|
||||
- Direct providers only
|
||||
- OmniRoute exclusively
|
||||
- Local models exclusively
|
||||
|
||||
## Revisit when
|
||||
A self-hosted router has operated reliably for at least 30 days.
|
||||
|
||||
## Related
|
||||
- [[model-routing]]
|
||||
- [[systems/omniroute]]
|
||||
- [[systems/openrouter]]
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Persistent shell enabled
|
||||
type: decision
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
review_after: 0001-01-01
|
||||
confidence: high
|
||||
tags: [automation, shell, decision]
|
||||
sources: []
|
||||
---
|
||||
# Persistent shell enabled
|
||||
## Decision
|
||||
Enable persistent shells for Hermes.
|
||||
|
||||
## Reasons
|
||||
- Preserve terminal state across turns
|
||||
- Avoid re-activating virtualenvs and aliases every call
|
||||
|
||||
## Alternatives considered
|
||||
- Always transient shell
|
||||
- Manual re-activation by user
|
||||
|
||||
## Revisit when
|
||||
Use case becomes critical again.
|
||||
|
||||
## Related
|
||||
- [[persistent-shells]]
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Rollback Steel to Camoufox
|
||||
type: decision
|
||||
status: active
|
||||
created: 2026-08-02
|
||||
updated: 2026-08-02
|
||||
verified_on: 2026-08-02
|
||||
confidence: high
|
||||
tags: [decision, browser, steel, camofox, rollback]
|
||||
sources: [session-history, live-config]
|
||||
---
|
||||
|
||||
# Decision: Rollback Steel Browser → Camoufox
|
||||
|
||||
## Date
|
||||
2026-07-30
|
||||
|
||||
## Context
|
||||
Steel Browser was deployed on CT201 on 2026-07-29 as the primary browser automation backend, replacing Camoufox. It ran for approximately 24 hours before being reverted.
|
||||
|
||||
## Options Considered
|
||||
| Option | Pros | Cons |
|
||||
|---|---|---|
|
||||
| **Keep Steel** | Full CDP access, session viewer UI, Docker isolation | CDP URL normalization issues, network hop, empty-stream errors |
|
||||
| **Revert to Camoufox** | Local (no network hop), already authenticated, fewer failure modes | Headed display consumes resources, no built-in session viewer |
|
||||
| **Both (Steel primary, Camoufox fallback)** | Redundancy | Complexity, two backends to maintain, unclear which one Hermes uses per-request |
|
||||
|
||||
## Decision
|
||||
**Revert to Camoufox as primary.** Steel plugin disabled but left running on CT201.
|
||||
|
||||
## Rationale
|
||||
1. **Reliability:** Camoufox runs on the same host as Hermes (CT450) — no Docker networking, no CDP URL normalization patches, no container-to-host routing issues.
|
||||
2. **Auth persistence:** Camoufox's persistent profile `anthony` is already authenticated into key services (Uber Eats, LinkedIn). Steel required cookie re-exports.
|
||||
3. **Failure mode:** The `opencode-go/deepseek-v4-flash` empty-stream errors were hitting all providers, but Steel added an extra failure surface (CDP connection, plugin layer) on top of the same problem.
|
||||
4. **DeepSeek 0731 compatibility:** The new model's stricter tool name validation (`^[a-zA-Z0-9_-]+$`) affected all providers — not a Steel-specific issue, but another reason to minimise the toolchain.
|
||||
|
||||
## Consequences
|
||||
- **Positive:** Browser automation is stable again. Uber Eats report ran successfully via Camofox on 2026-08-01.
|
||||
- **Negative:** Steel's session viewer UI and full CDP access are no longer available to Hermes.
|
||||
- **Neutral:** Steel still runs on CT201 — can be re-enabled by uncommenting `.env` lines and enabling the plugin.
|
||||
|
||||
## Evidence
|
||||
- Camoufox verified working Jul 30: `browserConnected: true`, `sessions: 1`, `tabs: 1`, active 200s
|
||||
- Uber Eats report (Aug 1) successfully scraped via Camofox REST API — 11 orders, $264.51
|
||||
- Steel plugin `browser-steel` still present at `/home/hermes/.hermes/plugins/browser-steel/` — disabled
|
||||
|
||||
## Related
|
||||
- [[comparisons/steel-vs-camoufox]]
|
||||
- [[systems/browser-backend]]
|
||||
- [[concepts/browser-automation]]
|
||||
Reference in New Issue
Block a user