01 home and companion
Spark welcomes you back.
Open Hermes Console and return to Project Aurora from a home that brings conversations, instance status, and voice access together.
android client · hermes agent 
capabilities > capabilities
Not a chat app.
A console.
-
> chat --streaming --sse --attachments
Streaming chat
Real-time conversation with your Hermes Agent: responses arrive token by token, with visible reasoning and attachments. Messages and attachments go to the instance you configure, with no intermediary XPeta Lab backend.
-
> workspace --sessions --kanban --profiles
Full workspace
Sessions, kanban board, model picker and agent profiles. Full command of your Hermes, not just the chat.
-
> term --ssh --sftp --pty
SSH terminal + SFTP
A real terminal inside the app: SSH shell with a PTY and an SFTP browser to move files between your phone and your server.
-
> cron --cron --kanban --notifications
Cron & automation
Create, edit and trigger scheduled jobs from your phone. Cron and Kanban results can notify you and open the right run or conversation.
-
> approve --risk --notifications
Approvals with judgement
The agent asks before acting: every command arrives with its risk level and you approve or reject it — even from a notification with the app closed.
-
> spark --companion --moods
Spark, your companion
Hermes' spark lives in the app: an animated mascot that mirrors your agent's state — thinking, connecting, celebrating.
> product journey
Ask. Speak. Move. From anywhere.
Discover Hermes Console through a journey built from the real app interface with entirely fictional data.
02 pet
Make Spark yours.
Choose its presence, size, and whether it joins you on Home. The demo uses the default Spark companion.
03 voice
Speak. Hermes listens.
Open a dedicated voice session and see immediately when it is listening. Pause or end it from the same screen.
04 feature map
Everything has its place.
Appearance, pets, instances, models, SSH terminal, profiles, agents, and skills live in one clear tools map.
> connection
One server, or as many as you want.
Hermes Console is a pure client: your agent runs on your machine and the app connects over whatever network you choose. Messages and attachments go to the instance you configure; XPeta Lab does not receive them.
-
> connect --qr --gateway
Paired in seconds
Scan the QR and the app stores the Gateway, Dashboard, Bridge URL and encrypted per-instance tokens. You can also enter them manually.
-
> instances --multi --switch
All your instances
Home, VPS, homelab: save each server with its encrypted key and switch between them on the fly. The app diagnoses what every instance supports.
> setup --guide
Three steps. Your wire.
From zero to commanding your agent in minutes. No XPeta Lab account or first-party tracking.
Choose the system running Hermes Agent — not your phone system.
It is not detected automatically because you may be viewing this site on another device.
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | sh irm https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.ps1 | iex 1
Install the server
Choose Linux/macOS/Termux or Windows/WSL2. WSL2 uses Windows PowerShell. Setup starts and verifies Gateway, Dashboard and Mobile Bridge.
Unix sh · Windows PowerShell 2
Scan the QR
Only after checking identity, authentication and phone-facing access does setup print a complete QR. The app configures Bridge and Dashboard too.
hermes://pair 3
Command from your pocket
Done: chat, cron and your agent streaming back, from anywhere.
hermes > ready > privacy --audit
Privacy first.
By design.
Hermes Console requires no XPeta Lab account, and XPeta Lab operates no analytics or backend that receives your conversations. The app talks to your server; Privacy covers optional providers and the on-device ZXing QR scanner.
- No first-party tracking Zero XPeta Lab analytics, ads, or accounts. telemetry
- No XPeta Lab account The app requires no first-party login; accounts for optional services depend on your choices. accounts
- Routes under your control Messages and attachments go to your Hermes; voice and other providers only take part when you choose them. routing
- Encrypted on device Your API key is stored encrypted in the Android Keystore. keystore
- Minimal permissions Only what it needs to work. Nothing extra. perms
> docs open
Documentation.
The essentials to connect your agent. No detours.
Complete step-by-step guide Install the server, pair via QR, app tour and troubleshooting. So nobody gets lost. open guide →Requirements --requirements
- Android 7.0 or newer
- A machine running Hermes Agent: Linux, macOS, Termux or Windows/WSL2 with Windows PowerShell 5.1+
- The phone must reach the server over the network: LAN, Tailscale or HTTPS
Server install --install
Choose the system running Hermes Agent — not your phone system.
It is not detected automatically because you may be viewing this site on another device.
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | sh irm https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.ps1 | iex - Run the command matching the system of the machine running Hermes Agent
- It installs Hermes Agent if missing and brings up three services: Gateway (:8642), Dashboard (:9119) and Mobile Bridge (:9131)
- It verifies their real contracts, authentication, Bridge self-update and the address the phone will use
- Only then does it print a pairing QR for the app
It uses systemd on Linux, launchd on macOS and Scheduled Tasks—or Windows startup as a fallback—on Windows. For WSL2, run it from Windows PowerShell, outside WSL. On Unix without a persistent manager it keeps the current session working and warns that it will not survive a reboot.
Connecting --connect
- With QR: scan it from the app (or open the
hermes://pairlink) to fill Gateway, Dashboard, Bridge URL and both tokens - Manually: alongside the Gateway and API key, each instance can store its own Bridge URL and token
- You can save several instances and switch between them
Use LAN/Tailscale or HTTPS with a valid certificate. Setup never generates a QR for loopback or public HTTP and limits automatic firewall rules to private networks.
Settings --settings
- Themes — dark and light themes, including pure OLED; font and text size to taste
- Language — Spanish and English
- App lock — biometrics or PIN
- Notifications — approvals and Cron/Kanban results, deduplicated and linked to their conversation or run; no Google services
- Voice — choose per instance between “On this phone” and “Hermes server”; dictation, read aloud, and manual conversation remain available
- Accessibility — consistent switches, collapsible details, and selectors that stack with large text or limited width
- Gateway and Mobile Bridge — separate per-instance URLs and credentials; secrets are encrypted in Android Keystore
FAQ --faq
Does it work without internet? Yes, as long as phone and server share a network.
TLS certificate error. On a private network use LAN or Tailscale; for public domains, a valid certificate on the gateway.
I lost the QR. Open the guide, go to “Show the QR” and choose the system of the machine running Hermes.
Bridge outdated. The app uses its saved token to apply the validated self-update and confirms that the service comes back.
Does XPeta Lab collect data? No: it operates no telemetry, analytics, or conversation backend. Messages and attachments go to your Hermes; see Privacy for optional providers and the on-device ZXing QR scanner.
> install --android
Your agent awaits.
Download Hermes Console from Google Play, connect it to your Hermes Agent and take command from your pocket.
> donate --thanks
Support the project.
Hermes Console is an independent project built in my free time. If it serves you, a donation keeps the lights on.
> contact --ping
Talk to me.
Bug, idea or question? Write to me directly. I read every email.