Hermes setup
An always-on local AI orchestrator with long-term memory.
The operating environment behind everything else: a resident orchestrator that routes tasks to LLM workers, runs scheduled agents (like the weekly Field Monitor that feeds this site’s news), and maintains long-term memory — nightly ingestion of work sessions and notes into a searchable store. The design principle: the orchestrator plans and verifies; disposable workers execute.
Its panel is where the small watches surface. One of them reads my public repos once a day and says what is new since yesterday — a star, an issue, a question somebody asked and is waiting on. Publishing something is easy to forget afterwards.
- AI lane limits and live rows read from the registry
- Portal agents card shows every Foreman lane
- One shared lockd gate for every Hermes job
- Hindsight memory moved to plexmaster
- Foreman becomes the primary work status in portal
- Hermes portal scaffolded with Hindsight and Obsidian
- My agent fixed a database error by deleting the database
Worked. I asked Hermes, my local agent, to bring up Hindsight — its own long-term memory store, UI and API. It found the blocker and acted…