Hermes Desktop OS1: A Native macOS Interface for Hermes Agent on Orgo Cloud

What Hermes Desktop OS1 Does and Who It Targets

OS1 is a native macOS application built on top of the upstream Hermes Desktop fork. It adds first-class support for Orgo cloud computers, an infrastructure provider that gives each workspace one or more Linux VMs accessible through a platform API and per-VM WebSocket terminals.

The target user manages an AI agent running on a cloud computer rather than on a local machine. Instead of opening a browser, pasting SSH credentials into a terminal, and tracking tasks across separate tools, OS1 consolidates everything: cloud computer provisioning, agent installation, session browsing, kanban boards, file editing, skill management, and cron job scheduling in one focused window.

The description says the product is from OS1 by Element Software, powered by Orgo, forked from Hermes Desktop. The inspiration is stated explicitly in the README: the 2013 film Her, which is reflected in the design language (warm coral on cream, thin type, calm motion). SSH-connected hosts from the upstream Hermes Desktop are still supported, so existing SSH workflows continue without change.

Installing the App on macOS

The README instructions are to download the latest OS1.app.zip from the GitHub Releases page, unzip it, drag OS1.app into /Applications, and launch. The repository metadata shows no GitHub releases at the time of this review, so check the current state of the Releases page before following that path.

The binary is a universal build that runs on both Apple Silicon and Intel Macs. It is ad-hoc signed with an explicit designated requirement for com.elementsoftware.os1, which gives macOS a stable local app identity so privacy grants such as microphone access survive rebuilds. It is not notarized by Apple. On first launch, macOS may display a warning that the developer cannot be verified. The README instructs users to right-click the app, choose Open, and confirm.

For developers who prefer to build from source:

./scripts/build-macos-app.sh

The bundle lands at dist/OS1.app. The Swift test suite can be run with:

swift test

The repo uses Package.swift, so Swift Package Manager handles all dependencies.

Connecting to Orgo Cloud Computers

The setup flow for a cloud computer takes seven steps according to the README. Open the Connections tab, click Add Host, switch the transport picker to Orgo VM, paste the API key from orgo.ai/settings/api-keys, and click Verify and Save. The key persists in the macOS Keychain. Then pick a workspace, pick a computer or create one (defaults: Linux, 8 GB RAM, 4 CPU, 50 GB disk), and save.

The first time the workspace opens, if the Hermes Agent is not installed on the VM, the Overview screen shows an install banner. One click runs the official Hermes Agent installer on the VM. The README says it takes roughly 60 to 90 seconds, and the rest of the app remains usable during installation.

HTTP operations use a routing hierarchy. The app tries the platform proxy at https://www.orgo.ai/api/computers/{id}/... first. On a 5xx response that resembles a routing failure, it falls back to the direct VM URL at https://<fly_instance_id>.orgo.dev/... using the VNC password as bearer. Long-running operations skip the proxy entirely because its 30-second timeout would trip first.

The WebSocket Terminal

The terminal connects directly to a WebSocket endpoint at wss://<fly_instance_id>.orgo.dev/terminal?token=<vncPassword>. Bytes stream in real time. Terminal resize works. Output and history reflow cleanly when the window is resized.

This is a real interactive shell, not a command-runner that sends one command at a time. The README describes it as an interactive shell over the per-VM terminal websocket.

For SSH connections, the transport picker switches to SSH rather than Orgo VM. An alias or hostname, optional user and port, and optional Hermes profile are all that is required. The host needs python3 on the non-interactive SSH PATH and Hermes already installed.

Voice Mode via OpenAI Realtime

OS1 includes a WebRTC voice mode using OpenAI Realtime calls with gpt-realtime-2. The app starts a loopback session endpoint when the boot animation completes. The bottom-left Voice row toggles the live voice connection.

The voice mode also exposes Orgo MCP tools to the model as Realtime function tools. OS1 starts the MCP server locally, reads tools with tools/list, registers them with session.update, and forwards model tool calls back to tools/call. Orgo credentials stay in the Swift app and are never sent to the browser.

For development or custom configurations, the README documents these environment overrides:

OS1_ORGO_MCP_JS_PATH="/absolute/path/to/dist/index.js"
OS1_ORGO_MCP_PACKAGE="@orgo-ai/mcp"
OS1_REALTIME_ORGO_TOOLSETS="core,screen,files"
OS1_REALTIME_ORGO_DISABLED_TOOLS="orgo_upload_file"
OS1_REALTIME_ORGO_READ_ONLY="true"

The shell and admin toolsets are opt-in through OS1_REALTIME_ORGO_TOOLSETS. The README notes that these should only be enabled for agents and computers the developer is comfortable letting a voice model operate.

An OpenAI key is required for voice mode. Set it in the Providers tab to save it in the macOS Keychain, or pass OPENAI_API_KEY as an environment variable when running from source:

OPENAI_API_KEY="sk-..." swift run OS1

Platform Constraints and Maintenance

OS1 runs on macOS 14 or newer only. There is no Linux version, no Windows version, and no web version. The README states the macOS version requirement directly.

Live integration tests that hit a real cloud computer are skipped by default. To run them:

ORGO_LIVE_TESTS=1 \
ORGO_API_KEY="sk_live_..." \
ORGO_DEFAULT_COMPUTER_ID="<uuid>" \
swift test --filter OrgoTransportLiveTests

The last push to this repository was on 2026-05-09. It has no GitHub releases at the time of this review. The project is a fork, so the upstream Hermes Desktop repository may receive updates that are not yet reflected here. The MIT license allows teams to fork and customize, but there is no documented path for submitting changes back to this fork.

Hermes Desktop OS1 Versus General Terminal and SSH Apps

Tools like Warp or Tabby are general-purpose terminals with SSH support. They provide excellent command-line experiences and can connect to any SSH host, but they have no concept of an AI agent running on the connected host. Managing sessions, kanban tasks, skill files, or cron jobs for an agent requires switching to other tools or browser tabs.

OS1 makes the opposite trade-off. It sacrifices general-purpose terminal flexibility in exchange for agent-specific views built into the same window. The kanban board tracks what the agent is working on. The sessions browser with full-text search makes it easier to find a specific agent run. The skills viewer shows what skills are installed on the agent. None of these exist in a general terminal app.

The practical constraint is that OS1 is useful only if the agent in question is Hermes Agent running on Orgo infrastructure (or on an SSH host that already has Hermes installed). Teams using other agents, other cloud providers, or other orchestration systems gain nothing from OS1.

Editorial conclusion

macOS users who manage Hermes Agent on Orgo cloud computers get a purpose-built workspace in OS1: terminal, kanban, file editor, and cron in one native app rather than a mix of browser tabs. The one-click install button is a real time-saver on fresh VMs. Linux and Windows are not supported; the app is macOS 14+ only. The binary is ad-hoc signed rather than notarized by Apple, which means the first launch requires a right-click open to bypass macOS Gatekeeper. The metadata for this repository shows no GitHub releases despite the README instructing users to download from the Releases page; verify the current state of releases before following those instructions. The last push was on 2026-05-09. The MIT license permits forking and redistribution.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. nickvasilescu/hermes-desktop-os1 on GitHub
4. README