Ares

com.hermesagent.hermes_android
by Zapstore Catalog

Chat with your Hermes AI agent from your phone

Hermes Android connects your phone or tablet to your Hermes Agent over LAN, Wi-Fi, a private Tailscale network or a configured HTTPS endpoint. Use Remote Gateway JSON-RPC or REST/SSE chat with authenticated access to your own server. Features: • Stream text, exposed reasoning and tool groups in receipt order • Inspect delegated-task messages, tool arguments/results and exposed reasoning in a read-only popup above the parent chat • Refresh task history or load older rows; missing references and partial compression history carry explanations • Choose a model and thinking effort per Remote Gateway chat • Attach up to 10 images/files per Remote Gateway draft, capped at 64 MiB total; generic files have a 16 MiB per-file limit. REST supports one image • Browse, search, rename, branch, delete, pin chats on this device and move chats between server Projects • Copy/select text, read aloud, edit and resend, regenerate, stop and export • Dictate with a compatible device speech service and use the device's text-to-speech engine for spoken replies • Access Memory, Cron Jobs, Skills and Settings through the authenticated dashboard • Reopen app-owned stock Gateway turns across chat navigation and reconcile pending work after reconnect or process restart without resubmitting uncertain prompts • Review background-work, notification and battery settings, with one foreground-service disclosure and quiet per-chat ongoing status entries • Opt in to native Google-free UnifiedPush for a selected connection and an explicit list of durable sessions • Choose dark, light or system theme and compact chat density Task inspection needs compatible authenticated Dashboard history routes. The API-server key alone cannot read that richer history. A gateway may omit compression segments; the viewer does not claim complete history or control child runtimes. Exposed reasoning means text the server supplies for display. UnifiedPush is off by default and uses no Firebase/FCM SDK. Install a compatible distributor on Android and ask the operator to install and enable the separate mobile-push server companion, configure VAPID and grant your dashboard login the exact session scopes. Registration requires explicit consent and encrypted challenge confirmation. Push hints omit chat text; authenticated notification taps open the session and cannot approve actions or resubmit prompts. Background operation and push are best-effort. Force stop, Doze, OEM battery controls, offline devices, permissions and distributor availability can prevent or delay delivery. A foreground service does not guarantee uninterrupted networking. Stock history reconciliation is separate from the experimental exactly-once recovery contract, which needs gateway support. Requires a running Hermes Agent server reachable from the device. Hermes Android does not install or configure that server, a distributor or an external account.

First release: Nov 4, 2026, 16 total releases.

