audit(2026-10-10): DHL monitor retired (29 jobs / 26 enabled, verified by ID lookup); 10-10 fleet clean 174/0, 7 incidents closed - 5 open; gateway runtime env recurrence (mnemosyne + elevenlabs) verified fixed; new systems/paseo.md; mattermost unreachable; current-state + index + log updated
This commit is contained in:
@@ -0,0 +1,92 @@
|
||||
---
|
||||
title: Paseo Daemon
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-10-11
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
review_after: 2026-11-11
|
||||
confidence: high
|
||||
tags: [system, paseo, coding-agent, ct460, systemd]
|
||||
sources: [live-systemctl-user, live-ps, live-paseo-config, live-session-20261010]
|
||||
---
|
||||
|
||||
# Paseo Daemon (CT460)
|
||||
|
||||
Paseo is a **coding-agent orchestrator with a browser terminal workspace**. It runs on
|
||||
CT460 (`hermes`), hosts terminal sessions against repositories under `/home/hermes`,
|
||||
and brokers turns to external coding agents — Claude Code, Codex, Cline, OpenCode, and
|
||||
Hermes itself via ACP.
|
||||
|
||||
- Local: `http://127.0.0.1:6767`
|
||||
- Tailnet: `https://hermes.kangaroo-eel.ts.net:6767`
|
||||
|
||||
The daemon spawns provider processes on demand; a live example is
|
||||
`opencode serve --port 42021` running as a child of the unit.
|
||||
|
||||
## State (verified 2026-10-11 00:16 AWST)
|
||||
|
||||
| Item | Value |
|
||||
|---|---|
|
||||
| Unit | `paseo-daemon.service` — **user** unit, `enabled` |
|
||||
| Unit file | `/home/hermes/.config/systemd/user/paseo-daemon.service` |
|
||||
| State | `active (running)` since **2026-10-10 14:47:28 AWST** |
|
||||
| Daemon version | **0.11.2** (upgraded from 0.7.0 on 2026-10-10) |
|
||||
| Main PID | `163127` (`node --disable-warning=DEP0040 /home/hermes/.npm-global/bin/paseo daemon run`) |
|
||||
| Inner processes | supervisor `163168`, `Paseo Daemon` `163198`, terminal worker, `opencode serve` |
|
||||
| Listen | `0.0.0.0:6767` |
|
||||
| Binary used by the unit | `/home/hermes/.npm-global/bin/paseo` |
|
||||
| Config | `/home/hermes/.paseo/config.json` (mode `0600`) |
|
||||
| Logs | `/home/hermes/.paseo/<YYYYMMDD-HHMM>-NN-daemon.log` (10 MB rotation) and `journalctl --user -u paseo-daemon` |
|
||||
|
||||
## Maintenance
|
||||
|
||||
`sudo systemctl` will **not** see this unit — it belongs to the user manager:
|
||||
|
||||
systemctl --user status paseo-daemon
|
||||
systemctl --user restart paseo-daemon
|
||||
journalctl --user -u paseo-daemon -f
|
||||
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:6767/
|
||||
|
||||
Upgrade: `npm install -g @getpaseo/cli@latest`, then restart the unit. **The daemon keeps
|
||||
running the old version until the unit restarts.**
|
||||
|
||||
## Why `ExecStart` uses `daemon run`, not `daemon start`
|
||||
|
||||
`paseo daemon start` daemonises and returns immediately, so the foreground process exits
|
||||
`0`. Under `Type=simple` + `Restart=always` systemd reads that as a clean exit and
|
||||
restart-loops the service (the flapping observed during the 2026-10-10 repair).
|
||||
`paseo daemon run` stays in the foreground and is the correct supervised command.
|
||||
|
||||
The unit's `PATH` must include both `/home/hermes/.npm-global/bin` and `~/.local/bin`:
|
||||
agent CLIs the daemon shells out to are resolved through the *unit's* environment, not an
|
||||
interactive shell's.
|
||||
|
||||
## Known pitfalls
|
||||
|
||||
- **The `paseo` on `PATH` is not the daemon's version.** `/usr/bin/paseo` reports
|
||||
**0.7.2** while the unit runs the npm-global **0.11.2**. `paseo --version` therefore
|
||||
tells you nothing about what the daemon is running — read the unit's `ExecStart`, or
|
||||
the `daemonVersion` field in the daemon log.
|
||||
- **A truncated agent binary looks like a provider fault.** A partly-written `cline`
|
||||
binary (107 KB ELF instead of a full ~3 MB) made that one provider fail while every
|
||||
other provider worked. Check binary size before chasing provider config; reinstalling
|
||||
to 3.0.70 fixed it.
|
||||
- **Hermes as a Paseo provider needs the ACP extra** — `hermes pm install --extra acp`
|
||||
before the Hermes provider will load (its check reports `Hermes ACP check OK` once
|
||||
installed).
|
||||
- **Config edits need a restart.** `baseUrl`/CORS changes in `~/.paseo/config.json` only
|
||||
take effect after `systemctl --user restart paseo-daemon`. Backups are kept beside the
|
||||
config (`config.json.bak-20261010-corsfix`, `config.json.bak-20260809-codex-fix`).
|
||||
- **Cosmetic CLI error while the daemon is healthy (unresolved 2026-10-10).** When a
|
||||
`daemon.get_status.request` takes ~2.2 s the CLI prints
|
||||
`daemon detail request to 0.0.0.0:6767 failed` even though `127.0.0.1:6767` returns
|
||||
HTTP 200. Verify with the health checks above before treating a single such line as an
|
||||
outage.
|
||||
- **Pairing payloads are credentials.** The `#offer=…` URL and `~/.paseo/daemon-keypair.json`
|
||||
carry the daemon key — never paste them into the wiki or a shared channel.
|
||||
|
||||
## Related
|
||||
- [[systems/hermes-agent]]
|
||||
- [[systems/terminal-backend]]
|
||||
- [[infrastructure/network-map]]
|
||||
Reference in New Issue
Block a user