hermes-operator-stack

Generated source view for the actual executable productivity/hermes-operator-stack skill. The durable routing article is Agent Operations Skills. Source: skills/productivity/hermes-operator-stack/SKILL.md

Runtime Source

Bundled Resources

These files are part of the executable skill folder and must be preserved with the skill source.

Description

Audit and configure Kevin's Hermes Mac Mini operator stack: Hermes memory providers, Hindsight, Honcho, Telegram/Discord/WhatsApp gateway, launchd or Hermes cron jobs, agent-browser browser automation, ACP/SSH coding workers, Obsidian/qmd writeback, and information-intake monitors. Use when the user asks about Hermes configuration, personal agent OS, Mac Mini agent stack, Hindsight, Honcho, Hermes Desktop, Telegram gateway, launchd monitors, agent-browser enforcement, software-factory loops, or persistent agent memory.

Skill Source

---
name: hermes-operator-stack
description: "Audit and configure Kevin's Hermes Mac Mini operator stack: Hermes memory providers, Hindsight, Honcho, Telegram/Discord/WhatsApp gateway, launchd or Hermes cron jobs, agent-browser browser automation, ACP/SSH coding workers, Obsidian/qmd writeback, and information-intake monitors. Use when the user asks about Hermes configuration, personal agent OS, Mac Mini agent stack, Hindsight, Honcho, Hermes Desktop, Telegram gateway, launchd monitors, agent-browser enforcement, software-factory loops, or persistent agent memory."
---

# Hermes Operator Stack

## Overview

Use this skill to keep Kevin's persistent Hermes setup coherent across machine, model, memory, browser, messaging, cron, and wiki writeback layers.

## Required Reads

Read these before making recommendations or edits:

1. `wiki/architecture/hermes-mac-mini-agent-os.md`
2. `wiki/tools/hermes-agent.md`
3. `wiki/architecture/hermes-harness.md`
4. `wiki/tools/hindsight.md`
5. `wiki/tools/honcho.md`
6. `wiki/tools/agent-browser.md`
7. `wiki/tools/agent-client-protocol.md`
8. `wiki/meta/capability-routing-map.md`

## Audit Workflow

Check the stack in this order:

1. **Runtime** - Hermes is the persistent operator; Codex, Claude Code, OpenCode, and local models are workers, not the source of truth.
2. **Memory** - Hindsight is the active Hermes memory provider when long recall is needed. Honcho is the profile/modeling layer via MCP/SDK or a separate profile. Kevin-Wiki/qmd remains canonical memory.
3. **Browser** - agent-browser is the default browser automation surface. Use logged-in Chrome for auth-heavy flows. Use Playwright only for committed regression tests or existing repo test suites.
4. **Interfaces** - Telegram topic threads are the primary ops console; Hermes Desktop over SSH is the rich local console; Discord, WhatsApp, terminal, and ACP are secondary surfaces.
5. **Schedulers** - Use no-agent launchd or Hermes cron for deterministic monitors. Wake Hermes only when summarization, ranking, triage, or drafting requires reasoning.
6. **Intake** - Route feeds, Raindrop, YouTube, X/Last30Days/BirdClaw, LinkedIn, Economist, and FT through summaries first, deletion second, deep engagement selectively.
7. **Writeback** - Durable facts, preferences, failed guesses, decisions, and reusable workflows must land in wiki pages, skills, automations, or logs.

## Preferred Commands

Use only when Hermes or agent-browser is installed in the target environment:

```bash
hermes config check
hermes plugins
hermes memory setup
hermes acp --check
hermes send --list
agent-browser doctor
agent-browser batch "open https://example.com" "snapshot -i" "close"
```

For repo changes in `kevin-wiki`, close the loop with:

```bash
npm run skill-registry
npm run routing-doctor
npx tsx scripts/build-index.ts
qmd update
qmd embed
```

## Decision Rules

- Prefer Mac Mini M4 Pro 48GB for the always-on local operator box; treat older Apple Silicon as a prototype lane.
- Keep model routing pluggable. Do not bake one model into the architecture without an eval or local availability check.
- Keep Hindsight and Honcho separate unless Hermes explicitly supports a combined provider mode. One active memory provider means one active slot.
- Keep qmd/Obsidian as the durable knowledge repository. Runtime memory is cache and recall until written back.
- Use `hermes send` or no-agent cron for script output. Use an agentic cron only when the message content requires reasoning.
- Ask before enabling account-mutating browser actions, adding new credentials, or scheduling unattended paid model calls.

---

Timeline

• 2026-07-15 | Generated a browseable source page from the actual executable skill file. Source: skills/productivity/hermes-operator-stack/SKILL.md