Nous Research launches Hermes Desktop public preview for macOS, Windows, and Linux

• Nous Research moved Hermes Agent into NousResearch's Hermes Desktop announcement, a native desktop app now in public preview for macOS, Windows, and Linux, with the official landing page listing macOS 12+, Windows 10/11, and Linux distro support on the Hermes Desktop page.
• Setup now has two cleaner on-ramps: NousResearch's Portal post adds a hermes portal switch path to Nous's hosted model catalog, while Ollama's integration post points to Ollama's Hermes guide for both local and cloud-backed models.
• Remote use shipped rough edges and fixes on day one: Teknium's remote gateway repost showed Hermes Desktop connecting to a cloud agent through Settings → Gateway, and Teknium's Tailscale fix post says Nous pushed an update for GUI remote connections over Tailscale.
• The Windows story is bigger than a wrapper app. NousResearch's Windows support post and the Windows native guide describe Hermes as running natively on Windows, with Hermes Desktop acting as a thin GUI installer over the same local runtime as the CLI.

You can grab the public preview desktop app, skim the quickstart, check Nous Portal pricing and model access, and wire it into Ollama's local or cloud model flow. The interesting bit is not just a GUI. The docs tie the app to Hermes' existing memory, gateway, and provider stack, so the desktop client lands as a new surface on top of the same agent runtime.

Nous framed Hermes Desktop as "everything you love about Hermes, now native on your machine" in NousResearch's launch post. The official desktop page puts the scope in plain terms: desktop builds for macOS, Windows, and Linux, plus the same cross-surface agent model Hermes already uses across Telegram, Discord, Slack, WhatsApp, Signal, email, CLI, and the desktop UI.

The feature list on that page is broad, but it clusters into a few concrete buckets:

• Connect: one agent across chat surfaces
• Remember: persistent memory and auto-generated skills
• Schedule: unattended jobs through the gateway
• Delegate: subagents with isolated conversations and terminals
• Search: web search, browser automation, and vision tools

That makes the preview feel less like a stripped-down chat shell and more like a packaged front end for the existing Hermes stack.

Nous used the desktop launch to simplify provider setup from both directions. According to NousResearch's Portal announcement, running hermes portal switches Hermes over to Nous Portal, and the Portal page says paid tiers bundle credits, hosted tool usage, and access to 300-plus models.

Ollama went the other way, wiring Hermes into local inference. In Ollama's integration docs, ollama launch hermes can install Hermes if needed, point it at http://127.0.0.1:11434/v1, and set either a local or cloud model as primary. Ollama's post explicitly says Hermes Desktop works with Ollama for both local and cloud models.

The official quickstart fills in the operating assumptions:

• hermes setup for the default first run
• hermes model if you already know your provider
• hermes gateway setup after base chat works
• custom endpoint configuration for local or self-hosted models
• a recommended minimum of 64K context for models handling multi-step tool calls and memory

Day-one posts made clear that desktop does not mean local-only. In Teknium's repost of a cloud-agent setup, Hermes Desktop can attach to a remote gateway by pasting a URL into Settings → Gateway → Remote gateway, which turns the app into a client for an already-running agent.

A few hours later, Teknium's update said Nous had pushed a fix for users who were trying to connect the Hermes Agent GUI over Tailscale. That is a small release note, but it says a lot about how people are already using this preview: not just as a laptop chatbot, but as a control panel for agents running elsewhere.

The Windows docs add a useful detail the launch posts only hint at. In the official Windows native guide, Hermes runs without WSL, Cygwin, or Docker, installs into %LOCALAPPDATA%\hermes, and does not require admin rights.

The more interesting detail is how Hermes Desktop fits into that stack. The same guide says the desktop installer is a thin GUI that calls install.ps1 underneath, provisioning Python through uv, Node, PortableGit, and the rest of the local runtime, then sharing the same data directory as a PowerShell-installed hermes CLI after first run.

That means the app is not a separate consumer shell bolted onto a cloud service. On Windows, at least, the docs describe it as another entry point into the same local Hermes environment.