This project provides a visual UI layer for the Hermes agent orchestration system, addressing the complexity of managing multiple agents. It offers a browser-based dashboard for real-time visibility and control over agent fleets, making complex multi-agent workflows legible and directable for Hermes users. The benefit is a centralized, intuitive interface that replaces scattered terminal sessions with a clear operational overview.

How It Works

The Orchestration War Room acts as a visualization and coordination layer atop Hermes, leveraging its native multi-profile delegation and Kanban task board primitives. It shells out to the Hermes CLI, sharing the process namespace, and uses Server-Sent Events for live updates on agent activity and task progress. Its advantage lies in transforming Hermes' invisible background orchestration into a transparent, interactive dashboard, allowing users to monitor agent thought processes, tool calls, and delegation chains directly from a browser.

Quick Start & Requirements

• Prerequisites: Hermes installed on the host, Node.js 22+, and the Hermes dispatcher (hermes gateway) running.
• Production Install: Download the latest release tarball from GitHub Releases, extract, and run with Node.js: HERMES_HOME=$HOME/.hermes NITRO_HOST=127.0.0.1 NITRO_PORT=3000 node .output/server/index.mjs.
• Development Install: Clone the repository, run pnpm install, and then pnpm dev for a hot-reloading development server.
• Persistence: For development, tmux is recommended to keep sessions alive across logouts.
• Links: GitHub Releases

Highlighted Details

• Three-Page Interface: War Room (live operations, chat, Kanban board), The Team (agent roster for management), and Missions (historical archive).
• Agent Management: UI allows hiring, firing, retraining (editing SOUL.md, skills, tools, model), and deactivating agents.
• Technology Stack: Nuxt 4 frontend with Nuxt UI and Tailwind CSS, Nuxt Nitro backend, Dicebear Notionists avatars.
• Performance: Production builds offer significantly faster cold starts (~300ms) and lower idle memory usage (~80MB) compared to the development server.

Maintenance & Community

• Release Process: Automated releases via semantic-release on pushes to the main branch.
• Community: No specific community links (Discord, Slack) or roadmap details are provided in the README.

Licensing & Compatibility

• License: The repository's license is not specified in the README.
• Compatibility: Requires Hermes and Node.js 22+.

Limitations & Caveats

• Dependency: Heavily reliant on a correctly configured and running Hermes instance, including its dispatcher.
• License Uncertainty: The absence of a specified license poses a significant adoption blocker for many use cases.
• Development Session Persistence: Development server sessions are tied to the terminal and require external tools like tmux for persistence.