M57andM57 caed4db316 fix(chat): route ALL synthetic backend user rows to system events (#937)
The backend persists a whole class of internal scaffolding as plain
role=user rows with NO display_kind (SessionDB strips underscore metadata):
runtime nudges (max tool-call iterations), context injections ([System:/[CONTEXT/
[PRIOR CONTEXT), background/cron/delegation notices ([IMPORTANT: Background/
Cronjob Response:/[ASYNC DELEGATION), out-of-band markers ([OUT-OF-BAND), and
todo/planning injections ([Your active task list/[Planning state preserved).
These are NOT real human turns, but the mobile rendered them as user bubbles.

Mirror the backend's own synthetic-detection contract
(agent.context_compressor._synthetic_user_row) with a prefix map. Any role=user
row with no display_kind that starts with a known synthetic prefix is routed to
a SystemEvent instead of a user turn. The 90-calls nudge maps to a specific
"Reached tool-call limit" chip; the rest map to a generic "System notice" chip.
Real user messages (no synthetic prefix) are unaffected.

- FullBleedTurns: SYNTHETIC_USER_PREFIX_KINDS map + syntheticSystemKind() that
  tags matched rows so the timeline chip can name them.
- timelineMarkerLabelRes: max_iterations_reached + system_notice labels.
- Strings en/zh/ko for both.
- Tests: assert the new labels map; assert every synthetic prefix routes to a
  SystemEvent (not a user turn); assert a real user message stays a user turn.

The display_kind-tagged events (model/personality switches, auto-continue,
delegation complete, skill invocation, internal notification) are already
handled separately (PR #936, merged).

ktlint + Android Lint + unit tests green locally.

Co-authored-by: M57 <hy4ri@users.noreply.github.com>
2026-08-18 19:04:44 +03:00
2026-06-22 21:35:40 +03:00
2026-07-23 13:21:14 +03:00

Hermes Mobile

Native Android companion app for your Hermes AI agent.


Android Jetpack Compose Kotlin Material You

Latest Release CI minSdk 26 targetSdk 36

Get it on F-Droid Get it on Obtainium


Overview

Hermes Mobile is the native Android client for Hermes Agent. It connects securely to your local Hermes gateway (REST API and WebSocket TUI Gateway) over LAN, giving you pocket control over your AI assistant.


Screenshots

Hermes Mobile chat screen Hermes Mobile cron jobs screen Hermes Mobile Kanban screen Hermes Mobile skills screen

Chat, automation, productivity, and agent configuration — from your phone.


Features

  • Real-Time Chat: Message your agent with Room-backed local database history and inline reply notifications.
  • System Config: Manage active profiles, installed skills, plugins, toolsets, and LLM model/provider selections.
  • Operations: Stream and filter live logs, manage cron jobs, edit environment keys, test webhooks, and monitor processes.
  • Gateway Status: Monitor WebSocket connection, MCP servers, messaging channels, and OAuth providers.
  • Productivity: View and manage tasks via integrated Kanban boards, track agent milestones, and browse session history.
  • Analytics & Billing: Usage analytics dashboard and billing/subscription management.
  • Theming: 6 built-in color presets (Default, Monochrome, Gruvbox, Catppuccin, AMOLED, Neon Noir) plus Material You dynamic colors on supported devices.
  • Modern UX: Native Material 3 design with pull-to-refresh, scroll-aware TopBar, and customizable bottom navigation.

Quick Start

Prerequisites

  • JDK 21+ (required for Kotlin compilation and the Gradle toolchain)
  • Android Studio (Ladybug+) or a Nix development environment

Build & Deploy

  1. Clone the repository:
    git clone https://github.com/Hy4ri/hermes-mobile.git
    cd hermes-mobile
    
  2. Build the debug APK:
    ./gradlew assembleDebug
    
  3. Install on your emulator/device:
    adb install app/build/outputs/apk/debug/app-debug.apk
    

Note: For release builds, ensure keystore environment variables (KEYSTORE_PATH, KEYSTORE_PASSWORD, KEY_ALIAS, KEY_PASSWORD) are configured, or let the GitHub Actions release workflow handle it on tag push (v*).


Authentication

Once the app is installed, you need to point it at your Hermes gateway. The app auto-detects which auth mode the dashboard is using — just fill in the fields it shows.

1. Start the dashboard

On your host machine, start the dashboard:

hermes dashboard                          # loopback (127.0.0.1:9119) — no auth needed
hermes dashboard --host 0.0.0.0           # LAN — requires auth

For LAN access, configure credentials in ~/.hermes/config.yaml:

dashboard:
  basic_auth:
    username: admin # pick your own
    password: hermes # pick your own

2. Connect the app

Tap Sign in on the landing screen and enter the dashboard host and port. The app probes the dashboard and reveals the fields you need:

Auth mode When What you fill
Token only Dashboard on same machine (loopback) Token — grab from ~/.hermes/dashboard-token.txt or ~/.hermes/.env (HERMES_DASHBOARD_SESSION_TOKEN). The app can also auto-extract it from the dashboard page
Basic auth Dashboard on LAN with password gate Username + Password (default admin / hermes). The app logs in, gets a session cookie, and mints a WebSocket ticket automatically

The app communicates over plain HTTP — it's designed for trusted local networks only. Do not expose your Hermes gateway to untrusted networks.

Connection profiles

Have multiple gateways? Switch between them in Settings → Connection profiles. Each profile stores its own host, port, and token — just tap to swap.

Pairing (admin)

The Pairing screen lets you approve or revoke agents and services that are trying to connect to your gateway, such as Telegram or Discord sessions.


Project Structure

app/src/main/java/com/m57/hermescontrol/
├── data/          # Local (Room, AuthManager), Remote (Retrofit, OkHttp), WS (WebSocket), Models
├── notification/  # Foreground service + inline reply for chat notifications
├── theme/         # Preset-based design system (6 themes), status colors, spacing, typography
├── ui/            # 28 Compose feature screens + common components (HermesScaffold, StateViews)
├── util/          # CronExpressionFormatter, LocaleContextWrapper
└── Navigation*.kt # Navigation3 wiring, keys, screen registry, controller

Tech Stack

  • Language: Kotlin 2.4.10 with KSP 2.3.10 compiler plugin
  • UI & Layout: Jetpack Compose (BOM 2026.03.01) & Material 3 / Material You
  • Navigation: Navigation3 (Compose-first Routing)
  • Networking: Retrofit 3.0.0, OkHttp 5.4.0, Kotlinx Serialization 1.11.0
  • Database: Room 2.7.1 with SQLCipher 4.17.0 encryption
  • Security: EncryptedSharedPreferences (AES256-GCM), DataStore
  • Theming: 6 built-in presets (Default, Monochrome, Gruvbox, Catppuccin, AMOLED, Neon Noir) + Material You dynamic colors
  • Image Loading: Coil 2.7.0
  • Testing: JUnit 5, MockK, Turbine, Espresso, Compose UI testing
  • Formatting: ktlint 1.2.1 style rules (checked automatically in CI)

Contributing

Contributions are welcome! Please read CONTRIBUTING.md for our branch workflow, code style guidelines, and PR checklist.

For developer-specific details, code conventions, and project architecture notes, refer to AGENTS.md.


License

Copyright © 2026 M57 (Hy4ri).

This project is licensed under the Apache License, Version 2.0. See the LICENSE file for details.

S
Description
AITURK Mobil — Android companion for AITURK IDE (fork of Hy4ri/hermes-mobile, Apache-2.0)
Readme Apache-2.0
10 MiB
0 Stars 1 Watchers 0 Forks
Languages
Kotlin 99.9%