[Feature]: Native desktop/mobile client app

[AustinDZG]

Feature Description

A native desktop/mobile client app for Hermes Agent that interacts directly with the local Gateway/API Server, without relying on third-party messaging platforms as intermediaries.

Motivation

Current interaction methods each have limitations imposed by the platforms themselves:

• URLs in tool output get truncated, making links unclickable
• Message length limits force HTML file workarounds
• Interactive approval buttons degrade to plain text across versions
• Gateway restarts disconnect the session
• Technical config must be done via CLI separately

A native client would provide a purpose-built interface for AI agent interaction.

Proposed Solution

Cross-platform native app (Tauri/Flutter) reusing existing API Server + Gateway:

• Desktop: Windows/macOS/Linux
• Mobile: iOS/Android
• Shared sessions, skills, memory with CLI/Web UI
• Native push notifications, file handling, proper URL rendering

[alt-glitch]

Related to #11911 (native mobile app with voice calling) and #15774 (native Windows desktop app). This is a broader request encompassing both desktop and mobile with more technical specificity (Tauri/Flutter, reusing existing API Server + Gateway).

[realfishsam]

#52673

[HangbinYang]

Hi everyone, I’m the developer of HermesPilot, a native mobile client for Hermes Agent.

It’s designed for people who already run Hermes Agent locally or on their own machine and want a smoother way to access it from their phone.

Download:

• iOS App Store: https://apps.apple.com/app/hermespilot/id6765671330

What it does:

• Connects your phone to your own Hermes Agent through a local companion service called Hermes Link
• Supports pairing by QR code or manual pairing code
• Lets you chat with Hermes Agent from a native mobile interface
• Supports local-network access when available, with relay fallback for remote access
• Keeps multiple Links / machines manageable from the app
• Includes conversation management and mobile-friendly message rendering
• Supports push notifications for background task updates, where available
• Does not replace Hermes Agent itself; it is only a mobile client and connection layer for your existing Hermes setup

Basic setup:

npm install -g @hermespilot/link
hermeslink pair

[lujun2508]

Adding another user report in support of this request. The need is not only mobile chat: operators want to manage a long-running Hermes instance away from the desktop. A useful mobile MVP should include:

• shared/continued sessions with the desktop and gateway;
• push notifications for completed tasks, failures, and pending approvals;
• review of pending Memory/Skill writes, including approve, reject, and edit;
• batch review with risk/confidence/model rationale visible;
• basic Cron and Gateway status/management;
• secure remote connection to the user’s own Gateway/API Server.

This becomes especially valuable as write-approval queues grow: a mobile review inbox can let users handle only the uncertain cases without waiting to return to a desktop.