AI News HubLIVE
站内改写3 min read

Nous Research Releases Hermes Desktop: A Native Cross-Platform Front End for Hermes Agent v0.15.2 with Streaming Tool Output

Nous Research has released Hermes Desktop in public preview, a native application for macOS, Windows, and Linux that provides a graphical interface for the open-source Hermes Agent. It shares the same agent core, configuration, API keys, sessions, skills, and memory with the CLI and gateway, offering no-terminal operation with streaming responses, preview pane, file browser, voice I/O, and settings UI.

SourceMarkTechPostAuthor: Michal Sutter

Nous Research has released Hermes Desktop in public preview. It is a native application for macOS, Windows, and Linux. It gives the open-source Hermes Agent a graphical interface. Until now, users ran Hermes through a CLI and messaging gateways. The current build is Hermes Agent v0.15.2.

Per Nous Research’s documentation, the desktop reuses the same agent core. It shares configuration, API keys, sessions, skills, and memory with the CLI and gateway. The desktop is another surface over one agent, not a fork.

What is Hermes Desktop

Hermes Agent is an autonomous AI agent. It is not a coding copilot tied to an editor. It runs tasks, calls tools, and keeps state across sessions. An agent here means a model that plans, acts, and observes in a loop.

Hermes Desktop is a GUI on top of that same agent core. It needs no terminal to use. The window shows streaming responses and live tool activity. A right-hand pane previews web pages, files, and tool outputs. It also includes a file browser, voice input and output, and a settings UI.

Sessions are shared across surfaces. A conversation started in the desktop resumes in the CLI or TUI. The reverse also works, because state is not duplicated.

macOS and Windows offer direct installers. Linux installs from the terminal on any distribution. An install script with an --include-desktop flag builds the app against an existing install.

The Closed Learning Loop

Nous research team describes Hermes as having a closed learning loop. This is what separates it from a simple chat wrapper. After a complex task, the agent writes a reusable skill. Those skills then self-improve during later use.

Memory is persistent and agent-curated, with periodic nudges to save knowledge. Cross-session recall uses FTS5 session search with LLM summarization. User modeling runs through Honcho dialectic user modeling. In practice, longer use means more retained context and reuse. Skills follow the agentskills.io open standard.

How It Connects, Schedules, and Sandboxes

Hermes runs across messaging platforms from one gateway. The desktop lists Telegram, Discord, Slack, WhatsApp, Signal, Email, and CLI. You can start a task on one platform and continue on another.

Scheduling uses natural language for reports, backups, and briefings. These run unattended through the gateway on a built-in cron scheduler.

Delegation spawns isolated subagents with their own conversations and terminals. A subagent is a separate worker that handles one job. Python RPC scripts collapse multi-step pipelines into zero-context-cost turns.

Execution is sandboxed. The desktop lists five backends: local, Docker, SSH, Singularity, and Modal. It applies container hardening and namespace isolation. Namespace isolation limits what a running process can see or touch.

Built-in tools include web search, browser automation, vision, image generation, text-to-speech, and multi-model reasoning. Hermes also connects external tools through MCP. MCP is the Model Context Protocol, a standard for tool integration.

Nous Portal and the Tool Gateway

Hermes works with any provider, so API keys are optional. Nous Portal bundles them under one subscription instead. Portal tiers are Free, Plus, Super, and Ultra. Paid tiers include monthly credits and access to 300+ models. They also include built-in tool use.

The Tool Gateway routes several tools through one account. Web search uses Firecrawl and image generation uses FAL. Text-to-speech uses OpenAI and the cloud browser uses Browser Use.

The next evolution of Hermes Agent is here!

Introducing Hermes Desktop: everything you love about Hermes, now native on your machine.

First demoed in Jensen's GTC keynote, it's now in public preview. pic.twitter.com/8ND1k8hyaz

— Nous Research (@NousResearch) June 2, 2026

Strengths and Questions

Strengths:

Native installers remove the terminal requirement for most users

Streaming output and previews make tool calls easier to inspect

Persistent memory and self-improving skills reduce repeated instructions

Model-agnostic design avoids lock-in to a single provider

The MIT license allows audit, self-hosting, and modification

Questions:

The product is in public preview, so expect rough edges

Autonomous memory and scheduling raise oversight and review questions

The Linux desktop still installs through the terminal

Broad capability means a steeper learning curve for beginners

Key Takeaways

Nous Research released Hermes Desktop in public preview, a native macOS, Windows, and Linux app for its open-source Hermes Agent.

The GUI shares one agent core, configuration, API keys, sessions, skills, and memory with the CLI and gateway; sessions resume across surfaces.

It runs no-terminal with streaming tool output, a side-by-side preview pane, file browser, voice I/O, and a settings UI.

Hermes is model-agnostic and MIT-licensed, working with Nous Portal, OpenRouter, OpenAI, or any compatible endpoint.

The current build is Hermes Agent v0.15.2, backed by a closed learning loop, MCP tool support, and five sandbox backends.

Check out the Project here. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us

The post Nous Research Releases Hermes Desktop: A Native Cross-Platform Front End for Hermes Agent v0.15.2 with Streaming Tool Output appeared first on MarkTechPost.