Hermes Studio
A self-hosted workspace for running Hermes Agent chats, workflows, channels, and local runtime operations.
Per-dimension scores and reasoning
Evidence shows: README describes authentication mechanisms (token, username/password, default credentials admin/123456) and prompts users to change default password; sensitive data (e.g., API keys) stored in ~/.hermes/.env, and claims keys remain server-side. However, no code-level evidence for least privilege, user confirmation, or data flow transparency. Dependency security: package.json lists dependencies but no vulnerability scanning or audit evidence. External effects: README mentions auto-update, MCP injection, but no user confirmation. Rollback: update commands exist but no rollback mechanism. Source attribution: repository has clear author and license, but publisher unverified. Thus, most criteria score 1 because evidence is present but thin or asserted.
Evidence shows: README and package.json descriptions are consistent, test files exist, indicating some consistency. Dependency availability: broad dependency list but no lockfile or integrity checks. Failure messages: tests cover error handling but no user-friendly error message evidence. Thus, self-consistency scores 2, others 1.
Evidence shows: README describes multiple usage scenarios (desktop, npm, Docker) and provides environment variables and CLI commands, indicating adaptability to various environments. Capability boundaries: README lists features and non-goals (e.g., voice dialogue doc) but not detailed limitations. Trigger precision: no specific trigger conditions. Thus, audience and scenarios, capability boundaries, environment fit score 2, trigger precision 1.
Evidence shows: README is well-structured, provides installation instructions (desktop, npm, Docker), license is BSL-1.1, version in package.json. Naming stability: project renamed from Hermes Web UI to Hermes Studio, may affect stability. Examples and FAQ: README provides quick start but no FAQ. Known limitations: only mentioned in voice dialogue doc. Versioning changelog: no CHANGELOG. Maintenance responsibility: GitHub Actions workflows exist but no explicit maintainers. Thus, information architecture, install notes, license score 2, others 1.
Evidence shows: README describes rich features, output usability: provides various output formats (e.g., file previews). Marginal value: multi-platform integration and automation may add value. Cost-benefit: no performance or resource usage data. Thus, output usability and marginal value score 2, cost-benefit 1.
Evidence shows: Some claims in README are supported by tests (e.g., API tests), but not all claims are traceable. Cross-source corroboration: only internal repository evidence. Fact-inference separation: not clearly distinguished. Thus, all criteria score 1.
- Default credentials admin/123456 pose a security risk; users must change them immediately.
- Dependency security lacks audit evidence; recommend checking for vulnerabilities.
- Publisher is unverified; assess supply chain risks carefully.
- Project rename may affect stability of documentation and commands.
What does this agent do, and when should you use it?
Hermes Studio combines a desktop app, local runtime integration, and web console for Hermes Agent, with a Vue 3 frontend and Koa BFF server. Its Socket.IO `/chat-run` path streams conversations through the Hermes agent bridge into the Hermes Agent runtime. The dashboard manages local sessions, profiles, providers, models, credentials, files, logs, and runtime settings alongside agent chat. It also includes visual workflows, scheduled jobs, Kanban, group chat, a web terminal, voice features, and runners for Claude Code and Codex. It is distributed for Windows, macOS, and Linux, and can also be self-hosted through the `hermes-web-ui` npm CLI or Docker Compose. This is a fit for users who want a local control plane around Hermes profiles while operating multiple models and messaging channels.
A browser connects to the Koa BFF through Socket.IO /chat-run; the BFF starts or connects to the Hermes agent bridge, which invokes the Hermes Agent runtime, Hermes CLI, and selected profile. The dashboard manages profile config.yaml, auth.json, a local Web UI SQLite session database, and upload storage; it can discover provider models at /v1/models and manage OpenAI-compatible providers, model visibility, and OAuth/device flows. It browses and operates on local, Docker, SSH, and Singularity filesystems, downloads artifacts by resolved path, and previews generated HTML, PDF, DOCX, PPTX, XLSX, CSV, images, Markdown, and source files. It can execute Vue Flow workflows, cron jobs, Kanban tasks, and Socket.IO group-chat rooms. The desktop package also exposes managed MCP toolsets through hermes-studio-mcp [api|browser|devices|use] and includes a node-pty/@xterm/xterm web terminal.
- A local Hermes Agent user who needs persistent chat sessions, tool-call traces, and previews of generated files can run those conversations from one desktop or browser workspace.
- An administrator maintaining Telegram, Discord, Slack, WhatsApp, and other channel integrations can configure channel behavior and credentials per Hermes profile in one console.
- A team that needs Hermes, Codex, and Claude Code to follow approval gates, loops, and success/failure branches can build and replay those executions on the Vue Flow canvas.
- A developer retrieving agent artifacts from local, Docker, SSH, or Singularity workspaces can browse, edit supported text files, download path-resolved outputs, and attach workspace files to chat.
- An operator tracking local agent activity can review input/output tokens, estimated cost, cache-hit rate, model distribution, and a 30-day usage trend.
What are this agent's strengths and limitations?
- It unifies chat, profiles, models, channels, sessions, file handling, and runtime logs in one local control plane rather than providing chat alone.
- Its file operations cover local, Docker, SSH, and Singularity backends, with path-based artifact downloads and previews for many generated document types.
- Visual workflows retain frozen run snapshots, node conversations, edge decisions, and evidence playback—not just a graph definition.
- It offers desktop, npm CLI, Docker Compose, and managed MCP delivery modes for local and self-hosted use.
- Chat execution depends on the Hermes Agent runtime and bridge; without a source checkout, it relies on the installed
hermescommand's Python environment or system Python. - The documented bootstrap login is
admin/123456, so operators must change it and protect tokens, JWT secrets, and provider credentials. - Model discovery, OAuth/device authorization, and
/v1/modelsretrieval depend on each provider's endpoint, credentials, and compatibility. - The real-time voice stage explicitly does not provide simultaneous full-duplex listening and speaking, telephony, or always-on wake-word listening.
How do you install or deploy this agent?
Install and start the npm package:
npm install -g hermes-web-ui
hermes-web-ui startOpen http://localhost:8648. The first run generates an auth token unless AUTH_TOKEN is supplied. For username/password login, the bootstrap account is admin / 123456; change it after signing in. For Docker, run WEBUI_IMAGE=ekkoye8888/hermes-web-ui docker compose up -d and open http://localhost:6060. Backend chat requires a discoverable Hermes Agent source checkout containing run_agent.py; otherwise it falls back to the Python environment behind the installed hermes command, then system Python.
How do you use this agent?
Start the server, choose an authorized Hermes profile, and configure or discover providers and models under Models; complete the relevant OAuth/device flow when required. Create a session and send a message to receive streamed output and tool details over /chat-run, with uploads or workspace files attached as needed. For automation, add Hermes, Codex, or Claude Code nodes to a workflow canvas, configure edges, conditions, and approvals, then run or rerun it; cron schedules are configured under Scheduled Jobs. To expose a focused managed MCP surface, invoke hermes-studio-mcp api, browser, devices, or use.
How does this agent compare with similar options?
Compared with using the Hermes Agent CLI directly, Hermes Studio adds web/desktop chat, a session database, visual workflows, channel configuration, file UI, and runtime monitoring on top of the same Hermes profiles and runtime; it does not replace the underlying Hermes Agent runtime.
FAQ
Where does it keep local data?
HERMES_WEB_UI_HOME (default ~/.hermes-web-ui). Hermes data uses the platform-specific HERMES_HOME location.Can it use a custom model service?
/v1/models; actual availability depends on that provider's endpoint and credentials.How does first-run Docker authentication work?
./hermes_data/hermes-web-ui/.token.Can another service manage the Hermes gateway?
HERMES_WEB_UI_MANAGED_GATEWAY=0 and use hermes gateway start, or set HERMES_WEB_UI_DISABLE_GATEWAY_AUTOSTART to skip automatic gateway checks and startup.