ZON
Hermes Shadow Lane

Parallel, isolated, reversible.

OpenClaw stays production. Hermes runs as a separate shadow harness with its own home, ports, logs, outputs, and Feishu lane. The goal is to compare safely for 2-3 weeks before any migration decision.

Current State

Installed
shadow runtime ready

Hermes v0.9.0 plus Feishu dependencies are installed under the isolated runtime tree.

Production Risk

0
openclaw untouched

No edits were made to the current OpenClaw bot, cron, or writeback path.

Activation

Blocked
needs new feishu lane

A dedicated Feishu app and new group or prefix are still required before live shadow intake.

Compare Window

2-3w
trial not started

Token, quality, fault rate, and maintenance cost should be scored weekly.

Isolation Contract

Area Production Shadow
Runtime ~/.openclaw and current launchd services [REDACTED_LOCAL_PATH]
Gateway port 18789 OpenClaw, 19089 Edict 18652 API server, 18654 webhook reserve
Logs current OpenClaw and Codex IM log trees tmp/_codex/hermes-shadow/logs
Feishu intake existing main groups and writeback hooks new app plus new group or new prefix only
Outputs main board, main sheet, main writeback shadow-board and shadow-sheet only

Machine Snapshot

  • Apple M1 Pro
  • 8 CPU cores
  • 16 GB RAM
  • Can run two lanes in principle, but current memory pressure is not low.
  • Best practice: keep Hermes shadow in foreground first, avoid always-on dual browser-heavy flows.

Next Activation Steps

  • Fill home/.env with model provider credentials for Hermes.
  • Bind a new Feishu app or at minimum a new shadow group.
  • Keep FEISHU_HOME_CHANNEL pointed only at the shadow lane.
  • Run the doctor script, then run migration dry-run, then launch gateway in foreground.

Trial Scoreboard

Metric OpenClaw Hermes Shadow
Total tokensbaselinepending
Quality scorebaselinepending
Failure ratebaselinepending
Maintenance minutesbaselinepending

Verification

Doctor passed structure checks; provider and Feishu creds still missing
Gateway smoke foreground start confirmed under shadow home and shadow logs
OpenClaw migration preview user-data preset only, preview only, no files modified
Migration result 6 would import, 3 conflicts, 22 skipped, secrets not selected

Key Paths

Runtime[REDACTED_LOCAL_PATH]
Home[REDACTED_LOCAL_PATH]
Logs[REDACTED_LOCAL_PATH]
Runs[REDACTED_LOCAL_PATH]
Shadow board[REDACTED_LOCAL_PATH]
Shadow sheet[REDACTED_LOCAL_PATH]
This board is local-first and intended to remain outside the current production chain.
Installed an isolated Hermes shadow runtime with separate home, ports, logs, and local shadow outputs, while leaving the active OpenClaw bot, cron, and writeback untouched.
— One small system