wiki: publish pending edits (2026-10-20)

This commit is contained in:
Tony0410
2026-10-20 18:38:11 +08:00
parent 667ab7f41d
commit fbd4f297eb
46 changed files with 1012 additions and 197 deletions
+18 -5
View File
@@ -3,8 +3,8 @@ title: Camoufox vs Chrome
type: comparison
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
confidence: medium
tags: [comparison, browser]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -20,14 +20,26 @@ Compare the two browser-automation options for Hermes's browser tool.
|---|---|---|
| In use on this install | **Yes** — configured `cloud_provider` | No evidence found |
| Config | `browser.camofox.managed_persistence: true` (note: key is spelled `camofox` in config, not `camoufox`) | n/a |
| Driver | `cua-driver` v0.9.0 at `/home/hermes/.cua-driver/packages/releases/0.9.0-x86_64-unknown-linux-gnu/cua-driver` | n/a |
| Driver | `cua-driver` **v0.28.2** at `/home/hermes/.local/bin/cua-driver` (the `0.9.0` release path this page used to cite no longer exists) | n/a |
| Display | Headed, via Xvfb `:99` + fluxbox — see [[systems/headless-server]] | n/a |
| `use_gateway` | `false` | n/a |
## Detail
### Camoufox (in use)
- **Verified:** `browser.cloud_provider: camofox`, `inactivity_timeout: 120s`, `allow_private_urls: true`.
- **Verified 2026-10-20:** `browser.cloud_provider: steel`, `browser.engine: camofox`,
`browser.headed: true`, `browser.inactivity_timeout: 450`, `browser.use_gateway: false`,
`browser.camera_provider: camofox`, `browser.allow_private_urls: true`,
`browser.allow_unsafe_evaluate: true`, `browser.cdp_url: ''`,
`browser.command_timeout: 185`.
`browser.camofox:` → `adopt_existing_tab: true`, `managed_persistence: true`,
`rewrite_loopback_urls: true`, `user_id: anthony`.
**Note `inactivity_timeout` is 450s, not the 120s recorded here** — that value changed.
`cloud_provider` is `steel` with `engine: camofox`; the two keys describe different layers.
- **Live processes (2026-10-20):** `cua-driver serve` (PID 3312393), `camoufox-ws-server.mjs`,
and a live `camoufox-bin` (FirefoxDev build) tree under `/home/hermes/.cache/camoufox/`.
Camofox's REST port **9377 is not listening** on CT460 — the Camofox browser service runs on
**CT450**; see [[systems/browser-backend]].
- Runs headed under Xvfb rather than a true headless mode, per [[systems/headless-server]] — fluxbox provides the window manager, x11vnc/noVNC expose it for human viewing.
- `cua-driver` bridges Hermes's computer-use tool calls to the browser.
@@ -36,7 +48,8 @@ Compare the two browser-automation options for Hermes's browser tool.
- Included in the comparison because the page existed as a placeholder — if Chrome/CDP was evaluated and rejected, that reasoning isn't captured anywhere; worth a [[decisions/index]] entry if anyone remembers why Camoufox was chosen over stock Chrome.
## Verdict
This install uses **Camoufox exclusively**. There's no evidence Chrome/Chromium was ever wired in as an alternative on this host — the comparison exists more as a placeholder for a decision that may have been made outside this wiki than as an active either/or choice today.
This install uses **Camoufox exclusively** (via the `cua-driver` + `camoufox-ws-server.mjs` stack
on CT460 and a separate Camofox service on CT450). There's no evidence Chrome/Chromium was ever wired in as an alternative on this host — the comparison exists more as a placeholder for a decision that may have been made outside this wiki than as an active either/or choice today.
## Related
- [[systems/browser-backend]]
+12 -2
View File
@@ -3,8 +3,8 @@ title: Hermes vs Nanobot
type: comparison
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [comparison, hermes, nanobot]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -22,6 +22,16 @@ Compare Hermes (this agent) with Nanobot, another agent process in the homelab,
- It's publicly reachable via the same Cloudflare Tunnel that fronts Hermes: `nanobot.martinwa.org` → `100.122.189.81:8766`, and `nano-ssh.martinwa.org` → SSH on the same host.
- The earlier note "Nanobox on the PVE host at `192.168.178.39`" conflated Nanobot with `pve`'s own LAN IP (that address is Proxmox's web UI, per the tunnel's `pve.martinwa.org` entry) — an error, not a second Nanobot instance.
> **Re-verified 2026-10-20 — the core claims on this page still hold.** The `clawtest` peer is
> still on Tailscale at **`100.122.189.81`** (`tailscale status` → `100.122.189.81 clawtest
> anthonymau@ linux -`) and `http://nanobot.martinwa.org` still answers (**301**). So the
> correction recorded above remains accurate 90 days on.
>
> **One caveat worth adding:** CT333 now runs **both** Nanobot *and* ZeroClaw (the latter verified
> live on 2026-10-20 — see [[agents/zeroclaw]]). The page's framing of CT333 as the Nanobot host
> is not wrong, but the host is no longer single-purpose. Note also that **CT333 is `zeroclaw` in
> the current Proxmox naming** — the wiki uses the older "clawtest" label for the same LXC.
## At a glance
| | Hermes (ct460) | Nanobot (ct333 "clawtest") |
|---|---|---|
+15 -2
View File
@@ -3,8 +3,8 @@ title: Memory Backends
type: comparison
status: active
created: 2026-07-22
updated: 2026-08-12
verified_on: 2026-08-12
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [comparison, memory]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -30,6 +30,19 @@ The three archived scripts (`hindsight-watchdog.py.archived`, `hindsight_migrati
- Risk assessment flagged: schema mismatch, embedding drift, scope leakage, provenance loss, and one-way/no-rollback migration with no dry-run snapshot.
- **Verdict:** stay on Mnemosyne. Config verified `memory.provider: mnemosyne` (2026-08-12). No migration was performed.
> **Re-verified 2026-10-20 — Mnemosyne is still the only backend, and the OpenViking decision still
> holds.** `memory.provider: mnemosyne`, `memory_enabled: true`, `flush_min_turns: 6`,
> `memory_char_limit: 5000`, `user_char_limit: 3000`, `user_profile_enabled: true`,
> `nudge_interval: 10`; Mnemosyne sub-block `auto_sleep: true`, `default_scope: session`,
> `vector_type: int8`, `sleep_threshold: 50`, `profile_isolation: true`,
> `shared_surface_path: data/shared/mnemosyne.db`, `shared_surface_read: true`.
> No `openviking` key anywhere in `config.yaml`. No migration performed.
>
> **New since 2026-08-12:** `mnemosyne.skip_contexts: [cron, flush, subagent, background,
> skill_loop]` and `reflect.disabled_for_cron: true` — Mnemosyne capture is deliberately skipped
> in cron contexts, which is why scheduled jobs produce no working memories. See
> [[concepts/agent-memory]] and [[systems/mnemosyne]].
## Related
- [[systems/mnemosyne]]
- [[systems/memory-backend]]
+38 -8
View File
@@ -3,8 +3,8 @@ title: Model Routers
type: comparison
status: active
created: 2026-07-22
updated: 2026-08-12
verified_on: 2026-08-12
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [comparison, routing]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -18,17 +18,47 @@ Compare LiteLLM, OmniRoute, and OpenRouter as model-routing layers for Hermes.
## At a glance
| | LiteLLM | OmniRoute | OpenRouter |
|---|---|---|---|
| Role in Hermes | **Default/primary** provider | **Fallback/auxiliary** provider | Not configured as a standalone provider |
| Endpoint | `http://litellm:4000/v1` | `http://omniroute:20128/v1` (public: `omniroute.martinwa.org`) | n/a |
| Advertised model count | ~1512 | ~3430 | n/a |
| Role in Hermes | Fallback + a *custom_providers* entry | **Auxiliary + the pin on essentially every model-calling cron job** | Not configured as a standalone provider |
| Endpoint | `http://litellm:4000/v1` | `http://omniroute:20128/v1` (public: `omniroute.martinwa.org`) **and** `http://100.78.63.20:20128` (`omni-101`) | n/a |
| Model count (live, 2026-10-20) | **1869** (`/v1/models` with the configured key) | **6457** at `omniroute:20128/v1/models` | n/a |
| Model count (declared in `config.yaml`) | 1728 | 5398 (`Omniroute:20128`) / 5384 (`omni-101`) | n/a |
| Routing style | Straight proxy | Combo strategy, LKGP scoring, session affinity | n/a |
| Aux roles used for | — | `skills_hub`, `approval`, `mcp` | — |
| Config presence | `custom_providers` in `~/.hermes/config.yaml` | same | absent from `custom_providers`; only referenced via a kept [[decisions/keep-openrouter-as-fallback]] decision |
| Config presence | `custom_providers` in `~/.hermes/config.yaml` | same (two separate entries) | absent from `custom_providers`; only referenced via a kept [[decisions/keep-openrouter-as-fallback]] decision |
> **The "LiteLLM is the default/primary" row was wrong by 2026-10-20 (verified and corrected).**
> The live `model:` block in `~/.hermes/config.yaml` is:
> ```yaml
> model:
> provider: nous
> default: meituan/longcat-2.5-preview:free
> base_url: https://inference-api.nousresearch.com/v1
> api_mode: chat_completions
> persist_switch_by_default: false
> ```
> So the **primary model path is Nous Research direct**, not LiteLLM. LiteLLM is the *last* entry
> in the fallback chain (`or-inclusionai_ling-2_6-1t` via `custom` → `http://litellm:4000/v1`).
>
> **The two OmniRoute endpoints matter.** `Omniroute:20128` is a DNS name (m93p CT101);
> `omni-101` is the raw IP `100.78.63.20:20128` (node `omniroute-1`) and is the alias pinned on
> effectively every model-calling cron job. The two carry **different catalogs** (5398 vs 5384
> declared models) and the `omni-101` entry's own `model:` is `smart-route` while
> `Omniroute:20128`'s is `go-cheap`.
>
> **Also: both OmniRoute endpoints and LiteLLM now require authentication.** `curl` without a key
> returns **401 `invalid_api_key`** on all three `/v1/models` endpoints. The keys live in
> `~/.hermes/.env` via each provider's `key_env` (e.g. `HERMES_CUSTOM_OMNIROUTE_20128_API_KEY`).
> Any runbook that probes these endpoints with a bare `curl` will see 401 and may wrongly conclude
> the provider is down — it is not.
## Detail
### LiteLLM — primary
Default provider for main chat traffic (`freellmapi-auto` default model resolves through it). See [[systems/model-providers]].
### LiteLLM — fallback tail + a `custom_providers` entry
LiteLLM hosts the `freellmapi-auto` model alias and is reachable at `http://litellm:4000/v1`, but
it is **no longer the default chat path** — that is Nous direct
(`meituan/longcat-2.5-preview:free`, per the live `model:` block). LiteLLM appears in the
fallback chain as `or-inclusionai_ling-2_6-1t` via the `custom` provider.
See [[systems/model-providers]] and [[concepts/model-routing]].
### FreeLLMAPI — the router behind `freellmapi-auto`
Unified LLM router at `100.82.40.23:3001` (also `freellmapi.martinwa.org`). Verified 2026-08-12: