AI agent mission control that refuses to fork upstream

What it does

Hermes Workspace is a React/TypeScript interface that consolidates the Hermes Agent ecosystem into one browser tab. It offers real-time chat with tool-call rendering, a Monaco-backed file browser, a cross-platform PTY terminal, memory search and editing, and a skills marketplace. Point it at any OpenAI-compatible backend and it works as a chat client; connect the full Hermes Agent gateway and dashboard and it unlocks sessions, skills, jobs, and multi-agent swarm dispatch.

The interesting bit

The project is built around a “zero-fork” philosophy: it runs against vanilla NousResearch/hermes-agent and falls back to Workspace-native Swarm dispatch when the dashboard mission API is absent, so upstream updates should not break your UI. The Swarm Mode turns the workspace into a live control plane where persistent tmux workers keep context across tasks, role-based routing assigns builders, reviewers, and QA lanes, and a byte-verified review gate blocks release-branch PRs until agents sign off.

Key highlights

• Persistent tmux-backed agent workers with role-based dispatch (builder, reviewer, docs, research, ops, triage, QA, lab)
• Capability gates that render clean placeholders instead of mid-action crashes when upstream endpoints are missing
• PWA support with Tailscale access, effectively turning the web UI into a native-feeling app across your tailnet
• Auth middleware on every route, CSP, path-traversal guard, and fail-closed remote bind
• 2,000+ skills catalog with origin badges, filters, and source paths, plus an MCP marketplace and local config fallback

Caveats

• Advanced features (memory, skills, swarm dispatch, Conductor missions) require the Hermes Agent gateway and dashboard; a generic OpenAI backend limits you to chat and basic tooling.
• Swarm Mode’s autonomous PR lanes and review gates assume you are already running the full Hermes Agent infrastructure, so the “zero-fork” label applies to the UI code, not your server stack.

Verdict

Grab it if you are running Hermes Agent and want a polished, all-in-one control surface instead of juggling CLI tabs. If you are not using the Hermes/Nous stack, most of the orchestration and swarm features remain locked behind upstream APIs, leaving you with a solid chat-and-terminal UI.