Hermes Agent Pixel — Development skill for Claude Code

Hermes × Pixel Agents

**Watch your Hermes agent work, live, as an animated character in a pixel-art office.**


Hermes (`nemotron-3-super-120b`) running in the TUI on the left while its character moves through the office on the right — a teammate already seated at the meeting table.

This project makes [NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent) show up inside the [Pixel Agents](https://github.com/pixel-agents-hq/pixel-agents) office UI: every Hermes session becomes a character that types when it writes, reads when it searches, spawns **teammates** when it delegates subagents, and raises a "waiting" bubble when a turn ends. Hermes and Claude Code can run in the **same office at the same time**.

**About** — A bridge between Hermes (a self-improving Python agent) and Pixel Agents (a "watch your AI agents like The Sims" UI). Hermes wasn't supported by Pixel Agents — it has no transcript file and runs concurrent tools + real subagents. This adds a push-based Hermes provider so you can run `hermes` and literally see which agent is doing what, in real time, in the browser.

---

How it works

Hermes  (pixel_observer plugin)                 Pixel Agents server (standalone)
  hooks: session / tool / subagent  ──HTTP──▶   POST /api/hooks/hermes  (Bearer token)
  reads ~/.pixel-agents/server.json             └─▶ HermesBridge ─▶ AgentStateStore
  for {port, token}; fire-and-forget                 └─▶ WebSocket ─▶ office UI

• No Hermes core changes. The Hermes side is a normal plugin that registers lifecycle hooks (pre_tool_call, subagent_start, post_llm_call, …) and forwards them. It works for every Hermes frontend — CLI, TUI, gateway — not just ACP.
• No new Pixel Agents protocol. HermesBridge writes the existing AgentStateStore, emitting the same WebSocket messages the webview already renders. It shares that store with