Most recent release: Nov 20, 2026.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Nov 20, 2026 4.0.10
    ## What's Changed * fix(nextgen): replay open requests after the catch-up resume by @manuelanguitatrejo in https://github.com/rusty4444/ares/pull/295 * fix(nextgen): offer the profile after sign-in on a gated gateway by @manuelanguitatrejo in https://github.com/rusty4444/ares/pull/296 * fix(nextgen): fill the chat list past cron-only pages by @rusty4444 in https://github.com/rusty4444/ares/pull/298 * release: prepare v4.0.10 by @rusty4444 in https://github.com/rusty4444/ares/pull/299 **Full Changelog**: https://github.com/rusty4444/ares/compare/v4.0.9...v4.0.10
  • Nov 19, 2026 4.0.9
    ## What's Changed * fix(gateway): canonical session.create/resume params on session authority (#291) by @rusty4444 in https://github.com/rusty4444/ares/pull/293 * fix(nextgen): select the profile that holds the chats on a multiplexed gateway by @manuelanguitatrejo in https://github.com/rusty4444/ares/pull/292 * release: prepare v4.0.9 — canonical session params and multiplex profile preselect by @rusty4444 in https://github.com/rusty4444/ares/pull/294 **Full Changelog**: https://github.com/rusty4444/ares/compare/v4.0.8...v4.0.9
  • Nov 19, 2026 4.0.8
    ## Ares 4.0.8 NextGen catches up with Classic on two everyday actions (#288): - **Read aloud** — every completed assistant reply now offers Read aloud / Stop. One reply plays at a time: starting another stops the first, and switching chats stops playback. Uses your existing voice settings; long replies are chunked so playback completes reliably. - **One-tap code copy** — fenced code blocks show a labelled **Copy code** button that copies just that block's source. Classic's interface is unchanged. Install over the existing app — do not uninstall or clear app data. APKs are production-signed; checksums and exact-commit source materials are attached. The Google Play build updates through Play. Fixes #288 via PR #289. Thanks @Susensio for the detailed report. Full notes: [docs/releases/4.0.8.md](https://github.com/rusty4444/ares/blob/main/docs/releases/4.0.8.md).
  • Nov 19, 2026 4.0.7
    Ares 4.0.7: sending messages works against Hermes 0.23.x gateways, and NextGen history paging no longer re-fetches rows already on screen. Covers all changes since 4.0.5, including the paging fix prepared under the unpublished 4.0.6 tag. Base build **3063**; ABI split codes `30631` (armeabi-v7a), `30632` (arm64-v8a) and `30633` (x86_64), each above the highest published 4.0.5 split (`30623`). The production package and signer are unchanged. ## Install Install over the existing app (same package and signer); do not uninstall or clear app data. | APK | Device | Version code | | --- | --- | --- |
    More…
    | `app-arm64-v8a-release.apk` | Most current Android phones/tablets | `30632` | | `app-armeabi-v7a-release.apk` | Older 32-bit ARM devices | `30631` | | `app-x86_64-release.apk` | x86_64 devices/emulators | `30633` | ## What's fixed - **Sending works against Hermes 0.23.x gateways (#286, fixes #285, reported by @shmuelsash).** Hermes 0.23.0 began refusing a Desktop Gateway `prompt.submit` that carries no `submission_id`/`input_id` with a bare `invalid_params`, so every send over that transport failed with "Not sent: invalid_params" on those gateways, in new and existing chats, and Retry failed the same way. Both send paths now mint a UUID `submission_id` per turn and fall back once without it if a pre-0.23 gateway rejects the extra field. NextGen's Retry reuses the failed send's id (idempotent replay on ambiguous loss); the classic path recovers ambiguous sends from server history without resending. The fallback retry re-checks admission and socket ownership before writing again. - **NextGen paging carries growth overlap forward (#284, fixes #280, thanks @Thaeland).** After a burst of new rows beside a running turn, paging re-anchored on the shown rows and re-fetched offsets full of rows already on screen, and a live turn's stored rows could page back in as older duplicates. Each page's already-known rows now accumulate into a running shift so offsets strictly increase, and at turn end the controller adopts the unknown stored tail — for a turn of any length — and reconciles the shift, so paging resumes at the exact coverage boundary even when the reader paged during the turn or an adoption races an in-flight page. This removes the known limits recorded in 4.0.5. ## Publication note (v4.0.6) The v4.0.6 tag was pushed before the release identity was bumped, so its release workflow failed the identity gate and **no 4.0.6 APKs were published**. Its one change (#284) ships in this release. The changelog declares 4.0.6 source-only. ## Verification (merged commit `b3bde126`) - Fix PR #286 reviewed against the actual Hermes gateway source (0.23.1 `AuthorityConnection.submission` admission check and allowed field set; pre-0.23 `extra="forbid"` validation shape at tag `v2026.9.21`) and merged as `df7a53b3`. CI green on head `03c93b02` (runs 44400083111 / 44400083159). - Release PR #287: identity prep `69e420b5` plus one review-fix commit `373fe078`. A single read-only review pass found 0 blockers / 4 should-fix, all fixed with red-on-base regressions (each new test failed on the pre-fix tree and passes after): paging shift reconciliation + mid-fetch fence, removal of the five-page adoption cap, fallback admission re-check, and docs scope. CI green on head `373fe078` (Analyze & Test 44440822529; Native Android + Push 44440822494). - Merged-main push CI green on `b3bde126`: PR Quality Checks run 44443095304 (**5810 tests pass**) and Native Android + Push run 44443095307. The merge diff against the tested head is README store badges only (docs commits `be51f030` / `02baa6b6`); the application tree is unchanged. - Release built, signed and published by the tag workflow on `b3bde126` (run 44444976651). - Published APKs downloaded and checked: `versionName 4.0.7`, codes `30631/30632/30633`, package `com.hermesagent.hermes_android`, correct per-ABI native code; all three signed with the production certificate SHA-256 `475baf431b16d050c8f658ac838783b273f7c10bba06ed1d16bb0a4239f592fb`. Repository verifier `verify_release_apks.py --target b3bde126…` exit 0 with 22 packaged-blob checks per APK. - Source/relink bundle manifest names commit `b3bde126`, all three APK hashes match, the inner source archive digest matches, and its 1400-file inventory matches the commit. - Play AAB built from `b3bde126` with `ARES_PLAY_BUILD=true`, production-signed and verified by `verify_play_bundle.py` (version `4.0.7+3063`, target API 36, install permission and APK update provider removed); submitted to the Play production track. ## Not verified - No live reproduction on the reporter's own 0.23.2 gateway or device; the fix is verified against the gateway source contract and loopback wire tests, not a reverse-proxy/Tailscale path. No on-device paging/turn-end testing beyond the automated suite. Full notes: [`docs/releases/4.0.7.md`](https://github.com/rusty4444/ares/blob/v4.0.7/docs/releases/4.0.7.md) · [`CHANGELOG.md`](https://github.com/rusty4444/ares/blob/v4.0.7/CHANGELOG.md)
  • Nov 17, 2026 4.0.5
    Ares 4.0.5: NextGen history paging keeps working during a running turn, and password sign-in works against the gateway Webapp. Covers all changes since 4.0.4. Base build **3062**; ABI split codes `30621` (armeabi-v7a), `30622` (arm64-v8a) and `30623` (x86_64), each above the highest published 4.0.4 split (`30613`). The production package and signer are unchanged. ## Install Install over the existing app (same package and signer); do not uninstall or clear app data. | APK | Device | Version code | | --- | --- | --- |
    More…
    | `app-arm64-v8a-release.apk` | Most current Android phones/tablets | `30622` | | `app-armeabi-v7a-release.apk` | Older 32-bit ARM devices | `30621` | | `app-x86_64-release.apk` | x86_64 devices/emulators | `30623` | ## What's fixed - **NextGen history paging survives a running turn (#275, thanks @Thaeland).** Paging counts back from the newest stored row. When a running turn stored new rows while you were scrolled back, the next page could hold only rows already on screen, and paging stopped until a reconnect. An all-known page now moves a floor past that window instead of ending paging, and already-shown rows are dropped before the page is trimmed to its first prompt, so paging also carries on beside a long, tool-heavy turn. Known limits: after a burst of growth, paging can re-fetch rows that are already shown before reaching new ones (#280), and rows stored by a live turn can still briefly reappear as older items until the next resync, as in 4.0.4. - **Dashboard sign-in through the gateway Webapp (#282, fixes #281, thanks @manuelanguitatrejo).** The dashboard served by `hermes webapp` suffixes its sign-in cookie names with a per-gateway id and treats a session as signed out without its `hermes_webapp_signin_<gateway>` binding cookie. Ares now recognises the suffixed session cookie and sends the binding beside it. The standalone `hermes dashboard` keeps its bare names and no binding, so its requests are unchanged. ## Verification (merged commit `4b2b20ad`) - Contributor PRs reviewed at their exact heads: #275 (`c781d374`) with both earlier reproductions re-run on the controller and a 20,000-history paging model; #282 (`9049cfad`) round-tripped through the gateway's own cookie setters, readers and `webapp_sign_in.check` across 18 cookie shapes. CI green on both heads (runs 43971823842/43971823564 and 44099635895/44099636181). - Release-prep PR #283 changes identity, notes and store surfaces only; the application tree is byte-identical to `a756db83`. One read-only review pass found one wording overclaim, fixed in `ef484d46`. CI green on that head (Analyze & Test 44130818001; Native Android + Push 44130817815, rerun after a hung runner, passed in under 4 minutes). - Merged-main push CI green on `4b2b20ad`: PR Quality Checks run 44135755445 (**5798 tests pass**) and Native Android + Push run 44135755335. The merge tree equals the tested release-prep tree. - Release built, signed and published by the tag workflow on `4b2b20ad` (run 44138802495). - Published APKs downloaded and checked: `versionName 4.0.5`, codes `30621/30622/30623`, package `com.hermesagent.hermes_android`, correct per-ABI native code; asset digests and `SHA256SUMS` match; all three signed with the production certificate SHA-256 `475baf431b16d050c8f658ac838783b273f7c10bba06ed1d16bb0a4239f592fb`. Repository verifier `verify_release_apks.py --target 4b2b20ad…` exit 0 with 22 packaged-blob checks per APK. - Source/relink bundle manifest names commit `4b2b20ad`, all three APK hashes match, the inner source archive digest matches, and its 1394-file inventory is byte-identical to the commit. ## Not verified - Live sign-in against a running gateway Webapp on a physical phone, and paging during a live turn on a device, beyond automated tests. Full notes: [`docs/releases/4.0.5.md`](https://github.com/rusty4444/ares/blob/v4.0.5/docs/releases/4.0.5.md) · [`CHANGELOG.md`](https://github.com/rusty4444/ares/blob/v4.0.5/CHANGELOG.md)
  • Nov 16, 2026 4.0.4
    Ares 4.0.4 — NextGen back gesture closes the sidebar. In NextGen mode the back gesture opened the chat sidebar, but a second back exited the app instead of closing the sidebar. Back now dismisses the open sidebar, restoring the open/close toggle: back opens it, back again closes it. Pushed pages such as Settings and Scheduled still pop first. This is the only change since 4.0.3. Base build **3061**; ABI split codes `30611` (armeabi-v7a), `30612` (arm64-v8a) and `30613` (x86_64), each above the highest published 4.0.3 split (`30603`). The production package and signer are unchanged. ## Install Install over the existing app (same package and signer); do not uninstall or clear app data.
    More…
    | APK | Device | Version code | | --- | --- | --- | | `app-arm64-v8a-release.apk` | Most current Android phones/tablets | `30612` | | `app-armeabi-v7a-release.apk` | Older 32-bit ARM devices | `30611` | | `app-x86_64-release.apk` | x86_64 devices/emulators | `30613` | ## What's fixed - **NextGen back gesture closes the sidebar (#278).** The main screen's `PopScope(canPop: false)` veto was winning over the drawer's local-history entry, so the second back reached the handler with the drawer open and called `SystemNavigator.pop()`, exiting the app. The handler now closes the drawer when it is open; back with it closed still opens it. ## Verification (merged commit `1920539e`) - Fix PR #278 CI green on head `100af688` (Analyze & Test run 43832507130; Native Android + Push run 43832507161). Release-prep PR #279 CI green on head `11876038` (runs 43840663303 / 43840663236), plus a one-pass read-only review (verdict: ship, zero findings). - Merged-main push CI green on `1920539e`: PR Quality Checks run 43843122641 (**5793 tests pass**) and Native Android + Push run 43843122696. - Release built, signed and published by the tag workflow on `1920539e` (run 43844837319). - Published APKs downloaded and checked: `versionName 4.0.4`, codes `30611/30612/30613`, package `com.hermesagent.hermes_android`, correct per-ABI native code; `SHA256SUMS` matches; all three signed with the established production certificate SHA-256 `475baf431b16d050c8f658ac838783b273f7c10bba06ed1d16bb0a4239f592fb`. Repository verifier `verify_release_apks.py --target 1920539e…` exit 0 with 22 packaged-blob checks per APK. - Source/relink bundle manifest names commit `1920539e`, all three APK hashes match, the inner source archive digest matches, and its 1389-file inventory is byte-identical to the commit (including the fixed `main_page.dart`). - Regression test asserts back opens, closes, then reopens the NextGen sidebar without ever calling `SystemNavigator.pop`. ## Not verified - Live device / emulator integration and predictive-back gesture behaviour on a physical phone beyond automated widget tests. Full notes: [`docs/releases/4.0.4.md`](https://github.com/rusty4444/ares/blob/v4.0.4/docs/releases/4.0.4.md) · [`CHANGELOG.md`](https://github.com/rusty4444/ares/blob/v4.0.4/CHANGELOG.md)
  • Nov 16, 2026 4.0.3
    Ares 4.0.3 — full-message text selection. A long-press drag now selects as much of a reply as you want — across paragraphs, lists and fenced code — instead of being confined to a single block. Both chat interfaces are covered: the Classic **Select text** dialog and the NextGen inline reply. Tip: long-press → **Select all** → **Copy** grabs an entire reply in one go. ## Install Install over the existing app (same package and signer); do not uninstall or clear app data. | APK | Device | Version code | | --- | --- | --- |
    More…
    | `app-arm64-v8a-release.apk` | Most current Android phones/tablets | `30602` | | `app-armeabi-v7a-release.apk` | Older 32-bit ARM devices | `30601` | | `app-x86_64-release.apk` | x86_64 devices/emulators | `30603` | ## What's fixed - **Full-message text selection** in Classic and NextGen: the whole reply renders inside one selection scope with plain-text prose and fenced code, so a single drag spans the entire message. Link taps and the code copy/line-wrap controls are preserved. ## Verification (merged commit `765ad0c4`) - PR #277 CI green on head `d2af6730`: Analyze & Test (run 43790377379) and Native Android + Push Server (run 43790377397). - Full Flutter suite: **5793 tests pass**; analyzer clean; release-materials and README-window gates pass. - Release built and verified on `765ad0c4` (run 43792069140). - Published APKs checked locally: `versionName 4.0.3`, version codes `30601/30602/30603`, package `com.hermesagent.hermes_android`; `SHA256SUMS` verified; all three signed with the established production certificate SHA-256 `475baf431b16d050c8f658ac838783b273f7c10bba06ed1d16bb0a4239f592fb`. - Regression tests perform a real long-press-drag across paragraphs and a code fence (Classic dialog and NextGen); each fails without the fix and passes with it. Reporter confirmed the fix on a production-signed arm64 device build. ## Not verified - Live device integration beyond the reporter's phone test of the selection fix. Full notes: [`docs/releases/4.0.3.md`](https://github.com/rusty4444/ares/blob/v4.0.3/docs/releases/4.0.3.md) · [`CHANGELOG.md`](https://github.com/rusty4444/ares/blob/v4.0.3/CHANGELOG.md)
  • Nov 15, 2026 4.0.2
    **Full Changelog**: https://github.com/rusty4444/ares/compare/v4.0.1...v4.0.2
  • Nov 15, 2026 4.0.0
    # Ares - formerly Hermes Android 4.0.0 Stable release, base build **3048** (ABI splits `30481` / `30482` / `30483`). Each split is above the highest published 4.0.0-rc.10 split, `30473`, and above 3.2.8. The production package `com.hermesagent.hermes_android` and signing certificate are unchanged, so 4.0.0 installs over the existing app. This note records every change since **3.2.8**. The README showcase was recorded on the production-signed 4.0.0-rc.7 build during the candidate cycle, with illustrative fixture chats.
    More…
    ## Ares name and new icon Hermes Android is now **Ares - formerly Hermes Android**, with Ares as the launcher label. The new black-and-white Ares portrait is used for the launcher, adaptive, round, Android 13+ themed and store artwork. The app still connects to Hermes Agent. ## Classic and NextGen Settings switches the whole app between Classic and NextGen. Saved gateways and chats are shared. NextGen adapts the design and connection model of [Kyllene](https://github.com/Giton22/kyllene) by Giton22 (MIT), with Geist type, accent colours, pure black and glow options, a searchable chat sidebar with one-tap search clearing, pins, All / Running / Needs you filters, Scheduled, Insights, Capabilities and Archived. Cron-run conversations have their own Crons filter, separate from normal chats and Scheduled job management. New installs can choose Classic or NextGen before connecting. Its pill composer provides model and thinking-level controls, inline approvals and questions, steering, queuing, stop-and-send and dictation. Fenced code blocks in both interfaces offer copy and line-wrap controls. NextGen More opens Classic features Kyllene lacks: memory, projects, model management, provider sign-in, Nous Portal, the full cron editor and the gateway config file. Back opens the NextGen sidebar before leaving the app. Sidebar filters scroll sideways when translated labels do not fit. Desktop Gateway sessions open and resume as `source: desktop`, so stock Hermes provides its desktop file-delivery hint. The Android client-context note is not appended on that transport; REST/API-server prompts retain it. Older saved turns that contain the note still display cleanly. ## One dashboard sign-in A gateway can use its dashboard address and one username/password or browser PKCE sign-in, with token refresh and no API-server key on that path. The connect screen probes the server, discovers LAN dashboards, warns about unencrypted public addresses, stores Cloudflare Access service tokens per host, selects a profile when several are available and names a failed server, sign-in or live connection stage. Classic Add Connection offers the same flow. ## Files, plans and live work NextGen supports photo, camera and file attachments, client certificates and all shipped app languages. Images and other files up to 12 MB attach inline; larger uploads stream to the gateway up to its 100 MB limit. Save and Share stream delivered files up to 1 GiB, while previews retain the 25 MiB budget. `MEDIA:` deliveries render as download, open and share cards. The stacked session dock holds goal, loop and heartbeat controls, live tasks and subagent status. Unread chats, attention colours and timestamps make running, finished and waiting work easier to find. Background results and runtime notices collapse into readable cards. ## Notifications and catch-up Replies, failures, approvals, questions and secret requests can notify while out of sight, with Allow once and Deny actions where applicable. Ordered event replay uses `session.events.since` after a gap, reconnect or resume, with transcript fallback for incomplete, truncated or wrong-epoch replies. NextGen Settings includes notification controls, keep-alive, battery optimisation, a test notification and recent notification diagnostics. ## Google Play, privacy and AI-output reporting The Play AAB removes the GitHub APK install permission, update provider, update checks and prompts. Updates are managed by Google Play. The ordinary GitHub APK keeps its verified updater. Both builds link the public [privacy policy]( https://github.com/rusty4444/hermes-android/blob/main/PRIVACY.md) in Settings. Classic assistant message actions and completed NextGen replies offer **Report AI output**. The action opens a new public GitHub issue without automatically attaching chat content, credentials or attachment paths. ## Performance and reliability NextGen opens the latest 60 rows, pages earlier history as the reader scrolls, caches parsed Markdown and lays out long replies in paragraph chunks. Large history pages decode on a background isolate and trim tool and message payloads to the displayed budgets. Automatic backfill is bounded, preventing tool-only pages from repeatedly blocking the UI. Insights waits for the gateway's 7/30/90-day report windows and offers retry. Structured text parts no longer break NextGen or Classic delegated-task history (Kyllene #419). Provider chips in the NextGen model picker filter the list by provider and clear with a second tap or All. Selected chips use accent-tinted surfaces with explicit readable labels in dark mode. ## Verification Release commits are gated by the repository's analysis, test, identity, README-window, store-note, signing and publication checks. _Built with AI assistance (Hermes Agent) and reviewed before release._ **Full Changelog**: https://github.com/rusty4444/hermes-android/compare/v3.2.8...v4.0.0
  • Nov 11, 2026 3.2.8
    # Hermes Android 3.2.8 Stable release, base build **3036** (ABI splits `30361` / `30362` / `30363`). Every split upgrades the highest previously distributed split, 3.2.7's `30353`, so it installs in place over 3.2.7. The production package `com.hermesagent.hermes_android` and signing certificate are unchanged; install over the existing app rather than uninstalling. This release covers everything since **3.2.7**.
    More…
    ## M3 Expressive composer pill and last-reply quick actions (#271) The chat screen adopts an M3 Expressive floating composer pill alongside tonal quick-action chips beneath the latest completed assistant reply. - **Floating composer pill:** the input bar now floats in an elevated tonal pill (`surfaceContainerHigh`, 28 dp radius, hairline border and soft shadow) with a borderless text field and a formatting toolbar (`code`, `bold`, `italic`) that appears only once a draft is present. When the software keyboard opens, outer horizontal insets collapse so narrow viewports (`320 dp` at `200%` text scale) retain their full editor width. - **Animated Send FAB:** the Send button renders as a filled accent button that morphs from a circle to a squircle while a turn is active, preserving existing mid-turn steering and the separate **Stop** control. - **Last-reply quick actions:** the newest completed assistant reply displays 40 dp tonal circular chips for **Copy**, **Select text**, **Read aloud** and **Regenerate** whenever no turn is running. Long-pressing any quick-action chip opens the full message action sheet. - **Foldable cover-screen layout:** the failed-to-load state scrolls cleanly when a foldable cover display has the software keyboard open, backed by dedicated foldable viewport tests (`344 dp` cover, `700 dp` inner, and `1000 dp` unfolded). ### Thanks - [@esc247](https://github.com/esc247) contributed the M3 Expressive composer pill, last-reply quick actions, foldable cover-screen layout fix, and regression test suites (#271). ## Verification - `flutter analyze --no-pub --fatal-infos`: no issues. - `flutter test --no-pub`: the full suite passed on the release commit, with no failures or skipped tests. - The tag workflow builds, verifies and publishes the signed APKs, checksums and source/relink bundle. _Built with AI assistance (Hermes Agent) and reviewed before release._
  • Nov 10, 2026 3.2.7
    # Hermes Android 3.2.7 Stable release, base build **3035** (ABI splits `30351` / `30352` / `30353`). Every split upgrades the highest previously distributed split, 3.2.6's `30343`, so it installs in place over 3.2.6. The production package `com.hermesagent.hermes_android` and signing certificate are unchanged; install over the existing app rather than uninstalling. This release covers everything since **3.2.6**.
    More…
    ## In-app APK download and installation (#270) When a newer official GitHub release is available, supported Android builds can now download, verify and hand the matching APK directly to the system package installer from the update dialog. - **ABI-matched asset selection:** the update checker inspects the device's supported ABIs alongside the release's `SHA256SUMS` manifest and selects the matching split APK (`arm64-v8a`, `armeabi-v7a` or `x86_64`) with its expected size and SHA-256 digest. - **Pinned download and archive verification:** downloads accept only HTTPS URLs under `github.com/rusty4444/hermes-android/releases/download/` and the trusted GitHub release asset hosts, stream to a single-file cache with byte count and SHA-256 verification, and validate the downloaded APK against the installed app's package name, signing certificate digests, supported ABIs, `minSdkVersion`, and a strictly higher `versionCode` before installation. - **Unknown-sources permission handoff:** if Android requires permission to install unknown apps, the dialog opens the package-specific system settings page, retains the verified download across the round-trip, and re-verifies the staged APK on the worker executor before launching the system installer. - **Safe fallback:** when a release has no verified in-app asset or runs on a debug/non-Android build, the dialog keeps the external **View release** link. ### Thanks - [@esc247](https://github.com/esc247) contributed the in-app APK updater, native archive/signature verification, and regression test suite (#270). ## Verification - `flutter analyze --no-pub --fatal-infos`: no issues. - `flutter test --no-pub`: the full suite passed on the release commit, with no failures or skipped tests. - The tag workflow builds, verifies and publishes the signed APKs, checksums and source/relink bundle. _Built with AI assistance (Hermes Agent) and reviewed before release._
  • Nov 9, 2026 3.2.6
    # Hermes Android 3.2.6 Stable release, base build **3034** (ABI splits `30341` / `30342` / `30343`). Every split upgrades the highest previously distributed split, 3.2.5's `30333`, so it installs in place over 3.2.5. The production package `com.hermesagent.hermes_android` and signing certificate are unchanged; install over the existing app rather than uninstalling. This release covers everything since **3.2.5**.
    More…
    ## Slash-command autocomplete and execution (#269) Remote Gateway chats now discover and run Hermes slash commands directly from the message composer. - **Live catalogue discovery:** when a Remote Gateway chat connects, the app requests `commands.catalog` and merges built-in commands (`pairs` and `categories[].pairs`), plugin commands (`plugin_commands`), skill commands (`skills`), canonical aliases (`canon`), and argument metadata (`commands`). - **Autocomplete popup:** typing a leading `/` at the start of the composer opens a filterable popup above the input bar with category badges and descriptions. Selecting a command that takes arguments inserts `/command ` and keeps the keyboard ready; commands with no required arguments can be submitted immediately. - **Wire-accurate `slash.exec` handling:** leading slash invocations (including commands with arguments such as `/title My chat`) are sent over `slash.exec`. Plain worker and plugin replies (`{output, warning}`) appear as compact dismissible in-chat notices without re-sending the command as a normal prompt. Gateway `skill`, `send`, `prefill`, `plugin`, and `alias` directives are honoured directly. - **Safe fallback and delivery-uncertainty protection:** if a gateway does not support `slash.exec` or reports the command as unsupported, the app falls back to a normal prompt send. If a timeout or disconnect occurs after the `slash.exec` frame was already written to the socket, the app keeps your composer draft and shows a delivery-uncertain warning instead of re-sending the command as a normal prompt. ### Thanks - [@esc247](https://github.com/esc247) contributed the slash-command catalogue, autocomplete UI, `slash.exec` dispatch, and regression suite (#269). ## Verification - `flutter analyze --no-pub --fatal-infos`: no issues. - `flutter test --no-pub`: the full suite passed on the release commit, with no failures or skipped tests. - The tag workflow builds, verifies and publishes the signed APKs, checksums and source/relink bundle. _Built with AI assistance (Hermes Agent) and reviewed before release._
  • Nov 6, 2026 3.2.5
    Stable release covering everything since **3.2.4**. Base build `3033`; ABI splits `30331` / `30332` / `30333`, each above 3.2.4's highest split (`30323`), so this installs in place over 3.2.4. Package and signing certificate are unchanged. **Install over the existing app; do not uninstall or clear app data.** ### Chat pins sync with Hermes Desktop (#268) Until now, Android pins lived only on the phone. They never reached Hermes Desktop, and Desktop pins showed on the phone only as a faint marker. Android now uses the server's `pinned` flag, the same one Desktop reads and writes, so a pin follows the chat to every client of that host. - **Pin and Unpin** save with `PATCH /api/sessions/{id}` carrying only `pinned`, and count as saved only after the app reads that chat back from the server. A failed save leaves the row as it was and offers **Retry**. - **Pins made elsewhere** (Desktop, another phone) appear on the next list refresh. The server already includes every pinned chat on each list page, so old pinned chats need no extra requests. - **No flicker back:** a list read that started before your pin or unpin finished cannot undo it. Reads that start afterwards are authoritative, so later Desktop changes still come through. - **Pinned section:** Workspace Chats and the classic list both show pinned chats in a **Pinned** section ahead of the date groups, still inside the current search and filter.
    More…
    - **Archive:** archiving a pinned chat clears its pin in the same request, as Desktop does. If the chat was pinned somewhere else since this phone last loaded it, the archive reply shows that and the app unpins it too, so it never stays in Desktop's Pinned section. Archived chats and unsaved drafts don't offer Pin. A Quick chat archived only by this phone's expiry is still live on the server, so a pinned one keeps Unpin. - **Search results:** server search doesn't report pins, so each hit takes its pin from the matching chat in the list. A hit whose pin state isn't known offers neither Pin nor Unpin. **Moving existing pins.** Pins that 3.2.4 and earlier stored only on this device move to the server the first time Chats opens. A pin leaves the device only once its outcome is settled: the server confirmed it or already had it, reported the chat as not found, or the chat is archived or hidden. A network error, an unconfirmed save or an older server keeps it on the device for the next attempt. **Older Hermes servers.** Servers from before synced pins (August 2026) report no pin state, so Pin is hidden on them rather than offered and failing. Device pins from earlier versions are kept and move over once Hermes is updated. Archiving works as before, because `pinned` is only sent to servers that report it. All 12 shipped locales have the reworded strings (Pin chat, Unpin chat, Pinned, Could not update chat pin). ### Verification - `flutter analyze --fatal-infos` clean. CI on the merged commit `4d36370e` passed **5,562 tests** (PR Quality Checks run 42168975145), and the native Android and push-server run (42168975151) passed too. - One independent code review before merge; its four should-fix findings were fixed with regression tests, and each new test was confirmed to fail without its fix. - Published APKs downloaded and re-verified: `versionName 3.2.5`, codes `30331`/`30332`/`30333`, matching ABIs, production signer `475baf43…f592fb`, hashes matching `SHA256SUMS` and every GitHub asset digest and size. - `scripts/verify_release_apks.py` from a checkout at the publication commit: exit 0, 22 packaged-blob checks per APK. - Source bundle manifest names commit `4d36370e` and all three published APK hashes; the inner archive digest matches. ### Not verified No on-device or emulator testing, and no live two-way sync against a running Hermes Desktop. Pin sync was exercised against fixtures that follow the gateway's API contract. Please report anything that misbehaves on real hardware. Full notes: [docs/releases/3.2.5.md](https://github.com/rusty4444/hermes-android/blob/v3.2.5/docs/releases/3.2.5.md) · [CHANGELOG](https://github.com/rusty4444/hermes-android/blob/v3.2.5/CHANGELOG.md)
  • Nov 4, 2026 3.2.4
    Stable release covering everything since **3.2.3**. Base build `3032`; ABI splits `30321` / `30322` / `30323`, each above the highest previously distributed split (`3.2.4-rc.2`'s `30313`), so this installs in place over 3.2.3 or either 3.2.4 candidate. Package and signing certificate are unchanged — **install over the existing app; do not uninstall or clear app data.** Application code is byte-identical to the tested [v3.2.4-rc.2](https://github.com/rusty4444/hermes-android/releases/tag/v3.2.4-rc.2); only release identity and notes differ. ### Scheduled jobs are visible before they run (#259) **Crons** previously listed cron *run* conversations, so a job scheduled for next week showed nothing until after its first run. Crons now opens on **Upcoming**, listing scheduled job definitions with enabled/disabled state, schedule, next run and target conversation where the payload supplies one. **History** keeps the previous run browser, and the full cron manager still owns every schedule mutation — creating or deleting a job there re-reads Upcoming on return. Next-run times always state their zone. The schedule payload carries numeric UTC offsets rather than named IANA zones, so a next run renders like `Next: 2026-11-09 09:00 (UTC+11:00)`; where no zone information exists the app says so rather than assuming the phone's zone. A connection with no Dashboard route is told scheduled jobs need one, kept distinct from an empty list.
    More…
    ### Configurable server-side Projects root (#232) Projects created by the app landed under the server's conventional `<home>/Projects`, while TUI-created projects often live elsewhere, so neither side saw the other's folders. **More → Projects folder on the server** now sets the Projects root per saved connection. The default is unchanged, so existing setups behave exactly as before until you use it; a dashboard `locked_root` still outranks the local choice and shows read-only. **Projects → Add an existing folder** enumerates server folders, filters out paths already claimed by a registered Project, and adopts your choice through the existing project-creation contract. Where a host doesn't expose that listing route, the app says so and offers manual path entry rather than pretending to have scanned. Limits: changing the root does not move existing Projects; enumeration covers direct non-hidden children rather than recursing; manual paths get syntactic validation only; server-side symlinks are not resolved. ### Ukrainian and in-app language selection (#255) Ukrainian joins the shipped locales, with a persistent in-app language selector — pick any generated locale or follow the system default, and the choice survives restarts and configuration backup restoration. **Correction:** this merged *after* the `v3.2.3` tag, so despite appearing in the 3.2.3 changelog it is absent from that release's APKs. **3.2.4 is the first stable release that actually contains it.** Contributed by [@simplaerai-sv](https://github.com/simplaerai-sv), original commits preserved. ### Clearer API-only send refusals (#253) On a connection holding only an API-server key, sending into a Dashboard-owned chat is refused by the gateway with an in-band `permission_denied`; the app previously showed only the bare refusal. The terminal notice now appends what to check while preserving the server's wording verbatim, phrased conditionally — adding Dashboard credentials *may* allow the send, and the server *may* equally be refusing deliberately. Send routing, the principal used, the attach gate and retry behaviour are all unchanged, and no prompt is resent. ### Lighter background refresh on the chat list (#149) The visible-pane refresh ran a full aggregate read every ten seconds, including the dashboard's `archived=only` paging, even on filters that render no archived rows. The passive refresh is now scoped to the authority the selected surface displays. Over three ticks in fixtures, archive requests fall **8 → 2** on Chats and **10 → 4** on Crons, leaving only the initial scan. Archived keeps its full-scope refresh and fetches immediately when selected; previously loaded archived rows, device-local pins and Quick Chat records survive scoped ticks; explicit refreshes keep their scope. ### Also included - Widget coverage pinning API-server versus Dashboard principal routing on the send path (#254). Test-only. - A Buy Me a Coffee link at the top of the README (#263) — optional, gates nothing. ### Verification - `flutter analyze --fatal-infos` clean; **5,548 tests passed**, zero failures, zero skipped, every started test finished. - Published APKs downloaded and re-verified: package `com.hermesagent.hermes_android`, `versionName 3.2.4`, codes `30321`/`30322`/`30323`, matching ABIs, production signer `475baf43…f592fb`, hashes matching `SHA256SUMS` **and** every GitHub asset digest and size. - `scripts/verify_release_apks.py` from a checkout at the publication commit: exit 0, 22 packaged-blob checks per APK. - Source bundle manifest names commit `001994d6` and all three published APK hashes; inner archive digest matches. ### Not verified No on-device or emulator acceptance. No live multi-timezone server, no multi-root server, and no real gateway authorisation reproduction. The gates above are source and artefact checks, not field testing — please report anything that misbehaves on real hardware. Full notes: [docs/releases/3.2.4.md](https://github.com/rusty4444/hermes-android/blob/v3.2.4/docs/releases/3.2.4.md) · [CHANGELOG](https://github.com/rusty4444/hermes-android/blob/v3.2.4/CHANGELOG.md)
  • Nov 4, 2026 3.2.3
    ## v3.2.3 Resumable voice drafts, smoother streaming, and improved input handling. ### Highlights - Resume interrupted voice replies instead of losing them on reconnect or foreground switches. - Keep manual scroll position stable while new tokens stream in. - Restore the IME viewport correctly when entering chat from nested workspaces. - Harden shared-intent parsing so malformed attachments no longer crash the composer.
    More…
    ### Builds - `app-arm64-v8a-release.apk` - `app-armeabi-v7a-release.apk` - `app-x86_64-release.apk` SHA256SUMS and source relink are included in the release assets.
  • Nov 4, 2026 3.2.2
    ## Fallback providers and models Open **More → Agent → Model** to edit the selected profile's fallback chain. Add rows, change provider/model pairs, move rows up or down, and delete entries. Choose **Save fallback list** to apply the ordered list. Delete all rows and save to clear the primary list. Legacy `fallback_model` entries remain active in a separate protected section. Existing unknown models and routing metadata stay intact; custom routes retain their host-managed identities. ### Host compatibility Fallback editing requires a Hermes host whose OpenAPI schema advertises raw saved-config reads. Older or unverified hosts cannot use this editor. Main and auxiliary model controls remain independent. Updating the APK does not update the host or change provider credentials.
    More…
    [Model-management guide](https://github.com/rusty4444/hermes-android/blob/v3.2.2/docs/model-management.md) ### Install Version **3.2.2**, base **3028**: - **arm64-v8a**: `30282`, for most current phones. - **armeabi-v7a**: `30281`. - **x86_64**: `30283`. Install over the existing app without uninstalling or clearing data. This release keeps the production package and signing identity. ### Validation - Local acceptance: **5,309 Flutter tests passed**, zero skipped or unfinished; fatal analysis and release-material checks passed. - Independent specification and different-model quality reviews completed. A targeted recheck confirmed the CI test-timing repair; the repair changes no production chat code. - PR and post-merge quality/native/push checks passed. - Official tag build passed. Downloaded APKs match version **3.2.2**, all three ABI codes and the production signer, with 22 packaged notice/source checks per APK. - All five downloaded assets match GitHub's SHA-256 digests and sizes. The source/relink bundle matches the publication commit, including all **1,133 tracked source blobs**, and records the three published APK hashes. These checks do not establish bit-identical rebuilds. [PR #262](https://github.com/rusty4444/hermes-android/pull/262) · [Publication commit](https://github.com/rusty4444/hermes-android/commit/c031637d650f3fac85b266e0a12792f0b4faacce) Automated fixtures do not establish real-device or provider-failover results. No GitLab/F-Droid update accompanies this release. Hermes Agent assisted with implementation, review, tests and release preparation.