Jonathon's AI Wiki

Hermex — Native SwiftUI iPhone Client for Hermes Agent (uzairansaruzi, Swift, 39★)

4 min read

Source: raw/reddit-1ulucuw.md — r/hermesagent “Hermex is now open-source” (OP u/uzairansar, score 70, 30 comments, posted 2026-07-02). Repo: https://github.com/uzairansaruzi/hermex (MIT license; stats below verified via a direct repo fetch on 2026-07-02, not taken on faith from the announcement post alone).

Hermex is a native SwiftUI iPhone app for controlling a self-hosted Hermes agent, open-sourced 2026-07-02 by GitHub user uzairansaruzi (posted to Reddit by the same person as u/uzairansar). The author frames it as “a mobile cockpit for an AI agent that lives on a machine you control” — the app is a pure client that points at a hermes-webui server the user already runs, so agent computation and data stay on hardware the user controls. It is an independent, unofficial client, not affiliated with the upstream hermes-webui project, and it closes a real gap in this wiki’s Hermes client-app coverage: none of Hermes Console, Herm-TUI, Hermes Desktop (dodo-reach SSH client), or Hermes Desktop (official Nous app) is a native mobile client. ^[the “closes a gap” framing is this wiki’s comparative judgment against the existing client-app cluster, not a claim made in the source]

Key Takeaways

  • Native SwiftUI, not a web wrapper. Swift is 98.4% of the codebase; targets iOS 18+; requires Xcode 26+ to build locally; dependencies resolved via Swift Package Manager.
  • MIT-licensed and genuinely early but active. 39 stars / 9 forks at time of ingest (2026-07-02), verified via a direct repo fetch rather than taken on faith from the announcement.
  • Independent, self-hosted-only client. Requires the user to already be running their own hermes-webui server — Hermex has no server component of its own and is explicitly not affiliated with or endorsed by the upstream hermes-webui project.
  • Feature set: real-time streaming chat, session management/browsing, model/provider switching, task scheduling, skill browsing, workspace file exploration, agent memory and usage analytics, file/image attachments.
  • Operationally more mature than a weekend prototype. The repo ships documentation for dev workflow, a security policy, TestFlight operations, and contract testing against upstream hermes-webui — the last of these signals the author is actively tracking compatibility drift against the server project rather than assuming a fixed API surface.
  • First native mobile client tracked in this topic. Existing hermes-agent client-app coverage was an Obsidian plugin, a terminal TUI, and two desktop apps (one third-party SSH client, one official Nous app) — no phone client until this one.

Try It

  1. Clone the repo: git clone https://github.com/uzairansaruzi/hermex.
  2. Open the project in Xcode 26+ (required — the repo targets iOS 18+ and won’t build on older Xcode). Let Swift Package Manager resolve dependencies on first build.
  3. Have a self-hosted hermes-webui server already running and reachable — Hermex is a client only, it does not stand one up for you.
  4. Point the app at that server’s address and confirm real-time chat streams correctly before relying on it for session management or task scheduling.
  5. Read the repo’s security policy and dev-workflow docs before distributing it further (e.g. via TestFlight) or connecting it to a production agent.
  6. Check the repo’s contract tests against your installed hermes-webui version — the author’s own testing setup suggests version drift between client and server is a known risk area.

Open Questions

  • No hands-on wiki verification yet. This article is sourced entirely from the announcement post plus a repo-metadata fetch (license, stars, forks, language mix) — not from actually running the app. Day-to-day reliability, streaming performance, and UI quality are unverified here.
  • hermes-webui version compatibility matrix. The source doesn’t specify which hermes-webui versions are supported; the repo’s own contract-testing setup implies this is tracked upstream but the specifics weren’t captured in the raw source.
  • Distribution plans. TestFlight is mentioned as part of the repo’s documented ops, but whether there’s an open TestFlight beta or App Store plans isn’t specified in the source.

Graph View

Backlinks