Compare commits

...
Author SHA1 Message Date
Bailey Dixon 77e34c2c02 fix(android): preserve secure gateway routes 2026-07-28 19:35:14 -04:00
Bailey Dixon f4ee409106 docs(devlog): record Android 1.5.2 release 2026-07-28 18:20:37 -04:00
Bailey Dixon bfb608bea6 release(android): android-v1.5.2 2026-07-28 17:30:59 -04:00
Bailey Dixon 95a95fe7d2 Merge pull request #264 from Codename-11/fix/android-nous-native-auth
fix(android): support Nous system-browser sign-in
2026-07-28 17:28:56 -04:00
Bailey Dixon 1bdf2ae71b fix(android): support Nous system-browser sign-in 2026-07-28 17:15:26 -04:00
Bailey Dixon f9e7a2f320 Merge pull request #263 from Codename-11/fix/android-duplicate-compose-keys
fix(android): coalesce replayed chat message ids
2026-07-27 11:38:06 -04:00
Bailey Dixon 988fac8522 Merge pull request #262 from Codename-11/fix/android-oidc-manage-callback
fix(android): keep dashboard OIDC on cookie flow
2026-07-27 11:37:43 -04:00
Bailey Dixon d4832a6a38 fix(android): coalesce replayed chat message ids 2026-07-27 09:30:39 -04:00
Bailey Dixon f9c8736e5b fix(android): keep dashboard OIDC on cookie flow 2026-07-27 08:57:17 -04:00
dependabot[bot] a815dd33fa build(deps): bump com.android.library from 9.3.0 to 9.3.1 (#261)
Bumps com.android.library from 9.3.0 to 9.3.1.

---
updated-dependencies:
- dependency-name: com.android.library
  dependency-version: 9.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-27 11:56:57 +00:00
dependabot[bot] cc9c75a636 build(deps): bump androidx.browser:browser from 1.9.0 to 1.10.0 (#260)
Bumps androidx.browser:browser from 1.9.0 to 1.10.0.

---
updated-dependencies:
- dependency-name: androidx.browser:browser
  dependency-version: 1.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-27 11:55:03 +00:00
dependabot[bot] 43179e03c0 build(deps): bump com.android.application from 9.3.0 to 9.3.1 (#259)
Bumps com.android.application from 9.3.0 to 9.3.1.

---
updated-dependencies:
- dependency-name: com.android.application
  dependency-version: 9.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-27 11:55:00 +00:00
Bailey Dixon 693ac4ed64 Merge pull request #256 from Codename-11/release/android-1.5.1-patch
release(android): android-v1.5.1
2026-07-26 15:44:19 -04:00
Bailey Dixon f94d663ac4 release(android): android-v1.5.1 2026-07-26 15:35:21 -04:00
Bailey Dixon d1a21bd42e fix(android): use Compose resources for sign-in copy 2026-07-26 15:35:20 -04:00
Bailey Dixon 7ee2d73010 fix(android): preserve formatted chat completion position 2026-07-26 15:10:48 -04:00
Bailey Dixon 682bde84fe fix(android): merge API 36 target 2026-07-26 09:38:22 -04:00
Bailey Dixon 16bdbe5f44 fix(android): target API 36 2026-07-26 09:38:00 -04:00
Bailey Dixon f43fba9fed feat(android): merge chat readability and final-only voice 2026-07-26 09:13:57 -04:00
Bailey Dixon d1745413fd fix(android): release realtime background foreground turns 2026-07-26 08:57:00 -04:00
Bailey Dixon 1b7a8025c3 fix(android): restore standard voice narration 2026-07-26 08:56:42 -04:00
Bailey Dixon d92a87483e feat(android): enhance voice conversation experience 2026-07-26 08:56:23 -04:00
Bailey Dixon 0bea626ed8 Merge pull request #253 from Codename-11/fix/android-release-dispatch
fix(android): repair immutable release dispatch
2026-07-25 18:30:27 -04:00
Bailey Dixon f453dd27f3 fix(android): repair immutable release dispatch 2026-07-25 18:29:32 -04:00
Bailey Dixon 36546c2712 Merge pull request #251 from Codename-11/release/android-1.5.1
release(android): android-v1.5.0
2026-07-25 17:54:01 -04:00
Bailey Dixon fbe3fc3e05 release(android): android-v1.5.0 2026-07-25 17:34:26 -04:00
Bailey Dixon a77cebec43 fix(android): refine agent passport interactions 2026-07-25 17:28:46 -04:00
Bailey Dixon 8167f93705 fix(android): repair developer options and data actions 2026-07-25 16:33:03 -04:00
Bailey Dixon 52dc46072e feat(android): redesign agent passport drawer 2026-07-25 16:32:15 -04:00
Bailey Dixon c18ab4cce8 fix(android): complete new localized strings 2026-07-25 14:39:03 -04:00
Bailey Dixon 52b28e5b48 Merge pull request #246 from Codename-11/fix/reconcile-dev-delivery
fix(android): reconcile completed dev work
2026-07-25 14:35:13 -04:00
Bailey Dixon 575fd82c59 Merge branch 'fix/android-cold-start-api-toast' into dev 2026-07-25 14:32:28 -04:00
Bailey Dixon ead3f5fd4f fix(android): suppress cold-start API fallback 2026-07-25 14:24:56 -04:00
Bailey Dixon 36a922be64 Merge branch 'feature/image-generation-progress' into dev
# Conflicts:
#	app/src/main/kotlin/com/hermesandroid/relay/ui/components/MessageBubble.kt
2026-07-25 14:11:57 -04:00
Bailey Dixon 530a1c9591 feat(android): refine image generation progress 2026-07-25 14:10:28 -04:00
Bailey Dixon 353faa9da5 Merge branch 'chore/android-ci-feedback' into dev
# Conflicts:
#	DEVLOG.md
2026-07-25 14:07:10 -04:00
Bailey Dixon 76fdbcfd70 Merge branch 'fix/android-gateway-card-routing' into dev 2026-07-25 12:57:08 -04:00
Bailey Dixon 5365e22fff fix(android): keep gateway card actions on gateway 2026-07-25 12:56:42 -04:00
Bailey Dixon 1e3974fd88 feat(android): complete native dashboard sign-in 2026-07-25 12:33:01 -04:00
Bailey Dixon 72854d58b1 Merge origin/dev into dev before native sign-in completion 2026-07-25 11:45:47 -04:00
Bailey Dixon b63e0e726d Merge pull request #245 from Codename-11/fix/android-active-turn-notifications
feat(android): retain active turns in background
2026-07-25 11:42:44 -04:00
Bailey Dixon fff3ba8d91 feat(android): retain active turns in background 2026-07-25 11:41:41 -04:00
Bailey Dixon 7c155e3693 test(android): stabilize integrated UX fixtures 2026-07-25 11:38:45 -04:00
Bailey Dixon d15d3b594c fix(android): restore routing integration imports 2026-07-25 11:26:40 -04:00
Bailey Dixon 915b2ebe54 Merge branch 'feature/android-relay-ux-batch' into dev 2026-07-25 11:24:00 -04:00
Bailey Dixon cf3634ee2b Merge branch 'feature/hrui-059-072-routing' into feature/android-relay-ux-batch
# Conflicts:
#	TODO.md
2026-07-25 11:23:37 -04:00
Bailey Dixon 88b11856d3 test(android): fix recovery ack fixture 2026-07-25 11:23:07 -04:00
Bailey Dixon aede6c8cb3 fix(android): harden fallback model locks 2026-07-25 11:16:13 -04:00
Bailey Dixon c1187f0f2f Merge branch 'feature/hrui-030-approval' into feature/android-relay-ux-batch 2026-07-25 11:16:07 -04:00
Bailey Dixon 6ff473820c Merge branch 'feature/hrui-069-moa' into feature/android-relay-ux-batch
# Conflicts:
#	app/src/main/kotlin/com/hermesandroid/relay/network/upstream/GatewayEventMapper.kt
2026-07-25 11:15:57 -04:00
Bailey Dixon 847a21cc0c Merge branch 'feature/hrui-063-065-voice' into feature/android-relay-ux-batch 2026-07-25 11:15:04 -04:00
Bailey Dixon 8ebd97643d Merge attachment test fix into feature/android-relay-ux-batch 2026-07-25 11:15:03 -04:00
Bailey Dixon 8aded16da9 test(android): fix attachment assertion imports 2026-07-25 11:14:28 -04:00
Bailey Dixon a35c0b34f8 Merge branch 'feature/hrui-074-040-recovery' into feature/android-relay-ux-batch 2026-07-25 11:14:27 -04:00
Bailey Dixon 877cfad88a Merge branch 'feature/hrui-060-native-pkce' into feature/android-relay-ux-batch 2026-07-25 11:14:06 -04:00
Bailey Dixon fb0b8deef7 feat(android): expose profile approval modes 2026-07-25 11:10:48 -04:00
Bailey Dixon 1a710f071c fix(android): serialize gateway resume events 2026-07-25 11:07:59 -04:00
Bailey Dixon 89b1461431 fix(android): scope and serialize dashboard auth 2026-07-25 11:07:00 -04:00
Bailey Dixon ce72f7790e Merge branch 'feature/android-collapsible-attachments' into feature/android-relay-ux-batch 2026-07-25 11:05:57 -04:00
Bailey Dixon 51f4d29ebb Merge branch 'feature/hrui-073-resume-media' into feature/android-relay-ux-batch 2026-07-25 11:05:56 -04:00
Bailey Dixon 97a2dac96d Merge branch 'feature/hrui-manage-ux' into feature/android-relay-ux-batch 2026-07-25 11:05:55 -04:00
Bailey Dixon a569361d43 fix(android): reconcile MoA advisor state 2026-07-25 11:02:34 -04:00
Bailey Dixon 35dfc8c051 fix(android): narrate complete assistant runs 2026-07-25 11:01:09 -04:00
Bailey Dixon 4a1ece7ad0 fix(android): restore persisted image attachments 2026-07-25 10:58:38 -04:00
Bailey Dixon 41b6fb4f84 feat(android): add collapsible attachment groups 2026-07-25 10:56:19 -04:00
Bailey Dixon a15b247d1a feat(android): improve Manage diagnostics and model discovery 2026-07-25 10:53:18 -04:00
Bailey Dixon 2d486dd395 fix(android): preserve API fallback model routing 2026-07-25 10:51:08 -04:00
Bailey Dixon 0fcb833c83 feat(android): surface MoA advisor progress 2026-07-25 10:49:40 -04:00
Bailey Dixon 4507b2270a fix(android): recover failed gateway turns 2026-07-25 10:49:10 -04:00
Bailey Dixon 1cd3da5ac6 feat(android): add native dashboard auth foundation 2026-07-25 10:46:16 -04:00
Bailey Dixon afe2be9304 Merge pull request #242 from Codename-11/fix/android-interaction-notifications
fix(android): notify for blocked gateway interactions
2026-07-25 09:47:58 -04:00
Bailey Dixon 60c14b5db1 Merge origin/dev into fix/android-interaction-notifications 2026-07-25 09:40:24 -04:00
Bailey Dixon e3d6dd9509 Merge pull request #244 from Codename-11/fix/onboarding-permissions-setup
fix(android): add onboarding permission setup
2026-07-24 22:59:24 -04:00
Bailey Dixon 91d05c982e Merge origin/dev into fix/onboarding-permissions-setup 2026-07-24 22:50:57 -04:00
Bailey Dixon 85bbbd004d Merge pull request #243 from Codename-11/fix/android-markdown-user-ca
fix(android): harden Markdown and private CA connections
2026-07-24 22:37:54 -04:00
Bailey Dixon a8f61f2aeb docs: restore route and localization checks 2026-07-24 22:04:46 -04:00
Bailey Dixon d554c1819a fix(android): preserve promoted background task rows 2026-07-24 22:04:42 -04:00
Bailey Dixon 920e7d58f0 fix(android): add onboarding permission setup 2026-07-24 17:34:20 -04:00
Bailey Dixon 0ce7c6c6b3 fix(android): trust user-installed certificate authorities 2026-07-24 16:44:36 -04:00
Bailey Dixon 46e8f90c39 fix(android): guard markdown highlight ranges 2026-07-24 16:44:35 -04:00
Bailey Dixon 2d28f171e0 fix(android): hide dashboard source badge 2026-07-24 16:29:44 -04:00
Bailey Dixon fdd8301796 fix(android): smooth image generation transition 2026-07-24 08:29:40 -04:00
Bailey Dixon c9ddc2ef8d fix(android): notify for blocked gateway interactions 2026-07-23 22:05:26 -04:00
Bailey Dixon b0d662b802 feat(relay): bridge image generation activity 2026-07-23 21:36:13 -04:00
Bailey Dixon 63ca0a1428 Merge feature/hrui-ledger-all-20260723 into dev 2026-07-23 21:11:00 -04:00
Bailey Dixon 8196856d76 docs: align upstream impact ledger guidance 2026-07-23 21:10:08 -04:00
Bailey Dixon 605ff00cc0 fix(android): consume upstream display metadata 2026-07-23 21:09:01 -04:00
Bailey Dixon c9b1e1b04e fix(android): keep active chat progress visible 2026-07-23 20:57:10 -04:00
Bailey Dixon a4466e4ca0 fix(android): show image animation when tools are hidden 2026-07-23 20:34:41 -04:00
Bailey Dixon e13e381e3a docs(android): clarify shared dashboard sessions 2026-07-23 20:20:31 -04:00
Bailey Dixon 19d33910d0 fix(android): share dashboard session across routes 2026-07-23 20:17:57 -04:00
Bailey Dixon 41480a3254 fix(android): refresh dashboard-only route changes 2026-07-23 19:33:13 -04:00
Bailey Dixon 50f151edba fix(android): derive dashboard for QR routes 2026-07-23 19:18:50 -04:00
Bailey Dixon 0f108fe971 fix(android): move dashboard with active route 2026-07-23 18:42:13 -04:00
Bailey Dixon c8d6119e1a fix(android): probe remote health with GET 2026-07-23 17:18:10 -04:00
Bailey Dixon b2b7a2572b fix(android): restore remote route surfaces 2026-07-23 09:03:20 -04:00
Bailey Dixon 1ccf87401a fix(android): rebind gateway turns and dedupe sessions 2026-07-22 23:23:34 -04:00
Bailey Dixon 50b1a17895 release(server): server-v1.4.3 2026-07-22 22:52:27 -04:00
Bailey Dixon d536923c55 release(android): android-v1.5.0 2026-07-22 22:50:30 -04:00
Bailey Dixon 14a2e01ac5 Merge feature/hrui-063-standard-voice-streaming into dev 2026-07-22 22:12:47 -04:00
Bailey Dixon a0d03f6947 feat(android): stream Standard Hermes voice replies 2026-07-22 22:12:39 -04:00
Bailey Dixon 478eeac3f7 Merge fix/hrui-061-correction-copy into dev 2026-07-22 22:01:35 -04:00
Bailey Dixon 799159457a fix(android): finish active-turn correction copy 2026-07-22 22:01:18 -04:00
Bailey Dixon f90650bdc9 Merge docs/hrui-056-ops-audit into dev 2026-07-22 21:06:06 -04:00
Bailey Dixon 6a41ec154c Merge feature/hrui-android-diagnostics-manage into dev 2026-07-22 21:05:57 -04:00
Bailey Dixon 53f4c8187b Merge feature/hrui-android-gateway-controls into dev 2026-07-22 21:05:49 -04:00
Bailey Dixon 675252090c Merge feature/hrui-plugin-compat-diagnostics into dev 2026-07-22 21:05:42 -04:00
Bailey Dixon e94db467e8 docs: add Hermes update restart audit 2026-07-22 21:05:25 -04:00
Bailey Dixon 65dae79c8c feat(android): consume dashboard health hints 2026-07-22 21:04:52 -04:00
Bailey Dixon e5d0334c8b feat(android): use gateway redirect and compress RPCs 2026-07-22 20:57:47 -04:00
Bailey Dixon 9cc7b25fd1 fix(plugin): align diagnostics and config route hygiene 2026-07-22 20:34:43 -04:00
Bailey Dixon 2ce352a320 fix(android): add voice settings translations 2026-07-20 20:40:37 -04:00
Bailey Dixon a6957268b9 Merge feature/upstream-ledger-next-batch into dev 2026-07-20 20:22:30 -04:00
Bailey Dixon 8f42b96be1 feat: consume upstream interim gateway events 2026-07-20 20:22:02 -04:00
Bailey Dixon 8a9c058ddb Merge feature/voice-settings-layout-v2 into dev 2026-07-20 20:08:59 -04:00
Bailey Dixon 5ef2c40f81 feat(android): expand voice settings discovery 2026-07-20 20:08:52 -04:00
Bailey Dixon 6b32fe7ddd Merge feature/voice-settings-preview into dev 2026-07-20 10:52:26 -04:00
Bailey Dixon 02f38322fa feat(android): improve voice settings previews 2026-07-20 10:52:11 -04:00
Bailey Dixon f40b7abaf0 Merge feature/open-ledger-batches into dev 2026-07-20 10:20:50 -04:00
Bailey Dixon 5fcbe5ff63 Merge origin/dev into dev 2026-07-20 10:20:37 -04:00
Bailey Dixon 6ce504b1c9 Merge OAuth dashboard binding fix 2026-07-20 10:07:17 -04:00
Bailey Dixon 31ebef825f fix(android): bind oauth flow to dashboard 2026-07-20 10:07:03 -04:00
Bailey Dixon 68abbf156d Merge Manage localization follow-up 2026-07-20 09:39:02 -04:00
Bailey Dixon 73a8af7c8f fix(android): localize manage parity strings 2026-07-20 09:38:44 -04:00
Bailey Dixon 2db00d4c59 Merge feature/hrui-direct-chat-compat 2026-07-20 09:10:47 -04:00
Bailey Dixon 847444d115 fix(android): cap inline image lifecycle memory 2026-07-20 09:09:27 -04:00
Bailey Dixon 798e8eef55 Merge feature/hrui-manage-parity 2026-07-20 09:05:14 -04:00
Bailey Dixon 35f791be50 Merge pull request #238 from Codename-11/feature/axi-129-image-generation-animation
feat(android): show diffusion animation during image generation
2026-07-20 09:03:45 -04:00
Bailey Dixon e727979897 fix(android): safely gate hosted oauth 2026-07-20 09:03:35 -04:00
Bailey Dixon 91025b733f fix(android): bound inline data image memory 2026-07-20 09:01:16 -04:00
Bailey Dixon 34da86a96a fix(android): refresh locale source hashes after image gen string
Translated catalogs already include image_generation_rendering; update
localization-status source_sha256 so check-android-locales stays green.

Forge: AXI-129
2026-07-20 08:56:50 -04:00
Bailey Dixon 30f9f51e2a fix(android): preserve hosted oauth scope 2026-07-20 08:54:33 -04:00
Bailey Dixon 713529f79f Merge feature/hrui-session-controls 2026-07-20 08:50:09 -04:00
Bailey Dixon 16d1728306 fix(android): honor session control reset semantics 2026-07-20 08:49:20 -04:00
Bailey Dixon 7a813995ba feat(android): show diffusion animation during image generation
Specialize pending image_generate tool parts with a theme-aware procedural
diffusion placeholder and accessibility announcement. Vanilla Hermes already
emits the generic tool lifecycle, so this stays client-only.

Forge: AXI-129
2026-07-20 08:49:12 -04:00
Bailey Dixon c86b2224ce feat(android): align direct chat with upstream contracts 2026-07-20 08:47:20 -04:00
Bailey Dixon 11a782bc44 feat(android): add hosted manage parity 2026-07-20 08:36:48 -04:00
Bailey Dixon 884a17ded7 Merge certification coverage fixes 2026-07-20 08:25:32 -04:00
Bailey Dixon 745904d468 test: cover background delivery ownership 2026-07-20 08:21:54 -04:00
Bailey Dixon 4258322acc test: run delegation ownership certification 2026-07-20 08:17:43 -04:00
Bailey Dixon 2c544b8ab0 Merge feature/hrui-live-certification 2026-07-20 08:11:43 -04:00
Bailey Dixon 5122ee69f6 test: automate upstream compatibility preflight 2026-07-20 08:11:18 -04:00
Bailey Dixon 512199448e Merge origin/dev into dev 2026-07-20 08:02:22 -04:00
dependabot[bot] 7a7b10f08a chore(deps): bump com.meta.spatial:spatial-gradle-plugin-impl (#237)
Bumps com.meta.spatial:spatial-gradle-plugin-impl from 0.13.1 to 0.13.2.

---
updated-dependencies:
- dependency-name: com.meta.spatial:spatial-gradle-plugin-impl
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-20 11:56:33 +00:00
dependabot[bot] f7845291e7 chore(deps): bump spatialsdk from 0.13.1 to 0.13.2 (#236)
Bumps `spatialsdk` from 0.13.1 to 0.13.2.

Updates `com.meta.spatial:meta-spatial-sdk` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-compose` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-ovrmetrics` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-toolkit` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-vr` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-isdk` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-castinputforward` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-hotreload` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-datamodelinspector` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-uiset` from 0.13.1 to 0.13.2

Updates `com.meta.spatial:meta-spatial-sdk-mruk` from 0.13.1 to 0.13.2

---
updated-dependencies:
- dependency-name: com.meta.spatial:meta-spatial-sdk
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-compose
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-ovrmetrics
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-toolkit
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-vr
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-isdk
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-castinputforward
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-hotreload
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-datamodelinspector
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-uiset
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.meta.spatial:meta-spatial-sdk-mruk
  dependency-version: 0.13.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-20 11:56:03 +00:00
dependabot[bot] 689219405b chore(deps): bump the testing group with 2 updates (#235)
Bumps the testing group with 2 updates: [io.github.takahirom.roborazzi:roborazzi](https://github.com/takahirom/roborazzi) and [io.github.takahirom.roborazzi:roborazzi-compose](https://github.com/takahirom/roborazzi).


Updates `io.github.takahirom.roborazzi:roborazzi` from 1.68.0 to 1.70.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](https://github.com/takahirom/roborazzi/compare/1.68.0...1.70.0)

Updates `io.github.takahirom.roborazzi:roborazzi-compose` from 1.68.0 to 1.70.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](https://github.com/takahirom/roborazzi/compare/1.68.0...1.70.0)

---
updated-dependencies:
- dependency-name: io.github.takahirom.roborazzi:roborazzi
  dependency-version: 1.70.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: testing
- dependency-name: io.github.takahirom.roborazzi:roborazzi-compose
  dependency-version: 1.70.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: testing
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-20 11:55:47 +00:00
Bailey Dixon f4e9de425a Merge feature/upstream-ledger-batch into dev
# Conflicts:
#	app/src/main/kotlin/com/hermesandroid/relay/ui/screens/DiagnosticsScreen.kt
#	docs/upstream-surface-matrix.md
2026-07-20 07:41:48 -04:00
Bailey Dixon 2bfe21eaff chore(ci): shorten Android validation feedback 2026-07-19 20:50:36 -04:00
Bailey Dixon d4cdb96bab fix: preserve running queued recovery handoff 2026-07-19 20:20:36 -04:00
Bailey Dixon 481ad48c57 chore(release): prepare Android 1.4.9 2026-07-19 19:55:35 -04:00
Bailey Dixon c5f35145b4 Merge queued recovery boundary fixes 2026-07-19 19:53:02 -04:00
Bailey Dixon 3283c9b601 fix: preserve resumed gateway turn boundaries 2026-07-19 19:52:46 -04:00
Bailey Dixon 74be630e05 Merge pull request #231 from Codename-11/feature/dashboard-primary-connections
feat(android): make dashboard the primary connection
2026-07-19 19:47:04 -04:00
Bailey Dixon 44f030f93b docs: block one-turn model automation on atomicity 2026-07-19 19:44:35 -04:00
Bailey Dixon abce00f49e Revert "Merge feature/hrui-046-model-once"
This reverts commit 61c4337807, reversing
changes made to 6e1338004c.
2026-07-19 19:44:19 -04:00
Bailey Dixon a61d27a92d feat(android): make dashboard the primary connection
Make the Hermes dashboard the standard connection path with API fallback and optional Relay pairing. Redesign onboarding and connection management, add startup preference and route/security details, reconcile pinned profile identity and hostname discovery, and update tests, docs, and localized resources.
2026-07-19 19:39:28 -04:00
Bailey Dixon 123f1d1263 docs: record upstream ledger follow-ups 2026-07-19 19:37:47 -04:00
Bailey Dixon 61c4337807 Merge feature/hrui-046-model-once 2026-07-19 19:26:42 -04:00
Bailey Dixon 6e1338004c Merge feature/hrui-047-queued-recovery 2026-07-19 19:25:59 -04:00
Bailey Dixon 348152a7cb Merge feature/hrui-044-windows-ca 2026-07-19 19:25:59 -04:00
Bailey Dixon 3ec34502ec feat(chat): add one-turn model selection 2026-07-19 19:25:55 -04:00
Bailey Dixon d30de8656d fix(android): scope diagnostics toolsets to profile 2026-07-19 19:25:52 -04:00
Bailey Dixon 9b9b8c7c06 Merge feature/hrui-038-profile-routing
# Conflicts:
#	app/src/main/kotlin/com/hermesandroid/relay/network/upstream/DashboardApiClient.kt
2026-07-19 19:25:21 -04:00
Bailey Dixon 93b82aa538 feat: surface queued recovery and project labels 2026-07-19 19:24:20 -04:00
Bailey Dixon 7f2049fa0a fix(desktop): trust Windows system certificate authorities 2026-07-19 19:24:16 -04:00
Bailey Dixon 92444a7039 feat(android): route multiplex profile API traffic 2026-07-19 19:23:31 -04:00
Bailey Dixon a02d7e10df Merge feature/hrui-diagnostics-bundle
# Conflicts:
#	docs/upstream-surface-matrix.md
2026-07-19 19:18:29 -04:00
Bailey Dixon 8a3935ffa1 feat: add upstream gateway diagnostics 2026-07-19 19:17:18 -04:00
Bailey Dixon e48935929a Merge bootstrap database initialization follow-up 2026-07-19 19:07:15 -04:00
Bailey Dixon 1e82347e7d fix(plugin): offload bootstrap database initialization 2026-07-19 19:06:59 -04:00
Bailey Dixon 75ed3c4226 Merge feature/hrui-004-012-bootstrap-async 2026-07-19 18:34:26 -04:00
Bailey Dixon bade61ac34 fix(plugin): offload bootstrap compatibility state 2026-07-19 18:28:14 -04:00
Bailey Dixon f88559f856 docs: define upstream compatibility gates 2026-07-19 18:25:57 -04:00
Bailey Dixon 22e4d24817 Merge pull request #229 from Codename-11/fix/windows-gateway-pid-probe
fix(plugin): avoid signalling gateway PID on Windows
2026-07-18 21:58:15 -04:00
Bailey Dixon 7edaa2df14 test(plugin): preserve PID identity coverage 2026-07-18 21:57:07 -04:00
Bailey Dixon 165feaa0d6 fix(plugin): avoid signalling gateway PID on Windows 2026-07-18 21:55:03 -04:00
Bailey Dixon 8c516c3c8d Merge pull request #228 from Codename-11/main
chore: back-merge Android 1.4.8 hotfix
2026-07-18 12:22:29 -04:00
Bailey Dixon 40bb0a4ef8 Merge pull request #227 from Codename-11/fix/privacy-policy-url-hotfix
fix(android): restore Play privacy policy URL
2026-07-18 11:42:37 -04:00
Bailey Dixon d96898a6aa fix(android): restore Play privacy policy URL 2026-07-18 11:30:17 -04:00
Bailey Dixon b4e595e320 Merge pull request #226 from Codename-11/dev
release: Android 1.4.7
2026-07-18 10:29:31 -04:00
Bailey Dixon 31c41fb2ff Merge pull request #225 from Codename-11/fix/android-1.4.7-release-prep
release(android): android-v1.4.7
2026-07-18 09:56:28 -04:00
Bailey Dixon ab0f7b726a release(android): android-v1.4.7 2026-07-18 09:49:04 -04:00
Bailey Dixon f72904ab53 Merge pull request #206 from Codename-11/docs/branch-release-contract
docs: reconcile branch and release contract
2026-07-18 09:41:46 -04:00
Bailey Dixon 4fc5f668de merge: refresh branch contract from dev 2026-07-18 09:34:49 -04:00
Bailey Dixon cedc340091 Merge pull request #224 from Codename-11/fix/reconcile-dev-release
fix: reconcile release history and Android localization
2026-07-18 09:33:48 -04:00
Bailey Dixon 97cb30c927 merge: back-merge main release history into dev 2026-07-18 09:23:01 -04:00
Bailey Dixon ed41be3390 merge: reconcile Android localization into dev 2026-07-18 09:22:39 -04:00
Bailey Dixon 08816cfe63 Merge pull request #222 from Codename-11/fix/smooth-stream-rendering
fix(android): smooth streamed reply rendering
2026-07-17 14:44:40 -04:00
Bailey Dixon 01a0cde589 fix(android): smooth streamed reply rendering 2026-07-17 14:35:12 -04:00
Bailey Dixon ed6742afe4 Merge pull request #219 from Codename-11/fix/smooth-stream-finalization
fix(android): smooth streamed reply finalization
2026-07-17 09:22:45 -04:00
Bailey Dixon a6264df910 fix(android): smooth streamed reply finalization 2026-07-17 09:14:34 -04:00
Bailey Dixon 64e2e2eca6 Merge pull request #218 from Codename-11/fix/post-stream-history-scroll
fix(android): preserve chat anchor across history reload
2026-07-17 07:42:46 -04:00
Bailey Dixon 1ccaf2c4f1 fix(android): preserve chat anchor across history reload 2026-07-17 07:33:40 -04:00
Bailey Dixon 7686bb41e7 Merge pull request #217 from Codename-11/fix/stream-final-scroll-anchor
fix(android): retain chat bottom after stream completion
2026-07-16 21:03:11 -04:00
Bailey Dixon a940b4b8ea fix(android): retain chat bottom after stream completion 2026-07-16 20:55:01 -04:00
Bailey Dixon 46afdeab59 Merge pull request #216 from Codename-11/fix/critical-relay-security
fix(security): enforce Relay privileged boundaries
2026-07-16 20:23:16 -04:00
Bailey Dixon d4a8aad050 fix(ci): classify PR paths from merge commit 2026-07-16 19:38:00 -04:00
Bailey Dixon 0a6e95ae74 fix(ci): retry transient path classification failures 2026-07-16 19:36:05 -04:00
Bailey Dixon a6fc53e5cf docs: record critical relay hardening 2026-07-16 19:33:11 -04:00
Bailey Dixon c013daacda fix(security): prevent relay session self-upgrade 2026-07-16 19:27:39 -04:00
Bailey Dixon f5b1d377a4 fix(security): enforce terminal session grants 2026-07-16 19:26:12 -04:00
Bailey Dixon bb1e406f3f fix(security): redact remote profile config 2026-07-16 19:26:06 -04:00
Bailey Dixon 10213ca8ed fix(security): authorize Android bridge HTTP routes 2026-07-16 19:25:52 -04:00
Bailey Dixon cbfccd8ccf fix(security): keep voice provider origins host-controlled 2026-07-16 19:21:17 -04:00
Bailey Dixon c3c98caa31 fix(security): require host-authorized pairing 2026-07-16 19:18:02 -04:00
Bailey Dixon ed60abd57c Merge pull request #215 from Codename-11/fix/docs-docker-assets
fix(website): restore production docs build context
2026-07-16 17:42:30 -04:00
Bailey Dixon cab0d90530 fix(website): restore production docs build context 2026-07-16 17:40:03 -04:00
Bailey Dixon d977600f9d Merge pull request #214 from Codename-11/dev
merge: promote localized public experience
2026-07-16 15:51:48 -04:00
Bailey Dixon c902c00101 Merge pull request #213 from Codename-11/feature/docs-home-hub
feat: modernize and localize public experience
2026-07-16 15:38:49 -04:00
Bailey Dixon aa6b48a068 merge: sync latest main into public experience work
# Conflicts:
#	DEVLOG.md
2026-07-16 15:31:18 -04:00
Bailey Dixon 50297d1496 feat: modernize and localize public experience 2026-07-16 15:29:39 -04:00
Bailey Dixon d80f36a087 merge: add Android German Portuguese and Japanese 2026-07-16 08:46:29 -04:00
Bailey Dixon b6117c2d41 Merge pull request #212 from Codename-11/fix/docs-clean-urls
fix(website): serve VitePress clean URLs
2026-07-16 08:04:39 -04:00
Bailey Dixon b0ee6935fe fix(website): serve VitePress clean URLs 2026-07-16 08:02:26 -04:00
Bailey Dixon 33538fde0c Merge pull request #211 from Codename-11/fix/legacy-docs-redirect
fix(docs): add temporary legacy redirects
2026-07-16 07:58:37 -04:00
Bailey Dixon 603919c8ff fix(docs): add temporary legacy redirects 2026-07-16 07:56:09 -04:00
Bailey Dixon 52df3adbf6 Merge pull request #210 from Codename-11/fix/retire-github-pages
fix(docs): retire GitHub Pages
2026-07-16 07:42:52 -04:00
Bailey Dixon 3eab11c639 fix(docs): retire GitHub Pages 2026-07-15 21:48:20 -04:00
Bailey Dixon 2673f228bb Merge pull request #209 from Codename-11/fix/website-coolify-deployment
fix(website): add Coolify root-context build
2026-07-15 20:37:28 -04:00
Bailey Dixon 53b8f6a418 fix(website): add Coolify root-context build 2026-07-15 20:35:51 -04:00
Bailey Dixon 0146e2b25d release: Android 1.4.6 and Plugin 1.4.2 (#208)
Play preflight passed for the exact release tree. Publishes Android 1.4.6 and Plugin 1.4.2.
2026-07-15 20:28:27 -04:00
Bailey Dixon 126e5a9600 merge: sync main website release into dev 2026-07-15 20:15:33 -04:00
Bailey Dixon 55f50446a4 release(plugin): plugin-v1.4.2 2026-07-15 20:03:54 -04:00
Bailey Dixon effa834e4e release(android): android-v1.4.6 2026-07-15 20:03:26 -04:00
Bailey Dixon 6d480b4131 feat(website): add Hermes-Relay marketing site (#207)
feat(website): add Hermes-Relay marketing site
2026-07-15 20:02:50 -04:00
Bailey Dixon ea38fc4ab5 feat(website): add Hermes-Relay marketing site 2026-07-15 19:57:50 -04:00
Bailey Dixon 72e893dc81 merge: clarify profile image import fallback 2026-07-15 18:50:35 -04:00
Bailey Dixon 8dc7fdd7a0 fix(android): clarify profile image import fallback 2026-07-15 18:50:30 -04:00
Bailey Dixon 795851c592 merge: fix server-default profile session scope
# Conflicts:
#	DEVLOG.md
2026-07-15 18:22:56 -04:00
Bailey Dixon 02f407241f fix(android): scope server default sessions to active profile 2026-07-15 18:16:02 -04:00
Bailey Dixon d6f94b2b5b merge: add host profile image import 2026-07-15 17:42:59 -04:00
Bailey Dixon c5ee0670e9 feat(android): import profile icons from agent hosts 2026-07-15 17:42:50 -04:00
Bailey Dixon 87cd9e7b9d docs: keep main as GitHub default branch 2026-07-15 14:56:32 -04:00
Bailey Dixon 51a020bd22 merge: refresh branch contract from dev 2026-07-15 14:37:07 -04:00
Bailey Dixon 34ff4d0629 docs: reconcile branch and release contract 2026-07-15 14:37:01 -04:00
Bailey Dixon 06ba20406b Merge pull request #199 from Codename-11/feature/profile-management
feat(android): add profile display management
2026-07-15 14:19:14 -04:00
Bailey Dixon a63b9b9828 merge: refresh profile management from dev
# Conflicts:
#	DEVLOG.md
#	docs/localization-status.json
2026-07-15 14:10:56 -04:00
Bailey Dixon 72f1b68176 Merge pull request #201 from dependabot/github_actions/dev/actions/setup-node-7
chore(deps): bump actions/setup-node from 6 to 7
2026-07-15 14:02:10 -04:00
Bailey Dixon 18c3ecf531 docs: record Android 1.4.5 release 2026-07-15 13:46:25 -04:00
Bailey Dixon b6cb12e2da merge: sync android-v1.4.5 release 2026-07-15 13:45:33 -04:00
Bailey Dixon d99c2e5e45 Merge pull request #205 from Codename-11/dev
Automate the Play approval gate and advance Android 1.4.5 to versionCode 28.
2026-07-15 13:14:11 -04:00
dependabot[bot] 1ab9d2f4af chore(deps): bump kotlin from 2.4.0 to 2.4.10 (#204)
Bumps `kotlin` from 2.4.0 to 2.4.10.

Updates `org.jetbrains.kotlin.plugin.compose` from 2.4.0 to 2.4.10
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.0...v2.4.10)

Updates `org.jetbrains.kotlin.plugin.serialization` from 2.4.0 to 2.4.10
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.0...v2.4.10)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin.plugin.compose
  dependency-version: 2.4.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.jetbrains.kotlin.plugin.serialization
  dependency-version: 2.4.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-15 16:55:03 +00:00
Bailey Dixon b406ce0e3e fix(release): automate Play approval gate 2026-07-15 12:49:28 -04:00
Bailey Dixon b92a04de81 merge: reconcile dev dependency updates 2026-07-15 12:41:15 -04:00
dependabot[bot] 78f0710ee0 chore(deps): bump com.android.application from 9.2.1 to 9.3.0 (#203)
Bumps com.android.application from 9.2.1 to 9.3.0.

---
updated-dependencies:
- dependency-name: com.android.application
  dependency-version: 9.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-15 16:16:03 +00:00
dependabot[bot] 87c2a8f000 chore(deps): bump com.android.library from 9.2.1 to 9.3.0 (#202)
Bumps com.android.library from 9.2.1 to 9.3.0.

---
updated-dependencies:
- dependency-name: com.android.library
  dependency-version: 9.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-15 16:14:03 +00:00
dependabot[bot] f5533d262b chore(deps): bump actions/setup-node from 6 to 7
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 6 to 7.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](https://github.com/actions/setup-node/compare/v6...v7)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-15 16:13:29 +00:00
Bailey Dixon 896f276b7c Merge pull request #200 from Codename-11/dev
release(android): android-v1.4.5
2026-07-15 12:12:32 -04:00
Bailey Dixon af3c494697 merge: reconcile main release history
# Conflicts:
#	DEVLOG.md
2026-07-15 11:46:48 -04:00
Bailey Dixon 77c1c8bee5 release(android): android-v1.4.5 2026-07-15 11:46:19 -04:00
Bailey Dixon c452c25148 feat(android): integrate expanded language support 2026-07-15 11:24:54 -04:00
Bailey Dixon 0db5c02722 feat(android): add Japanese localization 2026-07-15 10:57:40 -04:00
Bailey Dixon 4630695c17 feat(android): add Brazilian Portuguese localization 2026-07-15 10:52:15 -04:00
Bailey Dixon f4ee440015 feat(android): add German localization 2026-07-15 10:52:15 -04:00
Bailey Dixon 2dc47e8ecd merge: gateway safety follow-up 2026-07-15 10:09:13 -04:00
Bailey Dixon a3fdfc2647 feat(android): align gateway safety signals 2026-07-15 10:09:02 -04:00
Bailey Dixon 7d08786d28 merge: upstream gateway interaction compatibility
# Conflicts:
#	CHANGELOG.md
#	DEVLOG.md
#	app/src/main/kotlin/com/hermesandroid/relay/viewmodel/ChatViewModel.kt
2026-07-15 09:27:46 -04:00
Bailey Dixon 2de9b40fc5 fix(android): handle upstream gateway interaction lifecycle 2026-07-15 09:24:55 -04:00
Bailey Dixon f7541e3795 merge: session continuity and drawer titles 2026-07-15 08:57:20 -04:00
Bailey Dixon d89fb906b0 fix(android): preserve running chats across session switches 2026-07-15 08:57:11 -04:00
Bailey Dixon 963f1b7d85 test(android): cover hidden default profile recovery 2026-07-14 22:56:35 -04:00
Bailey Dixon 5c045798ae feat(android): add profile display management 2026-07-14 22:41:12 -04:00
Bailey Dixon 22e557a533 fix(android): use session previews for drawer titles 2026-07-14 22:04:01 -04:00
Bailey Dixon 03883b59b7 Merge pull request #198 from Codename-11/fix/roborazzi-dependabot
chore(deps): align Roborazzi and Dependabot routing
2026-07-14 14:50:01 -04:00
Bailey Dixon d679add380 Merge dev into fix/roborazzi-dependabot 2026-07-14 14:39:56 -04:00
Bailey Dixon f3c4bc1ad5 Merge pull request #195 from Codename-11/fix/axi-104-active-profile
fix(relay): respect Hermes active profile
2026-07-14 14:39:48 -04:00
Bailey Dixon e8282ec8b1 Merge pull request #197 from Codename-11/fix/codex-ci-main
chore(ci): promote Codex review automation to main
2026-07-14 14:39:45 -04:00
Bailey Dixon eccf1b07ac chore(deps): align Roborazzi and Dependabot routing 2026-07-14 14:39:09 -04:00
Bailey Dixon 354ecb56ea Merge dev into fix/axi-104-active-profile
# Conflicts:
#	DEVLOG.md
2026-07-14 14:30:04 -04:00
Bailey Dixon 8c827b47e5 chore(ci): replace Claude automation with Codex review 2026-07-14 14:27:17 -04:00
Bailey Dixon d6bbd02b4e Merge pull request #196 from Codename-11/fix/replace-claude-ci
chore(ci): replace Claude automation with Codex review
2026-07-14 14:05:07 -04:00
Bailey Dixon e9203f0174 chore(ci): replace Claude automation with Codex review 2026-07-14 13:51:41 -04:00
Bailey Dixon 9ad7474901 fix(relay): respect Hermes active profile 2026-07-14 09:17:57 -04:00
Bailey Dixon 98bf8cc25c release(cli): cli-v0.4.0-alpha.2
Merge tested dev state into main for the Hermes-Relay-CLI 0.4.0-alpha.2 prerelease.
2026-07-13 21:08:39 -04:00
Bailey Dixon be56892e61 Merge branch 'main' into dev 2026-07-13 20:55:51 -04:00
Bailey Dixon f92ea07692 merge: native CLI systray and cli-v0.4.0-alpha.2 prep
Merges the CLI/TUI-first desktop architecture, native menu-only Windows systray, desktop-use safety controls, release hardening, and refreshed public documentation into dev.
2026-07-13 20:54:06 -04:00
Bailey Dixon 3294f28074 release(cli): cli-v0.4.0-alpha.2 2026-07-13 20:50:40 -04:00
Bailey Dixon cc86b56092 refactor(desktop): replace Tauri app with native systray 2026-07-13 20:47:55 -04:00
Bailey Dixon 37a2f35db5 docs: fix Star History chart embed 2026-07-13 08:46:39 -04:00
dependabot[bot] 1db3387ffa chore(deps): bump com.google.crypto.tink:tink-android (#190)
Bumps [com.google.crypto.tink:tink-android](https://github.com/tink-crypto/tink-java) from 1.16.0 to 1.23.0.
- [Release notes](https://github.com/tink-crypto/tink-java/releases)
- [Commits](https://github.com/tink-crypto/tink-java/compare/v1.16.0...v1.23.0)

---
updated-dependencies:
- dependency-name: com.google.crypto.tink:tink-android
  dependency-version: 1.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-13 11:55:17 +00:00
Bailey Dixon 0f18380bf1 release(android): 1.4.4 (#189)
Play preflight passed for the exact release tree; merge dev to main for Android 1.4.4.
2026-07-12 21:12:14 -04:00
Bailey Dixon 211a8738ea fix(plugin): preserve native loader imports 2026-07-12 21:00:05 -04:00
Bailey Dixon 0503f35479 fix(i18n): normalize translation source hashes 2026-07-12 20:45:55 -04:00
Bailey Dixon e0349ef6c4 release(android): android-v1.4.4 2026-07-12 20:44:38 -04:00
Bailey Dixon 2037583edb merge: Spanish and diagnostics review features 2026-07-12 20:05:59 -04:00
Bailey Dixon f78affd2b2 feat(android): improve changelog and plugin diagnostics 2026-07-12 20:01:53 -04:00
Bailey Dixon 5e12d24599 feat(i18n): add Spanish translation harness 2026-07-12 17:58:46 -04:00
Bailey Dixon cebc2a0166 merge: multi-profile presence and concurrent sessions 2026-07-12 17:18:31 -04:00
Bailey Dixon a0c70f7bb6 feat(android): support concurrent profile sessions 2026-07-12 17:15:34 -04:00
Bailey Dixon 9ba2b0fb0e feat(i18n): track translation verification 2026-07-12 16:50:17 -04:00
Bailey Dixon 0f867945bc merge: profile parity 2026-07-12 16:11:15 -04:00
Bailey Dixon 0f5a6b4c9c fix(android): enforce profile-scoped session operations 2026-07-12 16:11:07 -04:00
Bailey Dixon 45e4ff0a9e chore: merge dev for Android 1.4.3 preflight 2026-07-12 10:17:20 -04:00
Bailey Dixon f5dab50e4d feat: prepare Android 1.4.3 release 2026-07-12 10:04:00 -04:00
Bailey Dixon 2479ddb9a6 Merge pull request #188 from Codename-11/dev
fix(ci): publish global Play metadata changes
2026-07-11 22:31:05 -04:00
Bailey Dixon 45fef54c6e Merge pull request #187 from Codename-11/fix/play-global-metadata-trigger
fix(ci): publish global Play metadata changes
2026-07-11 22:28:01 -04:00
Bailey Dixon 258583527e fix(ci): publish global Play metadata changes 2026-07-11 22:25:56 -04:00
Bailey Dixon 851f7f4dfc Merge pull request #186 from Codename-11/dev
fix(play): publish required contact email
2026-07-11 22:21:22 -04:00
Bailey Dixon 2e5fd4a3cf Merge pull request #185 from Codename-11/fix/play-contact-email
fix(play): publish required contact email
2026-07-11 22:08:28 -04:00
Bailey Dixon 6d86d310ec fix(play): publish required contact email 2026-07-11 21:59:18 -04:00
Bailey Dixon e55dd99f62 Merge pull request #184 from Codename-11/dev
release(android): android-v1.4.2
2026-07-11 21:27:39 -04:00
Bailey Dixon 7793934edf Merge pull request #183 from Codename-11/feature/android-i18n-zh-salvage
feat(android): add scalable Simplified Chinese localization
2026-07-11 21:02:01 -04:00
Bailey Dixon f49c6c4203 release(android): prepare android-v1.4.2 2026-07-11 20:52:27 -04:00
Bailey DixonandEasongChung 52a7d67cc4 feat(android): add scalable Simplified Chinese localization
Salvages and integrates the user-facing localization work from PR #180 onto current dev, with complete catalogs, CI parity checks, translated entry points, and contributor guidance.

Co-authored-by: EasongChung <easong@users.noreply.github.com>
2026-07-11 20:52:07 -04:00
Bailey Dixon c52340ecde Merge pull request #182 from Codename-11/dev
Release Android and plugin v1.4.1
2026-07-11 16:46:18 -04:00
Bailey Dixon 7570f93dbf chore(release): finalize android-v1.4.1 and plugin-v1.4.1 2026-07-11 16:34:11 -04:00
Bailey Dixon 6d32ccf024 merge: chat in-flight session recovery 2026-07-11 10:34:46 -04:00
Bailey Dixon 4233817e9f feat(chat): recover in-flight sessions after reopen 2026-07-11 10:29:33 -04:00
Bailey Dixon 577732069f chore: merge background process start discovery fix 2026-07-10 18:24:15 -04:00
Bailey Dixon a738a0e151 fix(chat): discover background processes after turn completion 2026-07-10 18:24:07 -04:00
Bailey Dixon 42d6c77cfb chore: merge gateway background process UI for 1.4.1 2026-07-10 12:42:39 -04:00
Bailey Dixon bd9f53e8db feat(chat): surface gateway background processes 2026-07-10 12:42:29 -04:00
Bailey Dixon 2017d60f4c chore: merge unsolicited gateway completion fix 2026-07-10 10:14:19 -04:00
Bailey Dixon 1e133ee15c fix(chat): receive unsolicited gateway completions 2026-07-10 10:13:59 -04:00
Bailey Dixon 9a40ed9afc chore: merge 1.4.1 chat and voice enhancements
# Conflicts:
#	CHANGELOG.md
#	DEVLOG.md
#	TODO.md
#	app/src/main/kotlin/com/hermesandroid/relay/viewmodel/VoiceViewModel.kt
2026-07-10 08:27:25 -04:00
Bailey Dixon 9ce07b45f7 feat: enhance chat and voice for 1.4.1 2026-07-10 08:19:53 -04:00
Bailey Dixon 2fd90a6e81 docs: record 1.4.0 release completion 2026-07-09 23:31:06 -04:00
Bailey Dixon 7dd1125686 chore(release): Android and plugin v1.4.0 (#181)
chore(release): Android and plugin v1.4.0
2026-07-09 23:06:03 -04:00
Bailey Dixon 522c4fe82a chore(release): finalize android-v1.4.0 and plugin-v1.4.0 2026-07-09 22:39:13 -04:00
Bailey Dixon c9b30dabae chore: sync main into dev before 1.4.0 release 2026-07-09 22:17:00 -04:00
Bailey Dixon e9e92d03f2 fix(voice): harden background session recovery 2026-07-09 22:16:48 -04:00
Bailey Dixon da8e23068a fix(voice): recover sessions after background route loss 2026-07-09 19:23:14 -04:00
Bailey Dixon aaee75e7fc docs: record realtime voice live verification 2026-07-09 17:26:20 -04:00
Bailey Dixon 8ebb21b16d fix(relay): dedupe background voice handoffs 2026-07-09 17:19:38 -04:00
Bailey Dixon 0700ac81c6 fix(relay): use exact xAI result delivery 2026-07-09 17:00:07 -04:00
Bailey Dixon 015298f90a fix(relay): make realtime session start idempotent 2026-07-09 16:29:22 -04:00
Bailey Dixon 3c0e51f664 fix(android voice): honor realtime model selection 2026-07-09 16:29:03 -04:00
Bailey DixonandClaude Fable 5 92f96831c4 fix(relay): let the voice agent recall an already-delivered result without re-running
After a background result was seeded into provider history, a pure-recall
follow-up ('what did that say?') still triggered a full hermes_run_task
round-trip instead of answering from history. Cause: _native_instructions
told the provider to re-route whenever context is 'tool-derived' -- which a
delivered background result is.

Rewrite the clause to separate recall from new work: a Hermes result already
delivered earlier in the conversation is in history, so recall/quote/reference
answers directly (no re-run); call hermes_run_task again only for new,
updated, deeper, or re-verified info. Drop the blanket tool-derived re-route,
keep 'fresh data or verification you don't already have -> re-route'.

Instruction-only. test_provider_native_instructions_include_recent_context
extended to assert the recall carve-out; route + promotion suites green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 15:15:33 -04:00
Bailey DixonandClaude Fable 5 033dcc37ba feat(relay): seed fallback-delivered background result into provider history
After a background result falls back to relay TTS (the provider deferred
instead of reading the answer), the provider's conversation history retained
only its own deferral -- so a follow-up ('what did that say?', 'can't you see
we ran the task?') had no record of the result and failed or re-ran. A
provider-VOICED delivery already becomes a history item; only fallbacks left
the gap. The existing native_pending_delivery_note is a one-shot correction
attached to the next Hermes-routed response and is skipped by follow-ups that
don't route through that branch.

Add RealtimeAgentConnection.append_context_item(role, text): a silent
conversation.item.create (assistant->'text', user/system->'input_text', no
response.create) implemented for xAI + OpenAI. On both fallback paths
(_finish_forced_summary_provider_response validator fallback,
_speak_fallback_answer provider-death/request-failed) the broker seeds the
delivered answer as an assistant turn, so any later follow-up finds it in
history durably, independent of routing. Best-effort (dead socket no-ops);
fallback-only, so a provider-voiced success is never double-recorded. Kept
the pending note as a belt-and-suspenders correction. Logs result_seeded /
result_seed_failed with a preview.

104 realtime tests green; test_filler_summary_triggers_fallback_delivery
extended to assert the seeded assistant history item; append_context_item
added to all connection fakes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 15:02:56 -04:00
Bailey DixonandClaude Fable 5 a144962e66 feat(relay): log provider-spoken delivery + preamble text for signoff diagnosis
Background-result delivery outcomes could not be told apart from the flight
recorder: the fallback event carried provider_text_preview, but the SUCCESS
paths (forced_summary_streaming early-commit, forced_summary_delivered
end-validated) logged only char counts and the pre-run acknowledgement
(hermes_forced_preamble.finished) logged only metadata. So a clean delivery
could not be confirmed verbatim, and a fallback could not be distinguished
from a validator false positive.

Add a _compact_status_text (<=120 char) preview of the actually-spoken text
to three existing _log payloads: transcript_preview (preamble),
prefix_preview (committed early-commit prefix), provider_text_preview
(end-validated delivery). Reuses the fallback path's existing compaction; no
new session state; bounded by the 14-day run-dir retention sweep.

Live payoff: confirmed think-fast spoke a genuine deferral ('One moment...
I'll let you know') rather than reading the answer -- a real fallback, not a
validator miss -- and the behaviour is model-agnostic across grok variants.

104 realtime tests green; test_realtime_summary_validation extended to assert
the delivered text rides prefix_preview / provider_text_preview.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 14:30:42 -04:00
Bailey DixonandClaude Fable 5 c683ad290c docs(todo): capture background-task UX asks + 2026-07-09 voice e2e findings
Records the owner's background-tasks-as-first-class-chat vision (titles,
kickoff/result chat entries, expand-to-detail, persisted results,
in-session provider context for follow-ups, concurrent multi-task) plus
today's live findings: first confirmed provider-voiced delivery (but
inconsistent on grok-voice-latest), think-fast untested until forced, a
duplicate-status bug, and a status-speak logging gap.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 14:30:42 -04:00
Bailey DixonandClaude Fable 5 2968a173b1 fix(voice): render fallback deliveries in the voice overlay
A fallback-TTS delivery played audibly while the overlay sat on
"Thinking" — no waveform, no live text. Two client gates: the overlay
dropped every hermes-sourced voice.response.delta (a rule for mid-run
chatter, written before fallback TTS became a first-class delivery
mouth), and that handler was the only path flipping Thinking->Speaking,
so the Speaking-gated waveform envelope never fed.

- Relay: delivery responses now tagged on the wire (delivery:
  fallback/respeak/visual_only on started+delta events).
- App: hermes-sourced deltas with a delivery tag render (run chatter
  stays suppressed), and arriving output audio flips Thinking->Speaking
  so the waveform tracks any spoken response regardless of source.

116 realtime tests green with delivery-tag assertions on both fallback
paths; sideload debug build green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 22:14:34 -04:00
Bailey DixonandClaude Fable 5 5ff78da8e4 feat(relay): pre-RC observability hardening + realtime model updates
- Run-dir retention: sweep session JSONL logs + wav taps past
  realtime_voice.run_retention_days (default 14, 0 disables) at
  session-log creation — transcripts no longer accumulate indefinitely.
- Wav render tap is debug-only (debug_audio_tap, default off): artifact
  deleted after PCM streams, voice.response.done.audio_path blank.
- Delivery-outcome rollup: python -m plugin.relay.realtime_agent.report
  tallies provider-spoken vs fallback deliveries with reasons; new
  forced_summary_delivered marker makes end-validated deliveries countable.
- Models: OpenAI realtime default gpt-realtime-2 -> gpt-realtime-2.1
  (2.1-mini + rollback 2 selectable); xAI exposes the versioned
  grok-voice-think-fast-1.0 pin alongside the grok-voice-latest alias.
- Both providers surface the RESOLVED model id from session.created
  echoes (provider_model_resolved) so live rounds stay attributable
  across provider-side alias flips.

191 realtime/voice tests green, including new hygiene + report suites.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 20:48:10 -04:00
Bailey DixonandClaude Fable 5 ffe534454a docs: xAI voice platform re-baseline items (think-fast-1.0, alias flip, resumption)
grok-voice-latest now resolves to the new reasoning flagship
grok-voice-think-fast-1.0 (fast-1.0 deprecated); we default to the alias
everywhere, so live-round verdicts may predate the model change. Adds
re-baseline, lifecycle re-probe, and new-voices TODO items.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 20:26:37 -04:00
Bailey DixonandClaude Fable 5 49c183ef9a docs: OpenAI realtime next-RC roadmap, voice observability items, audit leftovers
- TODO: OpenAI realtime provider roadmap (model bump to gpt-realtime-2.1,
  live e2e verify, 60-min hard-cap handling, out-of-band exact delivery
  spike, async function-call delivery, tools guardrail) from the 2026-07-08
  research pass; full sourced findings in
  docs/plans/2026-07-08-openai-realtime-notes.md.
- TODO: voice observability pre-RC hardening (run-dir retention + wav-tap
  gating, delivery-outcome rollup, buffered flight-recorder writes).
- TODO: delivery-audit leftovers (respeak stays relay-TTS, exact-mode
  truncation cue) and post-audit hardening note on the live-verify item.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 19:42:55 -04:00
Bailey DixonandClaude Fable 5 906ce79a82 fix(relay): close five delivery-loss gaps found by adversarial audit
The provider-voiced delivery rework moved speak_verbatim from a synchronous
TTS render onto the async provider pipeline, opening failure windows the old
path couldn't have:

1. Foreground request_response was bare — a dead provider socket lost the
   answer and wedged native_forced_summary_active. Now falls back to the new
   shared _speak_fallback_answer relay-TTS mouth.
2. The delivery-confirm alarm only covered attached-background deliveries;
   foreground and deferred-resume injections now spawn it too.
3. A new user utterance mid-delivery wiped forced-summary state with no
   cancel and no record. New _preempt_pending_forced_summary cancels the
   stale response and lands a never-spoken answer as text.
4. Blocklist phrases present in the authoritative answer no longer flag a
   faithful exact reading; only model-added phrases count.
5. Structured JSON answers route to the summary prompt — no meaningful
   word-for-word reading exists for them.

Injection failure on the attached background path also now falls back to
spoken TTS immediately instead of waiting for the text-only alarm.

102 realtime tests green, five new covering each failure scenario.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 19:42:55 -04:00
Bailey DixonandClaude Fable 5 74f84d9492 docs: changelog + devlog for upstream-watch P1 batch
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 19:06:14 -04:00
Bailey Dixon c6bd418e30 Merge branch 'Codename-11/hrui-bootstrap-retire' into dev (HRUI-002) 2026-07-08 18:30:58 -04:00
Bailey Dixon 8b79c06922 Merge branch 'Codename-11/hrui-fallback-payloads' into dev (HRUI-001) 2026-07-08 18:30:57 -04:00
Bailey Dixon 7a63a0c6ea Merge branch 'Codename-11/hrui-prompt-submit-timeout' into dev (HRUI-016) 2026-07-08 18:30:44 -04:00
Bailey Dixon 83580cbf06 Merge branch 'Codename-11/hrui-manage-model-options' into dev (HRUI-022) 2026-07-08 18:30:43 -04:00
Bailey Dixon e636ca4715 Merge branch 'Codename-11/hrui-plugin-security' into dev (HRUI-014, HRUI-015) 2026-07-08 18:30:43 -04:00
Bailey DixonandClaude Fable 5 c1926f6434 fix(chat): align sessions/runs fallback payloads with upstream contract (HRUI-001)
Stop sending top-level messages/attachments fields the native upstream
session-chat and runs handlers never parse (silent data loss). Synthetic
phone-local history (voice intents, card dispatches, realtime voice
turns) now rides channels upstream actually consumes: tool-call pairs
render as a plain-text digest folded into the per-turn ephemeral system
prompt (system_message on sessions, instructions on runs, the system
message on completions); plain text turns splice into completions
messages and runs conversation_history. Attachments with no supported
channel are returned as ChatPayloadResult.droppedAttachments and logged
(the ChatViewModel user notice already existed) — never silently
discarded. Docs truth-up: HERMES-WEBAPI-REFERENCE session-chat body now
documents the native contract; decisions.md card-dispatch ADR gains an
HRUI-001 update note.

Verified: 18/18 HermesChatPayloadsTest unit tests green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 18:29:53 -04:00
Bailey DixonandClaude Fable 5 b78fe0244c feat(voice): provider-voiced exact result delivery
speak_verbatim no longer renders through relay TTS directly: every spoken
result_delivery mode now delivers through the realtime provider so
background/foreground Hermes answers keep the session's voice and tone.
Exact instructs a word-for-word reading of the authoritative answer
(_forced_hermes_exact_prompt); Summary keeps the natural-summary prompt.
The forced-summary validator, relay-TTS fallback, and delivery-confirm
alarm backstop both, so an off-script response degrades to the previous
TTS-direct behavior instead of losing the answer.

_speak_result_verbatim and the voice.response.verbatim_delivery event are
removed; foreground, background, and deferred-resume paths share the
injection pipeline. Voice Settings' delivery-mode info dialog, docs, and
the stale CHANGELOG keepalive bullet (superseded by idle-close recovery)
are updated to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 18:08:33 -04:00
Bailey Dixon d15f7860fc fix(voice): recover idle realtime sessions 2026-07-08 16:48:13 -04:00
Bailey DixonandClaude Fable 5 1660750b67 fix(cli): per-call RPC timeout override + long prompt.submit timeout
HRUI-016 (desktop half): RelayTransport.request() bounded every RPC by
the single env-tunable HERMES_RELAY_RPC_TIMEOUT_MS (default 120s), so a
legitimately long prompt.submit ack rejected mid-turn; the chat/voice
turn promises additionally wall-clock capped healthy turns at 10m/5m.

- RelayTransport.request() (and the Transport interface + GatewayClient
  pass-through) accept an optional per-call timeoutMs; the env-var
  default still covers every other call.
- Export PROMPT_SUBMIT_REQUEST_TIMEOUT_MS = 1_800_000 (mirrors upstream
  apps/desktop/src/hermes.ts, commit 164144183) and pass it at both
  prompt.submit call sites (chat.ts runOneTurn, voiceServer.ts) — the
  only two under desktop/src/.
- Convert the 10-min chat and 5-min voice turn caps into idle-progress
  watchdogs: the timer re-arms on every gateway event and only fires
  after that long with NO events at all, so streaming turns are never
  wall-clock capped.

Verified with npm run build (strict tsc).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:58:19 -04:00
Bailey DixonandClaude Fable 5 a1818579d9 fix(gateway): 30-min prompt.submit RPC timeout on Android, no fallback on slow ack
HRUI-016: upstream treats gateway prompt.submit as a long-running RPC —
the ack is effectively fire-and-forget (turn completion arrives via
stream events, not the RPC return) and can trail a MoA/deep-reasoning/
tool-heavy turn by minutes. Bounding it by the generic 15s rpc timeout
false-failed running turns into the SSE preflight fallback, resubmitting
the same prompt as a duplicate turn.

- Add PROMPT_SUBMIT_REQUEST_TIMEOUT_MS = 1_800_000 (mirrors upstream
  apps/desktop/src/hermes.ts, commit 164144183; matches the backend
  agent.gateway_timeout = 1800s ceiling) and pass it at the
  prompt.submit call site.
- Guard the submit-failure path: once this turn's own events are
  flowing (or it already ended), a slow/lost/socket-severed ack no
  longer fires onPreflightFailure — recovery stays with the idle
  watchdog and mid-turn rejoin. session.info is excluded from the
  "turn started" signal (connection-level, turn-independent).
- The 180s turn watchdog was already idle-progress (reset on every
  gateway event) — semantics unchanged, docs clarified.
- Expose rpc/submit/idle timeouts as constructor test seams (same
  pattern as midTurnRejoinWindowMs); harness gains a withheld-ack seam.
  4 new JVM tests: slow-ack survives past the generic timeout with no
  fallback, late ack timeout after completion does not resubmit, idle
  watchdog stays quiet while events trickle, and still fires on silence.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:57:54 -04:00
Bailey DixonandClaude Fable 5 f893330cfa docs(bootstrap): split supported-baseline vs compat-only surfaces in doctor/compat/TODO wording (HRUI-002)
Update every place that described the bootstrap as a sessions/skills
fallback to reflect the retirement split:

- plugin/doctor.py + plugin/compat.py docstrings, compat status
  recommendation, compat status text, and the legacy-bootstrap doctor
  check now state that compat covers only session search, memory, legacy
  skill detail/toggle, config, available-models, and slash middleware.
- TODO.md bootstrap-injection entry records the sessions + skills-list
  retirement as done (2026-07-08) and lists the still-gapped surfaces.
- CLAUDE.md bootstrap-maintenance bullet, compatibility-endpoints table,
  Key Files row, and Integration Points row updated to match.
- docs/upstream-surface-matrix.md, docs/upstream-integration-sync.md,
  docs/upstream-contributions.md, docs/decisions.md ADR 16 removal path,
  docs/HERMES-WEBAPI-REFERENCE.md, and docs/remote-access.md no longer
  claim the bootstrap injects sessions or the legacy skills list.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:55:30 -04:00
Bailey DixonandClaude Fable 5 16b16fd5ad refactor(bootstrap): retire native-upstream sessions + skills/toolsets injection (HRUI-002)
Remove the bootstrap handlers for surfaces current hermes-agent serves
natively: sessions CRUD/messages/fork (/api/sessions*, upstream PR #33134)
and the legacy read-only GET /api/skills list (superseded by /v1/skills +
/v1/toolsets, PR #33016). No pre-#33134 fallback remains; older core builds
degrade via the client capability probe to /v1/chat/completions or /v1/runs.

The bootstrap now injects only genuine compatibility gaps with no native
API-server replacement: GET /api/sessions/search, memory CRUD, legacy skill
detail (/api/skills/{name}) + the 501 toggle stub, config, available-models,
and the slash-command middleware. Registration stays method/path-aware so
native routes still win if any remaining surface lands in core.

Tests assert the split both ways: retired surfaces are never injected, kept
surfaces are, and native routes still win for kept surfaces.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:55:01 -04:00
Bailey DixonandClaude Fable 5 227748912d docs: keepalive final verdict — no protocol message resets xAI's 900s timer
Probe run 4 (valid): three session.update pings at 240/480/720s, each
acknowledged by the server, and the conversation still timed out at
exactly 900.0s. Combined with the silent-append runs: xAI's inactivity
timer counts only real conversation items. Remaining designs recorded
(scheduled reopen vs silent auto-reopen-on-next-turn with Hermes-session
context reseed; POC doc recommends the latter).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:47:16 -04:00
Bailey DixonandClaude Fable 5 9a1edf7d5a chore(deps): raise aiohttp floor to >=3.14.1 for 2026 CVE line
Upstream pinned all aiohttp paths to the patched 3.14.1 line
(CVE-2026-34993, CVE-2026-47265, and the earlier 2026 advisories). Raise
the relay floor to match in plugin/requirements.txt, pyproject.toml, and
the relay_server compat shim requirements, and update the version table
in docs/spec.md. README/AGENTS mention aiohttp without a version string,
so they need no change.

Refs HRUI-015.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:46:54 -04:00
Bailey DixonandClaude Fable 5 ab65ea7705 fix(manage): request include_unconfigured model options + keep provider setup rows (HRUI-022)
Upstream flipped the default of dashboard GET /api/model/options (and the
gateway model.options RPC) to configured-providers-only; unconfigured
provider skeleton rows now require an explicit include_unconfigured opt-in.
Relay Android called the route bare and parseModelOptions dropped
empty-models rows, so on new upstream every provider awaiting an API key
silently vanished from the Manage model picker along with its Keys-setup
affordance.

- DashboardApiClient.getModelOptions() always sends include_unconfigured=1
  (cached and refresh=1 paths); old upstream ignores the extra param.
- parseModelOptions keeps empty-models skeleton rows, resolves the provider
  id from the canonical slug first (what /api/model/set expects), defaults
  authenticated by model presence when picker hints are absent, and carries
  the upstream warning as a setupHint.
- ModelPickerDialog renders the setup hint (e.g. "paste X_API_KEY to
  activate") under empty skeleton providers, keeping the Keys guidance.
- Gateway-WS model.options callers audited: the only call site feeds the
  in-chat picker, which intentionally stays on the configured subset.

Verified: :app:testGooglePlayDebugUnitTest — DashboardApiClientTest (42)
and new ModelOptionsParserTest (5, incl. old-upstream back-compat fixture)
all pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:46:49 -04:00
Bailey DixonandClaude Fable 5 fde5030797 fix(relay): always-on credential denylist for /media/by-path permissive mode
Mirrors upstream hermes-agent media-delivery hardening
(gateway/platforms/base.py validate_media_delivery_path): even with
RELAY_MEDIA_STRICT_SANDBOX off, /media/by-path now refuses to serve
credential/system paths — ~/.hermes/.env, auth.json, config.yaml, OAuth
token stores, pairing/, mcp-tokens/, ~/.ssh and the other home credential
dirs, /etc and other system prefixes — plus the relay-specific
hermes-relay-qr-secret and hermes-relay-sessions.json secret stores.

The check runs after realpath resolution (a symlink can't launder a
denied target) and before the existence check (no 403-vs-404 existence
oracle for credential probes). Ordinary files keep serving in permissive
mode; strict-sandbox mode is unchanged except the denylist now outranks
the allowlist there too.

Refs HRUI-014.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:45:30 -04:00
Bailey DixonandClaude Fable 5 0173519183 fix(relay): hold result delivery while the user is mid-utterance
Live round-5 finding: a background task finishing while the user was
speaking delivered over them and ended their recording. The relay knows
the user is talking (live input_audio.append chunks now stamp
native_last_input_audio_at); _await_floor_idle_for_result additionally
requires the user quiet >= 1.5s before consuming the floor, bounded by
the existing wait deadline. Covers summary, fallback, and queued-start
transition deliveries. TODO logs the client half (don't end an active
recording on incoming audio), the end-of-response audio tail cut repro,
fallback path-speech polish, and the 4/4 grok delivery-instruction
failure stat elevating verbatim delivery to likely default.

Tests: input-quiet gate holds/proceeds cases; affected suites 42/42.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:44:34 -04:00
Bailey DixonandClaude Fable 5 c5d61bc427 test(probe): stamp stream-end time — a pre-ping socket death is not a mode verdict
The first session_update keepalive run died inside the initial 240s,
before any ping was sent (the pinger exits silently when the event stream
ends) — an unstamped clean stream end made that indistinguishable from a
keepalive failure. Stamp it so early deaths read as invalid runs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:29:05 -04:00
Bailey DixonandClaude Fable 5 f116d41295 docs: log live rounds 3-4 verdicts + keepalive negative + verbatim-delivery idea
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:27:13 -04:00
Bailey DixonandClaude Fable 5 4aedb9b839 test(probe): record silent-append verdict; add session_update keepalive mode
Empirical (relay host, live xAI, 2026-07-08): the 960s repro died at
exactly 900.0s, and the silent-PCM keepalive run ALSO died at exactly
900.0s — uncommitted input_audio_buffer.append does NOT reset xAI's
conversation-inactivity timer. POC doc revised; the silent-append
keepalive stays as harmless scaffolding until a working ping lands. Next
candidate: a session.update re-send (connection.configure()), now
available as --keepalive-mode session_update; if that fails too, the
remaining option is a scheduled provider-socket reopen.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:24:40 -04:00
Bailey DixonandClaude Fable 5 ba24b3e959 fix(relay): next-turn correction after system-side deliveries
Live round-4 finding: the fallback spoke the answer correctly, but the
provider never sees fallback/text-only deliveries — its conversation
history still read "running in background", so on the user's next turn it
claimed the task was still running.

Out-of-band deliveries (forced-summary fallback, text-only emit,
delivered-or-alarm force emit, respeak) now set a pending delivery note;
the next normal user turn's response carries it via per-response
instructions (composed WITH the session instructions, which per-response
instructions otherwise replace), then clears it: the task has ALREADY
COMPLETED, the answer was already spoken, don't re-deliver.

e2e filler test extended: after the fallback, the correction note must be
pending and carry the delivered answer. Realtime batch 85/85 green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:21:08 -04:00
Bailey DixonandClaude Fable 5 5896d4c672 fix(relay): summary validation — whole-word overlap, 2-hit early-commit bar, queue-speak blocklist
Live round-3 regression: the forced summary for a completed answer came
back as ANOTHER queue acknowledgement ("It's queued and will start
automatically once the Minnesota check finishes. I'll let you know…") and
early-commit approved it at 45 chars — substring matching let "will START
automatically" count as evidence for an answer containing "starting", the
audio played, the response was marked delivered, and the real answer never
spoke (so the delivered-or-alarm stayed silent too).

- _summary_overlap_hits: WHOLE-WORD evidence matching (substring was the
  hole); overlap check now counts hits
- early commit requires >= 2 whole-word hits (irreversible once audio
  plays, so the early bar is higher than end-of-response validation's 1)
- blocklist gains the queue/deferral class a final answer must never
  contain: "i'll let you know", "it's queued", "is queued", "queued and
  will", "in the queue"
- _start_next_queued_run gains an explicit phase-1 wait for the summary
  injection to BEGIN (correct ordering previously held only by task
  scheduling luck) before the existing wait-for-finish
- the queued-start spoken transition now waits for floor idle so it can't
  overlap a fallback TTS render of the previous result

Tests: live regression strings pinned (queue-speak flagged end-of-response,
substring non-overlap, single-weak-hit no-commit); realtime batch 85/85
green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 15:13:36 -04:00
Bailey DixonandClaude Fable 5 3c24e82e5e docs: log the background-run A-E batch
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 14:47:48 -04:00
Bailey DixonandClaude Fable 5 381c62d6b6 feat(voice): queued-count chip, respeak on DONE-chip tap, compact-mode chip, exit breadcrumb
Client half of the background-run A-E batch:

- chip shows "+N queued" (hermes.run.queued + queued_count on promoted)
- tapping the settled (DONE) chip asks the relay to respeak the last
  delivered answer (hermes.result.respeak); chip stays up while it plays;
  taps on live phases no-op
- the chip now renders in compact (non-focus) voice mode too — it
  previously existed only in the focus layout, so a running task had no
  visible presence there
- exiting voice mode with a live background run posts a chat system
  notice ("Background voice task still running (+N queued) — Hermes will
  report back") via VoiceViewModel.chatNoticeSink, wired in RelayApp to
  the shared ChatHandler
- `_thinking` drafting deltas drive a "Drafting the answer…" chip status
  line (never a tool pill)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 14:47:47 -04:00
Bailey DixonandClaude Fable 5 ad0139ba94 feat(relay): streaming summary delivery, answer-overlap validation, task queue, respeak
Background-run A-E batch (relay half):

- forced summaries STREAM: buffered only until the prefix (>=40 chars)
  clears the bad-phrase check and shows content overlap with the Hermes
  answer (_maybe_commit_forced_summary_early), then flush + live stream —
  removes the "silence, then the whole answer in one burst" delivery gap;
  committed responses skip end-of-response validation (audio already
  played)
- positive validation: _summary_overlaps_answer requires the summary to
  share content tokens with the answer (vacuous for bare confirmations);
  no_answer_overlap joins the bad-summary reasons
- delivered-or-alarm: _confirm_background_delivery force-emits the answer
  as text (+ delivery_unconfirmed log) when no spoken delivery lands
  within 30s — a background answer can never be silently lost
- respeak: hermes.result.respeak client message replays
  last_background_result via relay TTS (DONE-chip tap client-side)
- task queue: a long second ask is queued (FIFO, cap 3, status "queued")
  instead of refused; starts automatically when the current run's task
  completes (_start_next_queued_run waits for the summary to settle, runs
  the task as durable with a spoken transition); cancel clears the queue;
  hermes.run.queued event + queued_count on promoted /
  background_completed / get_status; queue-full keeps the busy answer
- _thinking drafted text is the answer of last resort when the
  response-delta path yields empty (answer_from_thinking)
- fast lane reuses one Hermes side-session per voice session
  (fast_lane_session_id) instead of one session per quick ask
- idle probe injects the relay xAI OAuth token like the broker does
  (_probe_provider_options) so it runs on the relay host

Tests: 93 green across the realtime batch — 8 new overlap/early-commit
cases, 4 new queue/side-session cases, and a route-level misbehaving-
provider e2e (filler summary -> fallback carries the real answer; the
filler never reaches the client). The second-ask contract changed from
already_running to queued; existing tests updated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 14:47:46 -04:00
Bailey DixonandClaude Fable 5 2abf9b000f docs: log the chip DONE-settle fix (sixth e2e finding)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 13:05:27 -04:00
Bailey DixonandClaude Fable 5 bc957ef641 fix(voice): background-run chip settles to DONE instead of vanishing mid-answer
The chip was nulled at the first summary-audio byte — it disappeared
exactly when the waveform/spinner returned to speak the answer, reading
as the background task being lost (second live e2e finding, same day).

- new BackgroundRunPhase.DONE: on first summary audio (or the 20s
  no-audio delivery watchdog) the chip settles to "Background task
  finished." — solid dot (no pulse), elapsed ticker frozen — lingers
  DONE_CHIP_LINGER_MS (10s), then auto-dismisses
- the chip ✕ on a DONE chip is a LOCAL dismiss, never a relay cancel
  (a late cancel used to overwrite a delivered answer); TalkBack label
  flips to "Dismiss"
- a newly promoted run replaces a lingering DONE chip and cancels its
  auto-dismiss timer so it can't clear the new chip's later DONE early
- progress / tool / reconnect handlers treat DONE like DELIVERING:
  a settled chip cannot be reanimated by stray late events

:app:assembleSideloadDebug green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 13:05:27 -04:00
Bailey DixonandClaude Fable 5 e3097682c1 docs: log e2e realtime forensics + the five voice fixes
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 12:47:03 -04:00
Bailey DixonandClaude Fable 5 63a7a79d2d fix(voice): five chained e2e fixes — stuck thinking pill, late-cancel answer loss, spoken run IDs, phantom queue, deferral filler
Live e2e forensics (session event log): the gateway streams drafting text
as a `_thinking` pseudo-tool (deltas only, never tool.completed) -> the
client rendered it as a forever-"running" pill -> the user cancelled an
ALREADY-COMPLETED run -> the unguarded cancel marked it cancelled and the
completed answer was never spoken. Independently the model read the full
32-char run id aloud, claimed to "queue" a request (no queue exists), and
one delivery spoke "One moment while I look that up" filler the summary
validator didn't recognize.

- client: `_`-prefixed tool names are internal (upstream hidden-tool
  convention) — hermes.tool.delta/.started no longer create ToolCall pills
  for them; text still feeds the detailed thinking trace
- relay: response.cancel only cancels a Hermes run that is actually in
  flight; late cancel still stops speech but cannot flip a completed run
  to "cancelled" or emit hermes.run.cancelled for it
- relay: run/session ids removed from every model-visible payload
  (interim ack, forced-summary metadata); "never say run IDs, session
  IDs, or other identifiers aloud" added to interim-ack, handoff, and
  summary instructions (get_status/cancel default to the active run)
- relay: "there is no task queue" added to handoff/busy instructions
- relay: _bad_forced_summary_reason gains deferral-filler phrases (one
  moment / report back / looking into / i'll look / as soon as i have);
  summary prompt reworded to speak the answer NOW
- relay: pre-Hermes status lead no longer carries the previous run's
  run_id/tool-count into a new run's first progress event

Tests: new plugin/tests/test_realtime_summary_validation.py (5, pinning
the exact observed filler), cancel route test updated to the
no-active-run contract; realtime batch 69/69 green;
:app:compileSideloadDebugKotlin green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 12:47:03 -04:00
Bailey DixonandClaude Fable 5 789f32cd25 docs: log fast lane + stale voice-prefs TODO closure + device deploy
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 11:24:34 -04:00
Bailey DixonandClaude Fable 5 6f0357c2e8 feat(relay): fast lane — answer quick asks inline during a background run
Background-run v2 item 1. A second hermes_run_task while a detached
(promoted/durable) run holds the single background slot used to get an
unconditional busy answer — even for a two-second lookup. The broker now
first tries the request INLINE on a separate ephemeral Hermes session
(session_id=None) within the normal grace window:

- completes inside grace -> the tool result is returned (fast_lane: true)
  and spoken as usual
- grace elapses, a known-long tool starts (_long_tool_hints), the call
  asks mode=background, or promotion is off -> the attempt is abandoned
  (stream cancelled client-side) and the reworded busy answer falls
  through unchanged
- gate requires the in-flight run to actually be detached
  (hermes_run_tier promoted/durable)

The fast lane keeps every observation in locals and touches NONE of the
session's hermes_* run state — run_id, status, progress counters, and the
chip stay owned by the in-flight run — and emits no client events of its
own (bounded by grace, so no chip is needed; one would fight the detached
run's). Session-log events: voice.hermes_fast_lane.completed / .abandoned
/ .error.

Tests: plugin/tests/test_realtime_fast_lane.py (7 — inline answer + state
non-interference, grace/long-tool fall-throughs incl. client-side
cancellation, background-mode/promotion-off/foreground-tier skips, error
reporting). test_second_run_task_answers_busy_without_orphaning_first
updated to per-stream cancellation tracking: the abandoned fast-lane
stream is the designed fall-through; the first run's stream must stay
uncancelled. Full realtime batch 64/64 green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 11:24:30 -04:00
Bailey DixonandClaude Fable 5 7569144cc4 docs: close stale voice-prefs connectionId TODO; correct the KDoc
The connectionId namespacing wiring already shipped in 0aa1b38 (2026-06-21):
RelayApp's (connection, profile) effect calls setVoicePrefsConnection before
onProfileChanged, and applyVoicePrefsScope pushes both into
VoicePreferencesRepository.setActiveScope. The deferred-list entry and the
"null until an integration wires this" KDoc paragraph described the
pre-wiring state.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 11:13:13 -04:00
Bailey DixonandClaude Fable 5 5b25b9b154 docs: log #131 closure + demo composer; close audit + demo TODO items
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:39:45 -04:00
Bailey DixonandClaude Fable 5 79dd6b44fe feat(app): demo composer answers with a canned notice instead of a no-op
Typing + Send in offline Demo mode did nothing (sendMessage early-returned
on the null API client), which read as broken. sendMessage now intercepts
while isDemoMode: echoes the user bubble and appends
DemoContent.composerReply — an honest "offline demo, tap Connect in the
banner" assistant notice. Both bubbles are clientOnly, so demo-exit's
clearMessages() wipes them with the rest of the transcript.

Wired via setDemoModeWiring unconditionally in RelayApp: in demo there is
no API client, so the client-gated chat init never runs and ChatViewModel's
own handler stays null — the wiring supplies both the demo flag and the
shared ChatHandler. UUID-based ids so rapid sends can't collide on
LazyColumn keys.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:39:44 -04:00
Bailey DixonandClaude Fable 5 d96b68c794 fix(app): guard streaming URL builds against malformed base URLs (#131)
sendChatStream / sendCompletionsStream / sendRunStream built their Request
before any try/catch or listener existed, so a malformed apiServerUrl
(hand-edited connection, corrupt settings import) made
Request.Builder.url(String) throw IllegalArgumentException synchronously
out of the ViewModel — the last open group in the #131 "Invalid URL host"
crash-class audit.

- authRequestOrNull() chokepoint backed by top-level buildApiRequestOrNull
  (mirrors ConnectionManager's buildRelayRequestOrNull so the guard is
  unit-testable without instantiating the client)
- a bad URL fails the turn through the normal onError channel with a
  human message and returns an inert EventSource; no side effects fire
  before the guard
- tests: valid/malformed URL cases in HermesApiClientTest

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:39:43 -04:00
Bailey DixonandClaude Fable 5 e3ba358331 docs: record delegate_task async-delivery verdict; retract voice nudge records
Upstream verification (clone @ 5057f03bf): delegate_task(background=true)
never dispatches async on the api_server surface — every api_server route
binds async_delivery=False and tools/delegate_tool.py downgrades the batch
to synchronous execution (upstream issue #10760). All standard voice turns
ride SSE/api_server, so the background-delegation nudge could not work as
designed and was reverted (45c7ef4); the speak-delegated-result-on-overlay
follow-up is closed on the same finding (no delayed completion turn exists
on that surface). TODO records the verified mechanism with source
locations; the CHANGELOG entry is withdrawn; DEVLOG item corrected.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:25:36 -04:00
Bailey Dixon 45c7ef49e2 Revert "feat(voice): nudge standard voice toward backgrounding long asks"
This reverts commit 5c214a2e6a.
2026-07-08 10:23:45 -04:00
Bailey DixonandClaude Fable 5 6003258c5d docs(devlog): log 2026-07-08 voice batch (keepalive, sync durability, nudge)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:15:16 -04:00
Bailey DixonandClaude Fable 5 a660b3825d docs: log realtime sync drain, provenance badge, and voice nudge
TODO: mark the durability + provenance-chip item shipped (gateway drain +
marker->badge + orphan dedupe), scope the remaining app-restart
persistence question, and mark the standard-voice delegate_task nudge
shipped with its on-device verify steps. CHANGELOG: user-facing entries
for the sync drain/badge and the background-delegation nudge under 1.4.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:13:33 -04:00
Bailey DixonandClaude Fable 5 5c214a2e6a feat(voice): nudge standard voice toward backgrounding long asks
Add a line to the ephemeral voice interface context telling the model the
user is waiting in a live voice session: clearly-long requests (builds,
research, multi-step tool work) should be delegated via
delegate_task(background=true) with a spoken "started it in the
background" acknowledgement, while quick questions keep answering
directly. Rides the per-turn SSE system_message — nothing is persisted
and text chat is unaffected. Deliberately hedged: false-positive
delegation is worse UX than a long turn (SSE recovery + the turn-complete
notification already make those survivable).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:13:33 -04:00
Bailey DixonandClaude Fable 5 c079a632ba fix(app): drain realtime turn sync on gateway + badge synced voice turns
Provider-answered realtime voice turns are folded into the Hermes session
as synthetic messages on the next chat/run request — but the gateway
prompt.submit can't carry them, and on a gateway-primary phone "wait for
the next SSE turn" meant never: the agent never learned what was said in
voice.

- force a gateway turn with unsynced synthetic sync messages (voice
  intents / card dispatches / realtime turns) onto the sessions SSE route
  so the traces land; guarded to an existing session id + the sessions
  fallback + the default profile (a non-default profile's gateway session
  is invisible to the shared api_server surface — the POST would 404 and
  fail the user's turn)
- mark traces synced based on the route the turn actually DISPATCHED on
  (effectiveEndpoint), fixing a latent duplicate re-send for voice turns
  forced onto SSE by their interface context
- RealtimeTurnSyncBuilder.stripProvenanceMarker(): recognize the synced
  "[Realtime Agent provider-native voice turn: ...]" marker in loaded
  history, strip the bracket noise, and restore the quiet "Realtime
  Agent" badge live turns get
- drop the superseded local clientOnly bubble when its synced copy loads
  from the server (the exchange rendered twice otherwise); unsynced
  traces stay preserved — they are still the only record of the turn
- tests: 4 new ChatHandlerTest load-path cases, 4 new
  RealtimeTurnSyncBuilderTest marker cases (incl. builder round-trip)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 10:13:13 -04:00
Bailey DixonandClaude Fable 5 c7de0da22d fix(relay): keep realtime provider sessions alive across long silence
xAI closes a realtime conversation after 900s of inactivity; with manual
turn-taking (turn_detection: None) the provider socket sees nothing while
the user is silent, so an open-but-quiet voice session — most commonly a
background-run wait — died with a raw provider error (observed live
2026-07-08).

- add _provider_keepalive_loop: per-connection broker task appends ~100ms
  of silent, never-committed PCM after RELAY_VOICE_PROVIDER_KEEPALIVE_MS
  of quiet (default 240s => 3 pings per 900s window; 0 disables); runs
  through detached periods; append-only so it can never race or clobber
  a user utterance
- stamp provider activity in two places only: client input_audio.append
  and once per provider event in _pump_provider_events
- classify residual provider idle-closes (_is_provider_idle_timeout) into
  a human-readable "voice session expired" error instead of raw provider
  text
- extend realtime-provider-idle-probe.py with --keepalive-ms for the
  relay-host repro (--windows 960) and fix verification
- revise ADR 33 Phase 0: xAI is needs-keepalive beyond ~900s (POC doc
  revision 2026-07-08 + decisions.md note)
- tests: 11 new in plugin/tests/test_realtime_keepalive.py; existing 54
  realtime tests green

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 09:57:23 -04:00
Bailey Dixon 16133ff081 docs(todo): standard-voice research follow-ups + xAI 900s idle-timeout diagnosis 2026-07-07 22:51:15 -04:00
Bailey Dixon 3a12221185 docs: mark realtime injection-framing fix as deployed to relay 2026-07-07 21:00:16 -04:00
Bailey Dixon 699653bf87 docs: log voice chip fix, screen-wake-lock, and injection-framing fix 2026-07-07 20:55:02 -04:00
Bailey Dixon 3d354080dd fix(relay): stop faking user turns for realtime voice injections
The forced-Hermes preamble, background-task handoff ack, and
completed-background-task summary were all injected via
conversation.item.create role=user — the model's history contained
fake turns like "the user" saying "Hermes has already handled the
user's previous voice request...".

response.create supports a per-response instructions field that
overrides the session prompt for one response only, with no
conversation item created at all. Confirmed supported by both
providers (OpenAI docs; xAI's Voice Agent API docs show the same
shape) — conversation:"none" (OpenAI-only true out-of-band) is
deliberately not used since the spoken summary should remain real
history for follow-up turns to reference.

request_response() gained an optional instructions kwarg on both
provider adapters; the 4 broker-authored injection sites switched
from send_text(prompt) to request_response(instructions=prompt).
The one genuine passthrough (real client-supplied text) is
untouched.
2026-07-07 20:54:32 -04:00
Bailey Dixon 427145ccce fix(android): voice tool-call chip ordering + screen-wake-lock
Background-run chip pinned a finished tool's status line until the
next unrelated event overwrote it (no hermes.tool.completed/failed
handler); CompactTranscriptRow rendered the reply above the tool
calls that produced it. Also add KeepScreenOnWhile so voice mode
holds the screen on for the whole session and chat holds it only
while a reply streams, matching call/video-playback conventions
instead of relying on the OS default throughout.
2026-07-07 20:54:00 -04:00
Bailey DixonandClaude Opus 4.8 654663bc3e docs(todo): add compaction-safe "Active — next up" snapshot
Leads TODO with the current state so work can resume cleanly after a session
compact: the prepped android-v1.4.0 / plugin-v1.4.0 release act (sign-off →
notes → merge/tag → discard the 1.3.0 Play draft), the two open voice bugs
(tool-completion handler + PCM click, both needing a logcat repro), and the
Mizu triage queue. Trimmed the now-shipped duplicate-toast voice item.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 18:14:55 -04:00
Bailey DixonandClaude Opus 4.8 75d965c32e fix(android): finish relay URL-guard sweep + voice error-recovery UX
Relay URL guards (rest of the #131 relay class):
- RelayVoiceClient validates its base in resolveHttpBase() → null on a
  malformed URL, so all 7 voice endpoints fail via the existing Result.failure
  guards instead of a throwing .url() on the IO dispatcher.
- RelayHttpClient's two string-URL sites (fetchMedia, listSessions) now use
  toHttpUrlOrNull() → Result.failure. RelayProfileInspectorClient was already
  guarded (toHttpUrl + catch everywhere).

Voice error-recovery UX (from the on-device realtime test):
- VoiceModeOverlay no longer pipes errorEvents to the app-wide bottom snackbar
  while it's up — the inline top banner is the single surface, killing the
  duplicate bottom toast on a failed/timed-out turn.
- clearError() now resets Error→Idle so a dismissed/retried failure lands
  usable; the banner gained a Dismiss beside Retry (was retry-only, which
  trapped the user).

Also diagnosed in TODO (need a repro-with-logs before fixing): realtime
tool-call spinners run forever (no hermes.tool.completed/failed handler in
VoiceViewModel though the relay forwards them); tap/static click between
sentences in realtime PCM playback.

Build + install + launch-clean verified on device.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 18:07:51 -04:00
Bailey DixonandClaude Opus 4.8 37355974b4 fix(android): guard malformed relay URL in ConnectionManager (relay half of #131)
Play crash on 1.2.6 (Galaxy S25 Ultra / Android 16): IllegalArgumentException
from okhttp3.HttpUrl$Builder.parse via ConnectionManager.doConnectInternal →
Request.Builder.url(). doConnectInternal runs on a background coroutine, so a
malformed relay host (from a corrupt/edited pairing payload) made OkHttp's url()
throw uncaught → app crash. This is the relay-socket half of the #131 "Invalid
URL host" class the TODO flagged (the #131 fix only covered Manage/voice HTTP).

- Extracted a pure buildRelayRequestOrNull() (try/catch → null on
  IllegalArgumentException). doConnectInternal treats null as a connection
  failure: "Invalid relay URL" diagnostic + Disconnected + close-replaced-socket
  + backed-off reconnect — the same path onFailure uses. No happy-path change.
- ConnectionManagerUrlGuardTest: valid ws/wss build; empty-host / space-in-host
  return null. Green via :app:testSideloadDebugUnitTest; APK rebuilt + installed
  + launched clean on device.

TODO #131 audit: ConnectionManager marked fixed; RelayHttpClient /
RelayProfileInspectorClient / RelayVoiceClient remain for a defense-in-depth pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 17:26:37 -04:00
Bailey DixonandClaude Opus 4.8 380ad0b4bf release: prep android-v1.4.0 + plugin-v1.4.0 (versions + changelog + devlog)
- Android → 1.4.0 (versionCode 22); plugin → 1.4.0 (all metadata in sync).
- CHANGELOG [Unreleased] → [1.4.0] - 2026-07-07.
- DEVLOG entry for the CI-path-coverage + Android-14 crash-safety work.

Prep only — in-app What's New / RELEASE_NOTES / Play notes, the dev→main
merge, and the android-v1.4.0 / plugin-v1.4.0 tags are the release act,
pending an on-device smoke test.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 16:31:24 -04:00
Bailey DixonandClaude Opus 4.8 13e747c6d9 fix(android): Android-14 crash-safety — removeFirst/removeLast + Tink pin
Built against SDK 35, Kotlin's removeFirst()/removeLast() resolve to Java 21's
List methods that don't exist below Android 15, crashing older devices.

- Replaced all 5 app-code removeFirst() calls (all on kotlin ArrayDeque, so
  members not the flagged MutableList extension — already safe, but converted
  per Google's guidance and for future-proofing) with removeAt(0). All sites
  are size-guarded, so behavior is identical.
- Pinned com.google.crypto.tink:tink-android:1.16.0 ahead of the transitive
  version security-crypto pulls, whose HybridConfig.<clinit> tripped the same
  Play pre-launch check. Our EncryptedSharedPreferences use is AEAD-only, so
  HybridConfig is almost certainly never loaded — this clears the static Play
  warning. Untestable without a build; on-device auth smoke-test queued in TODO.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 16:06:08 -04:00
Bailey DixonandClaude Opus 4.8 500387d3fa ci(plugin): trigger on all plugin/*.py, not just four named modules
The path list omitted doctor.py, compat.py, config.py, profiles.py, and 5
other top-level modules, so changes to them alone never ran plugin CI (my
doctor.py fix only got covered because it also touched plugin/tests/**). A
plugin/*.py glob covers every current and future top-level module.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 16:06:07 -04:00
Bailey Dixon 55904a600a Merge pull request #178 from Codename-11/fix/installer-stale-plugin-backup
fix(plugin): doctor + installer guard against stale duplicate plugin copies
2026-07-07 13:51:20 -04:00
Bailey Dixon 393a485f53 Merge branch 'dev' into fix/installer-stale-plugin-backup 2026-07-07 13:47:18 -04:00
Bailey Dixon 4fc1978df7 Merge pull request #176 from Codename-11/chore/todo-prune
chore(todo): prune shipped records + fix stale #8556→#33134 refs
2026-07-07 13:47:03 -04:00
Bailey Dixon 141a7560e7 Merge pull request #177 from Codename-11/revert/release-video-pipeline-repo-import
revert: remove release video pipeline import
2026-07-07 13:26:05 -04:00
Bailey DixonandClaude Opus 4.8 f965c205d7 fix(plugin): doctor + installer guard against stale duplicate plugin copies
The gateway plugin loader dedups discovered plugins by manifest name, so a
second directory declaring `name: hermes-relay` (a backup copy left by an
older installer, or a stray extra install) could win the dedup and make the
gateway load stale code — silently ignoring every later deploy. This was the
root cause of the 2026-06-29 phone-platform round-trip failure.

- doctor: new `_duplicate_plugin_dirs()` + `plugin-name-unique` check warns
  when >1 directory under the plugins dir declares the same plugin name
  (deduped by resolved real target); report gains `duplicate_dirs`/`plugins_dir`.
- install.sh: sweep the plugins dir after symlinking and remove any other
  entry declaring `name: hermes-relay`, so a stale duplicate can't linger.

Tests: 4 new doctor cases (14/14 green). install.sh grep-match validated in
isolation. Live-host verify queued in TODO.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 13:19:29 -04:00
Bailey Dixon a138165408 Revert "Merge pull request #175 from Codename-11/fix/release-video-pipeline"
This reverts commit 467e6722a2, reversing
changes made to 66728686b9.
2026-07-07 13:18:57 -04:00
Bailey Dixon 467e6722a2 Merge pull request #175 from Codename-11/fix/release-video-pipeline
feat: add release video pipeline
2026-07-07 13:12:50 -04:00
Bailey DixonandClaude Opus 4.8 b5c1d392fb chore(todo): prune shipped records + fix stale #8556 → #33134 refs
- Remove 11 shipped-and-released [x] records from "User-Added" (session
  delete, voice override, analytics/diagnostics, connections reframe,
  profile lock, etc.) — they live in DEVLOG; keep the one open [ ] item.
- Collapse the dot-matrix "thinking indicator" section: base + presets +
  colors shipped in android-v1.3.0; keep only the two real remainders
  (OS reduce-motion/TalkBack; optional avatar-style promotion).
- Fix the "Research / open questions" bootstrap notes: PR #8556 was closed
  as superseded; native upstream now covers sessions via #33134 and
  skill/toolset discovery via /v1/skills + /v1/toolsets (#33016). Bootstrap
  shrinks per surface, not one big delete. Stage 2 slash-preprocessor is
  unblocked (was "blocked on #8556").

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 13:10:22 -04:00
Bailey Dixon 5df941a179 feat: add release video pipeline 2026-07-07 13:02:26 -04:00
Bailey Dixon 66728686b9 Merge pull request #174 from Codename-11/chore/pr-batch-pre-minor
chore: batch 4 feature PRs onto dev for the next minor (#172, #170, #123, #171)
2026-07-07 13:00:36 -04:00
Bailey Dixon c05ee40db4 Merge PR #171 (bblicke1:feat/android-multi-device-bridge) into pr-batch — multi-device bridge targeting
# Conflicts:
#	DEVLOG.md
2026-07-07 12:44:17 -04:00
Bailey Dixon 66166b2c2a Merge PR #123 (feat/axi-26-notification-triggers) into pr-batch — notification triggers MVP
# Conflicts:
#	CHANGELOG.md
#	DEVLOG.md
2026-07-07 12:42:40 -04:00
Bailey Dixon c8a6534bec Merge PR #170 (feat/upstream-impact-cleanup-dashboard-serve) into pr-batch — upstream-impact Relay guardrails
# Conflicts:
#	CHANGELOG.md
#	DEVLOG.md
2026-07-07 12:39:49 -04:00
Bailey Dixon 8afbb6120d Merge PR #172 (feat/model-picker-refresh-parity) into pr-batch — model picker refresh parity
# Conflicts:
#	DEVLOG.md
2026-07-07 12:34:32 -04:00
Bailey DixonandClaude Fable 5 9c080f522c docs: changelog entry for #165 fix + devlog for the v1.3.0 release act
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 22:37:10 -04:00
Bailey DixonandClaude Fable 5 d2a2d01072 Merge branch 'fix/plugin-native-imports' into dev — native-loader imports + installer venv autodetect (#165, for plugin-v1.3.1)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 22:36:33 -04:00
dependabot[bot] fe297e2db9 chore(deps): bump io.github.takahirom.roborazzi:roborazzi-compose (#169)
Bumps [io.github.takahirom.roborazzi:roborazzi-compose](https://github.com/takahirom/roborazzi) from 1.64.0 to 1.66.0.
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](https://github.com/takahirom/roborazzi/compare/1.64.0...1.66.0)

---
updated-dependencies:
- dependency-name: io.github.takahirom.roborazzi:roborazzi-compose
  dependency-version: 1.66.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-07 02:22:41 +00:00
Bailey Dixon f5bb41e46d release: android-v1.3.0 + plugin-v1.3.0 (merge dev)
release: android-v1.3.0 + plugin-v1.3.0
2026-07-06 22:16:34 -04:00
Bailey DixonandClaude Fable 5 0b0e323b20 Merge branch 'main' into dev — sync dependabot bumps ahead of the release merge
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 22:16:08 -04:00
Bailey DixonandClaude Fable 5 d8cc3d7082 release(android): android-v1.3.0
Bump to 1.3.0 (code 21); cut the CHANGELOG [1.3.0] block; refresh
RELEASE_NOTES, whats_new, changelog.json, and Play notes; write
plugin-v1.3.0 release notes (with the #165 native-install known-issue
callout — that fix ships in v1.3.1).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 22:00:05 -04:00
Bailey DixonandClaude Fable 5 a8db3a2ed8 docs(todo): voice background-run v2 roadmap — fast lane, queue, tool-output surfacing, deferred concurrency
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 21:56:17 -04:00
Bailey DixonandClaude Fable 5 8dc874cbbf fix(voice): free the floor during background runs — chip-only progress, exit detaches, cancel never clobbers a delivered answer
Background-run progress events (tool.started/tool.delta/run.progress and the
shared emitStatus path) forced VoiceState.Thinking on every tick, pinning the
overlay in spinner+Stop and routing mic taps to the interrupt branch — the
relay's floor was free but the client never returned to Idle, so conversation
couldn't continue during a promoted run. Those paths now update only the
background chip while a run is active; inline (grace-window) turns keep
today's behavior.

Exit and Stop no longer kill a background task: exitVoiceMode detaches (the
relay delivers the result on the next session or as a proactive notification)
and interruptSpeaking silences audio only — the chip's ✕ remains the one
explicit cancel. hermes.run.cancelled in the chat sync now only replaces the
bubble with "Cancelled." when it holds no real content; a delivered answer
keeps its text and gets the Stopped badge, fixing the completed-task-shown-
as-cancelled transcript.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 21:45:21 -04:00
Bailey DixonandClaude Fable 5 ea8d09e7f0 fix(build): 2g test-worker heap — grown suite OOMs Roborazzi renders on the 512m default
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:26:47 -04:00
Bailey DixonandClaude Fable 5 5c6211e63f ci(android): add ChatStreamRecoveryTest to the focused test slice
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:18:41 -04:00
Bailey DixonandClaude Fable 5 8c8e24c4d0 Merge branch 'fix/chat-stream-recovery' into dev — sessions-stream answer recovery (#166)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:18:08 -04:00
Bailey DixonandClaude Fable 5 d16f477d81 fix(chat): settle streaming state on recovery abort + anchor by position (#166)
Aborting an in-flight answer recovery (session/profile switch, new
chat/thread, connection switch) called cancelAnswerRecovery(settleUi=false)
with no live stream, killing the poller but leaving ChatHandler._isStreaming
true and the "Reconnecting to your answer…" turn status frozen forever.
cancelAnswerRecovery now always settles the handler when a poller was
running: a silent clearStreamingStatus() on the abandon paths (no error
badge, per-message flags untouched so cancelStream's Stopped-badge findLast
still works) and the existing placeholder finalize on the new-send path.

The poller also anchored on the pending user message by trimmed-text
indexOfLast, so a short repeated prompt ("yes"/"continue") whose send never
reached the server could match a stale identical earlier row and adopt a
different turn's static (instantly "stable") answer. Recovery now captures
how many user rows existed before the send and requires the pending send to
be the (N+1)-th user row AND match its content; when it can't be established
it never adopts and fails fast to the error UI after confirming across two
polls, instead of polling to the 30-minute cap.

Also adds the clearPendingAsk(deny) parity the sibling stream-error branch
performs to the recovery give-up path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:16:55 -04:00
Bailey DixonandClaude Fable 5 357723392d ci(plugin): run native-layout import guard + document plugin-pkg parent assumption
plugin/tests/test_native_layout_imports.py (the AST guard against absolute
plugin.* imports + the native-loader smoke test) was never in ci-plugin.yml's
pytest file list, so a reintroduced absolute import would pass CI. Add it to
the invocation and switch the dependency step to `pip install -e .` so the
smoke test's full relay import chain (requests/httpx/segno/websocket-client)
resolves under CI's clean subprocess.

Also document, on _plugin_module()'s dotted-__package__ branch, the assumption
that our parent package is the plugin package (true for both real layouts:
plugin.dashboard and hermes_plugins.hermes_relay.dashboard).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:11:54 -04:00
Bailey DixonandClaude Fable 5 8e96a019a2 fix(installer): point generated systemd unit + shims at the detected venv
install.sh already autodetects the venv layout (classic venv, uv-managed
.venv, Docker), but the systemd unit template and the pair/status/relay/
tailscale shims still hardcoded the classic ~/.hermes/hermes-agent/venv
interpreter. On a uv-managed host the install reported success while
ExecStart pointed at a nonexistent python -> 203/EXEC, dead relay, broken
shims.

Rewrite the unit's ExecStart/PATH/VIRTUAL_ENV to the detected venv dir at
install time (sed over the committed classic-default template), and make
every generated shim try the detected interpreter first. HERMES_VENV_PY
still wins; the classic + uv layouts remain runtime fallbacks so a relocated
venv self-heals without a reinstall.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:11:53 -04:00
Bailey Dixon 71f3331f54 feat: add multi-device Android bridge targeting 2026-07-06 20:11:45 -04:00
Bailey DixonandClaude Fable 5 e9effeeb87 chore(batch): review nits, CI test-slice additions, changelog/devlog for the issue batch
Review-nit cleanup across the merged branches (KDoc placement, prefill KDoc
accuracy, synthetic test IP, RELEASE.md artifact wording, security.md plain-ws
gating description), ServerAddressTest + IssueReportAndDiagnosticsTest added to
the focused Android CI slice, and consolidated CHANGELOG/DEVLOG/TODO entries.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 20:00:18 -04:00
Bailey DixonandClaude Fable 5 e9b00757d5 Merge branch 'fix/onboarding-scroll' into dev — scrollable compact onboarding (#145)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:55:30 -04:00
Bailey DixonandClaude Fable 5 891085ed61 Merge branch 'fix/diagnostics-report-noise' into dev — severity-gated Report flow (#155 #154 #146)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:55:30 -04:00
Bailey DixonandClaude Fable 5 b53cfbc906 Merge branch 'docs/freshness-pass' into dev — UI labels, anchors, stale claims
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:55:30 -04:00
Bailey DixonandClaude Fable 5 045f42386d Merge branch 'fix/release-assets' into dev — 2-asset android releases (#144)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:55:29 -04:00
Bailey Dixon 44e6e9b6dd feat: add model picker refresh parity 2026-07-06 19:51:48 -04:00
Bailey DixonandClaude Fable 5 c46560aeeb fix(onboarding): scroll + compact-height adaptation so slide content is never cut off
Onboarding slide content overflowed below the fold with no scroll
affordance on short viewports or raised font scale (#145).

- OnboardingPage: outer Column now verticalScroll(rememberScrollState())
  per page; Arrangement.Center dropped (the pager's centering Box handles
  short content and Center conflicts under verticalScroll).
- Hero adapts via BoxWithConstraints: 232dp -> 160dp below 620dp available
  height, hidden below 480dp, so typical devices don't need to scroll;
  scrolling remains the safety net for font-scale/foldable extremes.
- OnboardingScreen: bottom nav (pinned outside the pager) tightens its
  48dp bottom padding + indicator spacer under compact screen heights.
- OnboardingCompactScreenshotTest: Roborazzi renders at w320dp-h480dp @
  1.5x font scale and w360dp-h600dp, scrolling to the last body line to
  prove reachability; no golden PNGs, store screenshots untouched.

Fixes #145

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:45:43 -04:00
Bailey DixonandClaude Fable 5 9593787482 docs(user-docs): expand troubleshooting for endpoint and streaming issues
- "No reachable endpoint" subsection: what the diagnostic means and how to
  check each saved route from the phone (LAN vs Tailscale, port 8642).
- Callout: never use localhost/127.0.0.1 as the server address on a phone.
- Tailscale checklist, including that the relay Tailscale helper serves
  the relay + API ports but not the dashboard :9119 (Manage needs it
  reachable separately).
- "Long turns with local models" entry: mid-turn stream drops recover the
  finished answer automatically; screen-on/plugged-in reduces drops.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:30:16 -04:00
Bailey DixonandClaude Fable 5 44ba8ebb41 feat(util): ServerAddress.loopbackHostWarning advisory helper
Pure helper returning an advisory string when a typed server address
parses to a loopback / any-interface host (localhost, 127.x.x.x, ::1,
0.0.0.0) - such an address points at the phone itself and can never reach
the server. Accepts scheme-less input via the existing parseUserInput
normalization; bare "::1" is handled explicitly since it never parses
without brackets. Not wired into any UI yet - wiring is a queued
follow-up owned by the connection-flow workstream.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:30:15 -04:00
Bailey DixonandClaude Fable 5 d25f805fa7 fix(diagnostics): severity-gate the Report flow and fix issue prefill noise
Routine Info-severity probe lines ("Testing API connection") were one tap
away from becoming "[Bug]:"-titled GitHub issues with an unedited
boilerplate body (#155, #154, #146). Now:

- Info entries require a free-text "What were you expecting to happen?"
  answer before the GitHub link is offered; the answer replaces the
  boilerplate "What happened" line (secret-redacted via the shared
  DiagnosticsLog path). Error entries keep the direct flow.
- Info/Warning entries prefill as "[Diagnostic]: <title>" with the existing
  "question" label; Error entries keep "[Bug]:" + "bug".
- The "Connection mode" line now carries the actual route role
  (entry.endpointRole, else inferred from the entry URL, else "unknown")
  instead of the literal "LAN / Tailscale / public TLS / other" template.

Prefill logic extracted to the pure DiagnosticIssuePrefill object so the
title/label/body contract is unit-testable without Compose.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:30:01 -04:00
Bailey DixonandClaude Fable 5 3cef7c39e3 fix(chat): recover a dropped sessions-stream turn from the persisted transcript (#166)
Slow local models + delegating skills outlive the phone's SSE socket
(screen-off / Doze / Wi-Fi power-save — not an OkHttp timeout). Upstream
api_server keeps running the turn after the SSE writer dies and persists
the final answer, but the client finalized the turn as an error after one
immediate history reload that raced the still-running run — stranding the
"Still working…" placeholder forever.

Client-side recovery, standard-path safe (no server/plugin changes):

- ChatStreamRecovery: poll `/api/sessions/{id}/messages` after a
  transport-class (IOException-family) drop on the SESSIONS endpoint —
  5s cadence with exponential backoff to 30s, capped at 30 minutes.
  Finish = a new non-empty assistant message postdating the pending user
  message, stable across two consecutive polls; intermediate persisted
  rows reconcile progressively. A reachable transcript that lacks the
  pending user message fails fast (the run never started).
- Recovered turns finalize with normal-completion side effects
  (turn-complete notification, queued-send drain, session-list refresh)
  via finalizeTurnSideEffects, extracted from onCompleteCb and shared.
  Cap expiry falls back to the existing error UI.
- Exactly one poller per turn; aborted on new send, user Stop, session
  or profile or connection switch, new chat/thread, and VM clear; a late
  onComplete cancels it (double-finalize guard).
- Gateway/runs/completions error paths are unchanged; user cancel keeps
  the existing intentionallyCancelled discipline.
- HermesApiClient: shared streamFailureMessage() + TRANSPORT_ERROR_PREFIX
  so transport failures are distinguishable from server-reported errors.
- UI: streaming placeholder reads "Reconnecting to your answer…" during
  recovery; input caption mirrors it via turnStatus; one diagnostics
  Warning entry when recovery starts. ChatHandler.onStreamError now also
  clears the stale turn-status caption.

Tests: virtual-time poller coverage (backoff cadence, stability window,
fail-fast, cap expiry, cancel) plus Robolectric + MockWebServer
end-to-end coverage (mid-turn socket kill -> polls -> placeholder
completes with the recovered answer; user cancel and new send abort the
poller; cap expiry surfaces the error UI).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 19:11:52 -04:00
Bailey DixonandClaude Fable 5 ba18fe95c0 docs(plugin): note the official Docker image install path
The immutable nousresearch/hermes-agent image (/opt/hermes/.venv) only
supports the native 'hermes plugins install' path; install.sh's
editable/systemd path is not applicable there.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:49:28 -04:00
Bailey DixonandClaude Fable 5 70015beb81 test(plugin): native-layout import guard + loader smoke test
Two layers so #165's failure class can't regress silently:
- AST guard over every runtime module under plugin/ asserting no
  absolute plugin.* imports remain (tests exempt).
- Native-layout smoke: copies the plugin tree to a tempdir under a
  different package name and, in a subprocess with top-level 'plugin'
  imports blocked, loads it exactly like upstream's
  PluginManager._load_directory_module, then imports the relay server
  chain, tailscale CLI, pair, doctor, and enhancements.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:49:28 -04:00
Bailey DixonandClaude Fable 5 5a44d4519a fix(installer): autodetect venv layouts and steer Docker installs to the native path
install.sh hardcoded ~/.hermes/hermes-agent/venv/bin/python and died
mid-run on the official Docker image (#165). Now auto-detects, in order:
the classic venv, a uv-managed .venv, and /opt/hermes/.venv (official
Docker image). The Docker layout is immutable — no clone, no user
systemd, site-packages reset on pull — so the installer refuses it
early with a steer to 'hermes plugins install
Codename-11/hermes-relay/plugin' and exits nonzero. An explicit
HERMES_VENV_PY still forces through.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:49:28 -04:00
Bailey DixonandClaude Fable 5 fcbf5666e4 feat(plugin): doctor check that imports the relay server chain
'hermes relay doctor' previously passed on installs where 'hermes relay
start' crashed at import time (#165) because no check ever imported the
relay code. Add a relay-import-chain check that imports
<plugin pkg>.relay.server under the CURRENT package layout and reports
an actionable error (update the plugin / reinstall) when it fails.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:49:27 -04:00
Bailey DixonandClaude Fable 5 865c39bd86 fix(plugin): package-relative imports so the native plugin loader works (#165)
hermes-agent's native installer imports the plugin directory as
hermes_plugins.hermes_relay — no top-level 'plugin' package exists there,
so every absolute 'from plugin.X' import crashed 'hermes relay start'
with ModuleNotFoundError: No module named 'plugin'.

- Convert all runtime absolute plugin.* imports to package-relative form
  (relay voice/realtime chain, tailscale CLI, pair, enhancements, tools).
- android_tool's direct-script fallback now imports the sibling module
  bare instead of via 'plugin.tools.'.
- dashboard/plugin_api.py is exec'd standalone by the dashboard web
  server (spec_from_file_location, no parent package), so relative
  imports can't work there: add a _plugin_module() bootstrap that
  imports through the real parent package when one exists, and
  otherwise synthesizes it (bare ModuleType with __path__ at the plugin
  dir under a stable sys.modules alias) without exec'ing
  plugin/__init__.py side effects.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:49:07 -04:00
Bailey DixonandClaude Fable 5 c76e906b30 docs: freshness pass — UI labels, deep-link anchors, stale claims
- Quote the real Connect-page button label ("Hermes", renamed from
  "Vanilla Hermes" in v1.2.2) in getting-started's connect and
  manual-setup instructions; concept-term usage left untouched
- Add explicit VitePress heading anchors so existing deep links resolve:
  #sideload-apk, #relay-server-optional, #install-the-server-plugin
  (getting-started), #self-update-hermes-relay-update and
  #install-from-source-node-21 (desktop installation),
  #demo-native-paste-into-the-attached-tui (desktop index)
- Repoint pre-existing dead anchors found by a full built-site anchor
  sweep: features index -> chat #slash-commands (x2) and
  getting-started #_3-connect-chat; desktop index -> tools
  #desktop-open-in-editor-and-interactive-patches
- README: correct registered tool counts (35 android_*, 25 desktop_*)
- docs/security.md: drop prototype framing; describe shipped state —
  plain ws:// consent dialog + TOFU SPKI pinning, per-channel grants and
  Bridge safety rails, on-device Bridge activity log + relay service log
- Home page chat card: gateway WebSocket preferred, HTTP/SSE fallback
- Release tracks: plugin update via hermes plugins install or the
  hermes-relay-update shim (matches install.sh)
- Desktop troubleshooting: pin mismatch text now says SPKI sha256 pin
  (matches certPin.ts), not whole-cert hash

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:47:48 -04:00
Bailey DixonandClaude Fable 5 b56dec859d fix(release): attach only sideload APK + googlePlay AAB + SHA256SUMS to android releases
Four assets per android-v* release confused new users: GitHub sorts
assets alphabetically so the non-installable googlePlay .aab listed
first, and the two parity/testing artifacts had no meaning to
non-developers (#144, follow-up from #65).

- release-android.yml: still builds all four artifacts, but attaches
  only the sideload APK, the googlePlay AAB, and SHA256SUMS.txt;
  checksums now cover exactly the attached files. The parity twins
  remain reproducible from the tag via CI. The sideload APK filename
  is unchanged — the in-app UpdateChecker matches ".apk"+"sideload"
  in asset names.
- RELEASE_NOTES.md: replaced the 4-row download table with a lead
  install callout (sideload APK / Google Play) plus an explicit note
  that the .aab is a Play Console upload bundle, not tap-installable.
- RELEASE.md §2: codified the Download-block format and the 2-asset
  policy as the required RELEASE_NOTES format for future releases.

Closes #144

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:37:34 -04:00
Bailey DixonandClaude Fable 5 b36666db74 docs(plan): open-issue resolution batch — triage of all 13 open issues + owner action queue
Multi-agent code-verified triage: 5 issues already fixed in released tags
(closure-only), 4 workstreams of real fixes (SSE stream recovery, native-install
imports, diagnostics report de-noising, onboarding scroll), release-asset and
docs-freshness passes, and release sequencing around the pending plugin-v1.3.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:29:41 -04:00
Bailey Dixon 91763a286f feat: add upstream-impact relay guardrails 2026-07-06 18:05:51 -04:00
dependabot[bot] bc6f288b0b chore(deps): bump androidx.compose:compose-bom in the compose group (#167)
Bumps the compose group with 1 update: androidx.compose:compose-bom.


Updates `androidx.compose:compose-bom` from 2026.06.00 to 2026.06.01

---
updated-dependencies:
- dependency-name: androidx.compose:compose-bom
  dependency-version: 2026.06.01
  dependency-type: direct:production
  dependency-group: compose
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-06 11:54:41 +00:00
Bailey DixonandClaude Fable 5 9554c7c153 feat(voice): live background-run chip — progress, connection phases, cancel
With timer-driven spoken progress off by default, the voice overlay's
background-run chip is the primary in-between signal — but it was a static
string. Make it live using the hermes.run.progress extras the relay already
sends (active_tool_name / completed_tool_count / elapsed_ms, now parsed into
RealtimeVoiceEvent):

- BackgroundRunState gains statusLine / completedToolCount / startedAtMs /
  phase (RUNNING / RECONNECTING / DELIVERING). Tool-start + progress events
  drive the live line; handoff labels flip the chip to RECONNECTING during a
  mid-run socket drop ("Reconnecting — your task is still running") and back
  on "Voice reconnected"; background_completed shows a DELIVERING chip until
  the first summary audio (20s watchdog covers visual-only delivery); a new
  turn mid-run sets "Still working on the earlier task…".
- BackgroundRunChip composable: pulsing dot (tertiary while reconnecting),
  phase-aware title, live detail line (step · N steps · m:ss ticker), and a
  cancel ✕ wired to the existing response.cancel path (chip flips to
  "Cancelling…"; hermes.run.cancelled clears it). Remembers the last non-null
  state so the exit fade doesn't snap empty.

Client-only; no relay changes. assembleSideloadDebug + lintSideloadDebug
green. Ambient visibility outside voice mode deferred to coordinate with the
connection-management status strip (TODO).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FCQnygBdT2VfEsa3bufJnX
2026-07-01 19:11:25 -04:00
Bailey DixonandClaude Fable 5 b047fc01c8 feat(voice): realtime resume retry loop + voice-mode session prewarm
- A failed realtime-agent resume used to park forever on "waiting for route
  change" while the relay held the detached session (and any background run's
  result) open for minutes. The client now also retries the resume every 10s
  for up to 5 minutes; a successful socket open clears the retry state, and
  the route-change watcher stays as the fast path on an actual network switch.
- entering voice mode prewarms the persistent Realtime Agent session (session
  POST + relay websocket + provider connect) so the first utterance skips that
  setup. Prewarm sends no input and skips all turn-scoped side effects (no
  Thinking state, no chat placeholder, guards disarmed); the first real
  utterance rides submitRealtimeTurn like any follow-up turn, and a failed
  warm-up is silent — the next turn simply opens fresh.

Verified: assembleSideloadDebug + lintSideloadDebug green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FCQnygBdT2VfEsa3bufJnX
2026-07-01 17:53:01 -04:00
Bailey DixonandClaude Fable 5 19d3945b83 feat(voice): harden ADR 33 background runs — deliver-on-reattach, adaptive promotion, milestone speech
Robustness batch from an architecture review of the realtime background-run
path (the interim-ack + later-injection shape matches current realtime-API
practice; these are the lifecycle/UX gaps around it):

- Deliver-on-reattach: a result completing while the phone is detached is held
  (pending_background_result) instead of spoken into the bounded replay ring
  (a long summary could evict its own head); resume injects it after replay.
  If the session dies first, _close_native_session pushes the result through a
  new proactive_push hook (ProactiveChannel.push, buffered while offline) —
  including the close-races-completion case.
- Busy answer: a second hermes_run_task while one is in flight returns a
  speakable already_running result instead of overwriting hermes_task and
  cancelling the first run's delivery (silent orphan).
- Adaptive promotion: known-long tools flag the run at tool-start
  (RELAY_VOICE_LONG_TOOL_HINTS); the grace wait races that signal and promotes
  after a 1.5s quick-finish window, so obviously-long runs hand off early
  while fast long-class calls stay Tier A.
- Milestone speech: timer-driven spoken progress is per-session config and OFF
  by default (realtime_voice_progress_spoken_after_ms: 0); handoff/completion/
  failure speech and the visual progress events are unchanged.
- Plumbing: done-callbacks retrieve+log unexpected hermes_task /
  background_delivery_task failures; provider websockets get an explicit
  heartbeat=20s with a connect-bounded (not total) timeout.

Tests: 4 new promotion tests (deferred-injection-on-resume, busy second task,
long-tool promotes before an 8s grace, config default 0); the spoken-status
routes test opts in via the new per-session knob. 65 realtime tests green via
python -m unittest. Pre-existing xai-oauth fixture failure recorded in TODO.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FCQnygBdT2VfEsa3bufJnX
2026-07-01 17:50:36 -04:00
Bailey DixonandClaude Opus 4.8 27c325b681 fix(voice): don't let a benign provider cancel-notice kill a live realtime turn
After a promoted/background Hermes run finished, the spoken summary was never
heard. The re-injection called cancel_response() with no active provider
response, xAI replied "Cancellation failed: no active response found", the relay
forwarded it as a fatal voice.error, and the client closed the whole realtime
session (error toast + Retry) right before the reply.

- broker.py: _inject_background_summary gains cancel_current; _deliver_background
  _result passes cancel_current=not floor_idle, so the needless cancel (and its
  benign error) is avoided when the floor is already idle. _pump_provider_events
  classifies benign provider notices via _is_benign_provider_error() and logs a
  non-fatal voice.realtime_agent.provider_notice instead of a fatal voice.error.
- RelayVoiceClient.kt: a voice.error matching a transient provider notice is
  logged and ignored instead of tearing down the session (defense in depth).

Test: benign provider ERROR is not forwarded as voice.error while a fatal one
still is. 61 realtime-broker tests green via python -m unittest.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 13:04:52 -04:00
Bailey DixonandClaude Opus 4.8 1c014a6b8d release(plugin): plugin-v1.3.0
Minor bump from 1.2.1 (still the latest plugin tag) to cover the accumulated
unreleased plugin work: the proactive phone platform (agent->phone push, agent
Threads, two-way reply, outbound buffering), the /phone/threads + update-check
routes, the per-profile enable helper, and the realtime-voice background-run
resilience fix. Version synced across pyproject.toml, plugin/relay/__init__.py,
plugin.yaml, and the dashboard manifest/package files; CHANGELOG [Unreleased]
gains the realtime-voice fix bullet.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 12:08:42 -04:00
Bailey Dixon 0eca419853 Update CLAUDE.md 2026-07-01 11:28:41 -04:00
Bailey DixonandClaude Opus 4.8 7879622be0 fix(relay): keep realtime background runs alive across transient drops
A promoted/durable realtime-voice run (ADR 33) lost its result on a brief network
drop: the relay closed the detached session 30s after any disconnect
(_RESUME_TTL_SECONDS), cancelling background delivery and orphaning the run long
before a minutes-long run finishes. The relay already replays unacked events on
resume, so the session just needs to survive that long.

- Keep a detached session alive while a background run is in flight: the resume
  window stretches from 30s to a background cap (default 6 min,
  RELAY_VOICE_BACKGROUND_DETACHED_MAX_MS); a poll loop closes only after the run
  finishes plus a grace. Resume then replays the recorded result.
- Bound a run at a hard cap (default 5 min, RELAY_VOICE_BACKGROUND_RUN_MAX_MS): a
  hung tool is cancelled and surfaced as a background_completed error.
- Cancel the orphaned hermes_task on session close so a hung tool can't keep
  running; guard _inject_background_summary's send_text so a dead provider socket
  can't raise unhandled in the delivery task.

Tests: two new promotion tests (detached session survives a shrunken base TTL and
records the result for replay; a hung run times out + is cancelled). 60
realtime-broker tests green via python -m unittest.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 11:24:07 -04:00
Bailey DixonandClaude Opus 4.8 e6e8527883 fix(chat): proportion markdown headings and tighten bubble grouping
Markdown h1..h6 were unset in markdownTypography(), falling through to the
mikepenz M3 display roles (h1=displayLarge, 57sp in this app's scale) so a single
`#` dwarfed the 14sp body in a ~272dp bubble. Set an explicit chat-tuned ramp
(h1 20sp -> h6 13sp, derived from bodyLarge/bodyMedium so the font-picker still
applies), unify paragraph/text/bullet/ordered/list to 14sp, size inline+fenced
code to 13sp with tracking 0, italicize/mute blockquotes, and give links a
primary accent + underline via textLink.

Also: gate the per-bubble timestamp to isLastInGroup (alpha 0.5 -> 0.6), break
same-author grouping on a >5min gap (GROUP_GAP_MS), fire a haptic when the
long-press action menu opens, and show the streaming dots only before the first
token. Deferred follow-ups recorded in TODO.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 11:23:36 -04:00
Bailey DixonandClaude Opus 4.8 2a4c5a1de4 refactor(connections): remove now-dead top-strip surface code
Follow-up to the two-connection rework: connection status lives in the chat
header subtitle + the bottom RelayStatusStrip cue, so the top-strip machinery is
unreachable. Removed:

- ConnectionHandoffBanner (wrapper, no callers) + ConnectionStatusBanner (the
  take-space/compact top render) + PulsingSyncIcon, and their orphaned imports.
- ConnectionStatusSurface enum + presentationSurface() (RelayUiState) and its
  ConnectionStatusSurfaceTest.
- Refreshed the stale KDoc refs in RelayStatusStrip.

Kept: ConnectionStatusToast, deliberately parked as a general-purpose toast
primitive (only surface with a live multi-step stepper), plus the shared
ConnectionStepRow/StepGlyph helpers and the ConnectionStatusSnapshot/
ConnectionHandoffStatus models (still feed the VM's globalConnectionStatus and
the bottom-strip cue). compileSideloadDebugKotlin green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 11:04:22 -04:00
Bailey DixonandClaude Opus 4.8 a458d5bd45 refactor(connections): status in header subtitle + bottom strip, drop top surface
Reworks connection-status UI (superseding the persistence-tiered top strip) after
on-device iteration surfaced that "connection" is really two independent connections,
and conflating them was the design error:

- Chat/agent (gateway/API) -> the chat header SUBTITLE (WhatsApp-style): the model
  line swaps to Reconnecting.../Connecting.../Disconnected and crossfades back to the
  model on recovery. Adds reconnecting-vs-connecting wording (everConnected).
- Relay socket (:8767, bridge/terminal/relay-voice) -> the bottom RelayStatusStrip
  "Reconnecting..." cue only. It never blocks chat, so it stays ambient.
- No top-of-screen surface at all (removed the Passive/Banner top strip). Route
  change is ambient-only (the bottom strip's route label).

Also in this pass:
- fix: a benign background->foreground re-handshake is now fully silent. New
  postResumeQuiet window gates the bottom-strip cue -- the health "Connecting" path
  used to leak it there, flashing then clearing with no resolution.
- Merge the three positive handoff branches into one, deciding "Connected to Hermes"
  vs "Connection changed - LAN -> Tailscale" at the actual connect via
  lastConnectedRole, so a flap or a swap can't emit a redundant pair.
- Permanent client-side logging (tag ConnectionVM, pairs with ConnectionManager) for
  every relay state/role transition + handoff record.

Diagnosed via a both-sides trace (client log + read-only relay journalctl): the
flapping was a Samsung adaptive-Wi-Fi teardown, not an app bug. The old
ConnectionStatusSurface/presentationSurface tiering + ConnectionStatusBanner top
render are now unused (kept for now, tracked in TODO); ConnectionStatusToast is
parked as a general toast primitive. Lint green; ConnectionStatusSurfaceTest green
(3 unrelated DataStore-rename failures are pre-existing Windows-local flakiness).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 09:46:58 -04:00
Bailey DixonandClaude Opus 4.8 52400f5415 refactor(connections): tier status surface by persistence, not severity
Routine reconnects no longer shove the whole screen down. The connection-
status surface is now tiered by how long a state persists, so the most
frequent event (a reconnect) is the least disruptive:

- ConnectionStatusSurface { None, Float, Banner } + presentationSurface():
  active (in-flight reconnect/checking) -> None; success (reconnected /
  route switched) -> Float; sustained Warning/Error -> Banner. Maps 1:1
  onto the existing handoff producers.
- RelayStatusStrip gains a `reconnecting` cue (amber, softly pulsing
  "Reconnecting..."), so a routine in-progress reconnect surfaces only in
  the always-visible bottom strip -- zero layout shift for the common case.
- RelayApp re-routes the two existing render sites off presentationSurface():
  take-space ConnectionStatusBanner fires only for Banner, floating
  ConnectionStatusToast only for Float. No component rewrites.

Prior split routed all non-error states to the take-space banner, and the
"error -> float" branch was dead (buildGlobalConnectionStatus never emits
Error). The post-resume suppression still fully silences benign resumes.

Adds ConnectionStatusSurfaceTest (pure mapping guard). Lint + unit test green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 21:28:03 -04:00
Bailey DixonandClaude Opus 4.8 a1bf362f56 fix(nav): Manage/Bridge back button no longer no-ops
The back arrow on Manage (DashboardManagementScreen) and Bridge did nothing.
They navigated to Chat via `navigate(Chat){ popUpTo(startDestination){saveState};
launchSingleTop; restoreState }`, but Chat IS the start destination — navigating
to the start with restoreState restored an equivalent stack and nothing moved
(a silent no-op). Navigating to Manage (not the start) worked, which is why only
the "back to Chat" paths were dead.

Fix: use the standard `popBackStack()` for the back arrows (Manage's onBack,
Bridge's onNavigateToChat in both flavors) — reliably returns to the screen the
user opened it from, matching every other sub-screen. bridgeReturnAction's
navigate-to-remembered-route drops saveState/restoreState so returning to Chat
works too. Renamed DashboardManagementScreen.onNavigateToChat → onBack and
relabeled the icon "Back to chat" → "Back".

Verified on-device (sideload debug on SM-S938U): the Manage back arrow now
navigates (previously inert). :app:assembleSideloadDebug BUILD SUCCESSFUL.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 20:53:33 -04:00
Bailey DixonandClaude Opus 4.8 a86b07d42b feat(relay): slow-poll reconnect tier + Doze battery-exemption nudge (sideload)
Two connection-management improvements from the sleep/backgrounding audit.

Slow-poll tier (ConnectionManager). Against a paired-but-dead server the
exponential backoff otherwise capped at ~16s and retried forever — steady
battery + log noise for no benefit. After SLOW_POLL_AFTER_ATTEMPTS (20, ~5 min
of continuous failure) the reconnect drops to a 5-min poll. A network change
re-resolves + reconnects immediately regardless, and reconnectAttempt resets to
0 on a successful onOpen, so recovery is never gated on the slow interval.

Doze battery-optimization exemption (sideload). A specialUse foreground service
holds the process up but does NOT exempt from Doze's network deferral, so the
"Persistent connection" keep-alive still drops the socket in deep sleep. New
util/BatteryOptimizations (isIgnoringBatteryOptimizations + launchRequest) and a
Settings → Quick Controls nudge — shown only when keep-alive is on and the app
isn't exempt — offer the one-tap system request. REQUEST_IGNORE_BATTERY_
OPTIMIZATIONS is declared in the sideload manifest only (Google Play restricts
it), and the nudge is gated on BuildFlavor.isSideload; it re-checks on ON_RESUME
so it clears once granted.

Verified: :app:assembleSideloadDebug + :app:lintSideloadDebug BUILD SUCCESSFUL.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 20:32:31 -04:00
Bailey DixonandClaude Opus 4.8 393920440e fix(relay): gate socket sends on auth + debounce resume re-probe
Two connection-management fixes surfaced by the live relay logs.

1. bridge.status auth race (the relay was rejecting connections). The live
   logs showed repeated "Auth failed … expected system/auth, got
   bridge/bridge.status" — BridgeStatusReporter's immediate/30s tick could beat
   the auth handshake on a fresh or reconnecting socket, so the relay rejected
   the whole connection and the phone reconnected. ConnectionManager.send() now
   holds every non-`system/auth` frame until `auth.ok` arrives (flag reset on
   each connect/close/failure/disconnect); dropping a periodic frame is harmless
   since the next tick re-sends once authenticated.

2. Resume re-probe debounce. revalidate() cleared the probe cache + re-probed
   every route (+ Probing badge flash) on every ON_RESUME, including sub-second
   app switches. New revalidateOnResume(awayMs) skips the heavy re-probe when
   the app was away briefly and the API connection is already healthy; RelayApp
   measures the away duration from ON_PAUSE→ON_RESUME. Network *changes* are
   handled by the ConnectivityObserver/callbacks, not revalidate(), so a brief
   skip can't miss a Wi-Fi↔cellular flip. Network-change callers of revalidate()
   are unchanged.

Verified: :app:lintSideloadDebug BUILD SUCCESSFUL. (Auth-gate confirmed against
live journalctl on the relay host: the exact rejection pattern this removes.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 20:15:37 -04:00
Bailey DixonandClaude Opus 4.8 950eb6e2ab fix(chat): suppress the cold-start "server isn't accepting connections" snackbar
On first load the background session-list load runs before the server is
reachable; its ConnectException was classified to "Connection refused / The
server isn't accepting connections" and shown as the global bottom snackbar —
a scary, redundant pop-up duplicating what the themed connection banner +
startup sphere already surface.

Add `isConnectivityError(Throwable)` (connection-refused / host-unresolved /
timeout) to RelayErrorClassifier, and gate `ChatViewModel.emitError` so the
bootstrap contexts (load_sessions, create_session) skip the snackbar for
connectivity-class failures while still recording them to diagnostics.
Actionable failures (auth rejected, server error) and interactive contexts
(send_message, …) still surface normally.

Adds classifier unit tests (connectivity vs non-connectivity). Verified via
:app:testSideloadDebugUnitTest (RelayErrorClassifierTest) — BUILD SUCCESSFUL.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 19:32:31 -04:00
Bailey DixonandClaude Opus 4.8 309c0e5a76 docs: DEVLOG + TODO for the app-facing update-check route
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 19:22:11 -04:00
Bailey DixonandClaude Opus 4.8 b129aa53f0 feat(update): app-facing relay update-check route + About version readout
Adds the app-side of update discovery (the dashboard/CLI shipped in efa51dc).

- plugin/relay/server.py: GET /relay/update-check on :8767 — the app-facing
  twin of the dashboard route (bearer for the app, loopback for diag).
  Reuses plugin/update_check.check() in an executor (off the event loop),
  caches the GitHub result 1h, degrades softly offline.
- RelayHttpClient.fetchUpdateCheck() → ConnectionViewModel.relayUpdateInfo
  (refreshed on each auth.ok) → an AboutScreen "Relay" row showing the
  connected relay's version + a soft "newer release available" nudge with a
  copy-the-fix command. Fail-soft: older relay (404) → no row.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 19:12:15 -04:00
Bailey DixonandClaude Opus 4.8 a51cef43cd fix(relay): don't force a re-pair on update over a schema version bump
The session file (~/.hermes/hermes-relay-sessions.json) already survives a
git-pull + restart update — it lives outside the updated tree — and a 180-day
trusted-device refresh token recovers a session without a QR when the short
session lapses. But _load_from_disk wrote a `version` field it never read and
handled a missing file silently, so a future on-disk schema change could
silently drop every record (forcing a mass re-pair), and an update that lost
the file gave no diagnostic.

Make the load path version-aware and drop-averse: a newer-versioned file (e.g.
after a relay downgrade) loads best-effort rather than being discarded, only
records that genuinely fail to parse are skipped, and the on-disk version is
logged. A missing session file is now logged explicitly so an update that lost
it is diagnosable instead of silently forcing re-pairs.

Adds version/visibility tests (newer-version file still loads sessions +
trusted devices; versionless file loads; missing file is logged). 22 tests in
test_session_persistence pass; 79 across the adjacent auth/session suites.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 19:08:28 -04:00
Bailey DixonandClaude Opus 4.8 5322586121 chore(store): regenerate 07_connections for the new list design
Update the ConnectionsScene mock to the new scannable connection list — each
card carries an Active badge + the capability timeline summary — replacing the
old single crammed active-card frame. Re-render host-side (Roborazzi, 1080x2160)
and re-export the Play graphic (phone-screenshots/7.png). Validation passed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:59:15 -04:00
Bailey DixonandClaude Opus 4.8 7fcdf886ec feat(connections): tabbed connection detail + animated, dismissible status banner
Split the overloaded Connections screen into a scannable list (level 1) and a
new tabbed ConnectionDetailScreen (level 2: Overview / Routes / Advanced /
Security). Each list card shows label + an Active badge + a one-line status +
the capability timeline summary; tapping drills into the detail, whose overflow
menu owns rename / re-pair / revoke / remove. Adds Screen.ConnectionDetail and
wires it in the NavHost; relocates the ADR-24 route block into a reusable
ActiveCardRoutesSection. Relay sessions get a clear home in the Security tab.

Make the non-error status banner take-space, animated (3-line per-step stepper:
spinner -> green check -> red x), and dismissible (close x + swipe-up, wired to
the existing dismissedStatusKey). Rename the reconnect handoff from the
misleading "Connection changed" to "Reconnecting", and suppress the transient
banner during a foreground-resume grace window so a same-connection
re-handshake after returning to the app doesn't flash a misleading status.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:56:38 -04:00
Bailey DixonandClaude Opus 4.8 efa51dcb55 feat(relay): per-profile enable helper + plugin update discovery
Fixes two productization gaps from the phone Threads work, reusing the
existing update mechanisms (no new updater).

Profiles (install-once / enable-per-profile / pair-once):
- plugin/profiles.py + `hermes relay profiles list|enable [--all|NAME]`
  enumerate the default config + every profiles/<name>/config.yaml and
  bulk-enable hermes-relay in plugins.enabled (backing up each rewritten
  file to .bak, skipping already-enabled configs). Pairing is unaffected
  — one relay, pair once.

Update discovery:
- plugin/update_check.py + `hermes relay update-check` + a dashboard
  "Plugin version" card compare plugin.relay.__version__ against the
  latest plugin-v* GitHub release and surface the right command
  (hermes-relay-update vs `hermes plugins update hermes-relay`). Dashboard
  route GET /api/plugins/hermes-relay/update-check caches the GitHub
  fetch 1h and degrades softly offline.

Docs: configuration.md gains "Profiles & the relay" + "Keeping the relay
plugin updated".

Tests: +39 (profiles discover/state/enable; semver/tag-pick/command-
detect/build-result; dashboard update-check available/up-to-date/error).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:48:42 -04:00
Bailey DixonandClaude Opus 4.8 8308fb87f3 feat(phone): auto-configure home channel + dashboard name field
Silences upstream's first-message onboarding notice ("📬 No home channel
is set for Phone … /sethome"), which fired on every new phone Thread's
first message. The nudge (gateway/run.py) checks the PHONE_HOME_CHANNEL
env var directly, not the adapter's seeded config; a single paired phone
has exactly one logical home, so /sethome is friction with no decision
behind it.

- phone_platform.py: register_phone_platform pre-fills
  PHONE_HOME_CHANNEL=phone when enabled and unset/blank (respects an
  explicit operator override) — presence is what the notice checks.
- dashboard: "Home channel" card on Relay → Management saves a display
  name via host PUT /api/env (PHONE_HOME_CHANNEL_NAME); backed by a new
  loopback GET /phone/config reading the adapter's env resolution.
  Rebuilt dist/index.js.
- user-docs: brief "Phone Threads — Beta" config subsection (opt-in,
  auto-home-channel, rename).

Tests: +4 home-channel-default (test_phone_platform), +2 /phone/config
(test_plugin_api) — 54 pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:09:39 -04:00
Bailey DixonandClaude Opus 4.8 e1bd38dd55 chore(store): regenerate screenshots without the mode strip
Update the Roborazzi harness for the navbar change: drop RelayModeStrip from the shared StoreCockpit (fixes the chat / landing / gallery scenes) and give ManageScene faithful Manage chrome (back arrow + Terminal/Settings/Refresh, no context meter, no hamburger). Re-render the store sources (assets/screenshots/*.png, 1080x2160) and re-export the Play phone screenshots. RelayModeStrip/RelayPrimaryMode stay defined in RelayCockpitChrome — only the harness stopped rendering them.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 14:50:16 -04:00
Bailey DixonandClaude Opus 4.8 71d61bdbe8 docs: fix connections.md switching — chip moved to the agent info sheet
The top-bar connection chip was replaced by the AgentInfoSheet's Connection section; update the 'Switching connection' steps to match (tap the agent name/avatar -> Connection radio list, shown for 2+ connections, disabled while a reply streams).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 14:00:27 -04:00
Bailey DixonandClaude Opus 4.8 3be6566eb0 docs: DEVLOG entry + accuracy pass for the nav / keep-alive changes
Add the 2026-06-30 DEVLOG entry (keep-alive reframe + Quick Controls, mode-strip removal, toast overlay, Tailscale reconnect fix). Correct current-state docs to match: CLAUDE.md RelayApp.kt key-file line (no bottom nav, no mode strip; bottomBar is a status pill); configuration.md navigation (Chat is home, Manage/Bridge via Settings); chat.md 'Persistent connection' section (renamed from 'Keep connected in background', new Settings -> Quick Controls path, 'Turn off' action); play-store-listing.md specialUse wording; flavor-differences.md feature name.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 11:14:52 -04:00
Bailey DixonandClaude Opus 4.8 f32376303b docs(todo): mark chat_id gap resolved via the /phone/threads plugin route
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:25:57 -04:00
Bailey DixonandClaude Opus 4.8 ea63052ffa feat(chat): seed reply routing from the relay's /phone/threads
Wire the app to the new relay route so Thread reply routing is complete,
not just for threads created this session:
- RelayHttpClient.fetchPhoneThreads() — GET /phone/threads (bearer), parses
  [{session_id, chat_id, title}]; fail-soft (404/older relay -> empty).
- ConnectionViewModel: fetch on every auth.ok (relay connect/reconnect) and
  expose phoneThreadChatIds; ChatViewModel.seedThreadChatIds merges it into
  the reply-routing map, authoritative over the in-memory learned map.
- RelayApp collects the flow into the chat layer.

So a Thread the app didn't create, or any Thread after a restart, now routes
its replies to the right conversation instead of falling back to the home
channel. Degrades gracefully if the relay lacks the route.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:25:04 -04:00
Bailey DixonandClaude Opus 4.8 f7d77ecc1c docs: changelog for Quick Controls, navbar simplification, toast overlay, reconnect fix
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:18:14 -04:00
Bailey DixonandClaude Opus 4.8 103b6e0552 feat(relay): GET /phone/threads — expose phone Thread chat_id from the store
A phone Thread is a source=phone gateway session keyed by a chat_id, but
/api/sessions returns only the opaque timestamp id + source — never chat_id
or session_key. So the Android client can't map a session to its Thread to
route a reply. The relay (our plugin, co-hosted with the gateway, same user)
reads the gateway session store read-only and surfaces session_id <-> chat_id
via GET /phone/threads, filling the gap without a fork or touching the
standard path.

- plugin/relay/session_store.py: read_phone_threads() globs ~/.hermes/state.db
  + profiles/*/state.db, mode=ro (safe alongside the running gateway/WAL),
  returns [{session_id, chat_id, title}] for source=phone rows, deduped;
  skips blank chat_id + older schemas without the column.
- server.py: handle_phone_threads — bearer for the app, loopback for diag
  (same gate as /context/injected); registered at GET /phone/threads.
- 5 unittest cases (read, skip-no-chat_id, root+profile dedup, old schema,
  missing home).

Client prefers this over its in-memory learned map; redundant once upstream
adds chat_id to /api/sessions (a later PR).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:17:40 -04:00
Bailey DixonandClaude Opus 4.8 62961322b9 feat(settings): promote Quick Controls to the top-level Settings landing
Persistent connection is a connection-level control flipped frequently, not chat-specific, so move the Quick Controls card out of Chat settings to the Settings root (beside the Active Agent / Profile lock cards) and add a Turn-complete alerts toggle. Both wire to the existing ConnectionViewModel flows (gatewayKeepAlive / notifyTurnComplete) - no new prefs. Removes the card from ChatSettingsScreen.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:16:46 -04:00
Bailey DixonandClaude Opus 4.8 9142fb8f79 fix(chat): debounce gateway client re-acquisition on route flips
Belt-and-suspenders on top of the network-layer reconnect-loop fix: the LaunchedEffect that re-acquires the gateway chat client now waits a 750ms settle window before rebuilding when only the resolved API route changed, so any residual sub-second LAN<->Tailscale flip can't shutdown the warm gateway socket (idle) or retarget mid-turn (burning MAX_TURN_REJOINS). First acquisition and non-url key changes are not delayed, so cold-start connect latency is unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 10:13:15 -04:00
Bailey DixonandClaude Opus 4.8 a313bac5d2 feat(chat): persist user-named Thread names across restart
The Thread-name override was in-memory only, so a named Thread reverted to
the gateway's auto-title after an app restart. Persist it: ThreadNameStore
(DataStore, sessionId -> name) saved on create, loaded on launch, re-applied
to ChatHandler on the names flow + on initialize() so a handler created
after the load still picks it up. ChatHandler.setUserThreadNames now merges
(doesn't clear) so a just-created name isn't clobbered by a stale load.
Wired ChatViewModel <-> ConnectionViewModel via RelayApp (onSaveThreadName +
a threadNames collector), since ChatViewModel has no Context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 09:32:26 -04:00
Bailey DixonandClaude Opus 4.8 03b05ad863 feat(nav): remove the mode strip from Manage/Bridge; add Up to Chat back arrow
Completes the mode-strip removal: drop RelayModeStrip from DashboardManagementScreen, BridgeScreen, and BridgeCoreScreen (Chat lost it in the prior commit). Each now reaches Chat via a TopAppBar back arrow (Up -> onNavigateToChat, matching the old strip's Chat tab); system Back still pops to Settings. Manage/Bridge stay reachable from Settings -> Hermes management / Bridge. RelayModeStrip/RelayPrimaryMode remain defined in RelayCockpitChrome for the store screenshot harness.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 09:32:00 -04:00
Bailey DixonandClaude Opus 4.8 4ca65c120c feat(chat): remove the Chat/Manage/Bridge mode strip from the chat home
Chat is the home screen; the triplicated mode strip spent a chrome band on the most-used surface. Manage and Bridge are already reachable from Settings (Settings -> Hermes management / Bridge), and Terminal + Settings remain quick icons in the chat top app bar, so the strip is redundant here. Removes the RelayModeStrip usage + its now-unused imports from ChatScreen. The component stays defined in RelayCockpitChrome for the other screens + the store screenshot harness.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 09:22:43 -04:00
Bailey DixonandClaude Opus 4.8 400c20af51 fix(chat): animate connection-status banner as a no-reflow overlay
The non-error connection-status banner rendered as a take-space banner above the Scaffold with fade-only AnimatedVisibility, so its height popped in/out and the content column hard-snapped to fit. Route it through the existing floating-overlay Column alongside the error toast, reusing the house slideInVertically+fadeIn / slideOutVertically+fadeOut spec. An overlay occupies zero layout space, so content no longer reflows on appear/disappear, and it drops out of the Scaffold status-bar inset accounting (matching the comment that already described it as a floating overlay).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 09:16:19 -04:00
Bailey DixonandClaude Opus 4.8 3140e85c04 feat(chat): Session sources section in Chat settings
A "Session sources" sub-section under Chat settings lists the common
external gateways (Discord/Telegram/Cron/Webhook/Web) with a show/hide
toggle each, editing the same persisted hiddenSources set the drawer
source filter uses — so you can hide a source even before it appears in
the session list. cron + webhook hidden by default; your chats + Threads
always show.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 09:07:38 -04:00
Bailey DixonandClaude Opus 4.8 97be04a722 feat(chat): drawer source badges, source filter, Beta-gate Threads
Desktop-style per-gateway attribution in the session drawer:
- A colored source chip on each row (Discord/Telegram/Cron/Webhook/Web/…);
  the app's own chats (tui/api_server) and phone Threads are unbadged
  (Threads keep their thread-spool).
- A source filter dropdown in the drawer header (show/hide sources),
  persisted in SessionSourcePrefs; default hides the noisy cron + webhook
  lanes so the drawer shows your chats + Threads. The filter row is now
  horizontally scrollable so it never crowds.
- "Beta" chip on the Threads filter chip + the best-path Threads capability
  row (full release gated on live /api/ws-in-foreground + unread + the
  chat_id upstream fix + outbox).

Setting persisted via DataStore (cron+webhook hidden by default); editable
from the drawer dropdown. A dedicated Chat-settings section (to toggle
sources not currently present) is a follow-up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 08:03:58 -04:00
Bailey DixonandClaude Opus 4.8 c17932c950 fix(chat): keep a user-named Thread's name (Discord-style, authoritative)
The gateway's async auto-titler (agent.title_generator) overwrote the name
the user gave a new Thread. Make the user's name authoritative: ChatHandler
holds a sessionId -> name override applied in updateSessions, so the
auto-title can't clobber it; switchToCreatedThread records it on create
(plus a best-effort server renameSession for other surfaces).

In-memory for now (sticks within a session); cross-restart persistence is a
follow-up, folded into the drawer source-attribution work.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 21:15:15 -04:00
Bailey DixonandClaude Opus 4.8 cc3db3a7f4 fix(chat): make Threads work against the real session shape (no chat_id in API)
On-device, the create-flow + in-thread reply were broken: a phone session's
id is a timestamp and /api/sessions exposes neither chat_id nor session_key
(only source). My code assumed the id encoded chat_id (…:dm:<chat_id>), so:
- switchToCreatedThread never matched -> never switched -> currentSessionId
  stayed null -> the reply couldn't inject (notified) and the rename never
  ran (auto-title instead of the user's name);
- existing-thread replies routed by a null chat_id.

Fixes (client-side; no API change):
- Find a created thread by session-list DIFF (the new source=phone session
  not present before the send), not by parsing chat_id from the id.
- Keep an in-memory sessionId -> chat_id map, learned at creation and from
  incoming phone.messages, to route replies to the right thread.
- Inject by source + learned chat_id; cover the pre-switch window via the
  creatingThread draft so the first reply shows inline, not as a notification.

Limitation (TODO): a thread the app didn't create this session has an unknown
chat_id until a message arrives while viewing it; proper fix is exposing
chat_id on /api/sessions upstream.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 21:00:45 -04:00
Bailey DixonandClaude Opus 4.8 2ecdb5c797 refactor(chat): retire the Hermes inbox view — agent messages live as Threads
With agent replies now rendering inline in the open Thread, the flat
HermesInboxScreen is redundant surface. Retire it:

- Delete HermesInboxScreen + its Screen.HermesInbox route + nav entry.
- Re-point the notification tap and Settings "View messages" to Chat
  (the message lives there as a Thread).
- Rename the surface "Hermes messages" -> "Threads" (the settings screen,
  the Settings entry, the notification channel) and reframe its copy
  toward conversations-in-Chat.
- ProactiveInboxStore is now a viewer-less write-only log (fully
  retireable — TODO); doc updated.

The opt-in setting (the enable gate + notification permission) stays — it's
still needed; only the inbox *view* is gone. No separate admin view: thread
management folds into the drawer + Settings + the desktop `relay queue`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 20:40:23 -04:00
Bailey DixonandClaude Opus 4.8 21b171c3c4 fix(chat): render agent Thread replies inline in the open Thread
The agent's reply to a Thread message only surfaced as a notification +
the legacy Hermes Messages inbox, never in the open Thread conversation.

ProactiveMessageHandler.dispatch now first tries injectIntoThread: an
inbound phone.message whose chat_id matches the Thread currently open in
Chat (or a pending "+ New Thread" draft) is rendered inline as an
ASSISTANT bubble (ChatHandler.addAgentThreadMessage — clientOnly,
idempotent on message_id) and the notification + inbox entry are skipped
(you're already looking at it). Falls back to home-channel match when a
side has no parseable chat_id, so the single home thread keeps working.
Non-matching / no-thread-open messages still notify + inbox as before.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 20:23:12 -04:00
Bailey DixonandClaude Opus 4.8 f96545beb7 feat: agent Threads - unified-session phone conversations in Chat
Elevate the proactive agent->phone inbox into first-class "Threads":
source=phone gateway sessions rendered in the one Chat surface (sessions
tagged by source), not a separate tab. See docs/decisions.md ADR 12.

App:
- Drawer source tags + custom thread-spool glyph + Threads filter, gated
  on relay pairing + "Let Hermes message me" (slice 1).
- Open a Thread from its server history (free via the existing path);
  composer reply in a source=phone session routes over proactive.reply
  with per-message delivery status Sending->Delivered/Failed (slices 2,4).
- "+ New Thread" (named, Discord-style): mint a chat_id, open it on the
  first message, poll-and-switch to the real session; multi-thread replies
  route by chat_id parsed from the session id (slice 8, user-initiated).
- Threads capability row in the best-path UI (slice 5).

Relay:
- proactive.reply.ack (settles the reply bubble) + a proactive.cancel WS
  verb; 25/25 proactive tests green (slice 7).

Built + installed sideload debug; on-device behavior unverified. Verifies
+ deferred tails in DEVLOG/TODO. "Delivered" needs the relay running the
updated proactive.py.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 20:15:30 -04:00
Bailey DixonandClaude Opus 4.8 8560895e57 feat(cli): relay queue — list/cancel the agent→phone outbound buffer
Host-side UI for the queued state added in ebb4f04 (the queue exists while the
phone is OFFLINE, so it belongs on a surface that's online while the phone is off).

- `relay queue` lists what's waiting for an offline phone (id · age · preview);
  `relay queue --clear` cancels all, `relay queue --cancel <id>` cancels one.
  Over the new loopback GET/DELETE /phone/outbound; loopback-only (403 off-host
  → explained, same as relay info/security). --json for scripting.
- cli.ts: `clear` added to BOOLEAN_FLAGS so `--clear` doesn't swallow a following
  arg; `--cancel <id>` stays a value-flag. relay help line updated.
- Docs: CLAUDE.md Key Files, CHANGELOG (relay bullet + offline-reply reliability
  note on the two-way entry), TODO (host-side CLI surfacing marked done; phone-side
  threaded pending-reply UI remains).

tsc build clean; `relay --help` renders the new subcommand.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 16:52:40 -04:00
Bailey DixonandClaude Opus 4.8 ebb4f041dd feat(relay): outbound buffering — queue agent→phone messages for an offline phone
Closes the gap the device test exposed: an agent answer pushed while the phone
had dropped its (connection-scoped) subscription used to 503 and be lost.

- ProactiveChannel.push() now queues on no-subscriber (bounded deque, drop-oldest,
  24h staleness TTL) and returns {delivered:false, queued:true, buffered:N} instead
  of raising 503. _flush_outbound delivers the backlog FIFO on the next
  proactive.subscribe; stale entries are pruned, and a socket that dies mid-flush
  re-buffers the remainder.
- Observe/cancel: peek_outbound()/cancel_outbound() + loopback routes
  GET /phone/outbound (count + summaries) and DELETE /phone/outbound[?message_id=]
  (cancel all / one) — the enabling layer for a host-side "queued + cancel" UI.
- Adapter send() unchanged (a 200 queued reads as success). Handler's no-subscriber
  503 path removed (now queues); ProactiveError is left only for a live write fail.
- Tests: 54 proactive+phone pass (flush-on-subscribe FIFO, bounded drop-oldest,
  stale-drop, cancel one/all, close clears).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 16:30:01 -04:00
Bailey DixonandClaude Opus 4.8 b5d30287a9 chore(phone): remove temp [phone-diag] tracing; document Phase 2c device fixes
Reverts the temporary file-based [phone-diag] scaffolding (connect/loop/register
tracing) added to localize the two-way-reply failure. The genuine fixes stay:
PhoneAdapter.connect(is_reconnect=...) (3018a18), and the registration `except`
upgraded from silent debug to a visible warning.

- DEVLOG: record the device round-trip + both faults — the connect() signature
  TypeError, and a stale duplicate plugin copy in the user-plugins dir winning the
  loader's name-dedup so the gateway loaded old code and ignored every deploy.
- TODO: mark Phase 2c device-verified; add the installer-purge-stale-backups fix
  and the usability roadmap (outbound buffering first; threaded agent surface per
  the "separate lanes, unified surface" decision; per-thread chat_id; status; title).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 16:14:18 -04:00
Bailey DixonandClaude Opus 4.8 9081fb341c chore(phone): file-based [phone-diag] trace (gateway filters plugin logs)
The gateway journal suppresses plugin logs at every level, so the WARNING
trace was invisible. Switch the diagnostics to append to ~/.hermes/phone-diag.log
so we can see exactly which hop fires: registration, connect() entry/abort,
reply-loop start. TEMPORARY — reverted once the connect gap is fixed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 12:54:35 -04:00
Bailey DixonandClaude Opus 4.8 39cfedf776 chore(phone): temporary [phone-diag] WARNING tracing for reply-loop connect debug
TEMPORARY diagnostics (to be reverted) to localize why the gateway's phone
adapter never polls /phone/replies despite registration+env_enablement working
in isolation. Plugin INFO is filtered from the gateway journal, so these trace
at WARNING: registration outcome (was silently swallowed), connect() entry, and
reply-loop start. Also upgrades the previously-silent registration except from
DEBUG to WARNING — a real improvement worth keeping.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 12:49:48 -04:00
Bailey DixonandClaude Opus 4.8 3018a186c9 fix(phone): accept is_reconnect in PhoneAdapter.connect — unbreak two-way reply
The gateway's platform supervisor calls adapter.connect(is_reconnect=...)
(BasePlatformAdapter.connect contract, gateway/run.py:3195). PhoneAdapter.connect
was declared connect(self), so every gateway connect raised TypeError, the
adapter never came up, and the Phase 2c inbound reply long-poll
(_run_reply_loop, spawned only inside connect()) never started. Net: the phone's
replies reached the relay and sat buffered forever (0 GET /phone/replies polls);
the agent never saw them and never answered back.

The 2026-06-29 device round-trip surfaced it: agent->phone push worked
(relay->phone), the reply buffered in the relay (proactive <<< ... buffered=1),
but the gateway never drained it.

- Add `*, is_reconnect: bool = False` to PhoneAdapter.connect (matches the base
  contract + the ntfy template it was modeled on). Behavior otherwise unchanged.
- Add ConnectContractTests regression guard (inspect-based — the live adapter
  binds to the gateway base class that's absent in CI, which is the blind spot
  that let this ship).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 12:23:06 -04:00
Bailey DixonandClaude Opus 4.8 64c0c25c25 docs: correct stale "re-pair after relay restart" claim — sessions persist
SessionManager persists sessions to ~/.hermes/hermes-relay-sessions.json
(server.py:88-90, persistence_path from RelayConfig.from_env), and a
trusted-device refresh token recovers a lost/revoked/reset session
without a new QR scan. Paired phones therefore survive a relay restart;
only the in-memory live-connection presence clears (reconnect is
automatic).

Fixes the stale "in-memory; wiped on restart → must re-pair" assertion in:
- CLAUDE.md (Server Deployment key conventions)
- docs/path-architecture.html (auth model table)
- skills/devops/hermes-relay-status/SKILL.md (presence vs pairing)
- ConnectionViewModel.kt / RelayHttpClient.kt (stale comment mechanism;
  fetch-gating logic unchanged — a URL can still outlive a pairing via
  expiry/revoke/never-paired)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-29 10:23:39 -04:00
Bailey Dixon 3897b8efc8 Merge branch 'Codename-11/phone-reply-2c' into dev
Phase 2c: two-way phone reply. Inbound proactive.reply flows relay ->
PhoneAdapter long-poll -> handle_message -> agent, continuing the same
session. Notification RemoteInput + inbox reply box on the app side.

- feat(relay): receive + buffer proactive.reply, expose /phone/replies long-poll
- feat(plugin): PhoneAdapter inbound reply loop — replies become agent messages
- feat(app): capture phone replies — notification RemoteInput + inbox reply box
- docs: record Phase 2c two-way phone reply (CHANGELOG/DEVLOG/TODO)

Not device-verified: live round-trip is owner-driven.
2026-06-29 08:25:11 -04:00
dependabot[bot] 96a6c963dc chore(deps): bump io.mockk:mockk from 1.14.9 to 1.14.11 (#162)
Bumps [io.mockk:mockk](https://github.com/mockk/mockk) from 1.14.9 to 1.14.11.
- [Release notes](https://github.com/mockk/mockk/releases)
- [Commits](https://github.com/mockk/mockk/compare/1.14.9...v1.14.11)

---
updated-dependencies:
- dependency-name: io.mockk:mockk
  dependency-version: 1.14.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 12:09:31 +00:00
dependabot[bot] 373b98f316 chore(deps): bump kotlinx-coroutines from 1.10.2 to 1.11.0 (#161)
Bumps `kotlinx-coroutines` from 1.10.2 to 1.11.0.

Updates `org.jetbrains.kotlinx:kotlinx-coroutines-android` from 1.10.2 to 1.11.0
- [Release notes](https://github.com/Kotlin/kotlinx.coroutines/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.coroutines/blob/master/CHANGES.md)
- [Commits](https://github.com/Kotlin/kotlinx.coroutines/compare/1.10.2...1.11.0)

Updates `org.jetbrains.kotlinx:kotlinx-coroutines-test` from 1.10.2 to 1.11.0
- [Release notes](https://github.com/Kotlin/kotlinx.coroutines/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.coroutines/blob/master/CHANGES.md)
- [Commits](https://github.com/Kotlin/kotlinx.coroutines/compare/1.10.2...1.11.0)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlinx:kotlinx-coroutines-android
  dependency-version: 1.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.jetbrains.kotlinx:kotlinx-coroutines-test
  dependency-version: 1.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 12:07:50 +00:00
dependabot[bot] 83609a4608 chore(deps): bump com.meta.spatial:spatial-gradle-plugin-impl (#163)
Bumps com.meta.spatial:spatial-gradle-plugin-impl from 0.12.0 to 0.13.1.

---
updated-dependencies:
- dependency-name: com.meta.spatial:spatial-gradle-plugin-impl
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 12:07:15 +00:00
dependabot[bot] 2c1d7df764 chore(deps): bump gradle-wrapper from 9.6.0 to 9.6.1 (#159)
Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 9.6.0 to 9.6.1.
- [Release notes](https://github.com/gradle/gradle/releases)
- [Commits](https://github.com/gradle/gradle/compare/v9.6.0...v9.6.1)

---
updated-dependencies:
- dependency-name: gradle-wrapper
  dependency-version: 9.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 12:03:12 +00:00
dependabot[bot] df536b308f chore(deps): bump markdown-renderer from 0.42.0 to 0.43.0 (#160)
Bumps `markdown-renderer` from 0.42.0 to 0.43.0.

Updates `com.mikepenz:multiplatform-markdown-renderer-m3` from 0.42.0 to 0.43.0
- [Release notes](https://github.com/mikepenz/multiplatform-markdown-renderer/releases)
- [Changelog](https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/mikepenz/multiplatform-markdown-renderer/compare/v0.42.0...v0.43.0)

Updates `com.mikepenz:multiplatform-markdown-renderer-code` from 0.42.0 to 0.43.0
- [Release notes](https://github.com/mikepenz/multiplatform-markdown-renderer/releases)
- [Changelog](https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/mikepenz/multiplatform-markdown-renderer/compare/v0.42.0...v0.43.0)

---
updated-dependencies:
- dependency-name: com.mikepenz:multiplatform-markdown-renderer-code
  dependency-version: 0.43.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.mikepenz:multiplatform-markdown-renderer-m3
  dependency-version: 0.43.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 12:01:08 +00:00
dependabot[bot] 65f89d4c0b chore(deps): bump io.github.takahirom.roborazzi:roborazzi-compose (#158)
Bumps [io.github.takahirom.roborazzi:roborazzi-compose](https://github.com/takahirom/roborazzi) from 1.43.1 to 1.64.0.
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](https://github.com/takahirom/roborazzi/compare/1.43.1...1.64.0)

---
updated-dependencies:
- dependency-name: io.github.takahirom.roborazzi:roborazzi-compose
  dependency-version: 1.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 11:58:58 +00:00
dependabot[bot] e78602c9d8 chore(deps): bump androidx.core:core-ktx from 1.18.0 to 1.19.0 (#157)
Bumps androidx.core:core-ktx from 1.18.0 to 1.19.0.

---
updated-dependencies:
- dependency-name: androidx.core:core-ktx
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-29 11:54:46 +00:00
Bailey DixonandClaude Opus 4.8 304e732650 docs: record Phase 2c two-way phone reply (CHANGELOG/DEVLOG/TODO)
- CHANGELOG [Unreleased] Added: reply to the agent's messages (two-way).
- DEVLOG: Phase 2c entry — three legs (relay buffer + /phone/replies long-poll,
  PhoneAdapter inbound loop, app RemoteInput + inbox reply box), the
  role_authorized default-deny decision, scope guardrails, verification.
- TODO: Phase 2c marked shipped (off-device); residual (persistent
  send-when-reconnected reply queue, inbound media) moved to Phase 3; added a
  maintainer reply-round-trip verification item.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 22:06:23 -04:00
Bailey DixonandClaude Opus 4.8 ec9bc72cd6 feat(app): capture phone replies — notification RemoteInput + inbox reply box
Phase 2c leg 1 — the app side of two-way phone messaging. The user can now
answer a proactive message; the reply rides the existing relay WS as a
`proactive.reply` envelope.

- ProactiveMessageNotifier: inline Reply action via RemoteInput + a MUTABLE
  getBroadcast PendingIntent (FLAG_MUTABLE guarded for API<31) carrying the
  message's chat_id/message_id; confirmReply() re-posts the slot to clear the
  system reply spinner (or tell the user to open the app if disconnected).
- New ProactiveReplyReceiver (BroadcastReceiver, exported=false in manifest):
  reads the typed text + extras, sends `proactive.reply` via a static
  ChannelMultiplexer slot (mirror of HermesNotificationCompanion), then
  confirms. Best-effort drop when offline.
- ProactiveInboxEntry gains chatId (back-compat default); the inbox sink +
  ProactiveMessage carry it through so a reply continues the right thread.
- HermesInboxScreen: per-card expandable reply box -> sendProactiveReply.
  Chat visuals untouched.
- ConnectionViewModel: sendProactiveReply(text, chatId, replyTo) + wire the
  receiver's static multiplexer alongside the notification companion.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 22:04:36 -04:00
Bailey DixonandClaude Opus 4.8 927ff81307 feat(plugin): PhoneAdapter inbound reply loop — replies become agent messages
Phase 2c leg 3 — wires the phone platform's INBOUND path so a reply continues
the agent conversation (was push-only; connect() was a no-op).

- connect() starts a background long-poll loop over the relay's loopback
  GET /phone/replies (mirror of the bundled adapters' receive-loop, e.g. ntfy
  _run_stream): self._running-guarded, backoff on transient errors.
- Each reply -> build_source(role_authorized=True) + MessageEvent(reply_to)
  -> handle_message(); the agent answers via the existing send(). The reply
  continues the originating thread (chat_id keys the session, reply_to anchors).
- role_authorized=True: the relay pairing/session-token layer already
  authenticated the device, so replies pass the gateway's default-deny user
  allowlist without forcing PHONE_ALLOW_ALL_USERS.
- disconnect() cancels the loop + closes the client.
- Pure gateway-independent helpers (_replies_url_and_headers, _normalize_reply)
  + path/timing constants; extend test_phone_platform.py.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 21:49:43 -04:00
Bailey DixonandClaude Opus 4.8 4d57e88e83 feat(relay): receive + buffer proactive.reply, expose /phone/replies long-poll
Phase 2c leg 2 — the relay side of two-way phone messaging. The phone can now
send its answer back; the relay buffers it for the gateway adapter to drain.

- ProactiveChannel.handle learns inbound `proactive.reply` ({text, chat_id,
  reply_to, message_id, ts}); empty-text replies dropped, ids/ts synthesized.
- Replies buffered in a bounded deque (drop-oldest) + asyncio.Event; new
  take_replies(timeout) long-poll drain. close() clears the buffer.
- New loopback-only GET /phone/replies in server.py (mirror of the outbound
  POST /phone/message hop), clamped long-poll window.
- proactive.reply added to the frozen wire-envelope docstring.
- Extend test_proactive_channel.py: buffer/drain, empty-text drop, late-reply
  wake, timeout->[], bounded drop-oldest, close clears.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 21:46:38 -04:00
Bailey DixonandClaude Opus 4.8 664a15bf30 fix(chat): drop per-bubble avatar gutter — identity stays in the top bar
The blend refresh added a 28dp assistant-avatar gutter to the left of every
assistant group, duplicating the profile avatar already in the top bar and
eating ~36dp of bubble width on a phone. Remove the gutter (and the now-unused
AssistantAvatar composable) so bubbles reclaim that width; identity is shown
once, in the top bar.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 21:30:31 -04:00
Bailey DixonandClaude Opus 4.8 3513f60b4a docs: queue phone two-way-reply + cron-deliver fix; add no-production-host guardrail
Loose ends from shipping + live-testing the phone-as-Hermes-platform feature:
- TODO: add Phase 2c (two-way reply — proactive is push-only today: no
  RemoteInput on the notification, one-way ProactiveChannel), and upgrade the
  cron/standalone line to a FIX (hermes send --to phone returns "Unknown
  platform: phone"; the kind=standalone plugin isn't discovered by the
  non-gateway send path — only the running gateway loads its register()).
- CLAUDE.md: add a "Don't touch production / remote hosts" rule — automation
  and orchestrated agents must never SSH/deploy/restart a live host; server
  deployment + on-device testing stay owner-driven.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 21:03:15 -04:00
Bailey DixonandClaude Opus 4.8 f29d8b166b Merge branch 'chat-ux-refresh' into dev
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 20:18:17 -04:00
Bailey DixonandClaude Opus 4.8 979b0aa130 Merge branch 'voice-standard-parity' into dev
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 20:15:59 -04:00
Bailey DixonandClaude Opus 4.8 71c8d8e966 Merge branch 'Codename-11/phone-platform' into dev
Advertise proactive phone messaging to the agent via the relay context seam
(PHONE_ENABLED-gated system-prompt block).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 20:03:33 -04:00
Bailey DixonandClaude Opus 4.8 d25c7c1aea feat(plugin): advertise proactive phone messaging to the agent
Add a relay-owned system-prompt context block (via the existing
RELAY_AGENT_CONTEXT_ENABLED seam) telling the agent it can reach the user
with send_message target=phone. Without this the capability worked but was
not proactively surfaced: platform_hint only injects for the inbound
platform (never, for a push-only platform) and the send_message schema's
target examples (upstream core, no-fork) don't list phone.

Gated on PHONE_ENABLED (only advertised when the platform is actually on)
plus a per-block opt-out RELAY_CONTEXT_PHONE_PLATFORM (default on); the
block is auditable/removable like media-sensitivity (GET /context/injected).

56 tests pass; existing context-injection tests unchanged (block off by
default).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 20:03:03 -04:00
Bailey DixonandClaude Opus 4.8 e22357992b Merge branch 'Codename-11/phone-platform' into dev
Phone as a first-class Hermes platform — proactive agent -> phone, via the
upstream plugin API (no fork). Plugin PhoneAdapter + register_platform;
relay ProactiveChannel + loopback /phone/message; app receive -> system
notification, dedicated Hermes inbox, and active-session injection
(per-message surfacing). Off by default behind PHONE_ENABLED + the
"Let Hermes message me" toggle + pairing.

Phase 3 (quiet hours / per-profile / rate limit / TTS-on-voice) deferred —
see TODO.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 19:25:59 -04:00
Bailey DixonandClaude Opus 4.8 579f9be96b feat(app): Hermes inbox + session injection for proactive messages
Phase 2 — the other two config-driven surfacings. The inbox is now the
always-present durable log: ProactiveMessageHandler records every received
message there, then adds the surface its `surfacing` hint selects —
notification (default), inbox-only, or session injection.

- ProactiveInboxRepository (DataStore, newest-first, deduped, capped 100)
  + HermesInboxScreen (self-contained cards, not the chat-ux MessageBubble).
- Session injection: ChatHandler.addProactiveMessage appends a SYSTEM-role
  clientOnly bubble (kept out of the voice TTS observer so it can't trigger
  uncontrolled speech; Phase 3 owns TTS-on-voice) preserved across history
  reconcile; ChatViewModel.injectProactiveMessage is the small entry point;
  the toSession sink is wired once at the RelayApp root.
- Notification tap + a "View messages" button open the inbox.

No chat visuals or voice internals touched. lint :app:lintSideloadDebug
BUILD SUCCESSFUL; no warnings in the new files.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 19:25:06 -04:00
Bailey DixonandClaude Opus 4.8 bf79c92018 docs(todo): park phone-platform Phase 2/3 + live-box verification items
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 17:11:53 -04:00
Bailey DixonandClaude Opus 4.8 a9f818d616 feat(app): "Let Hermes message me" enablement surface + permission prompt
Add the off-by-default opt-in for proactive messages: a dedicated
ProactiveSettingsScreen ("Hermes messages") with the enablement switch, a
POST_NOTIFICATIONS request on enable, a not-paired hint, and in-app docs of
the server-side PHONE_ENABLED requirement. Wired as a Settings category row
+ Screen.ProactiveSettings nav route. ConnectionViewModel.setProactiveEnabled
persists the flag; subscribe/unsubscribe is driven by the existing collector.

Completes the Phase 1 spine: send_message target=phone -> phone notification,
surfacing only when the server enables PHONE_ENABLED, the user opts in, and
the phone is paired.

Verified: ./gradlew :app:lintSideloadDebug BUILD SUCCESSFUL over the combined
1c+1d app spine; no warnings in the new proactive files.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 17:10:12 -04:00
Bailey DixonandClaude Opus 4.8 1a414db9cb feat(app): receive proactive messages + raise a system notification
Add the app-side receive path for agent-initiated messages: a "proactive"
branch in ChannelMultiplexer routes phone.message to a new
ProactiveMessageHandler (sibling of BridgeCommandHandler) that raises a
heads-up notification via ProactiveMessageNotifier (modeled on
TurnCompleteNotifier; stacks per message_id).

Receiving is gated off by default: KEY_PROACTIVE_ENABLED ("Let Hermes
message me", data/ProactivePrefs.kt) controls whether ConnectionViewModel
sends proactive.subscribe. Subscribe is re-sent on every auth.ok via a new
additive AuthManager.authOkEvents flow (sourced through _authManagerFlow so
it survives connection switches), guaranteeing it never races the auth
handshake and re-establishes the per-socket subscription after reconnects.

The Settings switch + notification-permission prompt land in Phase 1d.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 16:56:20 -04:00
Bailey DixonandClaude Opus 4.8 c402963adf feat(relay): proactive channel + /phone/message route for agent push
Add ProactiveChannel — the server->app mirror of the bridge handler. It
latches the phone WS on proactive.subscribe and pushes phone.message
envelopes via push(); best-effort, no awaited reply. Wire it onto
RelayServer (dispatch branch, disconnect detach, shutdown close) and add
a loopback-only POST /phone/message that the phone platform adapter calls.

Delivery is opt-in on both ends: the relay can only push when the app has
subscribed (user toggle), and the adapter is gated on PHONE_ENABLED.
503 when no phone subscribed, 502 on write failure.

11 channel unit tests; bridge+proactive+phone suites green together (40).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 16:45:49 -04:00
Bailey DixonandClaude Opus 4.8 0390f27477 fix(theme): apply selected font under a custom font scale (review fix)
Theme.kt's non-default font-scale branch passed the static `Typography`
constant (hardwired SansSerif) instead of the live `typography` built from
the selected font, so the font choice was silently ignored whenever the
in-app font-size slider was moved off 1.0×. Use the live `typography` in
both branches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 16:43:30 -04:00
Bailey DixonandClaude Opus 4.8 c39066808b feat(plugin): register paired phone as a Hermes platform (proactive push)
Add a push-only BasePlatformAdapter (PhoneAdapter) registered via the
upstream platform-plugin API so the agent can proactively message the
paired device: send_message target=phone and cron deliver=phone. send()
POSTs loopback to the relay (/phone/message); the relay forwards over the
existing phone WSS. Off by default behind PHONE_ENABLED; no fork.

Modeled on the bundled ntfy adapter, including a standalone_sender_fn so
out-of-process cron delivery works. Plugin stays kind=standalone;
registration wired into register() and guarded for older hosts.

22 unit tests cover gating, relay-URL precedence, payload build, and the
standalone sender over a fake httpx client.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 16:41:14 -04:00
Bailey DixonandClaude Opus 4.8 2c12770047 docs(voice): record standard-path voice parity work
CHANGELOG [Unreleased]: server voice config editor + ElevenLabs picker
(Added), capture/playback/VAD improvements (Changed), removed dead Auto-TTS /
STT-language controls (Removed). DEVLOG: full session entry incl. the Config-tab
read-only finding. TODO: on-device verification + follow-ups (generic Config
tab still read-only, default-change confirmation, profile-scope question).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:31:07 -04:00
Bailey DixonandClaude Opus 4.8 c79a7a66b5 feat(voice): align listen timing to desktop voice_mode; drop dead voice prefs
Bring the standard-path silence watchdog to parity with hermes-desktop
voice_mode defaults:
- end-of-speech default 1250 ms (was 3000) — desktop `silenceMs`
- idle/no-speech auto-close at 12 s, cancelling WITHOUT transcribing —
  desktop `idleSilenceMs` (replaces the old "wait forever")
- 60 s hard turn cap, transcribing whatever was captured
The existing 0.08 amplitude floor already matches desktop's 0.075 silenceLevel.

Also remove two dead client prefs surfaced by the parity audit: voice_auto_tts
(desktop has no read-every-typed-message feature — it only speaks responses
during an active voice conversation, which VoiceViewModel already does) and
voice_language (STT language is a server-side stt.*.language key, now editable
in the Server voice config card, not a transcribe param). Drops the fields,
keys, defaults, and setters.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:30:57 -04:00
Bailey DixonandClaude Opus 4.8 7e6de5d066 feat(voice): editable server voice config + ElevenLabs picker in Voice settings
Add a "Server voice config" card to Voice settings (standard/no-Relay path)
that loads the dashboard config schema + values, renders provider-scoped tts.*
/stt.* controls, and saves via GET -> merge -> PUT-whole — the same config.yaml
the desktop's Audio settings edit, and the same values the /api/audio/* voice
path reads. Includes the ElevenLabs voice picker (tts.elevenlabs.voice_id ->
dropdown from the server's key; graceful when available:false), the one genuine
desktop voice feature the app lacked. Writes target the launch-profile config
(profile = null) since standard voice is host-global.

The dashboard client is built per (dashboardUrl, connection) and disposed on
leave; RelayApp passes the effective dashboard URL + the VM's cached cookie
store. Also in this file: the silence-threshold slider is re-ranged to
0.75-5s/250ms steps (so the new 1.25s default lands on a stop), and the dead
"Coming soon" card (disabled Auto-TTS toggle + STT-language picker) is removed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:30:44 -04:00
Bailey DixonandClaude Opus 4.8 759c049b3e test(chat): blend chat + font-picker screenshot captures; docs
- Add host-side Roborazzi captures for the refresh: `s09_blend_chat`
  (Hermes dark + Nous-blue light) renders a grouped user/assistant thread with
  the avatar + a code block, and `s10_font_picker` frames the new Font picker to
  prove Inter/Nunito load as distinct faces.
- CHANGELOG [Unreleased]: font picker (Added) + refreshed chat look (Changed).
- DEVLOG: session entry for the refresh + verification.
- TODO: park the optional /font slash command + the on-device gate.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:22:14 -04:00
Bailey DixonandClaude Opus 4.8 9ce23e28a2 feat(chat): richer code blocks + inline-code contrast
- Rebuild the streaming code block Discord-style: a contrasting inset surface
  with a thin header (language label + a copy affordance that flips to a check),
  and a horizontally-scrollable monospace body.
- Fix code/inline-code backgrounds so they contrast against the assistant bubble
  (itself surfaceVariant) instead of blending in — the block uses the lowest
  container, inline code a subtle raised step.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:16:06 -04:00
Bailey DixonandClaude Opus 4.8 7982b2dd81 feat(chat): wider message bubbles, assistant avatar, Discord density
Refresh the chat surface toward the "Blend" look (wider bubbles + assistant
avatars + tighter rhythm):

- Assistant turns now show a small Hermes brand-mark avatar in a left gutter,
  drawn once per group (like the name label); the gutter reserves its width on
  every grouped message so bubbles stay aligned under the first. User bubbles
  stay right-aligned with no gutter.
- Raise the compact-phone bubble cap (300 -> 340dp) and trim the chat list inset
  so long turns fill more of the row instead of wrapping early.
- Tighten the bubble content padding for a denser, Discord-like vertical rhythm.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:15:38 -04:00
Bailey DixonandClaude Opus 4.8 7e5fd4d590 feat(theme): user-selectable font system with Inter default
Add an app-wide, user-selectable typeface system as a parallel axis to the
existing theme/font-scale prefs:

- Bundle Inter (default) and Nunito as OFL/SIL variable fonts in res/font,
  weight-instanced via FontVariation; commit their OFL licenses under licenses/.
- New AppFont registry (Inter / Nunito / System) -> FontFamily + label + preview.
- Parametrize Typography via appTypography(body); HermesRelayTheme rebuilds it
  from the selected AppFont so the whole app re-themes live, no restart. Code and
  metadata styles stay monospaced.
- Persist the choice in DataStore (ConnectionViewModel.appFont / setAppFont) and
  thread appFontId through the Compose theme root in RelayApp.
- Add a Font picker to Appearance settings, each option previewed in its own face.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 15:12:30 -04:00
Bailey DixonandClaude Opus 4.8 fedad55fb8 feat(voice): add dashboard config + ElevenLabs voices client primitives
Standard-path voice config was unreachable: the Manage Config tab GETs
/api/config/schema and renders it read-only via summarizeKeyValueOrList, so it
only ever showed two rows ("fields", "category_order") and never the tts.*/stt.*
values, and DashboardApiClient had no config-write path at all.

Add the client + pure helpers the voice-config editor needs:
- DashboardApiClient: getConfig(), getConfigSchema(), updateConfig(config,
  profile) (PUT /api/config, whole-tree per upstream save_config), and
  getElevenLabsVoices() (GET /api/audio/elevenlabs/voices) + ElevenLabsVoices
  models / parser.
- DashboardConfigEditing.kt: schema parsing (ConfigSchemaField + types),
  voiceConfigFields() (tts.*/stt.* by dot-path prefix), and immutable
  dot-path read/merge (configValueAt / withConfigValue / applyConfigEdits)
  enforcing the GET -> mutate -> PUT-whole invariant.

Pure-JVM + MockWebServer unit tests cover parsing, the whole-tree PUT body,
order preservation, and the no-API-key (available:false) path.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 14:53:27 -04:00
Bailey DixonandClaude Opus 4.8 d050c9e683 feat(voice): enable AEC + noise suppression on voice capture
Attach AcousticEchoCanceler and NoiseSuppressor to the AudioRecord capture
session when the device exposes them — parity with hermes-desktop's
getUserMedia({echoCancellation, noiseSuppression}). Both are best-effort:
devices that report isAvailable()=false capture raw exactly as before. AEC
keeps the device's own TTS playback from bleeding into the next captured
utterance during back-to-back voice turns. Effects are released with the
recorder.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 14:50:35 -04:00
Bailey DixonandClaude Opus 4.8 409bc4e374 fix(voice): warm audio output focus to fix cold-start silent first turn
defaultExoPlayer() built the TTS ExoPlayer with no audio attributes and no
focus handling, so the first clip of a cold standard-path voice session could
lose its opening syllables to the AudioTrack/HAL allocation window. Set
USAGE_MEDIA + CONTENT_TYPE_SPEECH attributes with handleAudioFocus=true so
focus is requested (warming the output path) before the first play(). This is
the standard-path twin of the relay PCM player's deep-buffer cold-start fix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 14:50:26 -04:00
Bailey Dixon d1680bfdc3 Merge pull request #153 from Codename-11/feature/dot-matrix-thinking-indicator
feat(chat): dot-matrix thinking indicator with patterns + colors
2026-06-28 13:46:51 -04:00
Bailey DixonandClaude Opus 4.8 fcdd0bd121 feat(chat): add dot-matrix "thinking" indicator with patterns + colors
Add a Compose-Canvas dot-matrix animation as an alternative to the
three-dot StreamingDots working indicator shown in a streaming reply
bubble — themed, and configurable from Chat settings.

- DotMatrixIndicator: a brand-themed dot grid driven by
  rememberAmbientPhase (frame-throttled ~30fps; paints a static frame
  when motion is off) rather than an always-on infinite transition.
- ThinkingMatrixPattern (Wave/Pulse/Bounce/Sparkle): Wave is a
  procedural sweep; the rest are authored frame sequences (row*cols+col
  indexing, the dot-anime-react convention) crossfaded between frames.
- ThinkingMatrixColor (Auto + brand accents) resolved against
  LocalBrand, so accents re-theme per app theme; Auto follows the
  bubble text color.
- Chat settings "Thinking indicator" selector (Dots/Matrix) with a
  Matrix-only Pattern selector + color swatch row and a live preview;
  backed by new ConnectionViewModel prefs. Default style: matrix.
- The style/pattern/color are provided via LocalThinkingIndicator at
  the chat root, so MessageBubble stays a pure presentation swap.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 13:33:47 -04:00
Bailey Dixon fd2a8b2546 Merge pull request #152 from Codename-11/dev
release: dev → main — activate dev-loop polish (github-script bump + deep-dive formatting)
2026-06-28 13:23:38 -04:00
Bailey Dixon 77badad279 Merge pull request #151 from Codename-11/fix/dev-loop-polish
fix(dev-loop): brief filter matches Claude-app comments; bump github-script; tidy deep-dive
2026-06-28 13:20:59 -04:00
Bailey DixonandClaude Opus 4.8 a00d989106 fix(dev-loop): brief filter matches Claude-app comments; bump github-script; tidy deep-dive
Follow-ups from the live triage smoke test (#150 / #146):

- start-issue.sh: the brief's "Automated triage notes" section filtered on
  author github-actions, but triage/deep-dive/follow-up comments are posted by
  the Claude GitHub App (author "claude"), so the section came up empty. Switch
  to an identity-proof match on the comment signatures, with the bot logins as
  a fallback. Verified against #150 (captures both bot notes, excludes owner
  comments).
- claude-triage.yml: bump actions/github-script@v7 → @v8 (clears the Node 20
  deprecation; v8 targets Node 24).
- claude-triage.yml: tell the deep-dive to use its headings as section
  separators and not add horizontal rules between sections — the first run
  rendered a rule under every heading, which read heavy.

The workflow tweaks activate on the next dev → main merge; the script fix is
live from dev.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 12:50:59 -04:00
Bailey Dixon 37ff218f33 Merge pull request #149 from Codename-11/dev
release: dev → main — activate Claude triage/review dev-loop (no version bump)
2026-06-28 12:07:00 -04:00
Bailey Dixon 4aa8859662 Merge pull request #148 from Codename-11/fix/update-banner-safe-calls
fix(update): drop unnecessary safe calls in update banner/checker
2026-06-28 11:40:53 -04:00
Bailey DixonandClaude Opus 4.8 cd6289e19d Merge dev into fix/update-banner-safe-calls
Resolve DEVLOG.md: keep both 2026-06-28 entries (dev-loop automation above
the safe-call cleanup).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:34:06 -04:00
Bailey Dixon fcf57abdf7 Merge pull request #147 from Codename-11/feature/claude-dev-loop
feat(ci): opinionated issue triage, deep-dive, follow-up loop + issue→worktree bridge
2026-06-28 11:32:07 -04:00
Bailey DixonandClaude Opus 4.8 c7b00c3396 docs(devlog): record the issue-triage dev-loop automation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:24:38 -04:00
Bailey DixonandClaude Opus 4.8 90dc6069f1 docs(devlog): record the update banner/checker safe-call cleanup
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:23:33 -04:00
Bailey DixonandClaude Opus 4.8 8862c31a66 fix(update): drop unnecessary safe calls in update banner/checker
Two Kotlin compiler warnings surfaced by a sideload build.

UpdateAvailableBanner: subtitle is non-null in every reachable `when`
branch, so the declaration is now String (not String?) and the
subtitle Text renders unconditionally instead of via a redundant ?.let.

UpdateChecker: OkHttp 5's Response.body is non-null, so the ?. on
resp.body was dead — and dropping it would leave an Elvis-on-non-null
warning. Replaced with resp.body.string() plus an explicit isBlank()
guard, preserving the original empty-body error path.

Behavior-preserving; resolves both `w:` warnings.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:02:14 -04:00
Bailey DixonandClaude Opus 4.8 77bf161055 feat(ci): opinionated issue triage, deep-dive, follow-up loop + issue→worktree bridge
Grow the Claude issue automation from a conservative classifier into a
surface-aware dev-loop, and make PR review more constructive.

claude-triage.yml (2 jobs → 4):
- auto-label now also applies an area:* surface label from keywords.
- triage-ai is no longer a pure classifier — it adds a hedged probable
  cause, likely files, and a suggested direction (one ≤180-word note),
  and invites the triage:deep label. Injection hardening preserved.
- deep-dive (new, opt-in via the triage:deep label) investigates the
  codebase and posts a root-cause hypothesis, a fix plan, a
  surface-specific verification plan, and a maintainer worktree
  quick-start.
- triage-followup (new) re-reads a bug thread on reporter replies and
  escalates to needs-maintainer-review + the maintainer after ~2 rounds.
  Not gated on commenter write-access, so external reporters get
  follow-up; bot-authored comments are excluded so it can't self-trigger.

claude-code-review.yml: keep the /code-review plugin depth, add a
constructive "Maintainer's-eye verdict" header and use_sticky_comment so
re-pushes update one comment instead of stacking.

scripts/start-issue.sh: local bridge — pulls an issue into a pre-briefed
git worktree (fix|feature|docs/issue-N-slug off origin/dev) with an
ISSUE-BRIEF.md carrying the body, the bot triage notes, and the surface's
verification commands.

docs/dev-loop.md documents the loop, the verification matrix, the label
setup, and the default-branch activation lag. .gitignore ignores the
generated ISSUE-BRIEF.md.

All jobs stay read-only against the repo; an auto-fix (contents: write)
path was intentionally left out as an injection risk.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:01:39 -04:00
Bailey Dixon 45e7911d3d Merge pull request #143 from Codename-11/dev
release(android): android-v1.2.6
2026-06-27 23:54:22 -04:00
Bailey DixonandClaude Opus 4.8 fa62264962 release(android): android-v1.2.6
Bump appVersionName 1.2.5 -> 1.2.6, appVersionCode 19 -> 20.
Bundles the #133 "Untitled chats" fix + profile-scoped rename + session
drawer refresh, and the connection-status overlay -> take-space banner
(plus a general top info banner). CHANGELOG/RELEASE_NOTES/whats_new/
changelog.json/Play notes refreshed; Desktop CLI items stay in
[Unreleased] for a future cli-v* release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 23:36:58 -04:00
Bailey DixonandClaude Opus 4.8 95f7c54335 feat(ui): top info/status banner instead of overlay toasts
The connection-status surface rendered as a floating overlay
(ConnectionStatusToast) that slid over content on every reconnect/
handoff/network change. Move the frequent transient/active/warning
states to the take-space ConnectionStatusBanner (slides content down,
above the header) and keep the floating overlay only for persistent
Error-tone status.

Also adds a general info banner: UiMessageBus + MessageBannerHost (thin,
auto-dismiss, coalesces duplicates, tap to expand recent), and routes
frequent snackbar confirmations (profiles updated, paired, copied,
profile/personality picks) to it instead of the bottom snackbar. Errors
stay on the snackbar.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 23:33:16 -04:00
Bailey Dixon 6fb9127d60 Merge pull request #142 from Codename-11/fix/session-untitled-and-rename-scoping
fix(sessions): stop "Untitled" clobber + profile-scope rename (#133)
2026-06-27 23:32:11 -04:00
Bailey DixonandClaude Opus 4.8 76d68622bb docs(sessions): record #133 follow-ups + client-titling drop
Document the session-title work: the upstream api_server titler PR and
the interim relay-side option, the resolved profile-scoped rename + its
audit result, and why client-side LLM titling was dropped (no
client-reachable LLM endpoint avoids persisting a session, so it would
spawn phantom title-generation rows in the drawer).

(Carries one incidental compileSdk-doc line that couldn't be hunk-split
from the #133 notes in the same file.)

Refs #133

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 22:27:54 -04:00
Bailey DixonandClaude Opus 4.8 8e89136477 docs: reconcile compileSdk 37 references across docs + gradle
The project moved to compileSdk 37 (206d182) but the docs and the
android.suppressUnsupportedCompileSdk flags still said 36. Align them:
CLAUDE.md "Compile SDK 36" → 37, docs/spec.md adds the Compile SDK line,
and gradle.properties + quest/gradle.properties suppress flags → 37.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 22:27:40 -04:00
Bailey DixonandClaude Opus 4.8 34115130da fix(sessions): stop "Untitled" clobber + profile-scope rename
Sessions read "Untitled" because ChatHandler.updateSessions copied the
server title verbatim, overwriting the optimistic first-message preview
with null whenever a re-list raced ahead of (or lacked) upstream's async
title write. The api_server SSE/runs/completions surfaces never auto-title
at all (only the gateway/cli path calls agent.title_generator).

- updateSessions: merge title (server wins when non-blank, else keep local)
- gateway-only post-turn title reconcile (+3s/+7s) via scheduleTitleReconcile
- serverAutoTitles flow + subtle "not auto-named here" drawer note on SSE
- profile-scope session rename: DashboardApiClient.renameSession +
  patchJsonObject, ConnectionViewModel.renameProfileScopedSession,
  ChatViewModel.profileSessionRenamer wired from RelayApp (write twin of
  the scoped delete; the unscoped PATCH hit the shared api_server DB)
- manual refresh icon in the session drawer header
- ChatHandlerTest: clobber-guard regression cases

Refs #133

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 22:17:53 -04:00
Bailey Dixon dbccdeba41 Merge pull request #141 from Codename-11/docs/app-access-char-limit
docs: trim Play App-access instruction to ≤500 chars
2026-06-27 19:45:58 -04:00
Bailey DixonandClaude Opus 4.8 f16e5916b9 docs: trim Play App-access instruction to ≤500 chars
Play Console caps the App-access reviewer-instructions field at 500
characters; the prior block was over. Replace it with a 423-char single
paragraph that still names the "Try the demo" entry points (first/Connect
screen + empty Chat after Skip) and the offline/no-login guarantee, and note
the cap in the lead-in.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 19:44:47 -04:00
Bailey Dixon 1ae0627d92 Merge pull request #140 from Codename-11/dev
release(android): android-v1.2.5
2026-06-27 19:08:23 -04:00
Bailey Dixon 9ffc6573df Merge pull request #139 from Codename-11/release/android-v1.2.5
release(android): android-v1.2.5
2026-06-27 18:56:27 -04:00
Bailey DixonandClaude Opus 4.8 6721701f16 release(android): android-v1.2.5
Bundles the day's Android work: the #131/#132 non-address-URL crash guard,
the offline Demo / Explore mode, and the demo-reachability + App-access polish.

- appVersionName 1.2.4 → 1.2.5, appVersionCode 18 → 19
- CHANGELOG: promote the Android items into [1.2.5]; Desktop CLI items stay
  in [Unreleased] for a future cli-v* release
- Refresh RELEASE_NOTES.md, in-app whats_new.txt + changelog.json, the Play
  what's-new, and the play-store-listing release-notes block

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 18:49:03 -04:00
Bailey Dixon 7350dc0ab8 Merge pull request #138 from Codename-11/Codename-11/demo-explore-polish
feat(app): surface Demo mode on every first-run dead-end + tighten App-access copy
2026-06-27 18:43:52 -04:00
Bailey DixonandClaude Opus 4.8 01fa7ca59a feat(app): surface Demo mode on the empty-chat dead-end + soften skip copy
Make the offline demo reachable from every first-run path, not just the
Connect surfaces, so a skipped / never-connected start (what a Play reviewer
hits) can always explore without a server.

- ChatScreen: the empty-chat "needs connection" card now offers a "Try the
  demo" action under "Connect Hermes" (new optional onTryDemo param) and reads
  warmer — "explore a quick demo first. You can connect anytime."
- RelayApp: wires the empty-chat card's onTryDemo to the existing enterDemo
  lambda (safe — that state only shows when nothing is configured).
- Onboarding "Skip setup?" dialog: reframed from "Chat and Manage won't load"
  to an inviting "explore the demo… connect anytime"; button → "Skip for now".
- docs/play-store-listing.md: tighten the App access guidance — choose
  "restricted" (the option that exposes the reviewer-instructions field), name
  the exact screens for "Try the demo", and add a paste-ready reviewer note.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 18:36:20 -04:00
Bailey Dixon 663b3eea98 Merge pull request #137 from Codename-11/Codename-11/feature-demo-mode
feat(app): offline Demo / Explore mode (Play review + first-run UX)
2026-06-27 14:27:38 -04:00
Bailey Dixon 2b72c492ae Merge remote-tracking branch 'origin/dev' into Codename-11/feature-demo-mode
# Conflicts:
#	DEVLOG.md
2026-06-27 14:19:59 -04:00
Bailey DixonandClaude Opus 4.8 e63b1be700 feat(app): add offline Demo / Explore mode for Play review + first-run UX
Google Play rejected v1.2.4 under "App access": a reviewer with no Hermes
server hit the empty Connect wall and bounced. The app is a client for a
user-run server, so there was no content — and no offline path — without a
connection.

Add an in-app Demo mode so anyone (reviewer or first-run user) can see the
app work with zero setup and zero network:

- "Try the demo" on the setup/Connect surface loads a canned, fictional
  conversation (Markdown, a tool-progress card, a rich card) through the
  REAL chat pipeline (DemoContent -> ChatHandler -> ChatViewModel -> ChatScreen),
  so there is no parallel UI.
- New pure-JVM DemoMode holder owns the active flag + transcript; entering
  does NOT complete onboarding.
- No network in demo: reconnectIfStale/revalidate/connectRelay and the API/
  relay health probes early-return while demo is active (runs in airplane
  mode); a back-nav effect clears demo on reaching a connect surface so a
  stale flag can never block the real connection.
- Persistent "Demo mode - sample data, not connected" banner whose Connect
  exits demo into the real wizard; Manage/Voice show a friendly demo empty
  state; Bridge/Terminal keep their pair-gate screens.

Verified: :app:testSideloadDebugUnitTest (new DemoContentTest/DemoModeTest)
and :app:lintSideloadDebug both green. Not built in Studio / not on-device.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 14:13:14 -04:00
Bailey Dixon ee6e84cbd1 Merge pull request #136 from Codename-11/Codename-11/fix-url-host-crash
fix(android): stop a malformed server URL from crashing Manage (#131)
2026-06-27 14:01:19 -04:00
Bailey DixonandClaude Opus 4.8 3573ba852f fix(android): stop a malformed server URL from crashing Manage (#131)
A non-URL value entered into a server-URL field could force-close the app
on the Manage / sign-in screen. The auto-captured crash (#131; dup #132) was
`IllegalArgumentException: Invalid URL host: "Manage sign-in and admin screens"`
from `okhttp3.Request$Builder.url`, inside a suspend lambda with a suppressed
`Dispatchers.Main.immediate` frame — a UI/docs label pasted into the Dashboard
URL field, normalized to `http://<spaces>` at save, then handed to okhttp's
*throwing* `url(String)` inside a `withContext(IO)` lambda whose caller sat on
Main → uncaught → crash. Same family as #124->#125 and #129->#128.

Root cause is user-entered (hypothesis a): the wizard's URL validators only
checked the scheme, never whether the value parsed as a host, and the save path
normalizes but does not validate. Hypothesis b (an internal label->host leak)
is ruled out — every DashboardApiClient/HermesApiClient is built from a URL
field, never a label.

Two layers:
- Layer 1 (UX): new `util/ServerAddress.kt` validates with the same engine the
  request builder uses (`toHttpUrlOrNull`). `apiUrlSchemeError` /
  `optionalHttpUrlError` now reject anything that won't parse, so a non-address
  shows an inline error and blocks submit.
- Layer 2 (crash guard): `DashboardApiClient` routes every request through a
  private `resolveUrl()` (`toHttpUrlOrNull`) -> `Result.failure`/`false` on a
  malformed base URL (~10 sites); `StandardHermesVoiceClient.transcribe`/
  `synthesize` get the same guard (same dashboard URL, also built before their
  try/catch). A bad value is now reported unreachable, never a Main-thread crash.

Tests: `ServerAddressTest` (pure JVM) covers the crash string, blank/whitespace/
missing-scheme/junk rejection, and bare-host/IP/localhost/host:port/http(s)
acceptance; `DashboardApiClientTest.malformedBaseUrl_returnsFailure_doesNotThrow`
asserts every verb returns `Result.failure`/`false` (no throw) for a junk base
URL. Affected `:app:testSideloadDebugUnitTest` classes green; `:app:lintSideloadDebug`
green. (Full suite has 12 unrelated pre-existing Windows DataStore-rename
failures in preferences tests.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 13:48:23 -04:00
Bailey Dixon de44059c8e Merge pull request #135 from Codename-11/dev
ci: activate issue triage on main (+ v1.2.4 devlog)
2026-06-27 12:17:23 -04:00
Bailey Dixon 50fd7bd048 Merge pull request #134 from Codename-11/feature/claude-triage
ci: automated issue triage (keyword + Claude)
2026-06-27 12:14:28 -04:00
Bailey DixonandClaude Opus 4.8 284cd9f585 ci: add automated issue triage workflow (keyword + Claude)
New `claude-triage.yml` triages issues on open, in two jobs:

- auto-label: a free, deterministic github-script labeler that maps the
  fixed issue-template title prefixes ([Bug]/[Feature]/[Docs]) to the
  bug/enhancement/documentation labels. Applied by the Actions bot, so it
  labels every issue regardless of who filed it — closing the gap where
  crash-reporter issues land unlabeled because GitHub ignores the app's
  `?labels=bug` deep-link param for non-collaborators.
- triage-ai: Claude (pinned to claude-sonnet-4-6, scoped to Bash(gh:*) +
  read-only code tools) reads the issue, checks open and closed issues for
  duplicates, ensures one correct primary label, and posts one short triage
  note. Guardrails: never closes, never @-mentions, restricted label set,
  treats the issue body as untrusted input.

Separate from claude.yml (the @claude responder, intentionally issues:read)
so the reactive responder's scope stays narrow. A workflow_dispatch trigger
with an issue_number input allows manual re-runs to backfill existing issues.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 12:02:28 -04:00
Bailey DixonandClaude Opus 4.8 e063fa694b docs(devlog): record android-v1.2.4 release
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 21:37:37 -04:00
Bailey Dixon 0327012666 release(android): android-v1.2.4 (#130)
release(android): android-v1.2.4
2026-06-25 21:36:31 -04:00
Bailey DixonandClaude Opus 4.8 2e58449aec release(android): android-v1.2.4
Crash fix (#129): currentSession() over a flaky Tailscale dashboard route
could re-throw a transient connect/abort onto the main thread and force-close
the app. Now degrades gracefully. Also ships the connection security indicator
across the chat chip, connection card, and route picker.

Android surface only (appVersionName 1.2.4, appVersionCode 18). Desktop CLI
items stay in [Unreleased] for a future cli-v* release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 21:23:56 -04:00
Bailey Dixon 41ffe0ce1c Merge pull request #127 from Codename-11/feature/connection-security-indicator
feat(android): connection security indicator (spec + implementation)
2026-06-25 08:51:38 -04:00
Bailey Dixon 81418d71b8 Merge pull request #128 from Codename-11/worktree-fix-currentsession-crash
fix(android): currentSession() must not re-throw network errors (crash)
2026-06-24 17:01:44 -04:00
Bailey DixonandClaude Opus 4.8 99b9cf1704 fix(android): currentSession() must not re-throw network errors (crash)
An on-device crash (FATAL EXCEPTION: main, SocketTimeoutException,
Caused by SocketException "Software caused connection abort") over a
Tailscale connection. Full trace recovered from a background logcat
capture pinned it to DashboardApiClient.currentSession().

Root cause: currentSession() returns Result<DashboardAuthSession> but did
a raw okHttpClient.newCall(req).execute() with NO try/catch — the lone
outlier among the client's methods (executeJson/executeJsonElement/
audioRoutesPresent all catch). The execute() ran on Dispatchers.IO
(correct), but a transient stale-pooled-connection abort re-threw out of
withContext(IO). The caller chain — ConnectionViewModel.probeStandardVoice()
-> viewModelScope.launch (Dispatchers.Main.immediate, the Suppressed frame
in the trace) — used try/finally with no catch, so the exception was
uncaught on the main thread and killed the app. (execute() being off-main
is why StrictMode never fired; the uncaught propagation was the bug.)

Fix:
- currentSession() wraps its request in try/catch -> Result.failure on any
  exception, honoring the Result contract callers rely on (mirrors
  executeJson()).
- Defense-in-depth: probeStandardVoice() gains a catch (rethrowing
  CancellationException) that degrades availability state instead of
  letting any probe sub-call crash the Main coroutine.

Test: DashboardApiClientTest.currentSession_onConnectionAbort_returnsFailure_doesNotThrow
(MockWebServer DISCONNECT_AT_START) asserts a connection abort yields
Result.failure, not a throw. :app:testSideloadDebugUnitTest green (25/25).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 16:51:51 -04:00
Bailey DixonandClaude Opus 4.8 f1e8bfd7ac feat(android): connection security indicator across all surfaces
Implements the spec in docs/plans/2026-06-24-connection-security-indicator.md
(decisions: Tailscale=green, ship all surfaces, "Encrypted · <mechanism>").

Single source of truth: data/ConnectionSecurity.kt computes a per-surface +
rollup verdict (TLS / Overlay / Mixed / Plain) from the active route's
schemes; ConnectionViewModel exposes it as a StateFlow. Overlay transports
(Tailscale/WireGuard/plugin proxy) count as encrypted, not just TLS — so a
ws:// route over a tailnet reads "Encrypted · Tailscale" (green), fixing the
old badge's hardcoded "Secure — TLS" lie.

Surfaces (all read the one flow):
- Chat status chip: leading security glyph (RelayStatusStrip slot).
- Connection card: full-width badge promoted out of the Advanced fold.
- Route picker: per-route glyph on each candidate.
- New ConnectionSecuritySheet: tap any badge for the per-transport
  breakdown + mechanism explainer + docs link.

Removed the duplicated, buried security computation from
ActiveConnectionSections (now delegates to the shared model).

Docs: new user-docs "Is my connection secure?" page; fixes the
Tailscale=TLS conflation in decisions.md / security.md / remote-access.md;
first user-facing mention of TOFU cert pinning.

Verified: ./gradlew :app:testSideloadDebugUnitTest (ConnectionSecurityTest
7/7) + :app:lintSideloadDebug both green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 11:40:19 -04:00
Bailey DixonandClaude Opus 4.8 75e617bfb1 docs(plan): connection security indicator — surfacing, wording & docs spec
Design spec for making connection security legible at a glance. Companion
to docs/plans/2026-06-18-native-secure-routes.md (which owns the routes /
plugin-proxy mechanics).

Key findings from the UI/code/docs audit:
- The security model already exists (TransportSecurityBadge tri-state,
  isEncryptedOverlayRoute, ActiveCardSecurityPosture) but is buried under
  Manage > Connections > Advanced and absent from every at-a-glance surface.
- The badge hardcodes "Secure - TLS" even for Tailscale/WireGuard routes
  (the "TLS lie") - likely why users keep asking "is it secure?".
- Security is inherently per-surface (gateway/API/dashboard/relay schemes
  are independent), so a binary verdict can't be honest - propose a
  connection rollup for the glance + per-surface truth on tap.

Spec covers: corrected mechanism-first wording (TLS / Tailscale / Mixed /
Not encrypted, with overlay = secure), placement (chat status chip, header,
route picker, new detail sheet) with mockups, the secure-proxy stub status,
a documentation plan to fix the Tailscale=TLS conflation, open decisions
for review, and tiered implementation with effort sizing.

No implementation yet - placement/wording decisions pending review.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 10:15:47 -04:00
Bailey Dixon ee0591457b Merge pull request #126 from Codename-11/dev
release(android): android-v1.2.3
2026-06-23 22:04:36 -04:00
Bailey DixonandClaude Opus 4.8 26811f0eb8 release(android): android-v1.2.3
Connection-stability hotfix. Promotes the TLS/Tailscale connect-crash fix
(#118, #124; likely #70) from [Unreleased] to [1.2.3]. appVersionName
1.2.3 / appVersionCode 17. Desktop CLI entries stay under [Unreleased] for
their own cli-v* cut.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 21:35:16 -04:00
Bailey Dixon eafdb4efe2 Merge pull request #125 from Codename-11/fix/evictall-network-on-main-thread
fix(android): close TLS sockets off the main thread on client shutdown
2026-06-23 21:31:04 -04:00
Bailey DixonandClaude Opus 4.8 802385c65c fix(android): close TLS sockets off the main thread on client shutdown
Connecting over an encrypted link (Tailscale Serve / public HTTPS) could
hard-close the app with NetworkOnMainThreadException. HermesApiClient,
DashboardApiClient and ConnectionManager all call ConnectionPool.evictAll()
inline in shutdown(); evictAll() closes pooled sockets synchronously, and a
live https/wss keep-alive close drains a TLS close-notify through
SSLOutputStream -- a real network write StrictMode forbids on the main
thread. Several call sites reach shutdown() from a viewModelScope
(Dispatchers.Main.immediate) coroutine -- probeStandardVoice()'s finally
block on every connect, and onCleared()'s connectionManager.shutdown() --
so the process was killed on connect over TLS. (Plaintext closes write
nothing, which is why every report is on Tailscale/public TLS.)

Push the guard into the leaf: a shared shutdownOffMainThread() runs the
executor-shutdown + evictAll() on a short-lived daemon thread when called
from the main thread, and inline otherwise (preserving the blocking
awaitTermination semantics for callers already on IO). Every shutdown()
call site is now safe regardless of dispatcher; the redundant
withContext(IO)/Thread wrappers in onCleared() are removed.

Adds a Robolectric NetworkShutdownTest asserting the teardown never runs on
the main thread when invoked from the main looper, and runs inline off it.

Fixes #118, #124. Likely resolves the v1.1.0/Tailscale crash in #70.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 20:58:17 -04:00
Bailey Dixon 4160cb1f85 feat(android): add notification trigger MVP 2026-06-23 08:58:48 -04:00
Bailey DixonandClaude Opus 4.8 ec05643b6b docs(devlog): record android-v1.2.2 release
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 22:58:55 -04:00
Bailey Dixon 984d9a2e63 release(android): android-v1.2.2 (#122)
release(android): android-v1.2.2
2026-06-22 22:38:07 -04:00
Bailey DixonandClaude Opus 4.8 65f22e21d9 Merge origin/dev into dev (adopt compileSdk 37, integrate typed stream events)
Catch up the local 1.2.2 work with origin/dev, which moved to compileSdk 37
(206d182) and added typed stream.event passthrough (PR #120). Dropped the
local markdown-renderer 0.41.0 / lifecycle 2.10.0 pins (a compileSdk-36
workaround) for compileSdk 37 + the 0.42.0 / 2.11.0 deps origin adopted.
Kept the 1.2.2 version bump (code 16) and all feature/fix work; both
2026-06-22 DEVLOG entries retained.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 22:22:38 -04:00
Bailey DixonandClaude Opus 4.8 36b05b637e fix(chat): refine clean-chat layout, scrolling, and history
Iterate the clean text-flow mode (refines 1dca285) to its final shape:

- Vertically-centered sphere + text group that rises toward the top third
  as the reply grows — no reserved empty "void", no gap above the composer
  (replaces the earlier fixed weight split).
- Top fade-edge applies only when the flow is actually scrolled, so a reply
  that fits shows its first line crisply instead of looking cut off.
- The flow now renders the recent CONVERSATION as one faded, scrollable
  transcript (user turns marked "›"), so scrolling up brings history into
  view; the line buffer accumulates across turns (keyed on a
  conversation-stable id) and the update loop keeps watching for new turns.
- Clean mode consumes stray pointer events in its empty areas (mirrors the
  voice overlay scrim) so taps/swipes don't fall through to the chat and
  session drawer behind it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 22:16:33 -04:00
Bailey Dixon 0dfc581117 Merge pull request #120 from Codename-11/feat/typed-stream-events
feat(relay): typed stream event passthrough
2026-06-22 20:55:05 -04:00
Bailey DixonandClaude Opus 4.8 08a4efdceb release(android): android-v1.2.2
Bump appVersionName 1.2.1 -> 1.2.2, appVersionCode 15 -> 16.

Headline: multi-profile reliability — deleting a session on a non-default
profile now sticks, and a cold start opens the session drawer on the right
profile instead of flashing the default one — plus a full-screen Diagnostics
status timeline, simpler "Hermes"/"Relay" connection wording, and a roomier
clean-chat text area.

Build fix folded in: the 2026-06-22 Dependabot wave raised the compileSdk
floor to 37 on two deps, breaking the dev build on our compileSdk 36. Pinned
markdown-renderer 0.42.0 -> 0.41.0 and lifecycle 2.11.0 -> 2.10.0 (both the
last versions that build on 36, and the 1.2.1-shipped values); guard comments
added. Do not bump past these without a compileSdk bump.

Docs: CHANGELOG [1.2.2] (Desktop-CLI entries stay under [Unreleased] for their
own cli-v* cut), RELEASE_NOTES, whats_new.txt, Play default.txt, and
changelog.json (also backfilled the missing 1.2.1 entry). Verified buildable:
:app:assembleSideloadDebug green (versionCode 16 APK).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:49:23 -04:00
Bailey Dixon 92adfafc81 fix(android): preserve typed stream event badges 2026-06-22 20:45:25 -04:00
Bailey DixonandClaude Opus 4.8 45326b377e docs: record cold-start profile-isolation fix
Note the session-drawer cold-start race fix (889273a) in TODO (batch
follow-ups + broader profile-isolation sweep), DEVLOG, and CHANGELOG
[Unreleased] Fixed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:19:50 -04:00
Bailey DixonandClaude Opus 4.8 889273aa85 fix(profiles): don't load the server-default session list before the profile resolves
On cold start the session drawer (and the restored session context) could
hydrate with the SERVER-DEFAULT profile's sessions and then visibly snap to
the persisted profile a beat later. The chat client became ready — and the
first refreshSessions() fired — before the per-connection agent-profile
list arrived to resolve the persisted selection, so the first
profile-scoped read ran with a null (server-default) profile; the list
landed a tick later, re-resolved the profile, and re-fetched correctly.

Add ProfileController.selectionSettled (true once the selection has
resolved, OR no non-default profile is pending, OR the profile list has
arrived so resolution was attempted) and gate the cold-start LaunchedEffect
on it. While a non-default profile is still resolving the first load waits
on a 2.5s backstop instead of fetching; the effect re-fires the instant the
profile resolves, cancelling the wait so only the correct, profile-scoped
load lands. The backstop keeps the drawer from ever stranding empty if the
profile list never arrives. Also defers the per-profile session-context /
transcript restore in the same effect.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:18:17 -04:00
Bailey Dixon 206d182704 chore(android): compile against api 37 2026-06-22 20:16:12 -04:00
Bailey DixonandClaude Opus 4.8 440f34080e docs: record 2026-06-22 outstanding-TODO orchestration batch
Check off the four resolved User-Added items (clean-chat viewport,
connections reframe, diagnostics/analytics, session-delete fix), add the
batch's deferred follow-ups (build+lint+device verify, diagnostics
re-probe trigger, pass-check timing), a DEVLOG entry, and CHANGELOG
[Unreleased] entries.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:07:53 -04:00
Bailey DixonandClaude Opus 4.8 6552566159 fix(sessions): persist session delete on non-default profiles
A non-default Hermes profile keeps its sessions in that profile's own
state.db, but the delete went through the unscoped api_server
DELETE /api/sessions/{id} — which hits the shared DB, leaves the row
intact, and lets the next profile-scoped list resurrect it. Route gateway
deletes through the dashboard profile-scoped surface (the write twin of
the existing list path): add DashboardApiClient.deleteSession(id, profile),
ConnectionViewModel.deleteProfileScopedSession(), a
ChatViewModel.profileSessionDeleter hook wired in RelayApp, and a
refreshSessions() after a successful delete so a still-present row can't
linger in the drawer. Off-gateway (one shared DB, no profiles) the plain
api_server delete is unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:03:46 -04:00
Bailey DixonandClaude Opus 4.8 c3098a951e feat(diagnostics): full-screen status-check timeline + analytics polish
Replace the Diagnostics modal bottom sheet with a dedicated
DiagnosticsScreen behind a new Screen.Diagnostics nav route. The screen
leads with a vertical status-check timeline (Network, API server, server
capabilities, chat transport, pairing/auth, relay, voice), each with a
green/amber/red/gray dot on a connecting rail and an inline failure
reason; checks backed by a logged error are tappable into the existing
DiagnosticDetailDialog. Checks derive read-only from existing
ConnectionViewModel flows plus the recent DiagnosticsLog (no new probing)
via a pure, testable buildStatusChecks(); the recent-activity log panel
stays below. Adds StatusCheck/CheckStatus models + a reusable
StatusCheckTimeline composable, and tidies AnalyticsScreen + StatsForNerds
visual hierarchy (no data/behavior change).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 20:02:40 -04:00
Bailey Dixon 85c70338dc feat(relay): add typed stream event passthrough 2026-06-22 19:50:30 -04:00
Bailey DixonandClaude Opus 4.8 c9fa8f722b refactor(ui): reframe "Vanilla/Standard Hermes" as "Hermes" in connections UI
Relabel the default connection path from "Vanilla Hermes" / "Standard
Hermes" to simply "Hermes", and "Hermes-Relay plugin" to "Relay plugin",
across the connections wizard, connection info/switcher sheets, voice
settings, permissions, QR scanner, and power-feature gate (28 display
strings, 10 files). Display text only — no enum names, sealed types,
when-branches, or stored route/storage values were changed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 19:48:16 -04:00
Bailey DixonandClaude Opus 4.8 1dca285cd6 feat(chat): give clean-chat mode a taller scrollable text viewport
Replace the fragile screenHeightDp*0.34f cap on the clean-mode text flow
with a weight split: the centered sphere keeps weight(1f) while the flow
takes weight(1.1f), so the readable/scrollable text area grows from ~34%
to ~52% of the vertical slack. Keeps the min=96.dp floor, internal
scroll + top-fade + a11y mirror paths, and composer/exit spacing intact;
drops the now-dead LocalConfiguration import.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 19:47:09 -04:00
Bailey DixonandClaude Opus 4.8 894b70ef62 chore: scrub private-infra identifiers from public tree
The repo is public and distributed; several files leaked real server
identifiers. Replace them with generic placeholders across docs, scripts,
source, and test fixtures:

- real LAN IP 172.16.24.250            -> 192.168.1.100 (blessed example)
- real Tailscale IP 100.71.8.56        -> 100.64.0.1
- real hostname docker-server / tail6f460 tailnet -> hermes-host(.tailnet.ts.net)
- ssh user@host targets                -> you@hermes-host
- server home path /home/bailey/       -> $HOME/
- custom voice id                      -> <your-voice-id>

Test fixtures changed on both input and assertion sides so suites stay
green (plugin.tests.test_pairing_mint_schema + test_voice_routes pass;
Kotlin URL-deriver/normalization fixtures consistent). No behavior change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 19:11:30 -04:00
Bailey DixonandClaude Opus 4.8 80ea95db1c docs(devlog): record plugin-v1.2.1 release
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 18:53:43 -04:00
Bailey DixonandClaude Opus 4.8 ed0b32e246 docs(devlog): record plugin-v1.2.1 release + live-server deploy
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 18:52:02 -04:00
Bailey Dixon 41037a3897 Merge pull request #119 from Codename-11/dev
Release plugin-v1.2.1 (dev → main)
2026-06-22 18:49:19 -04:00
Bailey Dixon 50c5fd8373 Merge branch 'main' into dev 2026-06-22 18:46:59 -04:00
Bailey DixonandClaude Opus 4.8 788d2abcb5 release(plugin): plugin-v1.2.1
Patch release for the Realtime Agent voice path:
- brokered Hermes turns no longer fail with session_not_found (broker
  mints/reuses a valid API Server session, retries once, reads the
  nested create-session response)
- realtime voice session survives long Hermes runs via heartbeat

Both fixes already merged to dev (f6b965a, d1820fb); this bumps the six
plugin version sources to 1.2.1, folds the relay fix into the [1.2.1]
CHANGELOG line, and rewrites PLUGIN_RELEASE_NOTES.md as the release body.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-22 18:41:48 -04:00
dependabot[bot] 3ec432cd8b chore(deps): bump kotlin from 2.3.21 to 2.4.0 (#114)
Bumps `kotlin` from 2.3.21 to 2.4.0.

Updates `org.jetbrains.kotlin.plugin.compose` from 2.3.21 to 2.4.0
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.3.21...v2.4.0)

Updates `org.jetbrains.kotlin.plugin.serialization` from 2.3.21 to 2.4.0
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.3.21...v2.4.0)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin.plugin.compose
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.jetbrains.kotlin.plugin.serialization
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:19:50 +00:00
dependabot[bot] ef5bae7ca5 chore(deps): bump gradle-wrapper from 9.5.1 to 9.6.0 (#113)
Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 9.5.1 to 9.6.0.
- [Release notes](https://github.com/gradle/gradle/releases)
- [Commits](https://github.com/gradle/gradle/compare/v9.5.1...v9.6.0)

---
updated-dependencies:
- dependency-name: gradle-wrapper
  dependency-version: 9.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:16:04 +00:00
dependabot[bot] 9be6422941 chore(deps): bump the networking group across 1 directory with 3 updates (#106)
Bumps the networking group with 3 updates in the / directory: [com.squareup.okhttp3:okhttp](https://github.com/square/okhttp), [com.squareup.okhttp3:okhttp-sse](https://github.com/square/okhttp) and [com.squareup.okhttp3:mockwebserver](https://github.com/square/okhttp).


Updates `com.squareup.okhttp3:okhttp` from 5.3.2 to 5.4.0
- [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md)
- [Commits](https://github.com/square/okhttp/compare/parent-5.3.2...parent-5.4.0)

Updates `com.squareup.okhttp3:okhttp-sse` from 5.3.2 to 5.4.0
- [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md)
- [Commits](https://github.com/square/okhttp/compare/parent-5.3.2...parent-5.4.0)

Updates `com.squareup.okhttp3:mockwebserver` from 5.3.2 to 5.4.0
- [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md)
- [Commits](https://github.com/square/okhttp/compare/parent-5.3.2...parent-5.4.0)

Updates `com.squareup.okhttp3:okhttp-sse` from 5.3.2 to 5.4.0
- [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md)
- [Commits](https://github.com/square/okhttp/compare/parent-5.3.2...parent-5.4.0)

Updates `com.squareup.okhttp3:mockwebserver` from 5.3.2 to 5.4.0
- [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md)
- [Commits](https://github.com/square/okhttp/compare/parent-5.3.2...parent-5.4.0)

---
updated-dependencies:
- dependency-name: com.squareup.okhttp3:mockwebserver
  dependency-version: 5.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: networking
- dependency-name: com.squareup.okhttp3:mockwebserver
  dependency-version: 5.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: networking
- dependency-name: com.squareup.okhttp3:okhttp
  dependency-version: 5.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: networking
- dependency-name: com.squareup.okhttp3:okhttp-sse
  dependency-version: 5.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: networking
- dependency-name: com.squareup.okhttp3:okhttp-sse
  dependency-version: 5.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: networking
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:15:01 +00:00
dependabot[bot] 3d0b090a64 chore(deps): bump androidx.test.ext:junit from 1.2.1 to 1.3.0 (#111)
Bumps androidx.test.ext:junit from 1.2.1 to 1.3.0.

---
updated-dependencies:
- dependency-name: androidx.test.ext:junit
  dependency-version: 1.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:13:52 +00:00
dependabot[bot] f972284dee chore(deps): bump spatialsdk from 0.12.0 to 0.13.1 (#109)
Bumps `spatialsdk` from 0.12.0 to 0.13.1.

Updates `com.meta.spatial:meta-spatial-sdk` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-compose` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-ovrmetrics` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-toolkit` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-vr` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-isdk` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-castinputforward` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-hotreload` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-datamodelinspector` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-uiset` from 0.12.0 to 0.13.1

Updates `com.meta.spatial:meta-spatial-sdk-mruk` from 0.12.0 to 0.13.1

---
updated-dependencies:
- dependency-name: com.meta.spatial:meta-spatial-sdk
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-castinputforward
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-compose
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-datamodelinspector
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-hotreload
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-isdk
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-mruk
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-ovrmetrics
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-toolkit
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-uiset
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.meta.spatial:meta-spatial-sdk-vr
  dependency-version: 0.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:12:45 +00:00
dependabot[bot] a0bb195d4d chore(deps): bump coil from 3.4.0 to 3.5.0 (#116)
Bumps `coil` from 3.4.0 to 3.5.0.

Updates `io.coil-kt.coil3:coil-compose` from 3.4.0 to 3.5.0
- [Release notes](https://github.com/coil-kt/coil/releases)
- [Changelog](https://github.com/coil-kt/coil/blob/main/CHANGELOG.md)
- [Commits](https://github.com/coil-kt/coil/compare/3.4.0...3.5.0)

Updates `io.coil-kt.coil3:coil-network-okhttp` from 3.4.0 to 3.5.0
- [Release notes](https://github.com/coil-kt/coil/releases)
- [Changelog](https://github.com/coil-kt/coil/blob/main/CHANGELOG.md)
- [Commits](https://github.com/coil-kt/coil/compare/3.4.0...3.5.0)

---
updated-dependencies:
- dependency-name: io.coil-kt.coil3:coil-compose
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: io.coil-kt.coil3:coil-network-okhttp
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:10:57 +00:00
dependabot[bot] 038a2a472b chore(deps): bump org.jetbrains.compose from 1.10.3 to 1.11.1 (#110)
Bumps [org.jetbrains.compose](https://github.com/JetBrains/compose-multiplatform) from 1.10.3 to 1.11.1.
- [Release notes](https://github.com/JetBrains/compose-multiplatform/releases)
- [Changelog](https://github.com/JetBrains/compose-multiplatform/blob/master/CHANGELOG.md)
- [Commits](https://github.com/JetBrains/compose-multiplatform/compare/v1.10.3...v1.11.1)

---
updated-dependencies:
- dependency-name: org.jetbrains.compose
  dependency-version: 1.11.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:09:30 +00:00
dependabot[bot] f8141a6a91 chore(deps): bump markdown-renderer from 0.41.0 to 0.42.0 (#117)
Bumps `markdown-renderer` from 0.41.0 to 0.42.0.

Updates `com.mikepenz:multiplatform-markdown-renderer-m3` from 0.41.0 to 0.42.0
- [Release notes](https://github.com/mikepenz/multiplatform-markdown-renderer/releases)
- [Changelog](https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/mikepenz/multiplatform-markdown-renderer/compare/v0.41.0...v0.42.0)

Updates `com.mikepenz:multiplatform-markdown-renderer-code` from 0.41.0 to 0.42.0
- [Release notes](https://github.com/mikepenz/multiplatform-markdown-renderer/releases)
- [Changelog](https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/mikepenz/multiplatform-markdown-renderer/compare/v0.41.0...v0.42.0)

---
updated-dependencies:
- dependency-name: com.mikepenz:multiplatform-markdown-renderer-code
  dependency-version: 0.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.mikepenz:multiplatform-markdown-renderer-m3
  dependency-version: 0.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:07:22 +00:00
dependabot[bot] c83f85745d chore(deps): bump org.robolectric:robolectric from 4.14.1 to 4.16.1 (#115)
Bumps [org.robolectric:robolectric](https://github.com/robolectric/robolectric) from 4.14.1 to 4.16.1.
- [Release notes](https://github.com/robolectric/robolectric/releases)
- [Commits](https://github.com/robolectric/robolectric/compare/robolectric-4.14.1...robolectric-4.16.1)

---
updated-dependencies:
- dependency-name: org.robolectric:robolectric
  dependency-version: 4.16.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:05:46 +00:00
dependabot[bot] 674d2e34a2 chore(deps): bump camera from 1.6.0 to 1.6.1 (#112)
Bumps `camera` from 1.6.0 to 1.6.1.

Updates `androidx.camera:camera-core` from 1.6.0 to 1.6.1

Updates `androidx.camera:camera-camera2` from 1.6.0 to 1.6.1

Updates `androidx.camera:camera-lifecycle` from 1.6.0 to 1.6.1

Updates `androidx.camera:camera-view` from 1.6.0 to 1.6.1

---
updated-dependencies:
- dependency-name: androidx.camera:camera-camera2
  dependency-version: 1.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: androidx.camera:camera-core
  dependency-version: 1.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: androidx.camera:camera-lifecycle
  dependency-version: 1.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: androidx.camera:camera-view
  dependency-version: 1.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 12:03:50 +00:00
dependabot[bot] 7531065bdf chore(deps): bump the lifecycle group across 1 directory with 5 updates (#104)
Bumps the lifecycle group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| androidx.lifecycle:lifecycle-runtime-ktx | `2.10.0` | `2.11.0` |
| androidx.lifecycle:lifecycle-runtime-compose | `2.10.0` | `2.11.0` |
| androidx.lifecycle:lifecycle-viewmodel-compose | `2.10.0` | `2.11.0` |
| androidx.lifecycle:lifecycle-process | `2.10.0` | `2.11.0` |
| androidx.lifecycle:lifecycle-viewmodel-ktx | `2.10.0` | `2.11.0` |



Updates `androidx.lifecycle:lifecycle-runtime-ktx` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-runtime-compose` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-viewmodel-compose` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-process` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-viewmodel-ktx` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-runtime-compose` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-viewmodel-compose` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-process` from 2.10.0 to 2.11.0

Updates `androidx.lifecycle:lifecycle-viewmodel-ktx` from 2.10.0 to 2.11.0

---
updated-dependencies:
- dependency-name: androidx.lifecycle:lifecycle-process
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-process
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-runtime-compose
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-runtime-compose
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-runtime-ktx
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-viewmodel-compose
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-viewmodel-compose
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-viewmodel-ktx
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
- dependency-name: androidx.lifecycle:lifecycle-viewmodel-ktx
  dependency-version: 2.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifecycle
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 11:58:48 +00:00
dependabot[bot] 0b922538f0 chore(deps): bump androidx.compose:compose-bom in the compose group (#103)
Bumps the compose group with 1 update: androidx.compose:compose-bom.


Updates `androidx.compose:compose-bom` from 2026.05.01 to 2026.06.00

---
updated-dependencies:
- dependency-name: androidx.compose:compose-bom
  dependency-version: 2026.06.00
  dependency-type: direct:production
  dependency-group: compose
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-06-22 11:54:36 +00:00
Bailey DixonandClaude Opus 4.8 3166139f9e docs(devlog): record android-v1.2.1 release
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 22:31:46 -04:00
Bailey Dixon 39cafc20c1 Merge pull request #102 from Codename-11/dev
release: android-v1.2.1
2026-06-21 22:28:41 -04:00
Bailey DixonandClaude Opus 4.8 8b15c6d357 release(android): android-v1.2.1
Promote CHANGELOG [Unreleased] -> [1.2.1] (Android-only; CLI + the relay
session_not_found fix stay under [Unreleased] for their own cli-v*/plugin-v*
cuts), rewrite RELEASE_NOTES.md, in-app whats_new.txt, Play release notes, and
the Play listing copy for 1.2.1. Also clarifies the per-surface CHANGELOG split
in RELEASE.md. Version source (1.2.1 / versionCode 15) was already committed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 22:27:09 -04:00
Bailey DixonandClaude Opus 4.8 c869733069 docs(desktop): document tray cockpit + computer-use grant approval
The tray is a visual cockpit over the CLI: it auto-starts the daemon on launch
(auto_start_daemon default), embeds Voice Mode + the TUI, and adds GUI surfaces
the headless CLI can't — a Grant Requests tab and pause / emergency-stop.

- index.md: "not a chat app" -> "not a full chat app" (it has a CLI-backed
  lightweight chat); document auto-start-daemon-on-launch (distinct from
  boot-persistence), Grant Requests + Voice Mode tabs, pause/emergency-stop.
- tools.md: new "Computer-use (experimental)" section covering the
  enable->observe->grant flow AND how grants are approved — interactive prompt,
  tray Grant Requests tab, and the headless HERMES_RELAY_GRANT_BRIDGE_DIR
  file-bridge (previously undocumented).
- subcommands.md: daemon tip notes the tray auto-runs the daemon (GUI
  equivalent of `daemon start`), same while-running lifetime, not boot-persist.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 22:13:54 -04:00
Bailey DixonandClaude Opus 4.8 7deb3efa88 chore(android): add Developer-options test harness for hard-to-trigger surfaces
Debug-only (FeatureFlags.isDevBuild) triggers in Developer options for the
on-device-only flows unit tests can't reach and that don't occur on demand:

- Emit sample Info/Warning/Error entries into DiagnosticsLog (exercises the
  list -> detail -> Copy/Share/Create-issue flow).
- Preview the in-app update banner via UpdateDebugOverride (Available ->
  Downloaded -> off), honoured by rememberUpdateAvailability ONLY in debug
  builds; cleared when the previewed banner is actioned/dismissed.
- Show What's New now (ConnectionViewModel.showWhatsNewNow()).
- Force a test crash to exercise the crash-report capture + dialog.

No release-build behaviour change: the section is gated by isDevBuild and the
update override is gated by BuildConfig.DEBUG.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 22:00:13 -04:00
Bailey Dixon f0e135c153 Merge: realtime-agent API Server session handoff (#101) into dev
Brokered Hermes turns from the Realtime Agent no longer fail with
session_not_found when the client session id came from another namespace,
and API Server session creation now parses the nested session.id shape.
2026-06-21 21:48:35 -04:00
Bailey DixonandClaude Opus 4.8 f6b965a97c fix(realtime): resolve API Server session handoff for brokered Hermes turns
The Realtime Agent's brokered Hermes path (hermes_run_task) could fail
two ways when reaching back to the API Server:

- a caller-supplied chat_session_id from another session namespace (the
  gateway/client session store) was passed straight to
  /api/sessions/{id}/chat/stream and rejected with 404 session_not_found
- _create_session() only read a flat id/session_id, but the current API
  Server returns the session nested under {"session": {"id": ...}}, so
  creation raised "Hermes API created a session without an id"

stream_task() now tracks whether it owns the API Server session and, on a
404 session_not_found for a caller-supplied id, mints a fresh API Server
session (emitting a session.bound handoff event) and retries the turn
once — a session it created itself, or a second failure, is not retried,
so there is no loop. Valid existing API sessions are reused untouched.
_create_session() parses both the nested and legacy flat response shapes.

Adds plugin/tests/test_hermes_tool_broker.py (13) covering both parsers
and the namespace-mismatch handoff/retry against a local aiohttp fake
API Server.

Closes #101

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 21:47:57 -04:00
Bailey DixonandClaude Opus 4.8 0aa1b38a18 feat(android): profile lock, voice fixes, diagnostics detail, in-app changelog, Play update nudge
Bumps appVersionName to 1.2.1 (versionCode 15).

Added:
- Profile lock (per-connection): pin to one profile and hide the rest; ProfileLockStore + ProfileController enforcement + Settings lock dialog with a not-found banner.
- In-app What's New / changelog from a bundled changelog.json; revisitable Settings entry sharing one renderer with the auto post-update dialog.
- Diagnostics detail view with Copy / Share / Create-GitHub-issue via a shared IssueReport helper (also adopted by the crash dialog); RelayErrorClassifier now records every classified error to DiagnosticsLog with a clean title + redacted stacktrace.
- Update-available banner: googlePlay uses Play In-App Update (FLEXIBLE; new app-update dep, flavor-scoped), sideload uses the GitHub checker; per-version dismissal + 6h throttle, never nags.

Fixed:
- Voice override now applies in Auto mode (effectiveRoute gate) and voice prefs are namespaced by connectionId.
- Realtime Stop halts playback immediately (suppress in-flight deltas); spoken-status throttle; client idle-watchdog relaxed on promoted/long runs.
- Hold-to-talk releases only on a real finger-up; voice overlay panel + bubbles opaque with non-wrapping labels; invalid engine/route combos gated.
- Connection status overlay terminal states auto-dismiss within ~5s.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 21:38:00 -04:00
Bailey DixonandClaude Opus 4.8 a22bdd9488 docs: add SECURITY.md + Code of Conduct; route issue reports to a private channel
- SECURITY.md: GitHub Private Vulnerability Reporting (preferred) + security@codename-11.dev fallback; scope, response expectations, safe harbor.
- CODE_OF_CONDUCT.md: Contributor Covenant 2.1 (conduct@codename-11.dev), adopted by reference.
- Issue config: replace the public "security guidance" link with a private "Report a vulnerability" link.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 21:37:53 -04:00
Bailey Dixon 26e4a054d2 Merge pull request #100 from Codename-11/dev
fix(ci): unblock cli-v release (tray smoke $home bug)
2026-06-21 21:18:57 -04:00
Bailey DixonandClaude Opus 4.8 9f568e12cb fix(ci): tray smoke uses $smokeHome, not read-only $home (unblocks cli-v release)
The tray smoke step in release-cli.yml assigned `$home = ...`, but $HOME is a
read-only automatic variable in PowerShell (names are case-insensitive), so it
threw "Cannot overwrite variable HOME because it is read-only or constant",
failing the tray job and skipping Publish. First cli-v* tag surfaced it — the
CLI binaries themselves built fine. Use a distinct scratch variable; the
$env:HOME / $env:USERPROFILE environment vars stay writable.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 21:17:39 -04:00
Bailey Dixon a0b4d3715c Merge pull request #99 from Codename-11/dev
release(cli): cli-v0.4.0-alpha.1
2026-06-21 21:03:24 -04:00
Bailey DixonandClaude Opus 4.8 e0a2a59957 release(cli): cli-v0.4.0-alpha.1
Bumps desktop/package.json 0.3.0-alpha.18 -> 0.4.0-alpha.1 (a new minor for the
command-surface uplift; stays in the experimental alpha track) and fills
CLI_RELEASE_NOTES.md for the GitHub Release body.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 20:59:47 -04:00
Bailey DixonandClaude Opus 4.8 738256238f feat(desktop): CLI first-class pass — audit/relay/logo, background daemon, visual layer
Brings the CLI up to the relay's v1.2.0 capabilities and gives it a consistent,
discoverable interface. New commands: `audit` (what the agent ran on this
machine, from a local log), `relay info/security/context` (inspect the relay
server and audit the system-prompt context it injects into the agent), `logo`,
and `daemon start/stop/status` for running the tool router in the background
(no console window, survives closing the terminal).

Every subcommand now answers `--help`; list output (devices/sessions) renders
as aligned tables with status dots; slow operations show a spinner; errors
suggest the fix; and pairing reports per-endpoint probe progress and warns
before a stored session expires. `voice` surfaces the enhanced-voice
(Gemini/xAI) block, and the desktop-tool consent prompt points at `audit`.

Adds a shared zero-dep lib/ (theme/table/spinner/hints/usage/logo/auditLog/
daemonStatus), an `npm run dev:install` local-binary helper, and refreshed
desktop user-docs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 20:59:42 -04:00
Bailey DixonandClaude Opus 4.8 d1820fb606 fix(relay): keep realtime voice heartbeat alive during long Hermes runs
The realtime voice agent killed a turn after ~90s of websocket silence
(client idle watchdog). The relay heartbeat stopped the moment
hermes_run_status left {running, waiting_for_confirmation}, so a long or
background Hermes run could starve it and trip the stall. The heartbeat
now continues while session.hermes_task is unfinished, and the spoken
progress repeat is raised 30s->90s and gated on a coarse status change so
tool-message churn no longer re-narrates.

Adds plugin/tests/test_realtime_heartbeat.py (11 cases).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 20:23:46 -04:00
Bailey DixonandClaude Opus 4.8 11274ce51b ci(android): add release-build smoke to catch tag-time breakage early
The android-v* release builds the release variant (bundleRelease
assembleRelease, both flavors); PR CI only built debug, so release-only
failures (R8/minify, resource shrinking, bundletool OOM) surfaced at the tag
— e.g. the v1.2.0 OOM at -Xmx2048m. Adds a debug-signed release-build smoke
(no secrets) on dev/main pushes and the dev->main release PR, so the same
build that the tag runs is exercised before tagging.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 18:22:55 -04:00
Bailey Dixon 6fb15ddc9c Merge: main (v1.2.0 release + CI fixes) back into dev 2026-06-21 18:08:20 -04:00
Bailey Dixon 15dcd6d637 fix(docs): pin search-insights for deterministic npm ci (#98)
Unblocks Deploy Docs.
2026-06-21 18:07:18 -04:00
Bailey DixonandClaude Opus 4.8 42d262bc79 fix(docs): pin search-insights so npm ci is deterministic across npm versions
The bundled docsearch declares search-insights as an OPTIONAL peer dep with
no resolved lock entry. npm 11.9 (local) treats it as satisfiable and passes;
CI's npm rejects it ("Missing: search-insights@2.17.3 from lock file").
Pinning it as a direct devDependency gives it a resolved node_modules entry,
so `npm ci` agrees on every npm version. Validated with a clean local npm ci.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 18:06:20 -04:00
Bailey Dixon b977b6b02a fix(ci): docs build on Node 24 to match lockfile (#97)
Unblocks Deploy Docs.
2026-06-21 18:02:02 -04:00
Bailey DixonandClaude Opus 4.8 d411764935 fix(ci): build docs on Node 24 (npm 11) to match the lockfile
Deploy Docs failed `npm ci` with "Missing: search-insights@2.17.3 from lock
file". user-docs/package-lock.json is generated by npm 11, which omits the
resolved entry for the optional `search-insights` peer dep of bundled
docsearch; CI's Node 20 / npm 10 demands it. Align CI to npm 11.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 18:01:26 -04:00
Bailey Dixon 73c31803e9 fix(ci): raise Gradle heap to 4g for release bundling (#96)
Unblocks the android-v1.2.0 re-cut.
2026-06-21 17:51:25 -04:00
Bailey DixonandClaude Opus 4.8 d7a15d08fe fix(ci): raise Gradle heap to 4g so release bundle packaging doesn't OOM
The android-v* release workflow builds both flavors' AABs+APKs
(bundleRelease assembleRelease); at -Xmx2048m, packageSideloadReleaseBundle
OOMed ("Java heap space") in bundletool after the googlePlay bundle. PR CI
only builds debug, so it never hit this. 4g clears it with margin and also
helps local release builds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 17:50:30 -04:00
Bailey Dixon da36172af3 Merge: main (v1.2.0 release) back into dev 2026-06-21 17:34:24 -04:00
838 changed files with 132247 additions and 30029 deletions
+4 -4
View File
@@ -1,10 +1,10 @@
blank_issues_enabled: true
contact_links:
- name: Security guidance
url: https://github.com/Codename-11/hermes-relay/blob/main/docs/security.md
about: Review the security model before posting sensitive vulnerability details publicly.
- name: Report a security vulnerability (private)
url: https://github.com/Codename-11/hermes-relay/security/advisories/new
about: Report privately via GitHub Security Advisories — do not open a public issue. See SECURITY.md for the full policy.
- name: User documentation
url: https://codename-11.github.io/hermes-relay/
url: https://hermes-relay.dev/docs/
about: Read setup, pairing, remote access, and troubleshooting docs.
- name: Contributing guide
url: https://github.com/Codename-11/hermes-relay/blob/main/CONTRIBUTING.md
+53
View File
@@ -0,0 +1,53 @@
name: Translation correction
description: Report or propose a clearer translation for one locale.
title: "[Translation]: "
labels: ["translation"]
body:
- type: markdown
attributes:
value: |
English defines the product meaning. Translation corrections are applied to the canonical locale catalog and credited through Git history.
- type: input
id: locale
attributes:
label: Language and locale
placeholder: Spanish (es), Simplified Chinese (zh-Hans), etc.
validations:
required: true
- type: input
id: location
attributes:
label: Screen and current text
description: Name the screen, resource key if known, and current translated wording.
validations:
required: true
- type: textarea
id: correction
attributes:
label: Suggested correction
description: Include the corrected text and what the English source means in this context.
validations:
required: true
- type: dropdown
id: proficiency
attributes:
label: Language familiarity
options:
- Native speaker
- Fluent speaker
- Professional translator
- Learner or machine-assisted report
- Prefer not to say
validations:
required: true
- type: checkboxes
id: sensitive
attributes:
label: Sensitive meaning
options:
- label: This affects permissions, privacy, security, destructive actions, payments, or recovery instructions.
- type: textarea
id: context
attributes:
label: Additional context
description: Optional screenshot, regional preference, or explanation of why the existing wording is misleading.
+14 -1
View File
@@ -12,10 +12,22 @@
-
## Lineage / contributor credit
<!--
If this PR salvages or supersedes earlier work, link every source PR and name
the original contributor(s). Preserve original commit authors where practical;
otherwise use verified Co-authored-by trailers. Write "N/A" for original work.
-->
- Source PR(s): N/A
- Attribution preserved by: N/A
## Checklist
- [ ] Target branch is `dev` unless this is a release PR
- [ ] Target branch is `dev`, unless this is a `dev` → `main` release PR or a focused production-tag hotfix PR to `main`
- [ ] Android changes: lint and focused unit tests ran, or rationale is listed above
- [ ] Translation changes: locale status/review references are accurate, `python scripts/check-android-locales.py` ran, and device/emulator review is documented, or N/A
- [ ] Server changes: focused `python -m unittest ...` checks ran, or rationale is listed above
- [ ] Desktop changes: `npm run build` or a narrower documented check ran, or rationale is listed above
- [ ] Docs/site changes: docs build or link check ran, or rationale is listed above
@@ -23,3 +35,4 @@
- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)
- [ ] CHANGELOG.md updated (if user-facing)
- [ ] Public writing hygiene checked: no secrets, private infrastructure, personal names, or AI/process narration
- [ ] Salvaged work links the source PR and preserves contributor authorship, or N/A
+3
View File
@@ -3,6 +3,7 @@ updates:
# Gradle dependencies
- package-ecosystem: "gradle"
directory: "/"
target-branch: "dev"
schedule:
interval: "weekly"
day: "monday"
@@ -24,10 +25,12 @@ updates:
patterns:
- "junit*"
- "androidx.compose.ui:ui-test*"
- "io.github.takahirom.roborazzi*"
# GitHub Actions
- package-ecosystem: "github-actions"
directory: "/"
target-branch: "dev"
schedule:
interval: "weekly"
labels:
+43
View File
@@ -0,0 +1,43 @@
'use strict';
function classifyCiPaths(paths) {
const forceAll = paths.some((path) => [
'.github/workflows/ci-required.yml',
'.github/scripts/classify-ci-paths.cjs',
'.github/scripts/classify-ci-paths.test.cjs',
].includes(path));
const exact = (values) => paths.some((path) => values.includes(path));
const under = (prefixes) => paths.some((path) => prefixes.some((prefix) => path.startsWith(prefix)));
return {
android: forceAll || under(['app/', 'relay-core/', 'relay-ui/', 'ui-preview/', 'quest/', 'gradle/']) || exact([
'build.gradle.kts', 'settings.gradle.kts', 'gradle.properties', 'gradlew', 'gradlew.bat',
'scripts/check-android-locales.py', 'scripts/android-locale-harness.py',
'scripts/check-android-collection-apis.py', '.github/workflows/ci-android.yml',
'.github/workflows/play-preflight-android.yml',
'.github/workflows/approve-release-android.yml',
'.github/workflows/release-android.yml',
]),
desktop: forceAll || under(['desktop/']) || exact([
'.github/workflows/ci-desktop.yml',
]),
plugin: forceAll || paths.some((path) => /^plugin\/[^/]+\.py$/.test(path)) ||
under(['plugin/relay/', 'plugin/tools/', 'plugin/tests/', 'relay_server/', 'hermes_relay_bootstrap/']) || exact([
'plugin/plugin.yaml', 'pyproject.toml', 'scripts/check-plugin-version-sync.py',
'scripts/check-server-version-sync.py', 'scripts/bump-plugin-version.sh',
'scripts/bump-server-version.sh', '.github/workflows/ci-plugin.yml',
]),
dashboard: forceAll || under(['plugin/dashboard/']) || exact([
'.github/workflows/ci-dashboard.yml',
]),
contract: forceAll ||
under(['app/src/main/kotlin/com/hermesandroid/relay/network/upstream/']) || exact([
'scripts/check-upstream-route-contract.py', '.github/workflows/ci-contract.yml',
]),
docs: forceAll || under(['user-docs/']) || exact([
'.github/workflows/docs.yml',
]),
};
}
module.exports = { classifyCiPaths };
@@ -0,0 +1,34 @@
'use strict';
const assert = require('node:assert/strict');
const { classifyCiPaths } = require('./classify-ci-paths.cjs');
const none = {
android: false,
desktop: false,
plugin: false,
dashboard: false,
contract: false,
docs: false,
};
assert.deepEqual(classifyCiPaths(['README.md']), none);
assert.deepEqual(classifyCiPaths(['desktop/src/cli.ts']), { ...none, desktop: true });
assert.deepEqual(classifyCiPaths(['relay-core/src/main/kotlin/Wire.kt']), { ...none, android: true });
assert.deepEqual(classifyCiPaths(['plugin/relay/server.py']), { ...none, plugin: true });
assert.deepEqual(classifyCiPaths(['plugin/dashboard/src/App.tsx']), { ...none, dashboard: true });
assert.deepEqual(classifyCiPaths(['user-docs/index.md']), { ...none, docs: true });
assert.deepEqual(
classifyCiPaths(['app/src/main/kotlin/com/hermesandroid/relay/network/upstream/DashboardApiClient.kt']),
{ ...none, android: true, contract: true },
);
assert.deepEqual(classifyCiPaths(['.github/workflows/ci-required.yml']), {
android: true,
desktop: true,
plugin: true,
dashboard: true,
contract: true,
docs: true,
});
console.log('CI path classification tests passed.');
@@ -0,0 +1,100 @@
# Hermes-Relay-Android — explicit public release approval
#
# Run from main only after the automated Play preflight passes and the release
# PR has merged. Starting this workflow is the release approval. Creating the
# stable tag triggers Play submission first, then GitHub publication.
name: Approve Android Release
on:
workflow_dispatch:
inputs:
version:
description: "Approved Android version (for example 1.4.3)"
required: true
type: string
permissions:
contents: write
actions: write
concurrency:
group: approve-android-release
cancel-in-progress: false
jobs:
approve:
name: Verify preflight and create release tag
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- name: Validate approval request
id: metadata
env:
REQUESTED_VERSION: ${{ inputs.version }}
run: |
if [ "$GITHUB_REF" != "refs/heads/main" ]; then
echo "::error::Approve Android Release must run from main, not $GITHUB_REF"
exit 1
fi
TOML_VERSION=$(grep -oP 'appVersionName\s*=\s*"\K[^"]+' gradle/libs.versions.toml)
if [ "$REQUESTED_VERSION" != "$TOML_VERSION" ]; then
echo "::error::Requested version $REQUESTED_VERSION does not match appVersionName $TOML_VERSION"
exit 1
fi
echo "version=$TOML_VERSION" >> "$GITHUB_OUTPUT"
echo "tree=$(git rev-parse 'HEAD^{tree}')" >> "$GITHUB_OUTPUT"
- name: Verify this exact release tree passed Play preflight
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.metadata.outputs.version }}
RELEASE_TREE: ${{ steps.metadata.outputs.tree }}
run: |
ARTIFACT_NAME="play-preflight-${VERSION}-${RELEASE_TREE}"
COUNT=$(gh api "/repos/${GITHUB_REPOSITORY}/actions/artifacts?name=${ARTIFACT_NAME}" \
--jq '[.artifacts[] | select(.expired == false)] | length')
if [ "$COUNT" -lt 1 ]; then
echo "::error::No successful Play preflight found for version $VERSION with tree $RELEASE_TREE"
exit 1
fi
echo "Verified Play preflight proof: $ARTIFACT_NAME"
- name: Ensure release tag does not already exist
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.metadata.outputs.version }}
run: |
if gh api "/repos/${GITHUB_REPOSITORY}/git/ref/tags/android-v${VERSION}" >/dev/null 2>&1; then
echo "::error::Tag android-v${VERSION} already exists"
exit 1
fi
- name: Create approved Android release tag
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.metadata.outputs.version }}
run: |
gh api --method POST "/repos/${GITHUB_REPOSITORY}/git/refs" \
-f ref="refs/tags/android-v${VERSION}" \
-f sha="$GITHUB_SHA"
- name: Start the tag release workflow
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.metadata.outputs.version }}
run: |
gh workflow run release-android.yml \
--ref=main \
-f version="$VERSION"
- name: Approval summary
run: |
echo "## Android release approved" >> "$GITHUB_STEP_SUMMARY"
echo "" >> "$GITHUB_STEP_SUMMARY"
echo "Created \`android-v${{ steps.metadata.outputs.version }}\` from main at \`$GITHUB_SHA\`." >> "$GITHUB_STEP_SUMMARY"
echo "The current release workflow was dispatched from main and will check out that immutable tag. It will submit the preflighted Play draft before creating the public GitHub Release." >> "$GITHUB_STEP_SUMMARY"
+86 -20
View File
@@ -1,42 +1,48 @@
# Hermes-Relay — Android CI Pipeline
#
# Runs on pushes to main/dev and on PRs targeting main/dev, scoped to
# Android-affecting paths so Python-only changes don't spin up the JVM.
# Runs directly on Android-affecting pushes to main/dev and is called by the
# path-aware required-check workflow for relevant pull requests.
#
# Pipeline: lint, build, and focused tests run concurrently. PRs build debug
# APKs before merge; dev pushes keep lint/tests only to avoid duplicate
# post-merge packaging. Main pushes keep APK artifacts.
#
# A release-build smoke (bundleRelease assembleRelease) runs on dev/main pushes
# and on the dev→main release PR so release-only breakage (R8/minify rules,
# resource shrinking, bundletool OOM) is caught BEFORE the android-v* tag,
# instead of mid-release. It is debug-signed, so it needs no signing secrets.
name: CI — Android
on:
workflow_call:
push:
branches: [main, dev]
paths:
- "app/**"
- "relay-core/**"
- "relay-ui/**"
- "ui-preview/**"
- "quest/**"
- "gradle/**"
- "build.gradle.kts"
- "settings.gradle.kts"
- "gradle.properties"
- "gradlew"
- "gradlew.bat"
- "scripts/check-android-locales.py"
- "scripts/android-locale-harness.py"
- "scripts/check-android-collection-apis.py"
- ".github/workflows/ci-android.yml"
pull_request:
branches: [main, dev]
paths:
- "app/**"
- "gradle/**"
- "build.gradle.kts"
- "settings.gradle.kts"
- "gradle.properties"
- "gradlew"
- "gradlew.bat"
- ".github/workflows/ci-android.yml"
- ".github/workflows/play-preflight-android.yml"
- ".github/workflows/approve-release-android.yml"
- ".github/workflows/release-android.yml"
# Cancel in-progress runs for the same branch/PR, but let main and dev finish
# Cancel superseded PR and dev runs. Never cancel main: every release-branch
# commit must finish its independent validation.
concurrency:
group: ci-android-${{ github.ref }}
cancel-in-progress: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/dev' }}
cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
jobs:
# ──────────────────────────────────────────────
@@ -48,7 +54,7 @@ jobs:
timeout-minutes: 20
steps:
- name: Checkout repository
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -61,6 +67,12 @@ jobs:
with:
cache-read-only: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/dev' }}
- name: Validate translation catalogs
run: python3 scripts/check-android-locales.py
- name: Reject unsafe Android collection APIs
run: python3 scripts/check-android-collection-apis.py
- name: Run Android lint
run: ./gradlew lint --console=plain
@@ -74,7 +86,7 @@ jobs:
timeout-minutes: 25
steps:
- name: Checkout repository
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -118,7 +130,7 @@ jobs:
continue-on-error: ${{ github.ref != 'refs/heads/main' && github.base_ref != 'main' }}
steps:
- name: Checkout repository
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -133,14 +145,27 @@ jobs:
# The broad Gradle `test` aggregate currently hangs in deferred JVM test
# suites tracked by issue #32. Keep CI release-relevant until that suite is
# split: pairing URL derivation plus connection switching are the stable
# Android regression slice for the active release work.
# split: run the stable connection slice plus focused Chat/Voice state,
# parser, layout, and accessibility regressions for the active release.
- name: Run focused Android unit tests
run: |
./gradlew :app:testSideloadDebugUnitTest \
--tests com.hermesandroid.relay.network.ArchitectureBoundaryTest \
--tests com.hermesandroid.relay.network.relay.RelayUrlDeriverTest \
--tests com.hermesandroid.relay.viewmodel.ConnectionSwitchTest \
--tests com.hermesandroid.relay.util.ServerAddressTest \
--tests com.hermesandroid.relay.util.IssueReportAndDiagnosticsTest \
--tests com.hermesandroid.relay.data.AppLanguageTest \
--tests com.hermesandroid.relay.viewmodel.ChatStreamRecoveryTest \
--tests com.hermesandroid.relay.viewmodel.ChatViewModelRealtimeTurnTest \
--tests com.hermesandroid.relay.network.relay.RealtimeVoiceEventParsingTest \
--tests com.hermesandroid.relay.voice.VoiceCommandInterpreterTest \
--tests com.hermesandroid.relay.data.VoiceModePresetTest \
--tests com.hermesandroid.relay.ui.components.BackgroundTaskCardTest \
--tests com.hermesandroid.relay.ui.components.DotMatrixIndicatorTest \
--tests com.hermesandroid.relay.ui.components.AttachmentGalleryLayoutTest \
--tests com.hermesandroid.relay.ui.components.MarkdownStreamingParserTest \
--tests com.hermesandroid.relay.ui.screens.ChatUnreadStateTest \
--console=plain
# Upload reports only for failures. Successful PR report uploads add
@@ -152,3 +177,44 @@ jobs:
name: test-reports
path: app/build/reports/tests/
retention-days: 7
# ──────────────────────────────────────────────
# Release build smoke — exercises the release variant the android-v* tag
# build runs (./gradlew bundleRelease assembleRelease, both flavors), so
# release-only breakage (R8/minify, resource shrinking, bundletool OOM) is
# caught BEFORE the tag instead of mid-release. Debug-signed — no secrets,
# so it also runs on fork PRs. Runs on dev/main pushes (early signal after
# each merge) and on the dev→main release PR (hard pre-tag gate); skipped on
# dev-targeted feature PRs to avoid re-running a ~12-min build per iteration.
# ──────────────────────────────────────────────
release-smoke:
name: Release build smoke (Android)
if: ${{ github.ref == 'refs/heads/dev' || github.ref == 'refs/heads/main' || (github.event_name == 'pull_request' && github.base_ref == 'main') }}
runs-on: ubuntu-latest
timeout-minutes: 35
steps:
- name: Checkout repository
uses: actions/checkout@v7
- name: Set up JDK 17
uses: actions/setup-java@v5
with:
distribution: temurin
java-version: 17
- name: Setup Gradle
uses: gradle/actions/setup-gradle@v6
with:
cache-read-only: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/dev' }}
# Mirrors release-android.yml's build step. No keystore is provided here,
# so app/build.gradle.kts falls back to debug signing — fine for a build
# smoke; the goal is to exercise the build, not to produce a shippable AAB.
- name: Build release bundles + APKs (both flavors, debug-signed)
run: ./gradlew bundleRelease assembleRelease --console=plain
- name: Scan release DEX for unsupported collection APIs
run: |
python3 scripts/check-android-collection-apis.py \
--apk app/build/outputs/apk/googlePlay/release/*.apk \
--apk app/build/outputs/apk/sideload/release/*.apk
+5 -10
View File
@@ -6,24 +6,19 @@
# boot, no pip install, no model keys); see scripts/check-upstream-route-contract.py
# for the design + tradeoff (catches renamed/removed routes; not runtime auth).
#
# PR/push runs check a pinned ref (non-flaky); the weekly schedule tracks
# upstream `main` as a drift siren so a route rename surfaces on our clock.
# Required-PR and direct push runs check a pinned ref (non-flaky); the weekly
# schedule tracks upstream `main` as a drift siren.
name: CI — Upstream Contract
on:
workflow_call:
push:
branches: [main, dev]
paths:
- "scripts/check-upstream-route-contract.py"
- ".github/workflows/ci-contract.yml"
- "app/src/main/kotlin/com/hermesandroid/relay/network/upstream/**"
pull_request:
branches: [main, dev]
paths:
- "scripts/check-upstream-route-contract.py"
- ".github/workflows/ci-contract.yml"
- "app/src/main/kotlin/com/hermesandroid/relay/network/upstream/**"
schedule:
- cron: "0 6 * * 1" # Mondays 06:00 UTC — upstream-drift siren (tracks main)
workflow_dispatch:
@@ -44,7 +39,7 @@ jobs:
timeout-minutes: 10
steps:
- name: Checkout hermes-relay
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Resolve upstream ref
id: ref
@@ -64,7 +59,7 @@ jobs:
echo "Checking standard-path route contract against upstream ref: $REF"
- name: Checkout vanilla upstream (no plugin, no bootstrap)
uses: actions/checkout@v6
uses: actions/checkout@v7
with:
repository: NousResearch/hermes-agent
ref: ${{ steps.ref.outputs.ref }}
+3 -7
View File
@@ -1,16 +1,12 @@
name: CI dashboard plugin
on:
workflow_call:
push:
branches: [main, dev]
paths:
- "plugin/dashboard/**"
- ".github/workflows/ci-dashboard.yml"
pull_request:
branches: [main, dev]
paths:
- "plugin/dashboard/**"
- ".github/workflows/ci-dashboard.yml"
permissions:
contents: read
@@ -25,10 +21,10 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v6
uses: actions/setup-node@v7
with:
node-version: "22"
cache: npm
@@ -0,0 +1,79 @@
# Hermes-Relay - Desktop Vanilla-Upstream Baseline
#
# Manual/scheduled confidence gate for HRUI-055. This keeps the first CI shape
# intentionally small: check out a clean upstream hermes-agent beside Relay and
# run the desktop typed-stream/renderer tests that protect the gateway event
# contract. A later expansion can boot the upstream gateway with a mock provider
# once that harness is stable enough for CI.
name: CI - Desktop Upstream Baseline
on:
workflow_dispatch:
inputs:
upstream_ref:
description: "NousResearch/hermes-agent ref to check"
required: false
default: "main"
schedule:
- cron: "30 6 * * 1"
concurrency:
group: ci-desktop-upstream-baseline-${{ github.ref }}
cancel-in-progress: true
jobs:
desktop-baseline:
name: Desktop typed gateway baseline
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- name: Checkout hermes-relay
uses: actions/checkout@v7
- name: Resolve upstream ref
id: ref
run: |
if [ -n "${{ github.event.inputs.upstream_ref }}" ]; then
REF="${{ github.event.inputs.upstream_ref }}"
else
REF="main"
fi
echo "ref=$REF" >> "$GITHUB_OUTPUT"
- name: Checkout vanilla upstream
uses: actions/checkout@v7
with:
repository: NousResearch/hermes-agent
ref: ${{ steps.ref.outputs.ref }}
path: _upstream
fetch-depth: 1
- name: Assert upstream checkout is vanilla
run: |
if [ -e "_upstream/hermes_relay_bootstrap" ] || \
[ -e "_upstream/plugin/hermes_relay_bootstrap" ] || \
find _upstream -name "hermes_relay_bootstrap.pth" 2>/dev/null | grep -q .; then
echo "FAIL: upstream checkout contains a relay bootstrap."; exit 1
fi
git -C _upstream status --short --untracked-files=no
- name: Run desktop gateway baseline contract
run: python scripts/check-desktop-upstream-baseline.py "_upstream"
- name: Set up Node
uses: actions/setup-node@v7
with:
node-version: "22"
cache: "npm"
cache-dependency-path: desktop/package-lock.json
- name: Install desktop dependencies
working-directory: desktop
run: npm ci
- name: Run desktop gateway baseline tests
working-directory: desktop
env:
HERMES_UPSTREAM_BASELINE: ${{ github.workspace }}/_upstream
run: npx tsx --test tests/gatewayTypes.test.ts tests/renderer.test.ts tests/typedStreamRenderer.test.ts
+19 -10
View File
@@ -1,15 +1,12 @@
name: CI desktop
on:
workflow_call:
push:
branches: [main, dev]
paths:
- 'desktop/**'
- '.github/workflows/ci-desktop.yml'
pull_request:
paths:
- 'desktop/**'
- '.github/workflows/ci-desktop.yml'
permissions:
contents: read
@@ -26,10 +23,10 @@ jobs:
run:
working-directory: desktop
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v6
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
@@ -38,9 +35,15 @@ jobs:
- name: Install deps
run: npm ci
- name: Verify CLI and tray versions are synchronized
run: npm run check:version-sync
- name: Type-check
run: npm run type-check
- name: Test typed stream rendering
run: npm test
- name: Build (tsc → dist/)
run: npm run build
@@ -62,10 +65,10 @@ jobs:
run:
working-directory: desktop
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v6
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
@@ -90,10 +93,10 @@ jobs:
run:
working-directory: desktop
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v4
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
@@ -105,6 +108,12 @@ jobs:
- name: Install deps
run: npm ci
- name: Check tray formatting
run: npm run tray:fmt
- name: Lint tray shell
run: npm run tray:lint
- name: Cargo check tray shell
run: npm run tray:check
+17 -30
View File
@@ -1,40 +1,18 @@
# Hermes-Relay — Plugin CI Pipeline
#
# Runs on pushes to main/dev and on PRs targeting main/dev, scoped to
# plugin-affecting paths so Android-only changes don't spin up the
# Python toolchain.
# Runs directly on plugin-affecting pushes to main/dev and is called by the
# path-aware required-check workflow for relevant pull requests.
#
# Pipeline: syntax-check and focused plugin tests run concurrently.
name: CI — Plugin
on:
workflow_call:
push:
branches: [main, dev]
paths:
- "plugin/__init__.py"
- "plugin/android_tool.py"
- "plugin/cli.py"
- "plugin/pair.py"
- "plugin/plugin.yaml"
- "plugin/relay/**"
- "plugin/tools/**"
- "plugin/tests/**"
- "relay_server/**"
- "hermes_relay_bootstrap/**"
- "pyproject.toml"
- "scripts/check-plugin-version-sync.py"
- "scripts/check-server-version-sync.py"
- "scripts/bump-plugin-version.sh"
- "scripts/bump-server-version.sh"
- ".github/workflows/ci-plugin.yml"
pull_request:
branches: [main, dev]
paths:
- "plugin/__init__.py"
- "plugin/android_tool.py"
- "plugin/cli.py"
- "plugin/pair.py"
- "plugin/*.py"
- "plugin/plugin.yaml"
- "plugin/relay/**"
- "plugin/tools/**"
@@ -63,7 +41,7 @@ jobs:
timeout-minutes: 10
steps:
- name: Checkout repository
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Set up Python 3.11
uses: actions/setup-python@v6
@@ -72,6 +50,7 @@ jobs:
- name: Syntax check (plugin relay — canonical location)
run: |
python -m py_compile plugin/relay/config.py
python -m py_compile plugin/relay/server.py
python -m py_compile plugin/relay/channels/terminal.py
python -m py_compile plugin/relay/channels/chat.py
@@ -102,7 +81,7 @@ jobs:
continue-on-error: ${{ github.ref != 'refs/heads/main' && github.base_ref != 'main' }}
steps:
- name: Checkout repository
uses: actions/checkout@v6
uses: actions/checkout@v7
- name: Set up Python 3.11
uses: actions/setup-python@v6
@@ -111,7 +90,12 @@ jobs:
- name: Install dependencies
run: |
pip install -r relay_server/requirements.txt
# Editable install pulls the full runtime dependency set from
# pyproject.toml (requests, aiohttp, segno, httpx, websocket-client,
# pyyaml). test_native_layout_imports imports the whole relay module
# chain in a clean subprocess, so the minimal relay_server/requirements
# set is not enough on its own.
pip install -e .
pip install pytest responses
- name: Run focused Plugin tests
@@ -119,4 +103,7 @@ jobs:
python -m pytest \
plugin/tests/test_relay_security.py \
plugin/tests/test_voice_routes.py \
plugin/tests/test_session_grants.py
plugin/tests/test_session_grants.py \
plugin/tests/test_native_layout_imports.py \
plugin/tests/test_profile_discovery.py \
plugin/tests/test_profiles_updated_broadcast.py
+121 -33
View File
@@ -1,49 +1,137 @@
# Required-checks sentinel — always runs on every PR + push to main/dev so
# branch protection on `main` has a check name it can rely on, regardless
# of which paths the PR touches.
# Path-aware required CI for pull requests targeting main or dev.
#
# Why this exists. The other CI workflows (`ci-android.yml`, `ci-plugin.yml`,
# `ci-desktop.yml`) are scoped via `paths:` filters so a docs-only or
# desktop-only PR doesn't spin up the Android toolchain. Branch protection's
# "required status checks" treat a check that doesn't run as failing — so
# any PR that didn't touch the protected paths was blocked from merging,
# even with all the relevant gates green. We were admin-overriding every
# desktop-only PR. Same for relay-touching PRs (the protection rule named
# `Relay Check (Python)` didn't even match any actual job — broken since
# day one).
#
# This sentinel + claude-review become the only required checks. The
# path-filtered workflows still run when relevant and surface their
# results on the PR — visible, clickable, but advisory rather than
# blocking. Reviewers (human + claude-review) eyeball them. This is the
# standard pattern for monorepos with path-filtered CI.
#
# Trade-off acknowledged: a broken Android build on an Android-touching
# PR could merge if the reviewer ignores the failing CI badge. Mitigation:
# claude-review reads CI conclusions in its review prompt + the project's
# release-merge cadence catches issues before they reach a tag. If a
# stricter gate is later wanted, fold it into this workflow as a job that
# fans out to the path-filtered work — but the simplest version (just an
# `echo`) is what's needed to make branch protection useful again today.
# The change detector selects the existing surface workflows, which are exposed
# through workflow_call. The final job keeps one stable branch-protection check
# while ensuring that every relevant build or test actually completed.
name: Required checks
on:
push:
branches: [main, dev]
pull_request:
branches: [main, dev]
types: [opened, synchronize, reopened, ready_for_review]
permissions:
contents: read
pull-requests: read
# Cancel in-progress runs for the same branch/PR. Doesn't matter much for
# a 5-second job, but matches every other workflow's concurrency shape.
concurrency:
group: ci-required-${{ github.ref }}
cancel-in-progress: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/dev' }}
cancel-in-progress: true
jobs:
changes:
name: Detect affected surfaces
runs-on: ubuntu-latest
outputs:
android: ${{ steps.filter.outputs.android }}
desktop: ${{ steps.filter.outputs.desktop }}
plugin: ${{ steps.filter.outputs.plugin }}
dashboard: ${{ steps.filter.outputs.dashboard }}
contract: ${{ steps.filter.outputs.contract }}
docs: ${{ steps.filter.outputs.docs }}
steps:
- name: Checkout repository
uses: actions/checkout@v7
with:
fetch-depth: 2
- name: Test path classifier
run: node .github/scripts/classify-ci-paths.test.cjs
- name: Classify changed files
id: filter
uses: actions/github-script@v8
with:
script: |
const { stdout } = await exec.getExecOutput(
'git',
['diff', '--name-only', 'HEAD^1', 'HEAD^2'],
);
const paths = stdout.split(/\r?\n/).filter(Boolean);
const { classifyCiPaths } = require(
`${process.env.GITHUB_WORKSPACE}/.github/scripts/classify-ci-paths.cjs`,
);
const outputs = classifyCiPaths(paths);
for (const [surface, affected] of Object.entries(outputs)) {
core.setOutput(surface, affected ? 'true' : 'false');
}
core.notice(`Changed paths: ${paths.join(', ')}`);
core.notice(`Selected checks: ${Object.entries(outputs).filter(([, value]) => value).map(([key]) => key).join(', ') || 'none'}`);
android:
needs: changes
if: needs.changes.outputs.android == 'true'
uses: ./.github/workflows/ci-android.yml
desktop:
needs: changes
if: needs.changes.outputs.desktop == 'true'
uses: ./.github/workflows/ci-desktop.yml
plugin:
needs: changes
if: needs.changes.outputs.plugin == 'true'
uses: ./.github/workflows/ci-plugin.yml
dashboard:
needs: changes
if: needs.changes.outputs.dashboard == 'true'
uses: ./.github/workflows/ci-dashboard.yml
contract:
needs: changes
if: needs.changes.outputs.contract == 'true'
uses: ./.github/workflows/ci-contract.yml
docs:
name: Build public docs
needs: changes
if: needs.changes.outputs.docs == 'true'
runs-on: ubuntu-latest
defaults:
run:
working-directory: user-docs
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- uses: actions/setup-node@v7
with:
node-version: 24
cache: npm
cache-dependency-path: user-docs/package-lock.json
- run: npm ci
- run: npm run build
guard:
name: Required checks
if: always()
needs: [changes, android, desktop, plugin, dashboard, contract, docs]
runs-on: ubuntu-latest
env:
CHANGES_RESULT: ${{ needs.changes.result }}
ANDROID_RESULT: ${{ needs.android.result }}
DESKTOP_RESULT: ${{ needs.desktop.result }}
PLUGIN_RESULT: ${{ needs.plugin.result }}
DASHBOARD_RESULT: ${{ needs.dashboard.result }}
CONTRACT_RESULT: ${{ needs.contract.result }}
DOCS_RESULT: ${{ needs.docs.result }}
steps:
- name: OK
run: echo "Required-checks sentinel — see ci-required.yml header for context."
- name: Require every selected check to pass
shell: bash
run: |
failed=0
for check in CHANGES ANDROID DESKTOP PLUGIN DASHBOARD CONTRACT DOCS; do
result_var="${check}_RESULT"
result="${!result_var}"
echo "$check: $result"
case "$result" in
success|skipped) ;;
*) failed=1 ;;
esac
done
exit "$failed"
+39
View File
@@ -0,0 +1,39 @@
name: Website CI
on:
pull_request:
paths:
- "website/**"
- "assets/screenshots/02_chat.png"
- "assets/screenshots/03_voice.png"
- "assets/screenshots/06_manage.png"
- "docs/media/screenshots.json"
- ".github/workflows/ci-website.yml"
push:
branches: [main, dev]
paths:
- "website/**"
- "assets/screenshots/02_chat.png"
- "assets/screenshots/03_voice.png"
- "assets/screenshots/06_manage.png"
- "docs/media/screenshots.json"
- ".github/workflows/ci-website.yml"
permissions:
contents: read
jobs:
build:
runs-on: ubuntu-latest
defaults:
run:
working-directory: website
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
cache: npm
cache-dependency-path: website/package-lock.json
- run: npm ci
- run: npm run build
-90
View File
@@ -1,90 +0,0 @@
name: Claude Code Review
on:
pull_request:
types: [opened, synchronize, ready_for_review, reopened]
# Optional: Only run on specific file changes
# paths:
# - "src/**/*.ts"
# - "src/**/*.tsx"
# - "src/**/*.js"
# - "src/**/*.jsx"
jobs:
claude-review:
# Optional: Filter by PR author
# if: |
# github.event.pull_request.user.login == 'external-contributor' ||
# github.event.pull_request.user.login == 'new-developer' ||
# github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
runs-on: ubuntu-latest
timeout-minutes: 20
permissions:
contents: read
pull-requests: read
issues: read
id-token: write
env:
# Any dev -> main PR is, by the branching model, the aggregate release PR
# (main only ever receives release merges from dev). Detect it by base+head
# alone — a title-format match (e.g. "release:") is fragile and silently
# let a "Release v1.0.0 …"-titled PR run the full review and time out.
IS_RELEASE_PR: ${{ github.event.pull_request.base.ref == 'main' && github.event.pull_request.head.ref == 'dev' }}
# Bot-authored PRs such as Dependabot do not receive the same secret
# surface as human-authored PRs, and Claude Code rejects bot actors unless
# explicitly allow-listed. Keep the required check green with a no-op and
# rely on the dependency CI/status checks for those PRs.
IS_BOT_PR: ${{ github.event.pull_request.user.type == 'Bot' }}
steps:
- name: Skip aggregate release PR review
if: env.IS_RELEASE_PR == 'true'
run: |
echo "Skipping Claude Code Review for aggregate dev -> main release PR."
echo "Feature work is reviewed before it lands on dev; release PRs are gated by CI and release metadata checks."
- name: Skip bot-authored PR review
if: env.IS_BOT_PR == 'true'
run: |
echo "Skipping Claude Code Review for bot-authored PR."
echo "Bot PRs are gated by Required checks plus their path-specific CI jobs."
- name: Checkout repository
if: env.IS_RELEASE_PR != 'true' && env.IS_BOT_PR != 'true'
uses: actions/checkout@v4
with:
# Depth 2 includes the pull_request merge commit's first parent, which
# lets the next step detect whether this PR changes the workflow file.
fetch-depth: 2
- name: Detect Claude review workflow changes
if: env.IS_RELEASE_PR != 'true' && env.IS_BOT_PR != 'true'
id: changed-workflow
shell: bash
run: |
if git rev-parse --verify HEAD^1 >/dev/null 2>&1 &&
git diff --name-only HEAD^1 HEAD | grep -Fxq ".github/workflows/claude-code-review.yml"; then
echo "claude_review_workflow=true" >> "$GITHUB_OUTPUT"
else
echo "claude_review_workflow=false" >> "$GITHUB_OUTPUT"
fi
- name: Skip Claude review workflow self-change
if: env.IS_RELEASE_PR != 'true' && env.IS_BOT_PR != 'true' && steps.changed-workflow.outputs.claude_review_workflow == 'true'
run: |
echo "Skipping Claude Code Review because this PR changes the review workflow itself."
echo "The Claude action requires this workflow file to match the default branch before it can exchange the app token."
- name: Run Claude Code Review
if: env.IS_RELEASE_PR != 'true' && env.IS_BOT_PR != 'true' && steps.changed-workflow.outputs.claude_review_workflow != 'true'
timeout-minutes: 15
id: claude-review
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'
plugins: 'code-review@claude-code-plugins'
prompt: '/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}'
# See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
# or https://code.claude.com/docs/en/cli-reference for available options
-50
View File
@@ -1,50 +0,0 @@
name: Claude Code
on:
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
issues:
types: [opened, assigned]
pull_request_review:
types: [submitted]
jobs:
claude:
if: |
(github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
(github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: read
issues: read
id-token: write
actions: read # Required for Claude to read CI results on PRs
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 1
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
# This is an optional setting that allows Claude to read CI results on PRs
additional_permissions: |
actions: read
# Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
# prompt: 'Update the pull request description to include a summary of changes.'
# Optional: Add claude_args to customize behavior and configuration
# See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
# or https://code.claude.com/docs/en/cli-reference for available options
# claude_args: '--allowed-tools Bash(gh pr *)'
+1 -1
View File
@@ -13,7 +13,7 @@ jobs:
steps:
- name: Fetch Dependabot metadata
id: metadata
uses: dependabot/fetch-metadata@v2
uses: dependabot/fetch-metadata@v3
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
-71
View File
@@ -1,71 +0,0 @@
# Hermes-Relay — Docs Deployment
#
# Builds VitePress docs and deploys to GitHub Pages.
# Triggers on pushes to main that change user-docs/ content,
# or manually via workflow_dispatch.
name: Deploy Docs
on:
push:
branches: [main]
paths:
- 'user-docs/**'
- '.github/workflows/docs.yml'
workflow_dispatch:
# Allow only one concurrent deployment
concurrency:
group: pages
cancel-in-progress: false
# Sets permissions for GITHUB_TOKEN to enable Pages deployment
permissions:
contents: read
pages: write
id-token: write
jobs:
build:
name: Build Docs
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v6
with:
fetch-depth: 0 # Full history for lastUpdated timestamps
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: 20
cache: npm
cache-dependency-path: user-docs/package-lock.json
- name: Install dependencies
run: npm ci
working-directory: user-docs
- name: Build VitePress site
run: npm run build
working-directory: user-docs
- name: Setup Pages
uses: actions/configure-pages@v6
- name: Upload artifact
uses: actions/upload-pages-artifact@v5
with:
path: user-docs/.vitepress/dist
deploy:
name: Deploy to GitHub Pages
needs: build
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5
+65
View File
@@ -0,0 +1,65 @@
name: Issue Triage
on:
issues:
types: [opened]
workflow_dispatch:
inputs:
issue_number:
description: "Issue number to label again"
required: true
type: string
concurrency:
group: issue-triage-${{ github.event.issue.number || github.event.inputs.issue_number }}
cancel-in-progress: false
permissions:
contents: read
issues: write
jobs:
auto-label:
if: >
github.event_name == 'workflow_dispatch' ||
(github.event_name == 'issues' && github.event.issue.user.type != 'Bot')
runs-on: ubuntu-latest
steps:
- name: Label from title prefix and issue area
uses: actions/github-script@v8
env:
ISSUE_NUMBER: ${{ github.event.issue.number || github.event.inputs.issue_number }}
with:
script: |
const issue_number = Number(process.env.ISSUE_NUMBER);
const { data: issue } = await github.rest.issues.get({
owner: context.repo.owner, repo: context.repo.repo, issue_number,
});
const title = (issue.title || '').toLowerCase();
const body = (issue.body || '').toLowerCase();
const haystack = `${title}\n${body}`;
const labels = [];
if (title.startsWith('[bug]')) labels.push('bug');
else if (title.startsWith('[feature]') || title.startsWith('[feat]')) labels.push('enhancement');
else if (title.startsWith('[docs]')) labels.push('documentation');
if (/\b(cli|desktop|terminal|daemon|pty|hermes-relay (install|binary|tray))\b/.test(haystack)) labels.push('area:cli');
else if (/\b(dashboard|plugin ui|react)\b/.test(haystack)) labels.push('area:dashboard');
else if (/\b(relay|plugin|aiohttp|python|pairing|voice (transcribe|synthesize)|bridge (endpoint|route))\b/.test(haystack)) labels.push('area:plugin');
else if (/\b(readme|user-?docs|documentation)\b/.test(haystack)) labels.push('area:docs');
else if (/\b(android|app|compose|apk|phone|samsung|gradle|chat|voice|notification|sphere|keystore)\b/.test(haystack)) labels.push('area:android');
if (!labels.length) {
core.info('No deterministic label matched; leaving the issue for maintainer triage.');
return;
}
try {
await github.rest.issues.addLabels({
owner: context.repo.owner, repo: context.repo.repo, issue_number, labels,
});
core.info(`Applied labels: ${labels.join(', ')}`);
} catch (error) {
core.warning(`Could not apply ${labels.join(', ')}: ${error.message}`);
}
@@ -0,0 +1,89 @@
name: Deploy legacy docs redirects
on:
pull_request:
paths:
- "legacy-pages-redirect/**"
- "website/public/privacy.html"
- ".github/workflows/legacy-docs-redirect.yml"
push:
branches: [main]
paths:
- "legacy-pages-redirect/**"
- "website/public/privacy.html"
- ".github/workflows/legacy-docs-redirect.yml"
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: legacy-docs-pages
cancel-in-progress: true
jobs:
build:
name: Build redirect artifact
runs-on: ubuntu-latest
steps:
- name: Check out repository
uses: actions/checkout@v6
- name: Build redirect-only site
shell: bash
run: |
set -euo pipefail
source_file="legacy-pages-redirect/redirect.html"
privacy_file="website/public/privacy.html"
output_dir="legacy-pages-redirect/_site"
rm -rf "$output_dir"
mkdir -p \
"$output_dir/guide/getting-started" \
"$output_dir/privacy" \
"$output_dir/reference/relay-server" \
"$output_dir/architecture"
for target in \
index.html \
404.html \
guide/getting-started.html \
guide/getting-started/index.html \
reference/relay-server.html \
reference/relay-server/index.html \
architecture/connection-security.html; do
cp "$source_file" "$output_dir/$target"
done
cp "$privacy_file" "$output_dir/privacy.html"
cp "$privacy_file" "$output_dir/privacy/index.html"
touch "$output_dir/.nojekyll"
test "$(find "$output_dir" -type f | wc -l)" -eq 10
grep -Fq '<h1>Privacy Policy</h1>' "$output_dir/privacy.html"
grep -Fq 'https://hermes-relay.dev/privacy.html' "$output_dir/privacy.html"
if grep -R -E '<title>VitePress|<div id="app">' "$output_dir"; then
echo "Full documentation content must not be deployed by this workflow." >&2
exit 1
fi
- name: Configure Pages
if: github.event_name != 'pull_request'
uses: actions/configure-pages@v6
- name: Upload redirect artifact
if: github.event_name != 'pull_request'
uses: actions/upload-pages-artifact@v5
with:
path: legacy-pages-redirect/_site
deploy:
name: Deploy redirect shim
if: github.event_name != 'pull_request'
needs: build
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5
+4 -4
View File
@@ -7,7 +7,7 @@ on:
- "assets/play-store-icon-512.png"
- "assets/play-store-feature-1024x500.png"
- "docs/media/screenshots.json"
- "app/src/googlePlay/play/default-language.txt"
- "app/src/googlePlay/play/*.txt"
- "app/src/googlePlay/play/listings/**"
- "scripts/screenshots.py"
- ".github/workflows/play-listing.yml"
@@ -20,7 +20,7 @@ on:
- "assets/play-store-icon-512.png"
- "assets/play-store-feature-1024x500.png"
- "docs/media/screenshots.json"
- "app/src/googlePlay/play/default-language.txt"
- "app/src/googlePlay/play/*.txt"
- "app/src/googlePlay/play/listings/**"
- "scripts/screenshots.py"
- ".github/workflows/play-listing.yml"
@@ -41,7 +41,7 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
- name: Set up Python
uses: actions/setup-python@v6
@@ -67,7 +67,7 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -0,0 +1,155 @@
# Hermes-Relay-Android — private Google Play preflight
#
# Run manually from the final dev or untagged main tree before creating
# android-v*. The job
# builds the same signed release artifacts, scans final DEX, and uploads the
# Google Play bundle as a production DRAFT. A successful upload is the automated
# Play gate while no public GitHub Release or sideload APK exists. Console-only
# pre-review and pre-launch reports are informational and do not block release.
name: Play Preflight — Android
on:
workflow_dispatch:
inputs:
version:
description: "Android version to preflight (for example 1.4.3)"
required: true
type: string
permissions:
contents: read
concurrency:
group: play-preflight-android
cancel-in-progress: false
jobs:
preflight:
name: Build and upload private Play draft
runs-on: ubuntu-latest
timeout-minutes: 40
steps:
- uses: actions/checkout@v7
- name: Require final release branch and matching version
id: metadata
env:
REQUESTED_VERSION: ${{ inputs.version }}
run: |
if [ "$GITHUB_REF" != "refs/heads/dev" ] && [ "$GITHUB_REF" != "refs/heads/main" ]; then
echo "::error::Run Play preflight from dev or untagged main, not $GITHUB_REF"
exit 1
fi
TOML_VERSION=$(grep -oP 'appVersionName\s*=\s*"\K[^"]+' gradle/libs.versions.toml)
VERSION_CODE=$(grep -oP 'appVersionCode\s*=\s*"\K[^"]+' gradle/libs.versions.toml)
if [ "$REQUESTED_VERSION" != "$TOML_VERSION" ]; then
echo "::error::Requested version $REQUESTED_VERSION does not match appVersionName $TOML_VERSION"
exit 1
fi
echo "version=$TOML_VERSION" >> "$GITHUB_OUTPUT"
echo "version_code=$VERSION_CODE" >> "$GITHUB_OUTPUT"
echo "tree=$(git rev-parse 'HEAD^{tree}')" >> "$GITHUB_OUTPUT"
- name: Require Play and release-signing secrets
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
HERMES_KEYSTORE_BASE64: ${{ secrets.HERMES_KEYSTORE_BASE64 }}
run: |
if [ -z "$PLAY_SERVICE_ACCOUNT_JSON" ]; then
echo "::error::PLAY_SERVICE_ACCOUNT_JSON is required for Play preflight"
exit 1
fi
if [ -z "$HERMES_KEYSTORE_BASE64" ]; then
echo "::error::HERMES_KEYSTORE_BASE64 is required for Play preflight"
exit 1
fi
- name: Set up JDK 17
uses: actions/setup-java@v5
with:
distribution: temurin
java-version: 17
- name: Setup Gradle
uses: gradle/actions/setup-gradle@v6
with:
cache-read-only: false
- name: Validate release metadata and source compatibility
run: |
python3 scripts/check-version-tracks.py
python3 scripts/check-privacy-policy.py --live
python3 scripts/check-android-locales.py
python3 scripts/check-android-collection-apis.py
python3 -m json.tool app/src/main/assets/changelog.json >/dev/null
- name: Decode release keystore
env:
HERMES_KEYSTORE_BASE64: ${{ secrets.HERMES_KEYSTORE_BASE64 }}
run: |
echo "$HERMES_KEYSTORE_BASE64" | base64 -d > "$RUNNER_TEMP/release.keystore"
echo "HERMES_KEYSTORE_PATH=$RUNNER_TEMP/release.keystore" >> "$GITHUB_ENV"
- name: Build final release artifacts
env:
HERMES_KEYSTORE_PASSWORD: ${{ secrets.HERMES_KEYSTORE_PASSWORD }}
HERMES_KEY_ALIAS: ${{ secrets.HERMES_KEY_ALIAS }}
HERMES_KEY_PASSWORD: ${{ secrets.HERMES_KEY_PASSWORD }}
run: ./gradlew bundleRelease assembleRelease --console=plain
- name: Scan final release DEX
run: |
python3 scripts/check-android-collection-apis.py \
--apk app/build/outputs/apk/googlePlay/release/*.apk \
--apk app/build/outputs/apk/sideload/release/*.apk
- name: Upload private production draft to Play
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
HERMES_KEYSTORE_PASSWORD: ${{ secrets.HERMES_KEYSTORE_PASSWORD }}
HERMES_KEY_ALIAS: ${{ secrets.HERMES_KEY_ALIAS }}
HERMES_KEY_PASSWORD: ${{ secrets.HERMES_KEY_PASSWORD }}
run: |
trap 'rm -f play-service-account.json' EXIT
printf '%s' "$PLAY_SERVICE_ACCOUNT_JSON" > play-service-account.json
./gradlew publishGooglePlayReleaseBundle \
--track=production \
--release-status=draft \
--resolution-strategy=ignore \
--release-name="Hermes-Relay ${{ steps.metadata.outputs.version }}"
- name: Record successful preflight for the exact commit
run: |
mkdir -p app/build/reports
cat > app/build/reports/play-preflight.json <<EOF
{
"version": "${{ steps.metadata.outputs.version }}",
"versionCode": "${{ steps.metadata.outputs.version_code }}",
"commit": "$GITHUB_SHA",
"tree": "${{ steps.metadata.outputs.tree }}",
"track": "production",
"status": "draft"
}
EOF
- name: Upload preflight proof
uses: actions/upload-artifact@v7
with:
name: play-preflight-${{ steps.metadata.outputs.version }}-${{ steps.metadata.outputs.tree }}
path: app/build/reports/play-preflight.json
if-no-files-found: error
retention-days: 30
- name: Preflight summary
run: |
echo "## Play preflight ready" >> "$GITHUB_STEP_SUMMARY"
echo "" >> "$GITHUB_STEP_SUMMARY"
echo "- Version: **${{ steps.metadata.outputs.version }}** (code ${{ steps.metadata.outputs.version_code }})" >> "$GITHUB_STEP_SUMMARY"
echo "- Commit: \`$GITHUB_SHA\`" >> "$GITHUB_STEP_SUMMARY"
echo "- Release tree: \`${{ steps.metadata.outputs.tree }}\`" >> "$GITHUB_STEP_SUMMARY"
echo "- Play track/status: **Production draft**" >> "$GITHUB_STEP_SUMMARY"
echo "" >> "$GITHUB_STEP_SUMMARY"
echo "The signed build, DEX scan, and Play draft upload passed. Ensure this exact release tree is on main, then run **Approve Android Release** from main. Console-only reports are informational and non-blocking." >> "$GITHUB_STEP_SUMMARY"
+120 -48
View File
@@ -3,7 +3,7 @@
# Triggered when an Android release tag (android-v*) is pushed.
# Validates the tag matches the app version in libs.versions.toml,
# runs focused Android checks, builds release APK/AAB artifacts, and creates a
# GitHub Release. Plugin/Python package releases use plugin-v* tags.
# GitHub Release. Server/Python package releases use server-v* tags.
name: Release Android
@@ -11,9 +11,20 @@ on:
push:
tags:
- "android-v*"
# Approve Android Release creates its tag with GITHUB_TOKEN, whose tag event
# does not recursively start workflows. It dispatches the current workflow
# definition from main, while every job checks out the immutable tag. Manual
# tag pushes continue to use the push trigger.
workflow_dispatch:
inputs:
version:
description: "Approved Android version"
required: true
type: string
permissions:
contents: write
actions: read
id-token: write
jobs:
@@ -22,12 +33,31 @@ jobs:
runs-on: ubuntu-latest
outputs:
version: ${{ steps.version.outputs.version }}
version_code: ${{ steps.version.outputs.version_code }}
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
with:
fetch-depth: 0
ref: ${{ github.event_name == 'workflow_dispatch' && format('android-v{0}', inputs.version) || github.ref }}
- name: Extract version from tag
id: version
run: echo "version=${GITHUB_REF#refs/tags/android-v}" >> $GITHUB_OUTPUT
env:
DISPATCHED_VERSION: ${{ inputs.version }}
run: |
if [ -n "$DISPATCHED_VERSION" ]; then
REF_VERSION="$DISPATCHED_VERSION"
TAG_COMMIT=$(git rev-list -n 1 "android-v${REF_VERSION}")
if [ -z "$TAG_COMMIT" ] || [ "$TAG_COMMIT" != "$(git rev-parse HEAD)" ]; then
echo "::error::Checked-out commit does not match immutable tag android-v${REF_VERSION}"
exit 1
fi
else
REF_VERSION="${GITHUB_REF#refs/tags/android-v}"
fi
VERSION_CODE=$(grep -oP 'appVersionCode\s*=\s*"\K[^"]+' gradle/libs.versions.toml)
echo "version=$REF_VERSION" >> "$GITHUB_OUTPUT"
echo "version_code=$VERSION_CODE" >> "$GITHUB_OUTPUT"
- name: Verify version sync
run: |
@@ -41,16 +71,52 @@ jobs:
echo "::error::Tag version ($TAG_VERSION) does not match appVersionName ($TOML_VERSION) in gradle/libs.versions.toml"
exit 1
fi
if ! grep -Eq "^## \\[(Android )?${TAG_VERSION}\\]" CHANGELOG.md; then
echo "::error::CHANGELOG.md has no Android release heading for $TAG_VERSION"
exit 1
fi
echo "Version validated: $TAG_VERSION"
- name: Verify public privacy policy URLs
run: python3 scripts/check-privacy-policy.py --live
- name: Verify tagged commit belongs to main
run: |
set -euo pipefail
git fetch origin main --no-tags
tag_commit="$(git rev-parse HEAD)"
if ! git merge-base --is-ancestor "$tag_commit" origin/main; then
echo "Android releases must be tagged from main; $tag_commit is not in origin/main" >&2
exit 1
fi
- name: Require successful Play preflight for this exact release tree
if: ${{ !contains(steps.version.outputs.version, '-') }}
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.version.outputs.version }}
run: |
RELEASE_TREE=$(git rev-parse 'HEAD^{tree}')
ARTIFACT_NAME="play-preflight-${VERSION}-${RELEASE_TREE}"
COUNT=$(gh api "/repos/${GITHUB_REPOSITORY}/actions/artifacts?name=${ARTIFACT_NAME}" \
--jq '[.artifacts[] | select(.expired == false)] | length')
if [ "$COUNT" -lt 1 ]; then
echo "::error::No successful Play preflight found for version $VERSION with tree $RELEASE_TREE"
echo "Run Play Preflight from the final dev tree, merge that unchanged tree to main, then approve the release."
exit 1
fi
echo "Play preflight proof found: $ARTIFACT_NAME"
ci:
name: CI Checks
needs: validate
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
with:
ref: ${{ github.event_name == 'workflow_dispatch' && format('android-v{0}', inputs.version) || github.ref }}
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -63,6 +129,13 @@ jobs:
with:
cache-read-only: false
- name: Validate release metadata and Android API compatibility
run: |
python3 scripts/check-version-tracks.py
python3 scripts/check-privacy-policy.py
python3 scripts/check-android-locales.py
python3 scripts/check-android-collection-apis.py
# Keep the tag release gate aligned with CI — Android's broad Gradle
# `test` aggregate currently hangs in deferred JVM suites tracked by
# issue #32, so the release gate runs the stable connection/pairing slice.
@@ -79,7 +152,9 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
with:
ref: ${{ github.event_name == 'workflow_dispatch' && format('android-v{0}', inputs.version) || github.ref }}
- name: Set up JDK 17
uses: actions/setup-java@v5
@@ -116,6 +191,12 @@ jobs:
# app/build/outputs/bundle/sideloadRelease/hermes-relay-<version>-sideload-release.aab
run: ./gradlew bundleRelease assembleRelease
- name: Scan release DEX for unsupported collection APIs
run: |
python3 scripts/check-android-collection-apis.py \
--apk app/build/outputs/apk/googlePlay/release/*.apk \
--apk app/build/outputs/apk/sideload/release/*.apk
- name: List produced artifacts (debug aid)
run: |
echo "=== APK outputs ==="
@@ -127,12 +208,40 @@ jobs:
# Flavor dimension adds an extra path segment to the AGP output layout.
# APKs live under `apk/<flavor>/release/`, AABs under `bundle/<flavor>Release/`
# (note the concatenated camelCase — AGP path quirk, documented but
# different between APK and AAB). The globs below match both flavors.
# different between APK and AAB). Checksums cover EXACTLY the files
# attached to the GitHub Release (see the 2-asset policy on the
# release step below) so SHA256SUMS.txt matches the assets 1:1.
run: |
cd app/build/outputs
sha256sum apk/*/release/*.apk bundle/*Release/*.aab > SHA256SUMS.txt
sha256sum apk/sideload/release/*.apk bundle/googlePlayRelease/*.aab > SHA256SUMS.txt
cat SHA256SUMS.txt
- name: Require Play credentials for stable release
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
if: ${{ !contains(needs.validate.outputs.version, '-') }}
run: |
if [ -z "$PLAY_SERVICE_ACCOUNT_JSON" ]; then
echo "::error::PLAY_SERVICE_ACCOUNT_JSON is required for stable Android releases"
exit 1
fi
- name: Submit preflighted Play draft to production review
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
if: ${{ !contains(needs.validate.outputs.version, '-') }}
run: |
trap 'rm -f play-service-account.json' EXIT
printf '%s' "$PLAY_SERVICE_ACCOUNT_JSON" > play-service-account.json
./gradlew promoteGooglePlayReleaseArtifact \
--update=production \
--version-code=${{ needs.validate.outputs.version_code }} \
--release-status=completed \
--release-name="Hermes-Relay ${{ needs.validate.outputs.version }}"
# Public distribution happens only after Play accepts the production
# submission above. This keeps a Play-detected release blocker from
# appearing after the sideload APK is already public.
- name: Create GitHub Release
uses: softprops/action-gh-release@v3
with:
@@ -140,50 +249,13 @@ jobs:
tag_name: android-v${{ needs.validate.outputs.version }}
body_path: RELEASE_NOTES.md
prerelease: ${{ contains(needs.validate.outputs.version, '-') }}
# Attach all four flavored artifacts — users sideload the
# `hermes-relay-<version>-sideload-release.apk` for the full
# Phase 3 / Tier 3/4/6 feature set; the
# `hermes-relay-<version>-googlePlay-release.aab` is what gets
# uploaded to Play Console. APK twin of the googlePlay flavor
# and AAB twin of the sideload flavor are included for parity
# (useful for diff tooling, not primary downloads).
# Deliberate 2-asset policy (#144): attach ONLY the installable
# sideload APK and Play AAB, plus checksums covering those files.
files: |
app/build/outputs/apk/*/release/*.apk
app/build/outputs/bundle/*Release/*.aab
app/build/outputs/apk/sideload/release/*.apk
app/build/outputs/bundle/googlePlayRelease/*.aab
app/build/outputs/SHA256SUMS.txt
- name: Upload to Play Console (production draft)
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
HERMES_KEYSTORE_PASSWORD: ${{ secrets.HERMES_KEYSTORE_PASSWORD }}
HERMES_KEY_ALIAS: ${{ secrets.HERMES_KEY_ALIAS }}
HERMES_KEY_PASSWORD: ${{ secrets.HERMES_KEY_PASSWORD }}
# Runs only when the Play service-account secret is configured AND this is
# a stable tag (prereleases — versions containing a dash — are skipped so
# an `-rc.N` build never lands on the production listing). HERMES_KEYSTORE_PATH
# was exported into $GITHUB_ENV by the "Decode release keystore" step above
# and persists across steps in this job, so the AAB is release-signed.
#
# `publishGooglePlayReleaseBundle` is the flavor-scoped task — only the
# googlePlay AAB is uploaded (sideload is disabled via playConfigs in
# app/build.gradle.kts). The play{} block pins releaseStatus = DRAFT, so the
# build lands on the Production track as a DRAFT: CI does the upload, a human
# clicks "Start rollout" in Play Console. A bad tag can never auto-go-live.
if: ${{ env.PLAY_SERVICE_ACCOUNT_JSON != '' && !contains(needs.validate.outputs.version, '-') }}
run: |
printf '%s' "$PLAY_SERVICE_ACCOUNT_JSON" > play-service-account.json
./gradlew publishGooglePlayReleaseBundle --track=production
rm -f play-service-account.json
- name: Play upload skipped (no secret)
env:
PLAY_SERVICE_ACCOUNT_JSON: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
if: ${{ env.PLAY_SERVICE_ACCOUNT_JSON == '' }}
run: |
echo "ℹ️ PLAY_SERVICE_ACCOUNT_JSON not set — skipped Play Console upload." \
"GitHub Release artifacts are still published; upload to Play manually" \
"(see RELEASE.md §5)." >> "$GITHUB_STEP_SUMMARY"
- name: Release summary
env:
HERMES_KEYSTORE_BASE64: ${{ secrets.HERMES_KEYSTORE_BASE64 }}
+94 -31
View File
@@ -1,24 +1,77 @@
name: Release CLI
name: Release Desktop
on:
push:
tags: ['cli-v*']
tags: ['desktop-v*']
permissions:
contents: write
jobs:
build-cli-binaries:
name: Build cross-platform CLI binaries via Bun compile
validate-release:
name: Validate tag, branch, and version metadata
runs-on: ubuntu-latest
defaults:
run:
working-directory: desktop
outputs:
version: ${{ steps.version.outputs.version }}
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
with:
fetch-depth: 0
- name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
cache-dependency-path: desktop/package-lock.json
- name: Install deps
run: npm ci
- name: Extract and validate tag version
id: version
shell: bash
run: |
set -euo pipefail
version="${GITHUB_REF_NAME#desktop-v}"
if [[ -z "$version" || "$version" == "$GITHUB_REF_NAME" ]]; then
echo "Expected a desktop-v* tag, got $GITHUB_REF_NAME" >&2
exit 1
fi
echo "version=$version" >> "$GITHUB_OUTPUT"
npm run check:version-sync -- --expect "$version"
if ! grep -Fq "## [$version]" ../CHANGELOG.md; then
echo "CHANGELOG.md has no release heading for $version" >&2
exit 1
fi
- name: Verify tagged commit belongs to main
shell: bash
working-directory: .
run: |
set -euo pipefail
git fetch origin main --no-tags
tag_commit="$(git rev-parse "${GITHUB_REF_NAME}^{commit}")"
if ! git merge-base --is-ancestor "$tag_commit" origin/main; then
echo "Desktop releases must be tagged from main; $tag_commit is not in origin/main" >&2
exit 1
fi
build-cli-binaries:
name: Build cross-platform CLI binaries via Bun compile
runs-on: ubuntu-latest
needs: validate-release
defaults:
run:
working-directory: desktop
steps:
- uses: actions/checkout@v7
- name: Setup Node.js (for npm ci + tsc)
uses: actions/setup-node@v6
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
@@ -35,6 +88,9 @@ jobs:
- name: Type-check
run: npm run type-check
- name: Test CLI
run: npm test
- name: Build dist/ (tsc)
run: npm run build
@@ -100,14 +156,15 @@ jobs:
build-windows-tray-installer:
name: Build Windows tray installer
runs-on: windows-latest
needs: validate-release
defaults:
run:
working-directory: desktop
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v4
uses: actions/setup-node@v7
with:
node-version: '22'
cache: npm
@@ -130,38 +187,44 @@ jobs:
- name: Build dist/ (tsc)
run: npm run build
- name: Check and lint tray shell
run: npm run tray:fmt && npm run tray:lint
- name: Test tray shell
run: npm run tray:test
- name: Install NSIS
run: choco install nsis --yes --no-progress
- name: Build tray installer
run: npm run tray:build
- name: Normalize installer asset name
shell: pwsh
run: |
New-Item -ItemType Directory -Force -Path dist/tray | Out-Null
$installer = Get-ChildItem -Path tray/src-tauri/target/release/bundle/nsis -Filter '*_x64-setup.exe' | Select-Object -First 1
if (-not $installer) { throw 'NSIS installer was not produced' }
Copy-Item -Force $installer.FullName dist/tray/hermes-relay-desktop-windows-x64-setup.exe
- name: Smoke-test tray exe launch
shell: pwsh
run: |
$home = Join-Path $env:RUNNER_TEMP 'hermes-tray-smoke-home'
New-Item -ItemType Directory -Force -Path $home | Out-Null
$env:USERPROFILE = $home
$env:HOME = $home
$proc = Start-Process -FilePath tray/src-tauri/target/release/hermes-relay-desktop.exe -WindowStyle Hidden -PassThru
# $HOME is a read-only automatic variable in PowerShell (names are
# case-insensitive), so use a distinct scratch name; only the
# $env:HOME / $env:USERPROFILE environment vars are writable.
$smokeHome = Join-Path $env:RUNNER_TEMP 'hermes-tray-smoke-home'
New-Item -ItemType Directory -Force -Path $smokeHome | Out-Null
$env:USERPROFILE = $smokeHome
$env:HOME = $smokeHome
$env:HERMES_RELAY_CLI_PATH = (Resolve-Path dist/bin/hermes-relay-win-x64.exe).Path
$proc = Start-Process -FilePath tray/target/release/hermes-relay-tray.exe -WindowStyle Hidden -PassThru
Start-Sleep -Seconds 5
if ($proc.HasExited) { throw "tray app exited early with code $($proc.ExitCode)" }
$proc.Refresh()
if ($proc.MainWindowHandle -ne 0) { throw 'menu-only systray created an application window' }
$traySize = (Get-Item tray/target/release/hermes-relay-tray.exe).Length
if ($traySize -gt 5242880) { throw "tray executable exceeds 5 MiB: $traySize bytes" }
Stop-Process -Id $proc.Id -Force
Write-Host "tray launch smoke OK pid=$($proc.Id)"
Write-Host "menu-only tray launch smoke OK pid=$($proc.Id) bytes=$traySize"
- name: Upload Windows tray release asset
uses: actions/upload-artifact@v4
with:
name: cli-windows-tray-installer
path: desktop/dist/tray/hermes-relay-desktop-windows-x64-setup.exe
name: cli-windows-installer
path: desktop/dist/tray/hermes-relay-windows-x64-setup.exe
retention-days: 7
publish-release:
@@ -173,13 +236,13 @@ jobs:
steps:
# Needed so CLI_RELEASE_NOTES.md is available to render into the release body
# (the other publish-release steps only consume downloaded build artifacts).
- uses: actions/checkout@v4
- uses: actions/checkout@v7
- name: Extract CLI version
- name: Extract Desktop version
id: version
run: echo "version=${GITHUB_REF_NAME#cli-v}" >> "$GITHUB_OUTPUT"
run: echo "version=${GITHUB_REF_NAME#desktop-v}" >> "$GITHUB_OUTPUT"
- uses: actions/download-artifact@v4
- uses: actions/download-artifact@v8
with:
path: release-assets
@@ -194,7 +257,7 @@ jobs:
# Render CLI_RELEASE_NOTES.md (hand-written per release) into the GitHub
# Release body. __VERSION__ = bare version (0.3.0), __TAG__ = full tag
# (cli-v0.3.0) so the install/pin commands stay accurate without manual edits.
# (desktop-v0.3.0) so install/pin commands stay accurate without manual edits.
- name: Render release notes
env:
VERSION: ${{ steps.version.outputs.version }}
@@ -207,7 +270,7 @@ jobs:
- name: Publish GitHub Release
uses: softprops/action-gh-release@v3
with:
name: Hermes-Relay-CLI v${{ steps.version.outputs.version }}
name: Hermes-Relay-Desktop v${{ steps.version.outputs.version }}
tag_name: ${{ github.ref_name }}
draft: false
prerelease: ${{ contains(steps.version.outputs.version, 'alpha') || contains(steps.version.outputs.version, 'beta') || contains(steps.version.outputs.version, 'rc') }}
@@ -218,5 +281,5 @@ jobs:
release-assets/cli-binaries/hermes-relay-linux-x64
release-assets/cli-binaries/hermes-relay-darwin-x64
release-assets/cli-binaries/hermes-relay-darwin-arm64
release-assets/cli-windows-tray-installer/hermes-relay-desktop-windows-x64-setup.exe
release-assets/cli-windows-installer/hermes-relay-windows-x64-setup.exe
release-assets/SHA256SUMS.txt
+28 -11
View File
@@ -1,39 +1,56 @@
name: Release Plugin
name: Release Server
on:
push:
tags:
- "plugin-v*"
- "server-v*"
permissions:
contents: write
jobs:
validate:
name: Validate Plugin release
name: Validate Server release
runs-on: ubuntu-latest
timeout-minutes: 5
outputs:
version: ${{ steps.version.outputs.version }}
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
with:
fetch-depth: 0
- name: Extract version from tag
id: version
run: echo "version=${GITHUB_REF#refs/tags/plugin-v}" >> "$GITHUB_OUTPUT"
run: echo "version=${GITHUB_REF#refs/tags/server-v}" >> "$GITHUB_OUTPUT"
- name: Verify Plugin version sync
run: python scripts/check-plugin-version-sync.py --expect "$TAG_VERSION"
- name: Verify Server version sync and changelog
run: |
python scripts/check-plugin-version-sync.py --expect "$TAG_VERSION"
if ! grep -Fq "## [$TAG_VERSION]" CHANGELOG.md; then
echo "::error::CHANGELOG.md has no release heading for $TAG_VERSION"
exit 1
fi
env:
TAG_VERSION: ${{ steps.version.outputs.version }}
- name: Verify tagged commit belongs to main
run: |
set -euo pipefail
git fetch origin main --no-tags
tag_commit="$(git rev-parse HEAD)"
if ! git merge-base --is-ancestor "$tag_commit" origin/main; then
echo "Server releases must be tagged from main; $tag_commit is not in origin/main" >&2
exit 1
fi
test:
name: Test Plugin package
needs: validate
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
- name: Set up Python 3.11
uses: actions/setup-python@v6
@@ -68,7 +85,7 @@ jobs:
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: actions/checkout@v7
- name: Set up Python 3.11
uses: actions/setup-python@v6
@@ -100,8 +117,8 @@ jobs:
- name: Publish GitHub Release
uses: softprops/action-gh-release@v3
with:
name: Hermes-Relay-Plugin v${{ needs.validate.outputs.version }}
tag_name: plugin-v${{ needs.validate.outputs.version }}
name: Hermes-Relay-Server v${{ needs.validate.outputs.version }}
tag_name: server-v${{ needs.validate.outputs.version }}
prerelease: ${{ contains(needs.validate.outputs.version, '-') }}
fail_on_unmatched_files: true
body_path: release_notes_rendered.md
+6 -1
View File
@@ -77,6 +77,9 @@ hermes-agent-fork/
.claude/
.claude-launcher/
# Per-issue dev-loop brief generated by scripts/start-issue.sh into each worktree
ISSUE-BRIEF.md
# Kotlin compiler cache
.kotlin/
@@ -88,5 +91,7 @@ keystore.properties
.smoke-relay.pid
.smoke-relay.log
# Generated tray frontend vendor assets copied from desktop/node_modules
# Legacy generated desktop tray assets may remain after upgrading a worktree.
desktop/tray/ui/vendor/
# Generated from assets/screenshots/02_chat.png before docs dev/build.
/user-docs/public/chat-demo.png
+46 -10
View File
@@ -5,26 +5,49 @@ coding agent (Claude Code, Codex, Cursor, etc.).
## Read this first
The detailed, authoritative context lives in **[CLAUDE.md](CLAUDE.md)** —
architecture, the upstream Hermes API reference, repository layout, per-language
code style, the dev loop, and the Key Files map. Read it before touching code,
then `docs/spec.md` and `docs/decisions.md`.
This file is the provider-neutral canonical agent context. Read it before
touching code, then `docs/spec.md` and `docs/decisions.md`. Provider adapters
such as **[CLAUDE.md](CLAUDE.md)** may add tool-specific guidance, but they do
not redefine the branch, release, or hotfix policy here and in `RELEASE.md`.
- Release process → **[RELEASE.md](RELEASE.md)**
- Contributor setup → **[CONTRIBUTING.md](CONTRIBUTING.md)**
- `android_*` toolset + MCP → **[docs/mcp-tooling.md](docs/mcp-tooling.md)**
- Follow-ups / deferred work / known gaps → **[TODO.md](TODO.md)** (the single home for "what's next" — never DEVLOG, never scattered code comments)
## Branch contract
| Contract item | Canonical source or target |
|---|---|
| Integration branch | `dev`; normal feature, fix, docs, and chore PRs target `dev` |
| Release branch | `main`; release history and hotfix integration only |
| Tag source | The new `main` tip after an approved `dev` → `main` release PR, or after an approved hotfix PR to `main` |
| Staging source | An exact tested `dev` SHA or release-candidate tag; staging is an environment, never a branch |
| Production source | Immutable `android-v*`, `server-v*`, or `desktop-v*` tags, selected by surface |
| Hotfix base | The immutable production tag for the affected surface |
| Back-merge target | `dev`; merge `main` back immediately after every hotfix |
Feature completion means merged and verified on `dev`; it does not mean
released. A release train is separate work owned by a Forge release
issue/session: reconcile only the affected surface version and notes on `dev`,
open the `dev` → `main` release PR, tag the resulting `main` tip, publish the
surface artifacts, deploy or roll out, and verify the live result. Never create
a staging branch.
## Non-negotiables (the short list)
- **Vanilla Hermes path = upstream-only.** The default (no-plugin) connection —
chat via the API server, Vanilla Hermes voice via the Hermes dashboard — must work
against unmodified upstream hermes-agent. Server-side needs go through upstream
PRs or the optional relay plugin, never fork patches.
- **Vanilla Hermes path = upstream-only.** The standard (no-plugin) connection
uses the upstream Dashboard/Gateway for chat, authentication, Manage, sessions,
and Vanilla Hermes voice. The API server is an optional automatic fallback and
advanced headless-compatibility surface; Relay adds optional extensions. This
path must work against unmodified upstream hermes-agent. Server-side needs go
through upstream PRs or the optional relay plugin, never fork patches.
- **Verify endpoints against upstream** (`gateway/platforms/api_server.py` /
`tui_gateway/server.py` in hermes-agent) before assuming a route exists.
- **Conventional Commits + `main`/`dev` branching.** Feature branches off `dev`,
`--no-ff` merges, version bumps at release-prep on `dev`, tags cut from `main`.
- **Conventional Commits + `main`/`dev` branching.** Normal branches start at
`dev` and PR back to `dev`; merge commits/no-ff are the repository policy.
Version bumps happen only during release preparation on `dev`, and production
tags are cut only from `main`.
- **Android:** Jetpack Compose only (no XML), kotlinx.serialization (no Gson),
OkHttp (no Ktor), `wss://` only. Run `./gradlew lint` before pushing Kotlin.
- **Plugin (Python 3.11+):** aiohttp + asyncio (no threading), type hints
@@ -32,6 +55,19 @@ then `docs/spec.md` and `docs/decisions.md`.
zero runtime deps, strict TS + ES modules, ship compiled `dist/`. Full
per-language style and the dev loop live in CLAUDE.md → "Code Style".
## Review guidelines
- Report only actionable correctness, security, compatibility, or release-risk
findings; avoid stylistic preferences unless they violate a documented rule.
- Treat the vanilla Hermes upstream boundary as release-critical. Flag any
default-path dependency on relay-only or fork-only server behavior.
- Check that changes preserve public-repo writing hygiene and do not expose
secrets, private infrastructure, or personal information.
- Use the affected surface's CI result as evidence, but do not imply Android UI
or device behavior was proven without an explicit on-device verification.
- Prioritize findings that warrant holding the merge. State the impacted path
and the concrete failure mode.
## Public-repo writing hygiene
Everything committed is public. In CHANGELOG, DEVLOG, README, docs, and release
+390 -3
View File
@@ -6,6 +6,388 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
## [Unreleased]
### Fixed
- **Windows-trusted certificates work in the desktop CLI.** The packaged Windows binary and newer Node runtimes add the Windows certificate store without dropping bundled or operator-supplied roots, while TLS verification and Relay certificate pinning remain enforced.
## [Android 1.5.2] - 2026-07-28
### Fixed
- **Dashboard sign-in completes across supported providers and network routes.** Self-hosted OIDC stays on the dashboard cookie flow, while Nous Portal opens in the system browser and completes standards-compatible PKCE through HTTPS, private-LAN, or Tailscale dashboard routes.
- **Replayed chat updates no longer destabilize the conversation list.** Duplicate upstream message identifiers are coalesced before Compose renders them.
## [Android 1.5.1] - 2026-07-26
### Added
- **Voice supports focused and conversational layouts.** Focus keeps spoken turns, Markdown, tools, media, and actions in a compact voice surface, while Conversation opens the full Chat renderer without leaving the active voice session.
- **Voice can speak only settled answers.** A global Voice setting keeps tool progress, service updates, and intermediate commentary visual while supported voice paths wait to speak the final Hermes answer.
### Changed
- **Chat answers are easier to read in every theme.** Primary assistant text now uses the theme's full-contrast foreground, and chat prose uses a 15sp size with 21sp line height.
- **Google Play builds target Android 16.** The app now targets API level 36 while retaining its existing minimum-device support.
### Fixed
- **Completed streamed answers render their formatting without losing the reading position.** Markdown headings, lists, emphasis, and code blocks replace the live text renderer only after completion, then the measured trailing edge remains anchored at the bottom.
- **Standard Voice speaks completed assistant replies again.** Session and message fences no longer suppress a valid final answer during the handoff from generation to narration.
- **Realtime background work no longer blocks the active voice controls.** A promoted task releases the foreground spinner and microphone while its progress, tools, cancellation, and final result remain available in the owning chat.
## [Server 1.4.3] - 2026-07-22
### Added
- **Relay diagnostics describe upstream Gateway compatibility.** Doctor and `/relay/info` report optional Gateway health, configuration-route, and capability signals so clients can distinguish an older upstream install from a Relay failure.
### Fixed
- **Relay trust boundaries are enforced across privileged interfaces.** Pairing policy is host-authorized, Android bridge and terminal dispatch require active grants, ordinary sessions can only reduce their own policy, remote profile config is restricted to a public schema, and voice callers cannot redirect host provider credentials.
- **Plugin bootstrap work no longer blocks the Gateway event loop.** Database initialization and compatibility-state inspection run off the async request path while preserving older upstream bootstrap behavior.
- **Starting Relay no longer terminates a running Hermes gateway on Windows.** Profile discovery now checks gateway PIDs through non-signalling process APIs, including during periodic rescans.
## [Android 1.5.0] - 2026-07-25
### Added
- **Voice settings are organized around Standard and Realtime paths.** Provider, model, and voice choices use a cleaner card layout with upstream-aware discovery, useful descriptions, inline previews, waveform feedback, loading skeletons, and an expandable scrolling voice browser.
- **Standard Hermes speech streams while replies are generated.** Android plays completed speech segments as they arrive, interrupts prior playback before starting another preview or reply, and stops audio when leaving voice mode.
- **Manage and diagnostics expose more upstream Gateway controls.** Android consumes health hints, follows canonical redirects, compresses larger RPC payloads, scopes diagnostics by profile, and surfaces compatibility information without requiring Relay-only behavior.
- **Chat shows richer upstream state and media.** One-turn model selection, approval policies, advisor progress, queued-recovery and project labels, collapsible attachments, persisted images, interim Gateway events, and a theme-aware image-generation animation make active work easier to follow.
- **The Agent Passport makes the active agent controllable.** The chat drawer now combines live connection and session context with profile switching, personality, model, reasoning, approval, and speed controls in one focused surface.
- **Android onboarding finishes with a permission setup step.** After connecting, users can enable background chat alerts with one deliberate Android prompt, review optional feature permissions individually, or continue immediately without granting phone access.
- **Image generation stays visible when upstream tool progress is hidden.** A paired Relay can expose read-only image-tool activity from Hermes session state so Android shows and completes its existing generation animation during Standard Gateway turns; native Gateway lifecycle events remain authoritative and Relay remains optional.
- **Background work stays actionable.** User-started turns remain protected until every active session settles, while privacy-safe notifications reopen the correct conversation for approvals, questions, elevated permissions, and secure responses.
### Fixed
- **Voice settings and active-turn correction remain usable across supported languages.** New voice controls are localized and correction copy accurately describes the turn being replaced.
- **Chat reconnects preserve the running Gateway turn without duplicating it.** Android reactivates the original live session after a socket loss, avoids resubmitting a prompt when its acknowledgement was lost, and de-duplicates session rows before they reach the drawer.
- **Relay pairing preserves Tailscale and other fallback routes.** Adding Relay to an existing Standard connection now keeps every signed QR route, restores older per-device endpoints hidden by the connection upgrade, and gives remote Dashboard routes their API fallback. When a host-scoped Dashboard sign-in is still required, Chat shows the route-specific sign-in action instead of loading indefinitely.
- **Remote routes move every Hermes surface together.** Android uses `GET /health` instead of misclassifying the API server's `405 Method Not Allowed` response to `HEAD`, and the selected Tailscale route now carries Dashboard/Gateway, sessions, Manage, and Standard Voice with API and Relay instead of leaving them pinned to the saved LAN host. Manage also distinguishes host-side Nous provider authentication from Dashboard sign-in.
- **Hosted Manage and direct-chat compatibility stay bounded and secure.** OAuth state remains tied to the selected dashboard, inline image memory is capped, and session reset and queued-recovery boundaries follow upstream contracts.
- **Dashboard sign-in is secure and route-aware.** Browser-based authorization is scoped and serialized to the selected host, while cold start no longer activates a temporary localhost API fallback or reports a missing key before stored connection state is ready.
- **Background and promoted voice work retain their owning chat rows.** Completing an initial spoken handoff no longer removes an otherwise empty assistant bubble that still owns a running task, and concurrent turns remain reachable without requiring an always-on idle connection.
- **Self-hosted rendering is safer.** Android accepts deliberately installed user certificate authorities without bypassing chain, hostname, or Relay-pin verification, and malformed syntax-highlighting ranges no longer crash Markdown rendering.
- **Developer Options reflect current product behavior.** The obsolete Relay feature toggle is removed, version-tap unlock and explicit relock persist correctly, and backup, import, reset, and completion messages now report their actual results.
## [1.4.9] - 2026-07-19
### Changed
- **Hermes connections now use the Dashboard/Gateway as their standard surface.** Chat, sessions, Manage, and voice share one upstream sign-in; the API server is an optional automatic fallback or headless compatibility path, while Relay remains optional for power features.
- **Connection management and onboarding now explain each path clearly.** Nearby and remote dashboard setup, Tailscale and custom ports, Relay pairing, startup preference, route details, and security posture are presented in dedicated flows.
### Fixed
- **Server default consistently displays Hermes' pinned active profile.** Chat, session drawers, agent details, settings, voice, diagnostics, and profile inspection now use the active profile identity while preserving server-default routing semantics.
- **Discovered connections show useful host identity.** Successful local dashboard probes resolve and retain a hostname without overwriting a user-supplied connection label.
## [1.4.8] - 2026-07-18
### Fixed
- **The Google Play privacy-policy URL is permanently available.** The canonical policy now lives on hermes-relay.dev, the historical GitHub Pages URL serves the complete policy for compatibility, and Android release automation blocks publication if either public page is unavailable.
- **Android opens the hosted privacy policy directly.** The About screen no longer sends users to a repository source file.
## [1.4.7] - 2026-07-18
### Added
- **Android adds German, Brazilian Portuguese, and Japanese.** Complete AI-assisted catalogs cover both product flavors, with language-picker integration and freshness validation against the canonical English resources.
### Fixed
- **Long streamed replies grow smoothly and remain at the latest text.** Android frame-paces bursty token delivery, expands the active bubble within clipped bounds, preserves bottom-following through completion, and avoids replacing the visible live transcript while readers who intentionally scroll up remain undisturbed.
## [Android 1.4.6] - 2026-07-15
### Added
- **Profile display order and visibility are customizable per connection.** The profile manager can reorder every profile, including Server default, selectively hide inactive profiles, restore hidden active profiles, and reset the saved presentation without changing server configuration.
- **Agent icons can come from the phone or paired host.** The profile manager offers the Android document picker and can import conventional host files such as `avatar.png` or `profile.jpg`, storing a per-connection/profile copy on the phone.
### Fixed
- **Profile image import reports host compatibility accurately.** Android now distinguishes an older Relay without the optional avatar endpoint from a profile that genuinely has no conventional image, and presents the system file picker as a clear fallback.
- **Server-default chats use one profile session scope.** Android resolves the Server default row through Hermes' sticky active profile before Gateway create/resume and dashboard session operations, so the drawer, transcript, writes, and agent no longer split across different profile databases when the dashboard was launched under another profile.
## [Plugin 1.4.2] - 2026-07-15
### Added
- **Profile avatars are available to paired clients.** Relay discovers conventional direct-child profile images such as `avatar.png` and `profile.jpg`, validates their type, size, and profile boundary, and serves them through an authenticated profile route.
### Fixed
- **Relay follows Hermes' sticky active profile.** The advertised Server default identity, model, SOUL, profile metadata, and avatar now come from the profile selected by Hermes' `active_profile` marker instead of always describing the root profile.
## [1.4.5] - 2026-07-15
### Fixed
- **Running Android chats survive session switching.** On the upstream Gateway path, opening another chat, profile, draft, or Thread now detaches the visible stream without interrupting Hermes. Each running session keeps its own durable UI checkpoint, reconnects the shared event socket across route loss, and reattaches through `session.activate`/`session.resume` when selected again. SSE fallback remains intentionally single-stream and cancels on navigation.
- **Expired Gateway prompts no longer remain actionable.** Android collapses matching secret and sudo cards when Hermes emits their expiry events, recognizes late expired responses, and is ready for an upstream session-scoped approval-expiry contract without guessing the server timeout.
- **Provider wait notices stay transient.** Canonical Hermes provider-wait, reconnect, and continuation notices now use Chat's live status line instead of accumulating in the assistant reasoning transcript.
## [0.4.0-alpha.2] - 2026-07-13
### Added
- **Desktop chat can use Relay typed streaming over WSS.** The opt-in `--relay-chat` mode sends `chat.send`, renders typed `stream.event` v1 assistant/tool/artifact/memory/skill/error lifecycles, de-duplicates reconnect events, and preserves the existing gateway chat path as the default.
- **Pending computer-use grants are manageable from the CLI.** `hermes-relay grants` lists and interactively approves or rejects local grant-bridge requests, with explicit `approve`, `reject`, and JSON forms for scripts.
- **Desktop use has a durable CLI control plane.** `hermes-relay computer-use` persists enablement, reports daemon and grant state, and cancels active task-scoped grants through the local daemon bridge.
### Changed
- **The optional Windows systray is a native context menu for the CLI.** The WebView dashboard, embedded terminals, overlays, chat, sessions, plugins, voice, and settings windows were removed. The sub-megabyte tray now invokes the single installed CLI for TUI, pairing, daemon control, grants, audit, and logs.
- **Systray daemon controls are state- and privilege-aware.** The menu cross-checks PID liveness, identifies User versus Administrator daemons, disables invalid lifecycle actions, shows pending-grant counts and version metadata, toggles sign-in startup, and requests UAC only for an explicit elevated daemon start or restart.
- **Systray desktop-use controls preserve safety across restart and elevation.** The menu enables or disables the persistent capability, displays active grant mode and expiry, raises a native pending-approval alert, supports immediate cancellation, and warns while Administrator input authority is active.
- **CLI and tray releases use one synchronized version contract.** A single npm lifecycle keeps package, compiled CLI, Cargo, and installer metadata aligned; local verification and tag CI reject drift, off-main release tags, and untested CLI changes before publishing.
### Fixed
- **Compiled CLI diagnostics report the physical executable.** `hermes-relay doctor` no longer mistakes Bun's virtual embedded path for the installed binary, so PATH and install-directory checks describe the executable that actually launched.
## [1.4.4] - 2026-07-12
### Added
- **Android adds AI-assisted Spanish.** A repeatable translation harness and freshness checks keep catalogs structurally complete while tracking fluent review separately.
- **Diagnostics exposes the Relay contract.** A manual refresh reports the installed plugin version, protocol version, capability count, profile enablement state, and last-check time; shared issue reports include sanitized Android and device metadata.
- **What’s New links to complete release history.** The polished modal now provides direct access to every bundled version, with large-text screenshot coverage.
### Fixed
- **Profile operations stay inside the selected Hermes profile.** Session list, history, rename, delete, and in-flight recovery no longer fall through to the default database after a scoped failure; optimistic writes roll back and repeated recovery failures stop cleanly.
## [1.4.3] - 2026-07-11
### Added
- **Language switching is available inside the app.** Settings → Appearance now offers System default, English, and Simplified Chinese, stays synchronized with Android's per-app language setting, and persists the choice on Android 12 and lower.
### Fixed
- **Release builds reject unsupported collection APIs.** CI now scans Kotlin sources and final minified APK bytecode for Java 21 list endpoint calls that can crash on Android versions before API 35.
## [1.4.2] - 2026-07-11
### Added
- **Android now supports Simplified Chinese.** Chat, Manage, Voice, connection setup, settings, diagnostics, notifications, accessibility labels, and both product flavors follow the device language, with Android per-app language discovery on supported versions.
- **Localization is contributor-ready.** CI enforces resource, plural, and format-argument parity; translated README and VitePress entry points establish a repeatable path for adding languages without duplicating fast-moving technical references.
### Fixed
- **Connection scan and queued-message counts use proper plurals.** Count formatting no longer depends on English-only suffix arguments and cannot fail when a locale needs a different plural structure.
## [1.4.1] - 2026-07-11
### Added
- **Background work is visible in Standard Chat.** A live process strip opens a mobile process sheet with running or recent state, output, elapsed time, Stop, and Dismiss controls. It remains compatible with older Hermes servers that do not expose process details.
- **Background work has a clearer Chat home.** Realtime work appears as a titled task card with working, waiting, delivery, and completion states, queued work, and an expandable tool timeline.
- **Multi-image messages open as galleries.** Adjacent images render in a compact grid and open at the selected image in a swipeable viewer while preserving sensitive-media reveal and original-file actions.
- **Voice gains commands and presets.** Spoken commands can stop speech, cancel background work, pause or resume listening, repeat a result, or start Standard voice chat. Hands-free, Low latency, Careful tools, and Quiet presets tune existing interaction settings.
### Changed
- **Streaming Chat content stays steadier and more readable.** Settled prose and headings adopt final Markdown styling during generation, wide tables scroll with readable columns, the thinking indicator respects system motion and TalkBack settings, and the jump-to-bottom control counts unread messages.
- **Offline Demo mode no longer starts Voice.** The mic action now explains locally that a Hermes connection is required.
### Fixed
- **An in-flight Chat turn survives reopening the app.** Session-backed replies restore partial text, live reasoning, lifecycle status, tool/subagent cards, background-task state, and unanswered approval or clarification cards. Current Hermes gateways reattach to the same running turn; older or finished sessions reconcile from history without duplicating the prompt or losing the final answer.
- **Realtime Agent delivery is protected.** Hermes results use exact provider speech where supported, delivery validation, generation-safe confirmation, and a single relay-TTS fallback if the provider closes or rejects delivery. Voice commands no longer leave synthetic cancellation turns or mute a later background answer.
- **Standard Chat receives background-process completions automatically.** When Hermes completes detached work and starts a follow-up turn on the originating Gateway session, Android shows the unsolicited assistant stream in the open conversation and reconciles history after a cold reconnect. The synthetic process prompt is rendered as a compact process notice rather than a user-authored message.
## [1.4.0] - 2026-07-09
### Added
- **Android model pickers can refresh the server catalog.** Chat's model sheet and Manage's main/profile model dialogs now expose upstream's explicit **Refresh Models** action, so dynamic/custom provider model lists can be reloaded on demand without making every picker open probe providers.
- **Server-backed session cleanup plumbing.** The dashboard client now supports single-session export, the upstream `/api/sessions/prune` route with a mandatory dry-run preview before destructive apply, plus soft archive/restore helpers and an `archived` session-list filter for the Manage surface.
- **Notification triggers MVP.** Settings → Notifications now has explicit opt-in proactive rules for the Notification companion: match by app package plus optional title/text filters, post a safe local "Ask Hermes?" prompt, show the latest trigger activity, and pause everything instantly with a kill switch.
- **Android bridge: multi-device targeting.** The relay can keep multiple Android bridge clients connected at once, route commands by `device` selector (`phone`, `pixel`, `fold`, `boox`, `note`, `notemax`, `tablet`, or device ID), expose `/bridge/devices` and `/bridge/select-active`, and advertise an optional `device` argument on the `android_*` tool schemas.
- **Voice: a second long request gets queued, not refused.** Ask for another long task while one is already running in the background and it's now queued (up to three) and starts automatically when the current one finishes — with a short spoken transition. The task card shows "+N queued", and cancelling the current task clears the queue.
- **Voice: background answers start speaking sooner and can never be silently lost.** The spoken summary now streams as it's generated (it used to be held until fully complete — a noticeable dead gap, then the whole answer at once). Delivery is verified two ways: the summary must actually reflect the answer's content (not just avoid known filler phrases), and if no spoken delivery lands within 30 seconds the answer is posted as text instead of vanishing.
- **Voice: tap the finished-task card to hear the answer again.** After a background task's card settles to "finished," tapping it replays the delivered answer. The card also now shows in the compact voice view (it previously existed only in the full-screen layout), a "Drafting the answer…" status appears as the reply is being composed, and leaving voice mode with a task still running leaves a note in chat so the work stays visible.
- **Voice: quick questions answered while a background task runs.** Realtime voice used to refuse *any* second request while a long task ran in the background — even a two-second lookup. A quick second ask is now answered inline on a side session (within the same few-second window that decides backgrounding); anything that turns out to be long still gets the "a task is already running" answer, and the running task is never disturbed.
- **Voice: the background-task card no longer vanishes mid-answer.** The card used to disappear the instant the spoken answer started (exactly when the waveform returned), reading as the task being lost. It now settles to a "Background task finished." state, lingers for a few seconds while the answer plays, then dismisses itself — and its ✕ during that settled state just dismisses the card instead of sending a cancel.
- **Voice: the "Thinking" pill no longer spins forever.** The server streams its drafting text as an internal pseudo-tool that never reports completion, and the app rendered it as a live tool pill — which then ran indefinitely in both chat and the voice overlay. Internal tool events no longer become pills (their text still feeds the thinking trace).
- **Voice: background-task answers can't be lost to a stray cancel.** Tapping cancel/stop after a background task had already finished used to mark the finished run "cancelled" — losing the answer that was about to be spoken. Cancel now only cancels a run that's actually still running; stopping the current speech works as before.
- **Voice: no more spoken run IDs or phantom queue state.** The realtime voice model no longer reads 32-character run IDs aloud after starting a background task (identifiers stay out of everything it's asked to speak), no longer claims a request was queued unless the relay accepted it, and a completed task's answer is spoken directly — deferral filler like "one moment while I look that up" in place of a finished result now triggers the fallback that speaks the real answer.
- **Voice: finished-task answers keep the realtime voice.** A completed background task's answer is now spoken by the same realtime voice you've been talking to — read word for word from the authoritative Hermes answer — instead of switching to the standard TTS voice mid-conversation. The answer always lands: if the realtime model goes off-script or the provider connection drops, standard TTS speaks it, and if you start talking mid-delivery it's posted as text instead of interrupting you. The "When the answer is ready" setting keeps its four modes (Exact / Summary / Notify / Show), now explained behind an info icon in Voice Settings.
- **Voice: realtime models refreshed.** OpenAI realtime now defaults to `gpt-realtime-2.1` (with the cheaper `gpt-realtime-2.1-mini` selectable), the versioned `grok-voice-think-fast-1.0` pin is available alongside xAI's `grok-voice-latest` alias, and session logs record which model the provider *actually* served — so provider-side alias moves no longer happen invisibly.
- **Voice: session logs clean up after themselves.** Realtime voice session logs are swept after 14 days by default (`realtime_voice.run_retention_days`, 0 disables), and the per-response TTS audio capture is now opt-in debug tooling (`debug_audio_tap`) instead of an always-on multi-MB tap.
- **Voice: one-command delivery health report.** `python -m plugin.relay.realtime_agent.report` summarizes recent voice deliveries — how many were spoken by the realtime voice vs fell back to TTS or text, and why — for quick health checks after live testing.
### Changed
- **Bootstrap compatibility layer slimmed to true gaps.** The optional compatibility hook no longer injects session CRUD/messages or the legacy skills list — current Hermes serves those natively; it now covers only surfaces with no native replacement yet (session search, memory, legacy skill detail/toggle, config, available-models, and the slash-command middleware). Older pre-session-API Hermes builds degrade to the standard completions/runs chat paths.
- **Dependency floor: aiohttp ≥ 3.14.1.** Raised from 3.9 across plugin requirements and package metadata to the patched line covering the 2026 aiohttp security advisories.
### Fixed
- **Realtime voice recovers after background route loss.** A recorded turn now waits for a relay-confirmed resumed socket, retains unacknowledged follow-up PCM for replay, and reports transport rejection instead of sitting on a dead persistent connection. Resume handshakes are coalesced, and the relay requires a valid resume claim before replacing the active phone socket, so a slower stale connection cannot detach background-result delivery. Long-lived sessions start their bounded retry window when the route actually drops instead of at voice-mode entry, and a bare socket open cannot reset it. Late callbacks from a retired session are ignored. Exiting voice mode clears its detached reconnect and confirmation state before another session opens; rejected or unacknowledged cancels no longer leave an undismissable background-task pill. Provider transcription no longer impersonates active microphone capture, Stop settles the local turn even when the route is gone, and provisional `Listening...` / `Still working...` rows cannot remain stuck in chat.
- **xAI exact background answers bypass model deferral.** Non-structured **Exact** deliveries now use xAI's provider-native forced speech event, preserving the selected realtime voice and normal assistant history while speaking the authoritative Hermes answer without asking the model to follow a read-verbatim prompt. Structured results and summary modes still use natural model summarization, and the validator plus standard-TTS fallback remain as safety nets.
- **Background voice handoffs no longer repeat themselves.** If the realtime provider already spoke an acknowledgement before calling Hermes, promotion keeps that first line and suppresses the redundant "running in the background" follow-up; silent tool calls still receive the configured spoken handoff. Provider protocols that report both response creation and output-item creation now also produce one client `response.started` event instead of two.
- **Realtime voice model and voice picks now apply to the next session.** Voice Settings persists the selected Realtime Agent model and voice per connection/profile and sends both when opening a session, so choosing a pinned model immediately controls the next session instead of requiring **Save realtime agent** to rewrite the relay config. The active voice UI reflects the override, changing it retires any prewarmed session, and the choice survives an app restart.
- **Fresh realtime sessions emit one ready event.** Android's required `session.start` acknowledgement no longer causes the relay to send a second `voice.session.ready`, avoiding duplicate event IDs and duplicate session-ready telemetry on every new voice conversation.
- **Relay media can no longer serve credential files.** `/media/by-path` now always blocks paths that resolve into credential or system locations (`~/.hermes/.env`, `auth.json`, `config.yaml`, OAuth/MCP token stores, `pairing/`, `~/.ssh`, and similar) even in the default permissive mode — mirroring upstream Hermes' media-delivery hardening — so a prompt-injected `MEDIA:` marker can't deliver live secrets to a paired phone. Symlinks are resolved before the check, and the relay's own QR-signing secret and session-token store are covered too.
- **Long agent turns no longer die or duplicate at the transport.** Gateway chat (Android and the desktop CLI) now gives `prompt.submit` up to 30 minutes to acknowledge — matching upstream desktop and the server's own turn ceiling — instead of short generic RPC timeouts that could falsely fall back to SSE (duplicating the turn on Android) or kill a legitimately long deep-reasoning turn. Turn liveness is governed by idle-progress watchdogs (no events at all for a stretch), never a hard cap while output is still streaming.
- **Manage → Models keeps providers that still need keys.** Newer Hermes hides unconfigured providers from the model catalog unless a management UI opts in; Android Manage now opts in and keeps rendering greyed provider rows with their key-setup guidance on both old and new servers. In-chat model picking is unchanged (configured providers only).
- **Phone-local context actually reaches the server on fallback chat paths.** The sessions/runs streaming payloads carried voice-intent traces, card dispatches, and attachments in fields the server never reads — silently dropping them. That context now rides channels the server actually consumes (a per-turn context digest, real history fields where they exist, inline images on the completions path), and any attachment with no supported channel is reported instead of silently discarded.
- **Relay plugin works under the native `hermes plugins install` path.** The plugin's runtime imports assumed the repo's editable layout, so upstream's native installer (which loads plugins under its own package namespace) broke `hermes relay start` and `hermes pair` with `ModuleNotFoundError: No module named 'plugin'`. All runtime imports are now package-relative, the dashboard module boots correctly when the upstream web server loads it standalone, and `hermes relay doctor` now exercises the real import chain so this class of breakage can't pass doctor again. (#165)
- **Installer handles modern venv layouts.** `install.sh` now autodetects the classic venv, uv-managed `.venv`, and containerized layouts — and everything it generates (the systemd unit and all four command shims) points at the interpreter it actually detected instead of a hardcoded classic path. On immutable container images it steers to the native install path with a clear message instead of dying mid-run. (#165)
- **Doctor catches dashboard URLs pointed at the wrong Hermes surface.** `hermes relay doctor` now distinguishes the dashboard/Manage surface from an API-server/headless backend URL and tells operators to use `hermes dashboard` when a configured dashboard URL is actually pointing at `hermes serve` / the API server.
- **Doctor and installer catch stale duplicate plugin copies.** The gateway plugin loader picks a discovered plugin by manifest name, so a second directory declaring `name: hermes-relay` (a leftover backup copy or a stray extra install) could win and make the gateway load stale code — silently ignoring every later deploy. `hermes relay doctor` now warns when more than one directory under the plugins dir declares the same plugin name, and `install.sh` removes any such duplicate so only the canonical plugin symlink remains.
- **Crash-safety on Android 14 and earlier.** Built against SDK 35, Kotlin's `removeFirst()`/`removeLast()` resolve to the new Java `List` methods that don't exist below Android 15, crashing older devices. All such calls in the app are now `removeAt(...)`, and Tink (pulled in by encrypted storage) is pinned ahead of the transitive version whose `HybridConfig` tripped the same Google Play pre-launch check.
- **No crash when a relay address is malformed.** A corrupt or hand-edited pairing address with an invalid host could crash the app the moment it opened the relay connection (the connection is built on a background thread, so the error escaped uncaught). A bad relay address is now handled as a normal connection failure — shown as disconnected with a "re-pair to refresh" note — instead of crashing. The same guard now also covers the relay's media, session, and voice HTTP calls. (relay half of #131)
- **Voice: cleaner error recovery.** A failed or timed-out voice turn no longer shows the same error twice (the top overlay banner and a duplicate bottom banner) and can now be **dismissed**, not just retried — so a stuck error state can't block the screen.
- **Voice: fallback-spoken answers no longer play into a frozen overlay.** When an answer is delivered by the standard TTS fallback (or replayed from the finished-task card), the voice screen now shows the waveform and the answer text while it speaks — previously it sat on "Thinking" with no visuals even though audio was playing.
- **Voice: a quiet realtime session no longer dies with a raw provider error.** xAI ends a realtime conversation after 900 seconds of inactivity, and no keepalive traffic resets that timer — so a voice session left open through a long background task (or simply left open) died with a raw provider error. That provider timeout is now treated as routine expiry: the session ends cleanly with no error banner, and your next voice turn transparently opens a fresh provider conversation that picks up from the same durable Hermes chat session.
- **No crash when a malformed server address reaches a chat send.** The three streaming chat paths built their HTTP request before any error handling, so a corrupt or hand-edited API URL could throw instead of failing the turn gracefully. They now surface "Invalid server address — edit the connection's API URL or re-pair" through the normal in-chat error channel (closes the remaining #131 crash-class gap).
- **Demo mode: typing a message now gets an honest reply.** Sending a message in the offline demo used to do nothing (the composer silently ignored it, reading as broken). The demo now echoes your message and answers with a short notice explaining it's an offline sample, pointing at the Connect action to chat for real.
- **Voice: realtime conversations reliably reach your chat history.** Turns the realtime voice model answers directly (without calling Hermes) are folded into the chat session on your next message — but on the default gateway connection that hand-off could be deferred indefinitely, so the agent never learned what was said in voice. The turn that carries them now routes so the sync actually lands. Synced voice turns also render cleanly when a chat reloads: a quiet "Realtime Agent" chip instead of a raw provenance footnote, and no more duplicated voice exchange after the sync.
## [1.3.0] - 2026-07-06
### Added
- **Voice settings: edit your server's voice engine.** Voice settings now has a **Server voice config** section that reads and writes the host's text-to-speech and speech-to-text settings — provider, voice, model, language, and per-provider options — over the dashboard, the same config the official desktop app edits. It includes an **ElevenLabs voice picker** that lists the voices available on your server's ElevenLabs key (and tells you when no key is set). Works on the no-plugin (Standard) path; sign in to Manage to use it.
- **Desktop CLI: `hermes-relay audit`.** Shows what the remote agent has actually run on this machine through the desktop tools — tool, status, and a short detail per call — read from a local log, no network or auth. Answers "what did the agent just do?" at a glance.
- **Desktop CLI: `hermes-relay relay`.** Inspect the relay server itself: `relay info` (version, uptime, sessions — on the relay host), `relay security` (runtime auth toggles), `relay context` (audit the system-prompt context the relay injects into the agent, which works from a remote machine with your session), and `relay queue` (list — or `--clear` / `--cancel <id>` — the messages your agent queued for an offline phone; on the relay host).
- **Desktop CLI: background daemon.** `hermes-relay daemon start` runs the headless tool router in the background (no console window, survives closing the terminal), with `daemon stop` and `daemon status` to manage it. `daemon status` reports state, uptime, relay, and advertised-tool count; bare `daemon` still runs in the foreground. Logs go to `~/.hermes/daemon.log`.
- **Desktop CLI: per-command help.** Every subcommand now answers `--help`, and `devices`/`sessions`/`plugins`/`voice`/`relay` print their own usage (sub-commands, flags, examples) instead of a terse "unknown sub-verb".
- **Desktop CLI: startup banner.** A slim "Hermes Relay" wordmark shows atop `--help`, the first-run welcome, and the chat REPL — and `hermes-relay logo` prints it on demand. Suppressed for piped/`--json`/`--no-color` output.
- **Animated "thinking" indicator.** While a reply streams, the in-bubble working indicator can now be a small dot-matrix animation instead of the three dots. Pick a motion (Wave, Pulse, Bounce, Sparkle) and a color (match-text or a brand accent) in Chat settings, with a live preview. It follows light/dark and your app theme, and goes static when animations are turned off.
- **Proactive messages from the agent to your phone.** Your Hermes agent can reach out to the paired phone on its own — via `send_message target=phone` or a cron `deliver=phone`. Messages surface as a system notification, collect in a dedicated Hermes inbox, and can be injected into the active chat to continue the conversation (selected per message). Off by default and gated on pairing: nothing is pushed unless you enable it on the server (`PHONE_ENABLED`) and opt in on the phone ("Let Hermes message me"). Delivered over the existing relay connection through the upstream platform-plugin API (no fork).
- **Reply to your agent's messages (two-way).** A proactive message is now a conversation, not a one-way ping: reply straight from the notification (inline Reply) or from the Hermes inbox, and your answer goes back to the agent and continues the same thread. The phone behaves like any other Hermes messaging platform — the reply arrives as an inbound message the agent processes and answers. Rides the same paired relay connection; no extra setup beyond the proactive opt-in above. If your phone is offline when the agent answers, the message is queued and delivered when you reconnect — not lost.
- **Pick your font.** A Font picker in Appearance sets the app-wide typeface — **Inter** (the new default), **Nunito**, or your **system** font — each previewed in its own face and applied instantly across the app, no restart. Code and timestamps stay monospaced. (Bundled faces are SIL OFL.)
- **Quick Controls in Settings.** A Quick Controls card at the top of Settings groups the switches you flip most often — **Persistent connection** and **Turn-complete alerts** — so they're one tap from the Settings root instead of buried in a sub-screen.
- **Connections: a cleaner list and a tabbed detail.** Settings → Connections is now a scannable list — each server shows an **Active** badge and an at-a-glance capability summary (API · Dashboard · Voice · Relay) — and tapping a server opens a focused detail screen with **Overview**, **Routes**, **Advanced**, and **Security** tabs. Rename / re-pair / revoke / remove moved into the detail's **⋮** menu, and **relay sessions** (review and revoke the phones paired with that server) get a clear home under Security.
- **Keep connected through deep sleep (sideload).** When **Persistent connection** is on, Settings offers a one-tap "Allow unrestricted battery" prompt so the connection survives Android's deep-sleep (Doze) — without it, the OS pauses background networking after the screen's been off a while even with a foreground service. (Sideload only; Google Play restricts this permission.)
### Changed
- **Reporting a diagnostic now files the right kind of issue.** The Report button on a diagnostics entry used to turn routine log lines into "[Bug]" GitHub issues with an empty template. Now informational entries first ask "what were you expecting to happen?" and file as a "[Diagnostic]" question, error entries keep the direct bug flow, and every report carries the connection mode you were actually on instead of a placeholder line. (#155, #154, #146)
- **Simpler release downloads.** Each Android release on GitHub now attaches just two files — the tap-to-install sideload APK and the Play Store upload bundle — plus checksums, with the release notes leading with the one file most people want. The extra "parity/testing" artifacts are gone from the release page (still reproducible from the tag via CI). (#144)
- **Clearer, snappier voice capture and playback.** Voice now engages the device's echo-cancellation and noise-suppression while recording (matching the desktop's microphone setup), and requests audio focus before the first reply so the opening words aren't clipped on a cold start. Listening timing also matches the official desktop: auto-stop ~1.25s after you stop speaking (was 3s), give up after 12s with no speech, and cap a turn at 60s.
- **Refreshed chat look.** Message bubbles are wider and denser, each assistant turn shows a small Hermes avatar to its left (once per group), and code blocks are richer — a language label, a copy button, and a clearer inset so fenced code and inline `code` no longer blend into the bubble.
- **Desktop CLI: visual + ergonomics refresh.** A single color theme across the CLI, aligned tables for `devices`/`sessions`, status dots for on/off states, and progress spinners for slow operations (the multi-endpoint pairing probe and the gateway connect) so nothing looks hung. Errors now suggest the fix (e.g. re-pair on auth failure).
- **Desktop CLI: smoother pairing.** The multi-endpoint probe shows per-endpoint progress and latency; a near-expiry session warns before it fails and prints the exact re-pair command; and a bare `ws://host` (no port) defaults to `:8767`.
- **Desktop CLI: voice + consent transparency.** `voice` now surfaces enhanced-voice capabilities (Gemini tone tags / persona, xAI speech tags); the desktop-tool consent prompt is clear that it persists per relay and points at `hermes-relay audit`; and computer-use's observe → grant → act flow is documented in `--help`.
- **Persistent connection (was "keep chat connected").** The background keep-alive and its notification are reframed from a "chat connection" to your overall connection to Hermes — it holds the app's connection open in the background so messages and live features stay responsive, and for relay-paired setups also keeps device control and notification mirroring reachable. The toggle moved out of Chat settings into the new top-level Quick Controls card.
- **Chat is the home; simpler top-level navigation.** The Chat / Manage / Bridge mode strip is gone — Chat is now full-height, and Manage and Bridge are reached from Settings (Settings → Hermes management / Bridge), each with a back arrow to Chat. Terminal and Settings remain quick icons in the chat top bar.
- **Gentler reconnects when your server is unreachable.** After the server has been unreachable for a while, the app stops retrying every ~15 seconds and drops to a slower poll — easier on the battery — and still reconnects immediately the moment the network changes or the server comes back.
- **Connection status stays out of your way.** Connection feedback now sits exactly where it matters and never covers the nav or shifts the screen. Your **agent's** connection shows in the header subtitle under the agent name — it reads *Reconnecting…* / *Connecting…* / *Disconnected* and crossfades back to the model when it recovers, the same place messaging apps put it. The **relay** link (bridge / terminal / voice) shows only as a small amber *Reconnecting…* cue in the bottom status strip, since it doesn't block chat. Returning to the app from the background is now fully silent instead of flashing a misleading "connection changed" for the same connection re-handshaking.
- **Realtime voice: quieter progress.** The periodic spoken status updates during a long task ("Using cronjob…") are now off by default — the agent speaks at the milestones that matter (task started in background, finished, or failed) and the visual progress chip covers the in-between. A server setting brings the timed narration back if you prefer it.
- **Realtime voice: a live background-task chip.** The "working on it" chip in voice mode now actually shows what's happening: the current step ("Running command"), how many steps have finished, and a running timer — with a pulse so you can tell it's alive. It also reads the connection honestly ("Reconnecting — your task is still running" during a blip, "Done — delivering the answer…" while the reply queues up), and a ✕ on the chip cancels the task outright.
- **Realtime voice: snappier long-task handoffs and first turns.** When a clearly long-running tool starts (cron, desktop, browser work), the agent hands the task to the background right away instead of waiting out the full grace period — and the voice session now warms up when you open voice mode, so the first turn skips the connection setup it used to pay.
### Removed
- **Two voice controls that did nothing.** The disabled "Auto-TTS" toggle and the "STT language" picker under "Coming soon" in Voice settings are gone: the official desktop doesn't read every typed message aloud, and speech-to-text language is a server-side setting now editable in the new Server voice config section.
### Fixed
- **Realtime voice: you can keep talking while a background task runs.** Progress updates from a background task were flipping the voice UI back into "Thinking" with a Stop button on every tick, so the mic never came back until the task finished. Progress now feeds only the task chip; the conversation stays open the whole time.
- **Realtime voice: leaving voice mode no longer cancels a running task.** Exiting (or tapping Stop to interrupt speech) used to kill an in-flight background task and could overwrite its already-delivered answer with "Cancelled." in the chat. Exit now detaches — the task keeps running and the result arrives on your next session or as a notification — and a delivered answer always keeps its text (a Stopped badge marks a genuine cancel). The chip's ✕ remains the one deliberate way to cancel.
- **Long answers are no longer lost when the connection drops mid-turn.** On slow local models (or skills that delegate long background work), the phone could drop the stream mid-turn — the server finishes and saves the answer, but the chat sat on "Still working…" forever. The app now detects the dropped stream and quietly re-checks the conversation until the finished answer arrives, then completes the turn normally (with the usual done-notification if you've backgrounded the app). Switching chats or sending something new cancels the wait. (#166)
- **Onboarding slides fit every screen.** Intro slide text could run past the bottom of the screen with no way to scroll on short displays or large font sizes. Slides now scroll when needed and compact their artwork on short viewports, so no setup guidance is unreachable. (#145)
- **Docs: fixed stale setup labels and broken links.** The setup guide referenced a "Vanilla Hermes" button the app hasn't shown since v1.2.2 (it's labeled "Hermes"), several deep links into the getting-started page were dead, and the README under-counted the available phone tools. (docs site)
- **Back button on Manage and Bridge now works.** The back arrow on the Manage ("Hermes management") and Bridge screens did nothing — it tried to jump to Chat in a way that silently no-op'd. Back now reliably returns to the screen you opened it from.
- **Dropped relay connections from a status-report race.** The phone's periodic device-status report could occasionally be sent to the relay *before* the connection had finished authenticating, which made the relay reject the whole connection and forced a reconnect. The app now holds every message until the connection is authenticated, so the handshake always completes first.
- **Fewer needless connection re-checks when switching apps.** Returning to the app after a quick glance at another app no longer triggers a full connection re-probe (and the brief "checking…" flash) when the connection was already healthy — it only re-checks after a longer absence or if something actually looks off.
- **No more scary "server isn't accepting connections" pop-up on first load.** A bare bottom message could flash on cold start while the app was still establishing its first connection (the background session-list load failing before the server was reachable). That state is now shown only by the themed connection banner at the top — the redundant pop-up is suppressed for cold-start/reconnect bootstrapping, while real failures while you're using the app still surface normally.
- **Reconnect loop on remote (Tailscale) connections.** Connecting from off your home network could make chat loop — repeatedly reconnecting before it finally settled — because a brief route-probe miss flipped the active route back to the (unreachable) home address and rebuilt the chat connection against it. The app now keeps the last working route through a transient miss, tolerates a slow first handshake on remote links, and absorbs VPN-interface churn, so a remote connection settles quickly instead of thrashing.
- **Realtime voice: background tasks survive a brief disconnect.** Asking the voice agent to run a longer task in the background no longer loses the result to a momentary network drop — the server keeps the run alive across the reconnect and delivers the answer once you're back, and a task that runs too long is now stopped cleanly instead of hanging silently.
- **Realtime voice: the spoken answer is no longer dropped when a background task finishes.** When the agent completed a longer background task, a harmless internal provider notice was being treated as a fatal error and closed the voice session right as the reply was about to be spoken (surfacing an "xAI realtime error" toast with Retry). Those transient notices no longer end the turn, so the answer is actually spoken.
- **Realtime voice: the answer waits for you instead of playing to a dead connection.** If a background task finishes while your phone is disconnected, the spoken summary is now held and delivered when the voice session reconnects — and the phone keeps retrying that reconnect for several minutes instead of giving up after one attempt. If the voice session is gone for good, the result arrives as a notification instead (the full answer is always in the chat).
- **Realtime voice: asking for a second task while one is running no longer breaks the first.** The agent now tells you the earlier task is still in progress (wait, check status, or cancel) instead of silently losing its result.
## [1.2.6] - 2026-06-27
### Added
- **Session drawer refresh.** A refresh button in the session drawer re-pulls the chat list on demand, so a title the server generates a moment after a turn shows up without waiting for the next reload.
### Changed
- **Calmer connection status.** Transient connection status — reconnecting, checking, LAN↔Tailscale handoffs — now renders as a thin banner at the top that takes its own space (the screen slides down) instead of a card floating over the chat. The floating alert is reserved for persistent errors. Frequent confirmations (copied, profiles updated, profile/personality switches) moved to the same top banner instead of the bottom pop-up.
### Fixed
- **Chats stuck showing "Untitled".** The session drawer no longer overwrites a chat's first-message preview with a blank title when the server hasn't auto-named it yet (and the SSE path never does), so chats stop reading "Untitled"; titles also reconcile once the turn settles. (#133)
- **Rename on a non-default agent profile.** Renaming a chat while a non-default profile is active now persists to that profile's own store instead of the shared one — matching the earlier session-delete fix.
## [1.2.5] - 2026-06-27
### Added
- **Demo mode.** A "Try the demo" option on the setup / Connect screen — and on the empty chat screen if you skip setup — opens an offline preview of the real Chat UI: a sample conversation with Markdown, a tool-progress card, and a rich card, with zero setup and zero network (works in airplane mode). A persistent "Demo mode — sample data, not connected" banner offers a one-tap Connect that opens the real setup wizard; other tabs show a friendly "connect your Hermes server" empty state. Lets a first-run user — or a Play reviewer with no server — see what the app does before connecting.
### Fixed
- **Crash when a non-address is entered as a server URL.** Typing or pasting non-URL text (for example a label, or a line copied from the docs) into the API server or Dashboard URL field could force-close the app on the Manage / sign-in screen: the value was handed to the networking layer as a host, which rejected it with an uncaught error on the main thread. The setup fields now reject anything that isn't a valid host or `http(s)://` URL with an inline error, and the dashboard and voice request paths treat a malformed address as "unreachable" instead of ever crashing. (#131, #132)
## [1.2.4] - 2026-06-25
### Added
- **Connection security indicator.** The chat status chip, the connection card, and the route picker now show at a glance whether your connection is encrypted — 🔒 **Encrypted · TLS**, 🛡️ **Encrypted · Tailscale** (both secure), 🛡️ **Mixed routes**, or ⚠️ **Not encrypted** — and tapping it opens a per-transport breakdown (chat, API, relay tools). A Tailscale/WireGuard route is now correctly shown as encrypted rather than implied insecure. Adds a new "Is my connection secure?" docs page explaining the difference between TLS and overlay (WireGuard) encryption.
### Fixed
- **Crash when a dashboard connection drops mid-check.** A transient network blip on the dashboard session check (e.g. a pooled connection aborting or timing out over Tailscale) could close the app: the check returned a result type but re-threw the network error instead of reporting it, and it surfaced on the main thread. The check now reports the failure cleanly, and the connection probe degrades gracefully instead of ever crashing. (#129)
## [1.2.3] - 2026-06-23
### Fixed
- **Crash on connect over TLS / Tailscale.** Connecting to a server over an encrypted link (Tailscale Serve or public HTTPS) could hard-close the app with `NetworkOnMainThreadException`. Tearing down an HTTP client closed live SSL sockets on the main thread, and a TLS socket close performs a network write — which Android forbids on the main thread. Client shutdown now always closes sockets off the main thread, so connecting over a secured link no longer crashes. (#118, #124; likely the v1.1.0 / Tailscale crash in #70)
## [1.2.2] - 2026-06-22
### Added
- **Diagnostics: status timeline.** Diagnostics now opens full-screen and leads with a top-to-bottom list of subsystem health checks — network, API server, chat transport, pairing, relay, and voice — each with a clear pass / warning / fail state and, when something's wrong, the reason why; tap a failing check for full detail. The recent-activity log stays below it.
### Changed
- **Connections wording simplified.** The default connection is now just "Hermes" (previously "Vanilla" / "Standard Hermes"), and the optional power features are labelled "Relay" / "Relay plugin", across the connection setup, switcher, voice, and permissions screens.
- **Clean chat mode shows more text.** The distraction-free chat view gives its text a noticeably taller, scrollable area instead of capping it near a third of the screen.
### Fixed
- **Deleting a session on a non-default profile now sticks.** Removing a chat while a non-default agent profile was active could leave it on the server, so it reappeared after the list refreshed; the delete is now scoped to the active profile.
- **Session drawer opens on the right profile from a cold start.** When launching with a non-default profile selected, the session list could briefly show the default profile's chats and then snap to the correct ones; it now waits for the profile to resolve and loads the right list directly.
## [1.2.1] - 2026-06-21
### Added
- **Profile lock.** Settings → Profile lock pins the app to a single agent profile and hides the rest from the pickers; the lock screen stays the one place that lists every profile, with a clear notice if the locked profile isn't on the current server.
- **In-app What's New & changelog.** A new Settings entry shows the current and past release notes any time — not just the post-update popup.
- **Diagnostics: tap for detail + report.** Logged errors now carry clean titles and open a detail view with Copy / Share / Create-GitHub-issue (the same flow as crash reports); classified errors across voice, chat, and connection are captured centrally.
- **Update-available nudge.** A dismissable in-app banner when a newer version is live — Google Play In-App Update on Play installs, GitHub Releases on sideload. Per-version dismissal, throttled, never nags.
### Changed
- **Crash reports can be shared without GitHub.** The crash dialog now has a **Share** action alongside Copy and Report, handing the full report to the system share sheet (email, chat apps, notes, Drive). This covers users without a GitHub account and sideload installs that Play vitals never sees. Every outbound path stays user-initiated — nothing is sent automatically.
### Fixed
- **Voice override applies in Auto mode.** A chosen per-profile/enhanced voice now takes effect when the engine is on Auto with the relay paired — previously only "Relay" mode applied it. Per-profile voice settings are also namespaced by connection.
- **Realtime voice "Stop" stops immediately.** Tapping Stop while the agent is speaking now halts realtime playback at once; over-chatty spoken status is throttled; and long background tasks no longer time out the turn (relay keeps the session alive while the task runs).
- **Realtime Agent: brokered Hermes turns no longer fail (relay).** When the Realtime Agent reached back to Hermes for context or tool work, a session-namespace mismatch could make the API Server reject the turn with `session_not_found`. The relay now mints or reuses a valid API Server session and retries once, and reads the API Server's current nested create-session response. Provider-native turns are unaffected.
- **Hold-to-talk no longer releases on accidental drift.** The mic button holds until the finger genuinely lifts, instead of cancelling when it drifts off the button.
- **Voice overlay is readable.** The voice dropdown panel and its status bubbles are opaque (no bleed-through), and the Focus/Overlay/Exit labels no longer wrap to two lines; invalid engine/route combinations are no longer selectable.
- **Connection status overlay clears faster.** Resolved (error/warning) connection toasts auto-dismiss within ~5s instead of lingering.
## [1.2.0] - 2026-06-20
### Added
@@ -310,11 +692,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
- **Pre-release hardening: uninstall, doctor, first-run prompts, version-aware install.** Four parallel workstreams that close the "feels like a dev preview" gap before tagging `desktop-v0.3.0-alpha.1`. (1) **Uninstall scripts** — new `desktop/scripts/uninstall.{sh,ps1}` matching install one-liners, 3-tier: default `--binary-only` (removes binary + PATH entry, preserves `~/.hermes/remote-sessions.json`), `--purge` (also wipes the shared session store with a loud cross-surface warning about Ink TUI + Android tooling dependencies), `--service` (stub for when daemon service installers ship — prints canonical systemd/launchd/sc.exe paths without acting). iex-pipe safety: Windows falls back to `HERMES_RELAY_UNINSTALL_{PURGE,SERVICE}` env vars since `$args` drops through `irm | iex`. Shell rc files deliberately untouched (mirrors install.sh philosophy). (2) **`hermes-relay doctor` subcommand** — local-only diagnostic report (225 lines, `src/commands/doctor.ts`); human format uses `!!` prefix for warnings + hint line at bottom, `--json` for support-paste / scripts. Fields: version / binary_path / install_dir / on_path / sessions file + size + count + summaries (no tokens — total omission, not even prefix) / daemon detection (stat of canonical service unit file paths) / platform + node version. Case-insensitive PATH comparison on Windows. (3) **Interactive first-run fallback** — new `src/relayUrlPrompt.ts` (~180 lines) with `promptForRelayUrl()` (readline on stderr, `^wss?:\/\/\S+$` validation, 3 retries) and `resolveFirstRunUrl()` (auto-picks single stored session, numbered picker for multiple, first-run banner for zero). Wired into `connectAndAuth` in `shell.ts` / `chat.ts` / `tools.ts` and `resolvePairTarget` in `pair.ts`, replacing the hard `No relay URL` error. Fresh-install UX: bare `hermes-relay` now prints `Welcome to hermes-relay. No stored sessions yet — let's pair with a Server.` → URL prompt → pairing code prompt → drops into shell. `--non-interactive` still fails fast. Daemon command deliberately untouched — headless binaries must never prompt; fails closed on missing credentials/consent as before. (4) **Version-aware install** — `install.{sh,ps1}` now read `$target --version` before download and print one of `upgrading X → Y`, `reinstalling X`, `will replace (could not read version)`, or `installing fresh` (no prior install); post-install readback re-invokes the new binary to confirm. Pinned-version mismatches (`HERMES_RELAY_VERSION=desktop-v0.3.0-alpha.1`) print a non-fatal WARN rather than failing (pre-release version-name drift is expected). 5s timeout on the version call (where `timeout(1)` available); all diagnostic failures fall through to the "could not read version" path. Cross-version normalizer strips `desktop-v` / `v` prefix + `-alpha.N` / `-beta.N` / `-rc.N` suffix for matching. All structural flow (SHA256 verify, tmp cleanup, PATH injection, quarantine note) preserved additively. Type-check + build green; live smoke: `doctor` both modes, `daemon` fails-closed without credentials, help text includes all new surfaces.
- **`hermes-relay daemon` — headless WSS + tool router, lifts the "tools only work while a shell is open" ceiling.** New `desktop/src/commands/daemon.ts` subcommand that opens a persistent relay connection and attaches `DesktopToolRouter` without a TTY. The agent can now reach the user's machine any time of day — first step toward "feels-local" parity. Fails closed on missing credentials (no stored session + no `--token` → exits 1) and on missing consent (no `toolsConsented: true` on the stored record → exits 1 unless `--allow-tools` is passed alongside an explicit `--token`); a headless binary must never be the thing that first grants tool access. Inherits `RelayTransport`'s reconnect state machine as-is — exp backoff 1s → 30s (5min on 429), reconnect listeners persistent across close/reconnect cycles because `channelListeners` is a Map on the transport (not wiped on socket close), so the router's `attach()` fires exactly once. Structured logging defaults to JSON-line on stderr (parseable by journald / log shippers / jq), auto-switches to human-readable when stderr is a TTY, or force either with `--log-json` / `--log-human`. Lifecycle events: `starting` → `authed` (includes `server_version`, `transport`) → `ready` (with `advertised_tools` list) → `reconnecting` (attempt + delay_ms) / `reconnected` → `shutdown` on SIGTERM/SIGINT/SIGHUP → `transport_exited` when the transport exhausts reconnects (exits 1 so the service manager restarts fresh). Live smoke against `ws://172.16.24.250:8767`: `starting` → `authed` (server 0.6.0) → `ready` (5 tools advertised) in ~120ms. New BOOLEAN_FLAGS entries: `log-human`, `log-json`, `allow-tools`. Service installers for Windows `sc.exe` / systemd user unit / macOS launchd plist are the obvious follow-up; the daemon binary is runnable standalone today via `hermes-relay daemon --remote <url>`.
- **`hermes-relay daemon` — headless WSS + tool router, lifts the "tools only work while a shell is open" ceiling.** New `desktop/src/commands/daemon.ts` subcommand that opens a persistent relay connection and attaches `DesktopToolRouter` without a TTY. The agent can now reach the user's machine any time of day — first step toward "feels-local" parity. Fails closed on missing credentials (no stored session + no `--token` → exits 1) and on missing consent (no `toolsConsented: true` on the stored record → exits 1 unless `--allow-tools` is passed alongside an explicit `--token`); a headless binary must never be the thing that first grants tool access. Inherits `RelayTransport`'s reconnect state machine as-is — exp backoff 1s → 30s (5min on 429), reconnect listeners persistent across close/reconnect cycles because `channelListeners` is a Map on the transport (not wiped on socket close), so the router's `attach()` fires exactly once. Structured logging defaults to JSON-line on stderr (parseable by journald / log shippers / jq), auto-switches to human-readable when stderr is a TTY, or force either with `--log-json` / `--log-human`. Lifecycle events: `starting` → `authed` (includes `server_version`, `transport`) → `ready` (with `advertised_tools` list) → `reconnecting` (attempt + delay_ms) / `reconnected` → `shutdown` on SIGTERM/SIGINT/SIGHUP → `transport_exited` when the transport exhausts reconnects (exits 1 so the service manager restarts fresh). Live smoke against `ws://192.168.1.100:8767`: `starting` → `authed` (server 0.6.0) → `ready` (5 tools advertised) in ~120ms. New BOOLEAN_FLAGS entries: `log-human`, `log-json`, `allow-tools`. Service installers for Windows `sc.exe` / systemd user unit / macOS launchd plist are the obvious follow-up; the daemon binary is runnable standalone today via `hermes-relay daemon --remote <url>`.
- **Desktop CLI v0.2 — PTY shell, local tool routing, multi-endpoint pairing, reconnect + TOFU, devices, contextual banner.** The `@hermes-relay/cli` package at `desktop/` grew from a chat-only scripting surface into a full Hermes-experience thin client. Bare `hermes-relay` now drops into `shell` mode (interactive PTY pipe through the existing relay `terminal` channel → `tmux new-session -A` + post-attach `exec hermes` → the full local `hermes` banner/skin/session id verbatim, zero server changes). `Ctrl+A .` detaches preserving tmux; `Ctrl+A k` destroys it. New `devices` subcommand drives the relay's `GET/DELETE/PATCH /sessions` HTTP endpoints for listing, revoking, and extending server-side paired-device tokens. Status now surfaces `grants:` (per-channel expiry) and `expires:` (session TTL) pulled from the `auth.ok` handshake the transport already received — `RemoteSessionRecord` gained `grants`, `ttlExpiresAt`, `endpointRole`, `toolsConsented` (additive, back-compat preserved via a `SaveSessionOptions | string | null` overload on `saveSession`). Contextual connect banner (`Connected via LAN (plain) — server 0.6.0`) replaces the flat `Connected (server X)` line across `chat` + `shell`. Multi-endpoint pairing (ADR 24): `--pair-qr <payload>` / `HERMES_RELAY_PAIR_QR` accepts a full v3 QR payload (compact JSON or base64), decodes the `endpoints[]` array, probes each candidate with strict-priority-within-tier racing (`Promise.any` + `AbortSignal.any`, 4 s per-candidate timeout, 60 s reachability cache), and auto-selects the first reachable — role propagates into the banner + stored record. Reconnect-on-drop: `RelayTransport` gained a `ReconnectState` machine (`idle|connecting|connected|reconnecting`), exponential backoff (1 s → 30 s, 5 min on 429), `reconnectGate` re-checked both at schedule time and post-backoff (matches Android's mid-sleep purge-race lesson), `'reconnecting'` + `'reconnected'` events, and bufferedEvents-cleared-on-reconnect. TOFU cert pinning: TLS probe runs before the WebSocket opens on `wss://`, extracts peer-cert SPKI sha256 (`sha256/<base64>`, OkHttp-compatible), compares against the stored pin or captures it first-time; mismatches error out with a human-readable "re-pair to reset" pointer. Client-side tool routing (Phase B): new `desktop` relay channel on the server (`plugin/relay/channels/desktop.py` + `plugin/tools/desktop_tool.py` registering `desktop_read_file` / `desktop_write_file` / `desktop_terminal` / `desktop_search_files` / `desktop_patch`) forwards tool calls from Hermes to the connected Node CLI; client-side `DesktopToolRouter` dispatches to in-process handlers (`fs`, `terminal`, `search`) under a 30 s AbortController, 30 s heartbeat advertising the tool names. Gated behind a one-time per-URL consent prompt (`toolsConsented` on the session record) + `--no-tools` kill-switch; non-TTY stdin fails closed. New files on the client: `src/banner.ts`, `src/endpoint.ts`, `src/pairingQr.ts`, `src/certPin.ts`, `src/commands/devices.ts`, `src/tools/router.ts`, `src/tools/consent.ts`, `src/tools/handlers/{fs,terminal,search}.ts`. New files on the server: `plugin/relay/channels/desktop.py`, `plugin/tools/desktop_tool.py`, `docs/relay-protocol.md §3.5`. Still zero runtime deps on the client (Node ≥21 global `WebSocket` + `fetch` + `tls.connect` + `node:crypto` X509Certificate + `AbortSignal.any`). Build clean; live smoke passed for `status` / `tools` / `devices`; interactive `shell` + tool-call smoke pending user walk-through. Delivered as four parallel implementation agents (multi-endpoint, reconnect+TOFU, server-side desktop, client-side tool handlers) + one synthesis-and-integration pass; the `connectAndAuth → {relay, url, endpointRole}` return-shape refactor in `chat.ts` / `shell.ts` / `tools.ts` unifies how `--pair-qr`'s winning-endpoint URL overrides `--remote` across every subcommand.
- **Desktop thin-client CLI (`@hermes-relay/cli`) v0.1 under `desktop/`.** Node ≥21 package — installable via `npm install -g @hermes-relay/cli`, `npx @hermes-relay/cli`, or the new `scripts/install.sh` / `install.ps1` curl+iwr one-liners. One `hermes-relay` binary with four subcommands: `chat` (REPL + one-shot + piped-stdin, default), `pair` (one-time handshake → persists session token), `status` (local read of `~/.hermes/remote-sessions.json`), `tools` (`tools.list` RPC → enabled/available toolsets on the server). Credential precedence matches the Ink TUI exactly: `--token` → `HERMES_RELAY_TOKEN` → `--code` → `HERMES_RELAY_CODE` → stored session → interactive readline prompt. Reuses the **same** `~/.hermes/remote-sessions.json` store as the TUI, so a user paired via either surface sees the other work with no re-pair. Zero server changes: the CLI consumes the existing relay `tui` WSS channel + `tui_gateway` subprocess events (`message.delta`, `tool.start/complete`, `thinking.delta`, `status.update`, `error`, `approval.request`, …) and renders them as plain lines to stdout, with decorated tool arrows on stderr. Flags: `--remote <url>`, `--code <CODE>`, `--token <TOKEN>`, `--session <id>`, `--json` (event-per-line for `jq`), `--verbose`, `--quiet`, `--no-color`, `--non-interactive`, `--reveal-tokens` (opt-in full-token output on `status --json` — default redacts). Transport, gateway types, session storage, graceful-exit, and rpc helpers are **vendored verbatim** from `hermes-agent-tui-smoke/ui-tui/src/` (feat/tui-transport-pluggable) with a header note; the CLI and TUI stay in lockstep on the envelope protocol (docs/relay-protocol.md §3.7) until the shared surface can be lifted into a `@hermes-relay/core` package post-stabilization. SIGINT during a turn calls `session.interrupt` via a per-turn `{ promise, cancel }` handle — the REPL's cancellation state lives and dies with the turn so a late-arriving `error` event for a cancelled turn can't be misread by the next turn's handler. Smoke-tested end-to-end against `ws://172.16.24.250:8767` (hermes-relay 0.6.0, hermes-agent 0.10.0): connect/auth/session.create/prompt.submit/tools.list/--json/piped-stdin all clean. Not yet wired: interactive approval/clarify/sudo/secret request response (renderer logs a warning; out of scope for v0.1). Upstream PR candidate once the sibling Ink TUI stabilizes — see `desktop/README.md` and vault `Desktop Client.md` for the broader thin-client roadmap.
- **Desktop thin-client CLI (`@hermes-relay/cli`) v0.1 under `desktop/`.** Node ≥21 package — installable via `npm install -g @hermes-relay/cli`, `npx @hermes-relay/cli`, or the new `scripts/install.sh` / `install.ps1` curl+iwr one-liners. One `hermes-relay` binary with four subcommands: `chat` (REPL + one-shot + piped-stdin, default), `pair` (one-time handshake → persists session token), `status` (local read of `~/.hermes/remote-sessions.json`), `tools` (`tools.list` RPC → enabled/available toolsets on the server). Credential precedence matches the Ink TUI exactly: `--token` → `HERMES_RELAY_TOKEN` → `--code` → `HERMES_RELAY_CODE` → stored session → interactive readline prompt. Reuses the **same** `~/.hermes/remote-sessions.json` store as the TUI, so a user paired via either surface sees the other work with no re-pair. Zero server changes: the CLI consumes the existing relay `tui` WSS channel + `tui_gateway` subprocess events (`message.delta`, `tool.start/complete`, `thinking.delta`, `status.update`, `error`, `approval.request`, …) and renders them as plain lines to stdout, with decorated tool arrows on stderr. Flags: `--remote <url>`, `--code <CODE>`, `--token <TOKEN>`, `--session <id>`, `--json` (event-per-line for `jq`), `--verbose`, `--quiet`, `--no-color`, `--non-interactive`, `--reveal-tokens` (opt-in full-token output on `status --json` — default redacts). Transport, gateway types, session storage, graceful-exit, and rpc helpers are **vendored verbatim** from `hermes-agent-tui-smoke/ui-tui/src/` (feat/tui-transport-pluggable) with a header note; the CLI and TUI stay in lockstep on the envelope protocol (docs/relay-protocol.md §3.7) until the shared surface can be lifted into a `@hermes-relay/core` package post-stabilization. SIGINT during a turn calls `session.interrupt` via a per-turn `{ promise, cancel }` handle — the REPL's cancellation state lives and dies with the turn so a late-arriving `error` event for a cancelled turn can't be misread by the next turn's handler. Smoke-tested end-to-end against `ws://192.168.1.100:8767` (hermes-relay 0.6.0, hermes-agent 0.10.0): connect/auth/session.create/prompt.submit/tools.list/--json/piped-stdin all clean. Not yet wired: interactive approval/clarify/sudo/secret request response (renderer logs a warning; out of scope for v0.1). Upstream PR candidate once the sibling Ink TUI stabilizes — see `desktop/README.md` and vault `Desktop Client.md` for the broader thin-client roadmap.
### Changed
@@ -1318,7 +1700,12 @@ MVP release — native Android companion app for Hermes agent with direct API ch
- **Dev scripts** — build, install, run, test, relay via scripts/dev.bat
- **ProGuard rules** — okhttp-sse, markdown renderer, intellij-markdown parser
[Unreleased]: https://github.com/Codename-11/hermes-relay/compare/android-v1.0.0...HEAD
[Unreleased]: https://github.com/Codename-11/hermes-relay/compare/android-v1.4.4...HEAD
[1.4.4]: https://github.com/Codename-11/hermes-relay/compare/android-v1.4.3...android-v1.4.4
[1.4.3]: https://github.com/Codename-11/hermes-relay/compare/android-v1.4.2...android-v1.4.3
[1.4.2]: https://github.com/Codename-11/hermes-relay/compare/android-v1.4.1...android-v1.4.2
[1.4.1]: https://github.com/Codename-11/hermes-relay/compare/android-v1.4.0...android-v1.4.1
[1.4.0]: https://github.com/Codename-11/hermes-relay/compare/android-v1.3.0...android-v1.4.0
[1.0.0]: https://github.com/Codename-11/hermes-relay/compare/android-v0.8.0...android-v1.0.0
[0.8.1]: https://github.com/Codename-11/hermes-relay/compare/android-v0.8.0...android-v0.8.1
[0.8.0]: https://github.com/Codename-11/hermes-relay/compare/v0.7.0...android-v0.8.0
+294 -256
View File
@@ -1,12 +1,15 @@
# Hermes-Relay — Claude Code Context
# Hermes-Relay — Claude Code Adapter
> Read this before touching code. Then read docs/spec.md and docs/decisions.md.
> Read [AGENTS.md](AGENTS.md) first. It is the provider-neutral canonical agent
> context. Branch, release, staging, and hotfix rules live in `AGENTS.md` and
> [RELEASE.md](RELEASE.md); this file only adds Claude-specific project and tool
> guidance. Then read `docs/spec.md` and `docs/decisions.md`.
## What This Is
A native Android app (Kotlin + Jetpack Compose) paired with an optional Python relay plugin/server (aiohttp) for the Hermes agent platform. Vanilla Hermes chat, Manage, and dashboard voice work against unmodified upstream Hermes. Relay adds phone control, terminal, remote desktop tooling, extra voice engines, and dashboard Relay management.
A native Android app (Kotlin + Jetpack Compose) paired with an optional Python relay plugin/server (aiohttp) for the Hermes agent platform. Vanilla Hermes chat, Manage, and dashboard voice work against unmodified upstream Hermes. The Relay plugin adds phone control, terminal, remote desktop tooling, extra voice engines, and dashboard Relay management via the official Hermes web dashboard.
**Current state:** v1.0.0 stable. The default no-plugin path supports chat, Manage, and voice on vanilla upstream Hermes. Chat auto-prefers the dashboard `/api/ws` gateway transport when Manage auth is ready, then falls back to API-server SSE routes. Vanilla Hermes voice uses dashboard `/api/audio/*` with the Manage session. Relay remains an additive power path for terminal, bridge/device control, notification companion, extra/provider-native voice, remote access, and desktop tooling. Two Android product flavors ship: `googlePlay` (conservative, no unattended Device Control surface) and `sideload` (full-capability).
**Current state:** Reference latest released version for stable state and current dev branch for working state. The default no-plugin path supports chat, Manage, and voice on vanilla upstream Hermes. Chat auto-prefers the dashboard `/api/ws` gateway transport when Manage auth is ready, then falls back to API-server SSE routes. Vanilla Hermes voice uses dashboard `/api/audio/*` with the Manage session. Relay remains an additive power path for terminal, bridge/device control, notification companion, extra/provider-native voice, remote access, and desktop tooling. Two Android product flavors ship: `googlePlay` (conservative, no unattended Device Control surface) and `sideload` (full-capability).
## Architecture
@@ -25,60 +28,66 @@ The Vanilla Hermes path must stay upstream-only. API-server bearer auth and dash
**Vanilla Hermes endpoints (confirmed in hermes-agent source):**
| Endpoint | Purpose | Tool Call Format |
|----------|---------|-----------------|
| `POST /v1/chat/completions` | OpenAI-compatible chat (stream=true for SSE) | Inline markdown text (`` `💻 terminal` ``) — no separate tool events |
| `POST /v1/runs` | Start an agent run | Returns `run_id` |
| `GET /v1/runs/{run_id}/events` | SSE stream of run lifecycle events | **Structured events**: `tool.started`, `tool.completed`, `message.delta`, `reasoning.available`, `run.completed`, `run.failed` |
| `POST /v1/responses` | OpenAI Responses API format | Structured `function_call` objects (non-streaming only) |
| `GET /v1/capabilities` | Machine-readable feature + endpoint discovery | Use before assuming optional surfaces exist |
| `GET /v1/models` | List available models | — |
| `GET /v1/skills` | Read-only skill list for the API-server agent | `{"object":"list","data":[...]}` |
| `GET /v1/toolsets` | Read-only API-server toolset inventory | `{"object":"list","platform":"api_server","data":[...]}` |
| `GET/POST/PATCH/DELETE /api/sessions/*` | Native session CRUD, messages, fork, sync chat, SSE chat | Upstream merged via NousResearch/hermes-agent PR #33134 |
| `GET /health` | Health check | — |
| `GET/POST/PATCH/DELETE /api/jobs/*` | Cron job management (api_server surface) | — |
| Endpoint | Purpose | Tool Call Format |
| --------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `POST /v1/chat/completions` | OpenAI-compatible chat (stream=true for SSE) | Inline markdown text (``💻 terminal``) — no separate tool events |
| `POST /v1/runs` | Start an agent run | Returns `run_id` |
| `GET /v1/runs/{run_id}/events` | SSE stream of run lifecycle events | **Structured events**: `tool.started`, `tool.completed`, `message.delta`, `reasoning.available`, `run.completed`, `run.failed` |
| `POST /v1/responses` | OpenAI Responses API format | Structured `function_call` objects (non-streaming only) |
| `GET /v1/capabilities` | Machine-readable feature + endpoint discovery | Use before assuming optional surfaces exist |
| `GET /v1/models` | List available models | — |
| `GET /v1/skills` | Read-only skill list for the API-server agent | `{"object":"list","data":[...]}` |
| `GET /v1/toolsets` | Read-only API-server toolset inventory | `{"object":"list","platform":"api_server","data":[...]}` |
| `GET/POST/PATCH/DELETE /api/sessions/*` | Native session CRUD, messages, fork, sync chat, SSE chat | Upstream merged via NousResearch/hermes-agent PR #33134 |
| `GET /health` | Health check | — |
| `GET/POST/PATCH/DELETE /api/jobs/*` | Cron job management (api_server surface) | — |
**Compatibility endpoints (not all native upstream API-server routes):**
Upstream main now contains the focused session-control API (`#33134`) and read-only skills/toolsets (`#33016`). The original broad PR [#8556](https://github.com/NousResearch/hermes-agent/pull/8556) was closed as superseded. Keep these distinctions straight:
1. **Native upstream** — `/api/sessions`, `/api/sessions/{id}/messages`, `/api/sessions/{id}/chat`, `/api/sessions/{id}/chat/stream`, `/v1/capabilities`, `/v1/skills`, and `/v1/toolsets` exist in current `gateway/platforms/api_server.py`.
2. **Bootstrap compatibility** (`plugin/hermes_relay_bootstrap/`) — monkey-patches aiohttp on startup via `.pth` file for older or partial core builds. It skips native routes per method/path and should be retired per surface, not treated as the preferred path. The repo-root `hermes_relay_bootstrap/` package is a legacy import shim.
2. **Bootstrap compatibility** (`plugin/hermes_relay_bootstrap/`) — monkey-patches aiohttp on startup via `.pth` file, injecting only compatibility-only surfaces (session search, memory, legacy skill detail/toggle, config, available-models, slash middleware). Sessions CRUD/messages/fork and the legacy skills list are **retired** — native upstream owns them (#33134/#33016) and the bootstrap carries no fallback for old builds. Native routes still win per method/path for the remaining set. The repo-root `hermes_relay_bootstrap/` package is a legacy import shim.
3. **Legacy fork branches** — useful as lineage only. Do not cite `feat/session-api` / `#8556` as the current upstream contract.
| Endpoint | Purpose | Provided by |
|----------|---------|-------------|
| `GET /api/sessions` (CRUD) | Session list/create/rename/delete/fork | Native upstream (#33134); bootstrap only for old builds |
| `GET /api/sessions/{id}/messages` | Conversation history | Native upstream (#33134); bootstrap only for old builds |
| `POST /api/sessions/{id}/chat` | Synchronous session chat | Native upstream (#33134) |
| `POST /api/sessions/{id}/chat/stream` | Session-based SSE chat | Native upstream (#33134); bootstrap does NOT inject |
| `GET /v1/skills`, `GET /v1/toolsets` | Read-only skill/toolset discovery | Native upstream (#33016) |
| `GET /api/sessions/search` | Full-text message search | Bootstrap/fork legacy; not in current upstream main |
| `GET /api/config`, `PATCH /api/config` | Personalities + model config | Bootstrap/fork legacy or dashboard web-server surface; not current API-server upstream |
| `GET /api/skills`, `/{name}` | Legacy skill discovery/detail | Bootstrap/fork legacy; prefer native `/v1/skills` for lists |
| `PUT /api/skills/toggle` | Enable/disable installed skill | `hermes_cli/web_server.py` dashboard surface; bootstrap stub returns 501 |
| `GET/POST/PATCH/DELETE /api/memory` | Memory CRUD | Bootstrap/fork legacy; not current API-server upstream |
| `GET /api/available-models` | Provider model list | Bootstrap/fork legacy; not current API-server upstream |
| Endpoint | Purpose | Provided by |
| -------------------------------------- | -------------------------------------- | -------------------------------------------------------------------------------------- |
| `GET /api/sessions` (CRUD) | Session list/create/rename/delete/fork | Native upstream (#33134); bootstrap injection retired |
| `GET /api/sessions/{id}/messages` | Conversation history | Native upstream (#33134); bootstrap injection retired |
| `POST /api/sessions/{id}/chat` | Synchronous session chat | Native upstream (#33134) |
| `POST /api/sessions/{id}/chat/stream` | Session-based SSE chat | Native upstream (#33134); bootstrap does NOT inject |
| `GET /v1/skills`, `GET /v1/toolsets` | Read-only skill/toolset discovery | Native upstream (#33016) |
| `GET /api/sessions/search` | Full-text message search | Bootstrap/fork legacy; not in current upstream main |
| `GET /api/config`, `PATCH /api/config` | Personalities + model config | Bootstrap/fork legacy or dashboard web-server surface; not current API-server upstream |
| `GET /api/skills/{name}` | Legacy skill detail | Bootstrap compat; list (`GET /api/skills`) retired — use native `/v1/skills` |
| `PUT /api/skills/toggle` | Enable/disable installed skill | `hermes_cli/web_server.py` dashboard surface; bootstrap stub returns 501 |
| `GET/POST/PATCH/DELETE /api/memory` | Memory CRUD | Bootstrap/fork legacy; not current API-server upstream |
| `GET /api/available-models` | Provider model list | Bootstrap/fork legacy; not current API-server upstream |
The Android client probes per-endpoint capability via `HermesApiClient.probeCapabilities()` (returns `ServerCapabilities`). When `streamingEndpoint = "auto"`, `ConnectionViewModel.resolveStreamingEndpoint()` picks `sessions`, `completions`, or `runs` based on the capability snapshot.
**Dashboard web server (separate surface — standard Manage / Desktop remote gateway):**
hermes-agent ships a second web server at `hermes_cli/web_server.py` that hosts the React admin dashboard at `hermes_cli/web_dist/`. It has its **own** `/api/*` routes that **do not live on `api_server.py`** — notably: `GET/PUT /api/config` (full tree), `GET /api/config/schema`, `GET /api/config/defaults`, `GET/PUT /api/config/raw` (YAML text), `GET/PUT/DELETE /api/env` + `POST /api/env/reveal`, `PUT /api/skills/toggle`, `/api/cron/jobs/*` (different shape from `/api/jobs/*`), `/api/providers/oauth/*`, `/api/dashboard/themes`, `/api/dashboard/plugins`, `/api/model/info` + `/api/model/options` + `POST /api/model/set`, `/api/profiles/*` (CRUD, `POST /api/profiles/active`, per-profile soul/description/model), `/api/mcp/*`, `/api/logs`, `/api/analytics/usage`, and **`POST /api/audio/transcribe` + `POST /api/audio/speak`** (base64 data-url contract, built for hermes-desktop voice). The API server has **no audio routes** — its `/v1/capabilities` advertises `audio_api: false`; PR #8199 (`/v1/audio/*`) is the canonical future surface but is unmerged. Android's **Vanilla Hermes (no-plugin) voice** therefore rides this dashboard surface via `StandardHermesVoiceClient` with the per-connection dashboard cookie session (Manage sign-in unlocks voice); `AutoVoiceAudioClient` prefers Relay when paired and falls back to standard.
hermes-agent ships a second web server at `hermes_cli/web_server.py` that hosts the React admin dashboard at `hermes_cli/web_dist/`. It has its **own** `/api/*` routes that **do not live on `api_server.py`** — notably: `GET/PUT /api/config` (full tree), `GET /api/config/schema`, `GET /api/config/defaults`, `GET/PUT /api/config/raw` (YAML text), `GET/PUT/DELETE /api/env` + `POST /api/env/reveal`, `PUT /api/skills/toggle`, `/api/cron/jobs/*` (different shape from `/api/jobs/*`), `/api/providers/oauth/*`, `/api/dashboard/themes`, `/api/dashboard/plugins`, `/api/model/info` + `/api/model/options` + `POST /api/model/set`, `/api/profiles/*` (CRUD, `POST /api/profiles/active`, per-profile soul/description/model), `/api/mcp/*`, `/api/logs`, `/api/analytics/usage`, and `**POST /api/audio/transcribe` + `POST /api/audio/speak`** (base64 data-url contract, built for hermes-desktop voice). The API server has **no audio routes** — its `/v1/capabilities` advertises `audio_api: false`; PR #8199 (`/v1/audio/*`) is the canonical future surface but is unmerged. Android's **Vanilla Hermes (no-plugin) voice** therefore rides this dashboard surface via `StandardHermesVoiceClient` with the per-connection dashboard cookie session (Manage sign-in unlocks voice); `AutoVoiceAudioClient` prefers Relay when paired and falls back to standard.
Current upstream supports two auth modes on this surface. Loopback dashboards still use the injected `window.__HERMES_SESSION_TOKEN__` path. Remote/non-loopback dashboards use the Desktop-style dashboard auth gate: `/api/status` advertises `auth_required` and providers, `/auth/password-login` handles password providers, `/auth/login?provider=...` handles Nous/OIDC redirects, `/api/auth/me` returns the verified session, and `/api/auth/ws-ticket` mints a short-lived ticket for `/api/ws` / `/api/pty`. This dashboard session is **not** an `API_SERVER_KEY`. Android uses it for Manage, Vanilla Hermes voice, and the gateway chat transport. `/api/ws` is backed by `tui_gateway/server.py` (what hermes-desktop + the Ink TUI speak) and is the only upstream surface with **live** `reasoning.delta`/`thinking.delta` streaming; the api_server SSE paths remain the SSE fallback. Relay-only capabilities remain behind Relay pairing. **Do not proxy dashboard auth or dashboard admin APIs over the relay.**
**Tool call rendering paths:**
1. **Runs API** — Emits `tool.started`/`tool.completed` as real SSE events → `ToolProgressCard` in real-time.
2. **Sessions API** — Native upstream emits structured SSE (`run.started`, `message.started`, `assistant.delta`, `tool.progress`, `tool.started/completed/failed`, `assistant.completed`, `run.completed`, `done`). `run.completed.messages` can reconcile authoritative per-turn transcript.
3. **Annotation parser** — Fallback for servers emitting inline markdown annotations (`` `💻 terminal` ``).
3. **Annotation parser** — Fallback for servers emitting inline markdown annotations (``💻 terminal``).
## Key Instructions
- **Vanilla Hermes path = upstream-only.** The default (no-plugin) connection path — gateway/API chat, Manage, and Vanilla Hermes voice via the dashboard surface — must work against **unmodified upstream hermes-agent**: no fork patches, no bespoke server config as a dependency. The app ships on Google Play to users whose servers we don't control. Features that need server-side changes go through upstream PRs (with graceful degradation until merged) or live behind the opt-in relay plugin.
- **Always verify upstream before assuming an endpoint exists.** Check `gateway/platforms/api_server.py` in hermes-agent. If an endpoint isn't there, document whether bootstrap injects it or it requires the fork.
- If we use a non-standard endpoint, ensure `probeCapabilities()` covers it and the auto-resolver degrades gracefully.
- **Bootstrap maintenance:** Retire `plugin/hermes_relay_bootstrap/` per surface. Sessions and read-only skills/toolsets now have native upstream replacements; config, memory, legacy skill detail/toggle, available-models, and slash middleware still need explicit replacement decisions before full removal.
- **Bootstrap maintenance:** Retire `plugin/hermes_relay_bootstrap/` per surface. Done: sessions CRUD/messages/fork and the legacy skills list are retired from the bootstrap (native upstream #33134/#33016, no old-build fallback kept). Remaining: config, memory, legacy skill detail/toggle, available-models, session search, and slash middleware still need explicit replacement decisions before full removal.
## Repository Layout
@@ -115,6 +124,7 @@ hermes-android/
│ │ ├── transport/ # RelayTransport (reconnect state machine + TLS probe TOFU)
│ │ └── lib/ # gracefulExit, rpc, circularBuffer (vendored)
│ └── scripts/ # install.sh + install.ps1 curl/iwr one-liners
├── website/ ← Astro product/marketing site (static Coolify/Nixpacks deployment)
├── plugin/ ← Hermes agent plugin
│ ├── android_tool.py # 18 android_* tool handlers
│ ├── pair.py # QR pairing implementation
@@ -131,6 +141,7 @@ hermes-android/
## Project Conventions
### File Structure
- **Root-level:** README.md, CLAUDE.md, AGENTS.md, DEVLOG.md, TODO.md, .gitignore
- **docs/** — spec, decisions, security, and any other long-form documentation
- **DEVLOG.md** — update at end of each work session with what was done + verification (the factual record of *what happened*). It churns; do NOT park forward work here.
@@ -149,15 +160,17 @@ This is a **public, distributed repo** — every committed file (CHANGELOG, DEVL
- **DEVLOG.md** is a committed, factual engineering log — what changed, why, and verification — depersonalized and third-person, not a diary.
### Code Style — Android (Kotlin)
- **Jetpack Compose** — no XML layouts. Material 3 / Material You.
- **kotlinx.serialization** — not Gson. Type-safe, faster.
- **OkHttp** for WebSocket + SSE — `okhttp` for WSS relay, `okhttp-sse` for API streaming
- **Single-activity** — Compose Navigation for all routing
- **Namespace (Kotlin source tree):** `com.hermesandroid.relay` — stable, drives on-disk layout + class FQCNs
- **applicationId:** `com.axiomlabs.hermesrelay` (googlePlay), `com.axiomlabs.hermesrelay.sideload` (sideload)
- **Min SDK 26, Target SDK 35, Compile SDK 36** / **Kotlin 2.0+**, JVM toolchain 17
- **Min SDK 26, Target SDK 35, Compile SDK 37** / **Kotlin 2.0+**, JVM toolchain 17
### Code Style — Desktop CLI (Node/TypeScript)
- **Node ≥21** — uses built-in global `WebSocket` (no `ws`/`undici` dep). Strict TS, ES modules, `NodeNext` resolution.
- **Zero runtime deps** — `@types/node` + `tsx`/`rimraf`/`typescript` are devDeps only. Ship compiled `dist/`, not tsx.
- **One binary, subcommands** — idiomatic for Node CLIs (codex, continue, vite pattern). Bare invocation is `chat`.
@@ -165,170 +178,183 @@ This is a **public, distributed repo** — every committed file (CHANGELOG, DEVL
- **Dev loop:** `npx tsx src/cli.ts <args>` (no rebuild). `npm run build` + `npm link` before pushing to verify the bin shim. Never ship tsx in the published tarball — pre-build with `tsc` so Windows `npm install -g` can cmd-shim the JS directly.
### Code Style — Server (Python)
- **aiohttp** — async, matches existing Hermes relay patterns
- **Type hints everywhere** — Python 3.11+ syntax
- **asyncio** — no threading; **structured logging** — use `logging`, not print()
### Git
- **Conventional Commits:** `feat`, `fix`, `docs`, `refactor`, `test`, `chore`
- **Branching model (as of 2026-04-19):** `main` + `dev`. Feature branches target `dev`, not `main`. `main` receives only release merges (and tags). No straight-to-main exemption — even single-file typos go through `dev`.
- **Merge style:** `git merge --no-ff` — no squash. Preserves per-commit trail for agent-team branches on every merge in the chain (feature → dev → main).
- **Merging ≠ releasing.** Feature branches land on `dev` continuously as CI goes green; each PR appends to `[Unreleased]` in `CHANGELOG.md` on `dev`. Releases are a separate act — cut when accumulated state is worth shipping, not per-feature. See `RELEASE.md` "When to cut a release."
- **Version bumps happen on `dev`, then release-merge to `main`.** Bump only the surface being released: `scripts/bump-android-version.sh` for `android-vX.Y.Z`, `scripts/bump-plugin-version.sh` for `plugin-vX.Y.Z`, and `desktop/package.json` for `cli-vX.Y.Z`. The release commit lives on `dev`, then a release PR merges `dev` → `main` with `--no-ff`, then the surface tag is cut from `main`.
- **Server tracks `dev` for staging.** The hermes-host deployment pulls `dev` so merged features are exercised before they reach a tag. Released state lives on tags cut from `main`.
- **Branch protection** on `main` — direct push blocked; only release-merge PRs from `dev` land here. `dev` also requires CI to pass on PRs but accepts feature-branch merges freely.
- **Branch/release policy:** follow the branch-contract table in `AGENTS.md` and
the executable release and hotfix procedures in `RELEASE.md`. Do not maintain
a Claude-specific parallel policy here.
### Testing
- **Android:** JUnit + Compose testing for UI, MockK for mocks
- **Python:** `python -m unittest plugin.tests.test_<name>` — avoid bare `pytest` (conftest imports `responses` which may not be installed in the venv)
- **CI is split by path:** `.github/workflows/ci-android.yml` runs on app/Gradle changes; `.github/workflows/ci-plugin.yml` runs on plugin/Python changes. Both trigger on pushes to `main` and `dev` and on PRs targeting either. Build + tests must pass before merge to `dev`; release-merge to `main` requires the same.
- **CI and release gates:** follow the repository-wide requirements in
`AGENTS.md` and `RELEASE.md`; Claude-specific guidance does not redefine them.
## Key Files
| File | Why |
|------|-----|
| `docs/spec.md` | Full specification — protocol, UI layouts, phases, dependencies |
| `docs/decisions.md` | Architecture decisions — framework choice, channel design, auth model |
| `AGENTS.md` | Universal agent entry point — points here + the non-negotiables (standard-path, commits, writing hygiene) |
| `docs/mcp-tooling.md` | MCP server setup — android-tools-mcp + mobile-mcp; `android_*` tool usage patterns |
| **App — Core** | |
| `ui/RelayApp.kt` | Main scaffold — bottom nav, Compose navigation |
| `viewmodel/ChatViewModel.kt` | Chat orchestration — send, stream, cancel, slash commands |
| `viewmodel/ConnectionViewModel.kt` | Dual connection model (API + relay); `resolveStreamingEndpoint()`; derived `relayUiState` flow + `markPaired` hook stamp the active Connection |
| `viewmodel/RelayUiState.kt` | Shared sealed state for the relay row — 5 cases + `asBadgeState()` / `statusText()` extensions; 5s grace window before Stale |
| `network/HermesApiClient.kt` | Direct HTTP/SSE — `sendRunStream()`, `sendChatStream()`, `probeCapabilities()` |
| `network/GatewayChatClient.kt` | Gateway chat transport — JSON-RPC over dashboard `/api/ws` (tui_gateway); live `reasoning.delta`; fresh ws-ticket per connect; per-turn SSE fallback via `onPreflightFailure`; `prewarm()` (connect+resume off the send path); `setKeepAliveInBackground()` suppresses the 120s idle-close |
| `network/GatewayKeepAliveService.kt` | Opt-in `specialUse` foreground service (BOTH flavors; declared in main manifest; Play needs a Console FGS declaration) holding the process up so the gateway socket survives background/Doze; driven by ConnectionViewModel from the `KEY_GATEWAY_KEEP_ALIVE` toggle; stops on task-removal |
| `data/GatewayKeepAlivePrefs.kt` | Shared `KEY_GATEWAY_KEEP_ALIVE` pref key + `Context.setGatewayKeepAlive()` — used by ConnectionViewModel (StateFlow/setter) and the FGS Stop action |
| `network/GatewayEventMapper.kt` | Pure-JVM gateway event→callback mapping for one turn; unknown event types silently ignored; tui_gateway usage-key translation |
| `network/GatewayModels.kt` | `GatewayAvailability`, `ActiveTurnHandle`, `GatewayTurnCallbacks` (all members REQUIRED — forces dispatchOn main-thread wrap), `GatewayAsk`, `GatewaySubagentEvent`, `resolveStreamingEndpointPreference()` |
| `ui/components/ChatInputBar.kt` | Redesigned input bar — pill field, one trailing slot morphing Send/Voice/Stop/Steer/Queue, no slash button (long-press + opens palette) |
| `ui/components/SubagentLane.kt` | Per-taskIndex subagent progress lane — guide rail, compact tool rows, auto-collapse |
| `notifications/TurnCompleteNotifier.kt` | Turn-complete local notification when backgrounded — channel `chat_turn_complete`, cancel on resume, settings-gated |
| `network/ConnectionManager.kt` | WSS to relay with auto-reconnect; rebuilds OkHttpClient with fresh CertPinner on connect |
| `network/ChannelMultiplexer.kt` | Envelope routing by channel; `sendNotification()` for notification outbound |
| `network/handlers/ChatHandler.kt` | Chat message state, streaming events, tool annotation parser |
| `network/models/SessionModels.kt` | Session, message, SSE event data models |
| `data/FeatureFlags.kt` | Feature gating — DEV_MODE + DataStore overrides; `BuildFlavor` (googlePlay/sideload Tier flags) |
| **App — Auth** | |
| `auth/AuthManager.kt` | Wires SessionTokenStore + CertPinStore; parses auth.ok; `applyServerIssuedCodeAndReset()` |
| `auth/SessionTokenStore.kt` | Keystore (StrongBox) + EncryptedSharedPrefs fallback; lossless migration on upgrade |
| `auth/CertPinStore.kt` | TOFU cert pinning — SHA-256 SPKI per host:port in DataStore |
| `auth/PairedSession.kt` | PairedSession state + PairedDeviceInfo wire model |
| `data/Endpoint.kt` | `EndpointCandidate` / `ApiEndpoint` / `RelayEndpoint` — multi-endpoint pairing (ADR 24); `displayLabel()` for LAN/Tailscale/Public/Custom chips |
| `network/RelayHttpClient.kt` | OkHttp for /media, /sessions (list/revoke/extend), /health |
| **App — Bridge** | |
| `network/handlers/BridgeCommandHandler.kt` | Routes `bridge.command` → ActionExecutor; full path inventory + safety-rail integration |
| `viewmodel/BridgeViewModel.kt` | BridgeScreen VM — masterToggle, bridgeStatus, permissionStatus, activityLog |
| `bridge/BridgeSafetyManager.kt` | Blocklist + destructive-verb confirmation + auto-disable timer; fails-closed on /call and /send_sms |
| `data/BridgeSafetyPreferences.kt` | DataStore for blocklist, destructive verbs, auto-disable minutes, confirmation timeout |
| `ui/screens/BridgeScreen.kt` | Bridge UI — master → permission checklist → [Advanced] → unattended → safety → activity log (v0.4.1 reorder) |
| `ui/components/UnattendedAccessRow.kt` | Unattended toggle card (sideload); `enabled=masterEnabled`; inline `KeyguardDetectedAlert` |
| `ui/components/UnattendedGlobalBanner.kt` | 28dp amber strip at scaffold top when master+unattended on (sideload); tap → Bridge tab |
| `bridge/BridgeStatusOverlay.kt` | WindowManager overlay; `ConfirmationOverlayHost`; requires `SavedStateRegistryOwner` init order (CREATED→restore→RESUMED) |
| `accessibility/HermesAccessibilityService.kt` | AccessibilityService subclass; `@Volatile instance` singleton for BridgeCommandHandler |
| `accessibility/ScreenReader.kt` | UI tree → ScreenContent; `findNodeBoundsByText()`, `findFocusedInput()` |
| `accessibility/ActionExecutor.kt` | Gesture/text dispatch via GestureDescription + ACTION_SET_TEXT; pressKey maps vocab only |
| **App — Voice** | |
| `voice/VoiceViewModel.kt` | Voice turn state machine; TTS queue; `ignoreAssistantId`; `errorEvents: SharedFlow` |
| `audio/VoiceRecorder.kt` | MediaRecorder wrapper; perceptual amplitude curve; `.m4a` at 16kHz/64kbps |
| `audio/VoicePlayer.kt` | Media3 ExoPlayer (gapless TTS queue) + Visualizer; amplitude StateFlow; `awaitCompletion()` via coroutine; `audioSessionId` is a thread-safe `@Volatile` cache |
| `network/RelayVoiceClient.kt` | OkHttp for `/voice/transcribe`, `/synthesize`, `/config` |
| `voice/VoiceBridgeIntentHandler.kt` | Interface routing voice utterances to bridge; impls per flavor via factory |
| `voice/VoiceIntentClassifier.kt` | Regex phone-control classifier (sideload only); false-negatives preferred over false-positives |
| `ui/components/VoiceModeOverlay.kt` | Full-screen voice UI — MorphingSphere + VoiceWaveform + mic button |
| `ui/components/MorphingSphere.kt` | Compose renderer for the agent sphere — delegates math to `MorphingSphereCore` |
| `ui/components/MorphingSphereCore.kt` | Platform-agnostic sphere algorithm (`kotlin.math` only) — single source of truth; mirrored byte-for-byte in `preview/web/sphere.js` |
| `preview/web/` | Zero-dep browser harness — live `index.html` preview + `parity-check.mjs`; paired with `MorphingSphereCoreParityTest` (JVM) for struct/full checksum diffing |
| `user-docs/.vitepress/theme/components/SphereMark.vue` | Docs-site sphere embed — imports `preview/web/sphere.js` directly; autonomous fbm drift + pointer-proximity gaze/state blend; `<ClientOnly>` + `IntersectionObserver` + `prefers-reduced-motion` aware |
| **App — Media + Notifications** | |
| `util/MediaCacheWriter.kt` | `cacheDir/hermes-media/` LRU writer; returns FileProvider URIs |
| `util/MediaSaver.kt` | Save/share/open for chat media — MediaStore scoped-storage save (Pictures/Download `Hermes-Relay`, no perms on API 29+; pre-Q → share sheet); FileProvider share staging; remote-byte fetch; magic-byte image-MIME sniff for correct extensions |
| `ui/components/ChatImageViewer.kt` | Full-screen image viewer — pinch-zoom/pan (`detectTransformGestures`), double-tap 1×/2.5×, Share/Save/Close; `ChatImageViewerSource` decouples Coil-model/bitmap display from a suspend `bytesProvider` so Save keeps original bytes |
| `ui/components/InboundAttachmentCard.kt` | Discord-style attachment card for images/video/audio/pdf/text/generic; image tap → ChatImageViewer, file card long-press → Open/Share/Save menu |
| `ui/components/ChatImageContent.kt` | Parses `![alt](src)` out of assistant content; remote http(s) → Coil (tap → ChatImageViewer), server-local/failed → inline "can't render" notice with the path |
| `data/HermesCard.kt` | `CARD:{json}` envelope (ADR 26) — type/accent/fields/actions; kotlinx.serialization |
| `ui/components/HermesCardBubble.kt` | Rich-card renderer — accent stripe + FlowRow actions + dispatch stamp collapse |
| `viewmodel/CardDispatchSyncBuilder.kt` | Twin of VoiceIntentSyncBuilder — synthesizes card dispatches as `hermes_card_action` OpenAI pairs for session memory |
| `notifications/HermesNotificationCompanion.kt` | NotificationListenerService; cold-start buffer (50); forwards via ChannelMultiplexer |
| `util/RelayErrorClassifier.kt` | `classifyError(Throwable, context) → HumanError`; used by Voice/Chat/Connection |
| `util/TurnLatencyTracer.kt` | One `TurnLatency` INFO line per chat turn — `warm/cold` + `connect/session/submit/ttfe/ttft/done@…ms`; gateway + 3 SSE paths use it for desktop-comparable latency diagnosis; durations only |
| **Relay — Server** | |
| `plugin/relay/server.py` | Canonical relay — WSS + HTTP routes; bridge, media, voice, session, pairing handlers. `handle_pairing_mint` mirrors `pair.py:762` — top-level = API server, `relay.{url,code}` nested |
| `plugin/relay/auth.py` | PairingManager, SessionManager, RateLimiter; `math.inf` for never-expire |
| `plugin/relay/channels/bridge.py` | Bridge handler — `handle_command()` mints request_id, awaits response, 30s timeout |
| `plugin/relay/channels/notifications.py` | Bounded deque (100) of notification metadata; in-memory only |
| `plugin/relay/media.py` | MediaRegistry — LRU token store; `strict_sandbox` off by default for `/media/by-path` |
| `plugin/relay/voice.py` | Voice endpoints — transcribe, synthesize, voice_config; lazy tool imports |
| `plugin/relay/qr_sign.py` | HMAC-SHA256 QR signing; secret at `~/.hermes/hermes-relay-qr-secret`; canonical form preserves `endpoints` array order + role strings verbatim (ADR 24) |
| `plugin/relay/tailscale.py` | First-class Tailscale helper (ADR 25) — `status()` / `enable(port)` / `disable(port)` / `canonical_upstream_present()`; safe-absent via shell-out to `tailscale` CLI |
| `plugin/relay/_env_bootstrap.py` | Loads `~/.hermes/.env` before relay imports; called from both entry points |
| **Plugin — Tools + Installer** | |
| `plugin/tools/android_tool.py` | 18 `android_*` tool handlers (14 baseline + send_sms, call, search_contacts, return_to_hermes); `android_screenshot` first consumer of `register_media()` |
| `plugin/tools/android_navigate.py` | Vision-driven navigation loop; up to 20 iterations; `llm_gap` error until vision client wired |
| `plugin/pair.py` | QR payload builder + CLI; `build_payload(sign=True)`; `--register-code` fallback |
| `plugin/doctor.py` | `hermes relay doctor`; checks standard upstream API/dashboard reachability, Relay loopback state, plugin layout, and compat hook state |
| `plugin/compat.py` | `hermes relay compat status/install/remove`; owns the optional `hermes_relay_bootstrap.pth` lifecycle |
| `plugin/hermes_relay_bootstrap/` | Plugin-owned runtime compatibility patch; skips native routes per method/path; retire only after remaining config/memory/legacy skill/slash gaps are handled |
| `install.sh` | Canonical installer — 6 steps; idempotent; drops `hermes-relay-update` shim |
| `uninstall.sh` | Canonical uninstaller; reverses install.sh; never touches `.env` or `state.db` |
| `hermes_relay_bootstrap/` | Legacy import shim for old `.pth` files and editable installs |
| **Plugin — Dashboard** | |
| `plugin/dashboard/manifest.json` | Declares tab, entry bundle, and FastAPI module for hermes-agent discovery |
| `plugin/dashboard/plugin_api.py` | FastAPI router proxying 5 routes to relay over loopback; `/pairing` body = API-server overrides (host/port/tls/api_key), relay URL auto-derived |
| `plugin/dashboard/src/index.jsx` | React root registering `hermes-relay` plugin with 4-tab shell |
| `plugin/dashboard/dist/index.js` | Committed IIFE bundle loaded verbatim by dashboard |
| **Desktop CLI** | |
| `desktop/package.json` | `@hermes-relay/cli` package manifest — Node ≥21, one `hermes-relay` bin, pre-built dist |
| `desktop/bin/hermes-relay.js` | Tiny shim: `import('../dist/cli.js').then(m => m.main())` + error surfacing |
| `desktop/src/chatAttach.ts` | captureClipboardImage / captureScreenshot / readImageFile; ships base64 to server via `image.attach.bytes` RPC before next prompt.submit |
| `desktop/src/cli.ts` | argv parser + subcommand dispatcher — bare → `shell` (PTY), positional-only → `chat` |
| `desktop/src/commands/chat.ts` | REPL + one-shot + piped-stdin; `runOneTurn` returns `{promise, cancel}` for safe SIGINT; auto-wires `DesktopToolRouter` when consented |
| `desktop/src/commands/shell.ts` | Pipes the `terminal` relay channel to raw-mode stdin/stdout; post-attach `exec hermes` 350ms after tmux settles; `Ctrl+A .` detach / `Ctrl+A k` kill / `Ctrl+A Ctrl+A` literal |
| `desktop/src/commands/pair.ts` | Either 6-char code + `--remote`, or full v3 QR via `--pair-qr` — probes + picks endpoint, records role; `--grant-tools` (TTY prompt) / `--auto-grant-tools` (silent) stamp `toolsConsented` so `daemon` works without a `shell` round-trip |
| `desktop/src/commands/tools.ts` | `tools.list` RPC → enabled/available toolsets; `--verbose` lists individual tools |
| `desktop/src/commands/status.ts` | Local read of `~/.hermes/remote-sessions.json`; renders `grants:` + `expires:` + `route:`; `--json` redacts tokens, `--reveal-tokens` opts in |
| `desktop/src/commands/devices.ts` | Server-side session management — `GET/DELETE/PATCH /sessions` via `fetch` over http(s)://host:port; `list` / `revoke <prefix>` / `extend <prefix> --ttl <s>` |
| `desktop/src/banner.ts` | `buildConnectBanner({url, meta, endpointRole})` → "Connected via LAN (plain) — server 0.6.0"; `humanExpiry()` for TTL formatting |
| `desktop/src/endpoint.ts` | `EndpointCandidate` / `EndpointRole` types + `displayLabel()` — mirrors Android `data/Endpoint.kt` |
| `desktop/src/pairingQr.ts` | `decodePairingPayload` (JSON or base64), `payloadToCandidates` (v3 verbatim / v1–v2 synthesized), `probeCandidatesByPriority` (`Promise.any` within tier, `AbortSignal.any`, 4s timeout, 60s cache) |
| `desktop/src/certPin.ts` | `extractSpkiSha256(der)` via `crypto.X509Certificate` + `publicKey.export({type:'spki'})`; `pinKey(url)`, `comparePins()`, `isSecureUrl()` |
| `desktop/src/tools/router.ts` | `DesktopToolRouter.attach(relay)` — `onChannel('desktop')` dispatch under 30s `AbortController`; heartbeat enriched with host/platform/version/uptime_ms + sticky `last_error` for `desktop_health` |
| `desktop/src/tools/handlerSet.ts` | Single source of truth for the desktop tool map — `DESKTOP_HANDLERS` + `DESKTOP_ADVERTISED_TOOLS`; consumed by `chat.ts` / `shell.ts` / `daemon.ts` so adding a tool is a one-file change |
| `desktop/src/tools/consent.ts` | `ensureToolsConsent(url)` — stored per-URL in `toolsConsented`; TTY prompt; non-TTY fails closed |
| `desktop/src/tools/handlers/fs.ts` | `readFileHandler` / `writeFileHandler` / `patchHandler` — strict unified-diff applier, no fuzz |
| `desktop/src/tools/handlers/terminal.ts` | `bash -lc` / `cmd /c`, SIGKILL on timeout or abort, returns `{stdout, stderr, exit_code, duration_ms}` |
| `desktop/src/tools/handlers/powershell.ts` | Spawns `pwsh`/`powershell` directly with `-Command -`, script piped via stdin — no cmd.exe quote-mangling; auto-picks pwsh > powershell |
| `desktop/src/tools/handlers/process.ts` | `spawn_detached` (unref'd, returns pid+log_path), `list_processes` (tasklist /FO CSV — no /V to dodge window-title latency), `kill_process`, `find_pid_by_port` (netstat/lsof/ss) |
| `desktop/src/tools/handlers/jobs.ts` | Job API — `~/.hermes/desktop-jobs/<id>/{stdout.log, stderr.log, meta.json}` is source of truth across daemon restarts; `taskkill /T` on Windows so build trees die fully |
| `desktop/src/tools/handlers/transfer.ts` | `copy_directory` via `fs.cp`, `zip`/`unzip` via tar > zip > PowerShell probe, `checksum` streamed (sha256/sha1/md5) |
| `desktop/src/tools/handlers/search.ts` | ripgrep with pure-Node fallback, skips `.git`/`node_modules`/`dist`/`.next`/`.cache` |
| `desktop/src/renderer.ts` | Streams `message.delta` → stdout, tool events → decorated lines; NO_COLOR / --json / --quiet aware |
| `desktop/src/pairing.ts` | readline-based 6-char prompt (`A-Z0-9`); headless mirror of TUI's Ink prompt; `validatePairingPayloadString` discriminated-union wrapper |
| `desktop/src/credentials.ts` | Precedence: `--token` → `--pair-qr` (probe+pair) → `--code` → stored → prompt; returns `Credentials{sessionToken?, pairingCode?, resolvedEndpoint?}` |
| `desktop/src/transport/RelayTransport.ts` | Fork of ui-tui's transport + reconnect state machine (`idle/connecting/connected/reconnecting`, exp backoff 1→30s, 5min on 429, gate re-check post-sleep) + pre-WS TLS probe for TOFU |
| `desktop/src/remoteSessions.ts` | Same file path as TUI (`~/.hermes/remote-sessions.json`, 0600); schema widened with `grants`, `ttlExpiresAt`, `endpointRole`, `toolsConsented`; `saveSession` back-compat overload |
| `desktop/src/commands/daemon.ts` | Headless WSS + tool router for always-on access; JSON-line logs; fails closed on missing consent unless `--allow-tools` with explicit `--token` |
| `desktop/src/commands/doctor.ts` | Local-only diagnostic report — version / binary path / PATH / sessions / daemon detection; `--json` for support-paste; omits tokens entirely |
| `desktop/src/relayUrlPrompt.ts` | First-run URL fallback — `resolveFirstRunUrl()` auto-picks single stored session, numbered picker for multiple, welcome banner for zero; throws on non-interactive + ambiguous |
| `desktop/src/version.ts` | Build-time-generated constant (`npm run gen:version` before every build) — Bun compiled binaries can't read package.json via `__dirname` so version is embedded at build |
| `desktop/scripts/install.sh` / `install.ps1` | curl/iwr one-liner installers — download prebuilt Bun binary (no Node required), SHA256-verified, API-resolver for `latest` that includes prereleases, version-aware pre/post-install readback |
| `desktop/scripts/uninstall.sh` / `uninstall.ps1` | 3-tier removal — default (binary + PATH), `--purge` (also wipes `~/.hermes/remote-sessions.json`), `--service` (stub for future service installers); Windows iex-safe env-var fallback |
| `desktop/README.md` | User-facing install + usage reference |
| **Desktop CLI — dev iteration** | |
| `npm run smoke` (in `desktop/`) | Builds Windows binary + runs `--version` / `--help` / `doctor`, fails loud on zero-output. Local pre-flight before cutting any tag. |
| `npm run gen:version` | Regenerates `src/version.ts` from `package.json`. Runs automatically before every `build` / `build:bin:*`. |
| `release-cli.yml → Smoke-test Linux binary` step | CI-side equivalent: runs compiled Linux binary through the same 3-command check before uploading assets. Catches silent-exit-0 + segfault classes. |
| **Server — Desktop tool routing (Phase B)** | |
| `plugin/relay/channels/desktop.py` | Mirrors `bridge.py` — `desktop.command`/`desktop.response`/`desktop.status`, UUID-correlated futures, 30s timeout, single-client MVP, per-session advertised-tools set |
| `plugin/tools/desktop_tool.py` | 24 `desktop_*` tools (fs/shell/powershell/process/jobs/transfer/health) — registers with `tools.registry` under `desktop` toolset; per-tool `check_fn` pings `/desktop/_ping?tool=<name>`; `desktop_health` is `_RELAY_ONLY` and pings `/desktop/health` so it works even when the client is wedged |
| **Gradle modules — experimental Quest/XR (in development)** | |
| `relay-core/` | [EXPERIMENTAL] Android library (`com.axiomlabs.hermesrelay.core`) — shared pairing/transport/terminal/voice/wire for the Quest port; not yet wired into the shipped `:app` |
| `relay-ui/` | [EXPERIMENTAL] Android library (`com.axiomlabs.hermesrelay.ui`) — shared Compose UI (sphere, terminal WebView, QR scanner) for the Quest port; carries its own sphere copy |
| `quest/` | [EXPERIMENTAL] Meta Spatial SDK Quest/XR app — gradle `includeBuild("quest")`; needs further development, not shipped |
| **Tooling — dev iteration (not shipped)** | |
| `ui-preview/` | Desktop Compose Hot Reload harness — JVM Compose for Desktop; source-shares `MorphingSphereCore` from `:relay-ui`; `Main.kt` gallery; see `ui-preview/README.md` |
| `app/src/test/.../screenshots/StoreScreenshotTest.kt` | Roborazzi host-side store/docs screenshot renderer — deterministic, no device, exact 1080×2160; reuses real components+chrome with mock data; `capture(name, themeId){…}` renders any view; see `docs/screenshot-automation.md` §Deterministic rendering (JDK-21 + no-plugin gotchas) |
| File | Why |
| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `docs/spec.md` | Full specification — protocol, UI layouts, phases, dependencies |
| `docs/decisions.md` | Architecture decisions — framework choice, channel design, auth model |
| `AGENTS.md` | Universal agent entry point — points here + the non-negotiables (standard-path, commits, writing hygiene) |
| `docs/mcp-tooling.md` | MCP server setup — android-tools-mcp + mobile-mcp; `android_*` tool usage patterns |
| **App — Core** | |
| `ui/RelayApp.kt` | Main scaffold (Scaffold + Compose nav); Chat is home — no mode strip, Manage/Bridge reached via Settings; `bottomBar` is a status pill, not a NavigationBar |
| `viewmodel/ChatViewModel.kt` | Chat orchestration — send, stream, cancel, slash commands |
| `viewmodel/ConnectionViewModel.kt` | Dual connection model (API + relay); `resolveStreamingEndpoint()`; derived `relayUiState` flow + `markPaired` hook stamp the active Connection |
| `viewmodel/RelayUiState.kt` | Shared sealed state for the relay row — 5 cases + `asBadgeState()` / `statusText()` extensions; 5s grace window before Stale |
| `network/HermesApiClient.kt` | Direct HTTP/SSE — `sendRunStream()`, `sendChatStream()`, `probeCapabilities()` |
| `network/GatewayChatClient.kt` | Gateway chat transport — JSON-RPC over dashboard `/api/ws` (tui_gateway); live `reasoning.delta`; fresh ws-ticket per connect; per-turn SSE fallback via `onPreflightFailure`; `prewarm()` (connect+resume off the send path); `setKeepAliveInBackground()` suppresses the 120s idle-close |
| `network/GatewayKeepAliveService.kt` | Opt-in `specialUse` foreground service (BOTH flavors; declared in main manifest; Play needs a Console FGS declaration) holding the process up so the gateway socket survives background/Doze; driven by ConnectionViewModel from the `KEY_GATEWAY_KEEP_ALIVE` toggle; stops on task-removal |
| `data/GatewayKeepAlivePrefs.kt` | Shared `KEY_GATEWAY_KEEP_ALIVE` pref key + `Context.setGatewayKeepAlive()` — used by ConnectionViewModel (StateFlow/setter) and the FGS Stop action |
| `network/GatewayEventMapper.kt` | Pure-JVM gateway event→callback mapping for one turn; unknown event types silently ignored; tui_gateway usage-key translation |
| `network/GatewayModels.kt` | `GatewayAvailability`, `ActiveTurnHandle`, `GatewayTurnCallbacks` (all members REQUIRED — forces dispatchOn main-thread wrap), `GatewayAsk`, `GatewaySubagentEvent`, `resolveStreamingEndpointPreference()` |
| `ui/components/ChatInputBar.kt` | Redesigned input bar — pill field, one trailing slot morphing Send/Voice/Stop/Steer/Queue, no slash button (long-press + opens palette) |
| `ui/components/SubagentLane.kt` | Per-taskIndex subagent progress lane — guide rail, compact tool rows, auto-collapse |
| `notifications/TurnCompleteNotifier.kt` | Turn-complete local notification when backgrounded — channel `chat_turn_complete`, cancel on resume, settings-gated |
| `network/ConnectionManager.kt` | WSS to relay with auto-reconnect; rebuilds OkHttpClient with fresh CertPinner on connect |
| `network/ChannelMultiplexer.kt` | Envelope routing by channel; `sendNotification()` for notification outbound |
| `network/handlers/ChatHandler.kt` | Chat message state, streaming events, tool annotation parser |
| `network/models/SessionModels.kt` | Session, message, SSE event data models |
| `data/FeatureFlags.kt` | Feature gating — DEV_MODE + DataStore overrides; `BuildFlavor` (googlePlay/sideload Tier flags) |
| **App — Auth** | |
| `auth/AuthManager.kt` | Wires SessionTokenStore + CertPinStore; parses auth.ok; `applyServerIssuedCodeAndReset()` |
| `auth/SessionTokenStore.kt` | Keystore (StrongBox) + EncryptedSharedPrefs fallback; lossless migration on upgrade |
| `auth/CertPinStore.kt` | TOFU cert pinning — SHA-256 SPKI per host:port in DataStore |
| `auth/PairedSession.kt` | PairedSession state + PairedDeviceInfo wire model |
| `data/Endpoint.kt` | `EndpointCandidate` / `ApiEndpoint` / `RelayEndpoint` — multi-endpoint pairing (ADR 24); `displayLabel()` for LAN/Tailscale/Public/Custom chips |
| `network/RelayHttpClient.kt` | OkHttp for /media, /sessions (list/revoke/extend), /health |
| **App — Bridge** | |
| `network/handlers/BridgeCommandHandler.kt` | Routes `bridge.command` → ActionExecutor; full path inventory + safety-rail integration |
| `viewmodel/BridgeViewModel.kt` | BridgeScreen VM — masterToggle, bridgeStatus, permissionStatus, activityLog |
| `bridge/BridgeSafetyManager.kt` | Blocklist + destructive-verb confirmation + auto-disable timer; fails-closed on /call and /send_sms |
| `data/BridgeSafetyPreferences.kt` | DataStore for blocklist, destructive verbs, auto-disable minutes, confirmation timeout |
| `ui/screens/BridgeScreen.kt` | Bridge UI — master → permission checklist → [Advanced] → unattended → safety → activity log (v0.4.1 reorder) |
| `ui/components/UnattendedAccessRow.kt` | Unattended toggle card (sideload); `enabled=masterEnabled`; inline `KeyguardDetectedAlert` |
| `ui/components/UnattendedGlobalBanner.kt` | 28dp amber strip at scaffold top when master+unattended on (sideload); tap → Bridge tab |
| `bridge/BridgeStatusOverlay.kt` | WindowManager overlay; `ConfirmationOverlayHost`; requires `SavedStateRegistryOwner` init order (CREATED→restore→RESUMED) |
| `accessibility/HermesAccessibilityService.kt` | AccessibilityService subclass; `@Volatile instance` singleton for BridgeCommandHandler |
| `accessibility/ScreenReader.kt` | UI tree → ScreenContent; `findNodeBoundsByText()`, `findFocusedInput()` |
| `accessibility/ActionExecutor.kt` | Gesture/text dispatch via GestureDescription + ACTION_SET_TEXT; pressKey maps vocab only |
| **App — Voice** | |
| `voice/VoiceViewModel.kt` | Voice turn state machine; TTS queue; `ignoreAssistantId`; `errorEvents: SharedFlow` |
| `audio/VoiceRecorder.kt` | MediaRecorder wrapper; perceptual amplitude curve; `.m4a` at 16kHz/64kbps |
| `audio/VoicePlayer.kt` | Media3 ExoPlayer (gapless TTS queue) + Visualizer; amplitude StateFlow; `awaitCompletion()` via coroutine; `audioSessionId` is a thread-safe `@Volatile` cache |
| `network/RelayVoiceClient.kt` | OkHttp for `/voice/transcribe`, `/synthesize`, `/config` |
| `voice/VoiceBridgeIntentHandler.kt` | Interface routing voice utterances to bridge; impls per flavor via factory |
| `voice/VoiceIntentClassifier.kt` | Regex phone-control classifier (sideload only); false-negatives preferred over false-positives |
| `ui/components/VoiceModeOverlay.kt` | Full-screen voice UI — MorphingSphere + VoiceWaveform + mic button |
| `ui/components/MorphingSphere.kt` | Compose renderer for the agent sphere — delegates math to `MorphingSphereCore` |
| `ui/components/MorphingSphereCore.kt` | Platform-agnostic sphere algorithm (`kotlin.math` only) — single source of truth; mirrored byte-for-byte in `preview/web/sphere.js` |
| `preview/web/` | Zero-dep browser harness — live `index.html` preview + `parity-check.mjs`; paired with `MorphingSphereCoreParityTest` (JVM) for struct/full checksum diffing |
| `user-docs/.vitepress/theme/components/SphereMark.vue` | Docs-site sphere embed — imports `preview/web/sphere.js` directly; autonomous fbm drift + pointer-proximity gaze/state blend; `<ClientOnly>` + `IntersectionObserver` + `prefers-reduced-motion` aware |
| **App — Media + Notifications** | |
| `util/MediaCacheWriter.kt` | `cacheDir/hermes-media/` LRU writer; returns FileProvider URIs |
| `util/MediaSaver.kt` | Save/share/open for chat media — MediaStore scoped-storage save (Pictures/Download `Hermes-Relay`, no perms on API 29+; pre-Q → share sheet); FileProvider share staging; remote-byte fetch; magic-byte image-MIME sniff for correct extensions |
| `ui/components/ChatImageViewer.kt` | Full-screen image viewer — pinch-zoom/pan (`detectTransformGestures`), double-tap 1×/2.5×, Share/Save/Close; `ChatImageViewerSource` decouples Coil-model/bitmap display from a suspend `bytesProvider` so Save keeps original bytes |
| `ui/components/InboundAttachmentCard.kt` | Discord-style attachment card for images/video/audio/pdf/text/generic; image tap → ChatImageViewer, file card long-press → Open/Share/Save menu |
| `ui/components/ChatImageContent.kt` | Parses `![alt](src)` out of assistant content; remote http(s) → Coil (tap → ChatImageViewer), server-local/failed → inline "can't render" notice with the path |
| `data/HermesCard.kt` | `CARD:{json}` envelope (ADR 26) — type/accent/fields/actions; kotlinx.serialization |
| `ui/components/HermesCardBubble.kt` | Rich-card renderer — accent stripe + FlowRow actions + dispatch stamp collapse |
| `viewmodel/CardDispatchSyncBuilder.kt` | Twin of VoiceIntentSyncBuilder — synthesizes card dispatches as `hermes_card_action` OpenAI pairs for session memory |
| `notifications/HermesNotificationCompanion.kt` | NotificationListenerService; cold-start buffer (50); forwards via ChannelMultiplexer |
| `util/RelayErrorClassifier.kt` | `classifyError(Throwable, context) → HumanError`; used by Voice/Chat/Connection |
| `util/TurnLatencyTracer.kt` | One `TurnLatency` INFO line per chat turn — `warm/cold` + `connect/session/submit/ttfe/ttft/done@…ms`; gateway + 3 SSE paths use it for desktop-comparable latency diagnosis; durations only |
| **Relay — Server** | |
| `plugin/relay/server.py` | Canonical relay — WSS + HTTP routes; bridge, media, voice, session, pairing handlers. `handle_pairing_mint` mirrors `pair.py:762` — top-level = API server, `relay.{url,code}` nested |
| `plugin/relay/auth.py` | PairingManager, SessionManager, RateLimiter; `math.inf` for never-expire |
| `plugin/relay/channels/bridge.py` | Bridge handler — `handle_command()` mints request_id, awaits response, 30s timeout |
| `plugin/relay/channels/notifications.py` | Bounded deque (100) of notification metadata; in-memory only |
| `plugin/relay/media.py` | MediaRegistry — LRU token store; `strict_sandbox` off by default for `/media/by-path` |
| `plugin/relay/voice.py` | Voice endpoints — transcribe, synthesize, voice_config; lazy tool imports |
| `plugin/relay/qr_sign.py` | HMAC-SHA256 QR signing; secret at `~/.hermes/hermes-relay-qr-secret`; canonical form preserves `endpoints` array order + role strings verbatim (ADR 24) |
| `plugin/relay/tailscale.py` | First-class Tailscale helper (ADR 25) — `status()` / `enable(port)` / `disable(port)` / `canonical_upstream_present()`; safe-absent via shell-out to `tailscale` CLI |
| `plugin/relay/_env_bootstrap.py` | Loads `~/.hermes/.env` before relay imports; called from both entry points |
| **Plugin — Tools + Installer** | |
| `plugin/tools/android_tool.py` | 18 `android_*` tool handlers (14 baseline + send_sms, call, search_contacts, return_to_hermes); `android_screenshot` first consumer of `register_media()` |
| `plugin/tools/android_navigate.py` | Vision-driven navigation loop; up to 20 iterations; `llm_gap` error until vision client wired |
| `plugin/pair.py` | QR payload builder + CLI; `build_payload(sign=True)`; `--register-code` fallback |
| `plugin/doctor.py` | `hermes relay doctor`; checks standard upstream API/dashboard reachability, Relay loopback state, plugin layout, and compat hook state |
| `plugin/compat.py` | `hermes relay compat status/install/remove`; owns the optional `hermes_relay_bootstrap.pth` lifecycle |
| `plugin/hermes_relay_bootstrap/` | Plugin-owned runtime compatibility patch — compat-only surfaces (session search, memory, skill detail/toggle, config, available-models, slash middleware); sessions + skills-list injection retired (#33134/#33016) |
| `install.sh` | Canonical installer — 6 steps; idempotent; drops `hermes-relay-update` shim |
| `uninstall.sh` | Canonical uninstaller; reverses install.sh; never touches `.env` or `state.db` |
| `hermes_relay_bootstrap/` | Legacy import shim for old `.pth` files and editable installs |
| **Plugin — Dashboard** | |
| `plugin/dashboard/manifest.json` | Declares tab, entry bundle, and FastAPI module for hermes-agent discovery |
| `plugin/dashboard/plugin_api.py` | FastAPI router proxying 5 routes to relay over loopback; `/pairing` body = API-server overrides (host/port/tls/api_key), relay URL auto-derived |
| `plugin/dashboard/src/index.jsx` | React root registering `hermes-relay` plugin with 4-tab shell |
| `plugin/dashboard/dist/index.js` | Committed IIFE bundle loaded verbatim by dashboard |
| **Desktop CLI** | |
| `desktop/package.json` | `@hermes-relay/cli` package manifest — Node ≥21, one `hermes-relay` bin, pre-built dist |
| `desktop/bin/hermes-relay.js` | Tiny shim: `import('../dist/cli.js').then(m => m.main())` + error surfacing |
| `desktop/src/chatAttach.ts` | captureClipboardImage / captureScreenshot / readImageFile; ships base64 to server via `image.attach.bytes` RPC before next prompt.submit |
| `desktop/src/cli.ts` | argv parser + subcommand dispatcher — bare → `shell` (PTY), positional-only → `chat`; command-scoped `--help` falls through to each command |
| `desktop/src/lib/theme.ts` | Shared ANSI palette + `colorEnabled()` + `Theme` (semantic helpers, `statusDot`) — single visual language; `--no-color`/`NO_COLOR`/TTY aware |
| `desktop/src/lib/table.ts` | Zero-dep column-aligned table renderer (ANSI-width aware, last column flexes to terminal width) — used by devices/sessions/audit |
| `desktop/src/lib/spinner.ts` | Stderr braille spinner for slow ops (pair probe, gateway connect); no-op when piped/quiet/json |
| `desktop/src/lib/usage.ts` | `UsageSpec` + `renderUsage`/`printUsage`/`unknownSubcommand` — per-subcommand `--help` + self-documenting sub-verb fallback |
| `desktop/src/lib/hints.ts` | `suggestedFix(err, ctx)` → next-step command (re-pair on auth fail, etc.); `formatError` renders error + hint |
| `desktop/src/lib/logo.ts` | Slim box-drawing "Hermes Relay" wordmark; shown atop `--help`, first-run welcome, REPL header, and `hermes-relay logo`; theme/no-color aware |
| `desktop/src/lib/auditLog.ts` | Local desktop-tool audit JSONL (`~/.hermes/desktop-audit.jsonl`); router appends per dispatch; backs `audit` command (relay's ring is loopback-only) |
| `desktop/src/lib/daemonStatus.ts` | Daemon heartbeat file (`~/.hermes/daemon-status.json`) + `isPidAlive` liveness; backs `daemon --status` |
| `desktop/src/commands/audit.ts` | `hermes-relay audit` — tails the local audit log into a table (WHEN/TOOL/STATUS/DETAIL); `--limit`, `--json` |
| `desktop/src/commands/relay.ts` | `hermes-relay relay info/security/context/queue` — relay-server management surface; info/security/queue loopback-only, context works remote with bearer; `queue` lists/cancels the agent→phone outbound buffer (`--clear` / `--cancel <id>`) |
| `desktop/src/commands/chat.ts` | REPL + one-shot + piped-stdin; `runOneTurn` returns `{promise, cancel}` for safe SIGINT; auto-wires `DesktopToolRouter` when consented |
| `desktop/src/commands/shell.ts` | Pipes the `terminal` relay channel to raw-mode stdin/stdout; post-attach `exec hermes` 350ms after tmux settles; `Ctrl+A .` detach / `Ctrl+A k` kill / `Ctrl+A Ctrl+A` literal |
| `desktop/src/commands/pair.ts` | Either 6-char code + `--remote`, or full v3 QR via `--pair-qr` — probes + picks endpoint, records role; `--grant-tools` (TTY prompt) / `--auto-grant-tools` (silent) stamp `toolsConsented` so `daemon` works without a `shell` round-trip |
| `desktop/src/commands/tools.ts` | `tools.list` RPC → enabled/available toolsets; `--verbose` lists individual tools |
| `desktop/src/commands/status.ts` | Local read of `~/.hermes/remote-sessions.json`; renders `grants:` + `expires:` + `route:`; `--json` redacts tokens, `--reveal-tokens` opts in |
| `desktop/src/commands/devices.ts` | Server-side session management — `GET/DELETE/PATCH /sessions` via `fetch` over http(s)://host:port; `list` / `revoke <prefix>` / `extend <prefix> --ttl <s>` |
| `desktop/src/banner.ts` | `buildConnectBanner({url, meta, endpointRole})` → "Connected via LAN (plain) — server 0.6.0"; `humanExpiry()` for TTL formatting |
| `desktop/src/endpoint.ts` | `EndpointCandidate` / `EndpointRole` types + `displayLabel()` — mirrors Android `data/Endpoint.kt` |
| `desktop/src/pairingQr.ts` | `decodePairingPayload` (JSON or base64), `payloadToCandidates` (v3 verbatim / v1–v2 synthesized), `probeCandidatesByPriority` (`Promise.any` within tier, `AbortSignal.any`, 4s timeout, 60s cache) |
| `desktop/src/certPin.ts` | `extractSpkiSha256(der)` via `crypto.X509Certificate` + `publicKey.export({type:'spki'})`; `pinKey(url)`, `comparePins()`, `isSecureUrl()` |
| `desktop/src/tools/router.ts` | `DesktopToolRouter.attach(relay)` — `onChannel('desktop')` dispatch under 30s `AbortController`; heartbeat enriched with host/platform/version/uptime_ms + sticky `last_error` for `desktop_health` |
| `desktop/src/tools/handlerSet.ts` | Single source of truth for the desktop tool map — `DESKTOP_HANDLERS` + `DESKTOP_ADVERTISED_TOOLS`; consumed by `chat.ts` / `shell.ts` / `daemon.ts` so adding a tool is a one-file change |
| `desktop/src/tools/consent.ts` | `ensureToolsConsent(url)` — stored per-URL in `toolsConsented`; TTY prompt; non-TTY fails closed |
| `desktop/src/tools/handlers/fs.ts` | `readFileHandler` / `writeFileHandler` / `patchHandler` — strict unified-diff applier, no fuzz |
| `desktop/src/tools/handlers/terminal.ts` | `bash -lc` / `cmd /c`, SIGKILL on timeout or abort, returns `{stdout, stderr, exit_code, duration_ms}` |
| `desktop/src/tools/handlers/powershell.ts` | Spawns `pwsh`/`powershell` directly with `-Command -`, script piped via stdin — no cmd.exe quote-mangling; auto-picks pwsh &gt; powershell |
| `desktop/src/tools/handlers/process.ts` | `spawn_detached` (unref'd, returns pid+log_path), `list_processes` (tasklist /FO CSV — no /V to dodge window-title latency), `kill_process`, `find_pid_by_port` (netstat/lsof/ss) |
| `desktop/src/tools/handlers/jobs.ts` | Job API — `~/.hermes/desktop-jobs/<id>/{stdout.log, stderr.log, meta.json}` is source of truth across daemon restarts; `taskkill /T` on Windows so build trees die fully |
| `desktop/src/tools/handlers/transfer.ts` | `copy_directory` via `fs.cp`, `zip`/`unzip` via tar &gt; zip &gt; PowerShell probe, `checksum` streamed (sha256/sha1/md5) |
| `desktop/src/tools/handlers/search.ts` | ripgrep with pure-Node fallback, skips `.git`/`node_modules`/`dist`/`.next`/`.cache` |
| `desktop/src/renderer.ts` | Streams `message.delta` → stdout, tool events → decorated lines; NO_COLOR / --json / --quiet aware |
| `desktop/src/pairing.ts` | readline-based 6-char prompt (`A-Z0-9`); headless mirror of TUI's Ink prompt; `validatePairingPayloadString` discriminated-union wrapper |
| `desktop/src/credentials.ts` | Precedence: `--token` → `--pair-qr` (probe+pair) → `--code` → stored → prompt; returns `Credentials{sessionToken?, pairingCode?, resolvedEndpoint?}` |
| `desktop/src/transport/RelayTransport.ts` | Fork of ui-tui's transport + reconnect state machine (`idle/connecting/connected/reconnecting`, exp backoff 1→30s, 5min on 429, gate re-check post-sleep) + pre-WS TLS probe for TOFU |
| `desktop/src/remoteSessions.ts` | Same file path as TUI (`~/.hermes/remote-sessions.json`, 0600); schema widened with `grants`, `ttlExpiresAt`, `endpointRole`, `toolsConsented`; `saveSession` back-compat overload |
| `desktop/src/commands/daemon.ts` | Headless WSS + tool router for always-on access; JSON-line logs; fails closed on missing consent unless `--allow-tools` with explicit `--token` |
| `desktop/src/commands/doctor.ts` | Local-only diagnostic report — version / binary path / PATH / sessions / daemon detection; `--json` for support-paste; omits tokens entirely |
| `desktop/src/relayUrlPrompt.ts` | First-run URL fallback — `resolveFirstRunUrl()` auto-picks single stored session, numbered picker for multiple, welcome banner for zero; throws on non-interactive + ambiguous |
| `desktop/src/version.ts` | Build-time-generated constant (`npm run gen:version` before every build) — Bun compiled binaries can't read package.json via `__dirname` so version is embedded at build |
| `desktop/scripts/install.sh` / `install.ps1` | curl/iwr one-liner installers — download prebuilt Bun binary (no Node required), SHA256-verified, API-resolver for `latest` that includes prereleases, version-aware pre/post-install readback |
| `desktop/scripts/uninstall.sh` / `uninstall.ps1` | 3-tier removal — default (binary + PATH), `--purge` (also wipes `~/.hermes/remote-sessions.json`), `--service` (stub for future service installers); Windows iex-safe env-var fallback |
| `desktop/README.md` | User-facing install + usage reference |
| **Desktop CLI — dev iteration** | |
| `npm run smoke` (in `desktop/`) | Builds Windows binary + runs `--version` / `--help` / `doctor`, fails loud on zero-output. Local pre-flight before cutting any tag. |
| `npm run gen:version` | Regenerates `src/version.ts` from `package.json`. Runs automatically before every `build` / `build:bin:*`. |
| `release-cli.yml → Smoke-test Linux binary` step | CI-side equivalent: runs compiled Linux binary through the same 3-command check before uploading assets. Catches silent-exit-0 + segfault classes. |
| **Server — Desktop tool routing (Phase B)** | |
| `plugin/relay/channels/desktop.py` | Mirrors `bridge.py` — `desktop.command`/`desktop.response`/`desktop.status`, UUID-correlated futures, 30s timeout, single-client MVP, per-session advertised-tools set |
| `plugin/tools/desktop_tool.py` | 24 `desktop_*` tools (fs/shell/powershell/process/jobs/transfer/health) — registers with `tools.registry` under `desktop` toolset; per-tool `check_fn` pings `/desktop/_ping?tool=<name>`; `desktop_health` is `_RELAY_ONLY` and pings `/desktop/health` so it works even when the client is wedged |
| **Gradle modules — experimental Quest/XR (in development)** | |
| `relay-core/` | [EXPERIMENTAL] Android library (`com.axiomlabs.hermesrelay.core`) — shared pairing/transport/terminal/voice/wire for the Quest port; not yet wired into the shipped `:app` |
| `relay-ui/` | [EXPERIMENTAL] Android library (`com.axiomlabs.hermesrelay.ui`) — shared Compose UI (sphere, terminal WebView, QR scanner) for the Quest port; carries its own sphere copy |
| `quest/` | [EXPERIMENTAL] Meta Spatial SDK Quest/XR app — gradle `includeBuild("quest")`; needs further development, not shipped |
| **Tooling — dev iteration (not shipped)** | |
| `ui-preview/` | Desktop Compose Hot Reload harness — JVM Compose for Desktop; source-shares `MorphingSphereCore` from `:relay-ui`; `Main.kt` gallery; see `ui-preview/README.md` |
| `app/src/test/.../screenshots/StoreScreenshotTest.kt` | Roborazzi host-side store/docs screenshot renderer — deterministic, no device, exact 1080×2160; reuses real components+chrome with mock data; `capture(name, themeId){…}` renders any view; see `docs/screenshot-automation.md` §Deterministic rendering (JDK-21 + no-plugin gotchas) |
## What NOT to Do
@@ -339,15 +365,18 @@ This is a **public, distributed repo** — every committed file (CHANGELOG, DEVL
- **Don't put documentation in root** — long-form docs go in `docs/`
- **Don't forget DEVLOG.md** — update it (record *what happened*)
- **Don't bury follow-ups** — deferred work / known gaps go in `TODO.md`, never in DEVLOG or one-off code/doc comments
- **Don't touch production / remote hosts** — automation and orchestrated agents must NEVER SSH into, deploy to, pull/restart/reconfigure, or push code to a live/remote Hermes host. Building, on-device testing, and server deployment are owner-driven (see Server Deployment). Stop at committing on your branch; surface "this needs a deploy/on-device check" rather than doing it.
## MCP Tooling
Two MCP servers are configured for AI-assisted development. See `docs/mcp-tooling.md` for full reference.
| Server | Layer | Requires |
|--------|-------|----------|
| Server | Layer | Requires |
| ------------------- | --------------------------------------------------------------- | ---------------------------------------- |
| `android-tools-mcp` | IDE/Build — Compose previews, Gradle, code search, Android docs | Android Studio running with project open |
| `mobile-mcp` | Device/Runtime — tap, swipe, screenshot, app management | ADB + connected device/emulator |
| `mobile-mcp` | Device/Runtime — tap, swipe, screenshot, app management | ADB + connected device/emulator |
## Dev Workflow
@@ -378,7 +407,7 @@ Curls every bridge HTTP route via `localhost:8767`. Catches the silent-drop regr
2. **Python syntax check** — `python -m py_compile plugin/<file>.py`. Full tests run on the server.
3. **Kotlin changes** — do NOT run `gradle build`. Bailey builds via Android Studio's ▶ button. Never `adb install` from Claude.
4. **Before pushing Kotlin changes** — run `./gradlew lint` locally. It's the exact task CI runs and catches errors Android Studio's live inspections miss — e.g. `UnsafeOptInUsageError` with `kotlin.OptIn` vs `androidx.annotation.OptIn`, `FlowOperatorInvokedInComposition` (mapped flows inside Composables), Media3 `@UnstableApi` propagation. Android CI runs lint alongside build/test for faster feedback, but a local lint run still surfaces issues before the workflow spends runner time compiling and packaging.
5. **Commit + push** — feature branch off `dev`, merged back to `dev` via PR. `main` is reserved for release merges.
5. **Commit + push** — follow `AGENTS.md` and `RELEASE.md`; normal work PRs to `dev`.
6. **Pull + restart on server** — see Server Deployment below.
7. **Test on phone** — Bailey builds from Studio, installs to Samsung device, pairs via `/hermes-relay-pair`.
@@ -386,96 +415,105 @@ Curls every bridge HTTP route via `localhost:8767`. Catches the silent-drop regr
Server is a Linux box running hermes-agent with hermes-relay editable-installed (`pip install -e`). Sensitive details (IP, user, secrets) in `~/SYSTEM.md` on the server — not in this repo.
| What | Where |
|---|---|
| hermes-agent repo | `~/.hermes/hermes-agent/` |
| hermes-relay clone | `~/.hermes/hermes-relay/` |
| Plugin symlink | `~/.hermes/plugins/hermes-relay` → `~/.hermes/hermes-relay/plugin` |
| Config | `~/.hermes/config.yaml` + `~/.hermes/.env` |
| Relay log | `journalctl --user -u hermes-relay -f` |
| What | Where |
| ------------------ | ------------------------------------------------------------------ |
| hermes-agent repo | `~/.hermes/hermes-agent/` |
| hermes-relay clone | `~/.hermes/hermes-relay/` |
| Plugin symlink | `~/.hermes/plugins/hermes-relay` → `~/.hermes/hermes-relay/plugin` |
| Config | `~/.hermes/config.yaml` + `~/.hermes/.env` |
| Relay log | `journalctl --user -u hermes-relay -f` |
**Update:** `hermes-relay-update` (idempotent, re-fetches install.sh). Or manually: `git pull --ff-only && systemctl --user restart hermes-relay`.
**Compat hook:** `hermes relay compat status/install/remove` manages only the
optional `hermes_relay_bootstrap.pth` startup hook. New installs load the
plugin-owned bootstrap from `plugin/hermes_relay_bootstrap/`; the repo-root
package is only a legacy import shim. Vanilla Hermes chat, Manage, and dashboard voice
must not depend on this hook.
**Key conventions:**
- Phone re-pairs after each relay restart (SessionManager is in-memory; wiped on restart)
- Phone pairing **survives** relay restart — `SessionManager` persists sessions to `~/.hermes/hermes-relay-sessions.json` (`server.py:88-90`, `persistence_path` from `RelayConfig.from_env`); a trusted-device refresh token recovers a lost/revoked/reset session without a new QR scan. (Only the in-memory *live-connection presence* clears on restart; the phone reconnects automatically.)
- Use `python -m unittest` not `pytest` — conftest imports `responses` which may not be installed
- `_env_bootstrap.py` loads `~/.hermes/.env` on every relay start — no stale API keys
### Where Python vs. Kotlin changes land
| Change type | Who restarts? | Command |
|---|---|---|
| Plugin tool (`android_tool.py` etc.) | `hermes-gateway.service` | `systemctl --user restart hermes-gateway` |
| Relay code (`plugin/relay/*.py`) | `hermes-relay.service` | `systemctl --user restart hermes-relay` |
| Pair CLI / skill files | — | No restart — fresh process / scanned on invocation |
| Android app | Bailey (Studio) | Studio run button |
| Change type | Who restarts? | Command |
| ------------------------------------ | ------------------------ | -------------------------------------------------- |
| Plugin tool (`android_tool.py` etc.) | `hermes-gateway.service` | `systemctl --user restart hermes-gateway` |
| Relay code (`plugin/relay/*.py`) | `hermes-relay.service` | `systemctl --user restart hermes-relay` |
| Pair CLI / skill files | — | No restart — fresh process / scanned on invocation |
| Android app | Bailey (Studio) | Studio run button |
### Release Process
See [RELEASE.md](RELEASE.md) for the full recipe.
- **Android version source:** `gradle/libs.versions.toml` (`appVersionName`, `appVersionCode`); bump with `scripts/bump-android-version.sh`
- **Relay plugin version source:** `pyproject.toml`; keep plugin/dashboard metadata synced with `scripts/check-plugin-version-sync.py`; bump with `scripts/bump-plugin-version.sh`
- **Desktop CLI version source:** `desktop/package.json`; regenerate `desktop/src/version.ts` with `npm run gen:version`
- **Track audit:** `python scripts/check-version-tracks.py` reports Android, plugin, and CLI versions without forcing them to match
- **`appVersionCode` is monotonic** — always increment across Android prereleases
- **Cut a release:** bump the target surface → commit → merge `dev` to `main` → tag with `android-v*`, `plugin-v*`, or `cli-v*` → push tag → CI builds + GitHub Release
- **Required secrets:** `HERMES_KEYSTORE_BASE64`, `HERMES_KEYSTORE_PASSWORD`, `HERMES_KEY_ALIAS`, `HERMES_KEY_PASSWORD`
See [AGENTS.md](AGENTS.md) for the canonical branch contract and
[RELEASE.md](RELEASE.md) for version sources, release trains, surface tags,
hotfixes, secrets, publishing, and verification. Claude-specific automation
must not infer release authority from feature completion.
## Integration Points
| Surface | Endpoint | Notes |
|---------|----------|-------|
| Chat (gateway) | Dashboard `POST /api/auth/ws-ticket` -> WS `/api/ws` | Vanilla Hermes dashboard/tui_gateway path; live thinking/reasoning; requires dashboard auth |
| Chat streaming | `POST /v1/runs` → `GET /v1/runs/{id}/events` | Structured tool events; async run-control path |
| Chat (sessions) | `POST /api/sessions/{id}/chat/stream` | Native upstream session-persisted SSE; preferred when capability probe finds it |
| Chat (compat) | `POST /v1/chat/completions` (stream=true) | Inline tool annotations only |
| Session CRUD | `GET/POST/PATCH/DELETE /api/sessions` | Native upstream (#33134); bootstrap fallback only for old builds |
| Manage | Dashboard `/api/status`, `/api/auth/me`, `/api/config`, `/api/profiles/*`, `/api/env`, `/api/model/*`, `/api/mcp/*` | Vanilla Hermes dashboard surface; do not proxy through Relay |
| Vanilla Hermes voice | Dashboard `POST /api/audio/transcribe`, `POST /api/audio/speak` | Vanilla Hermes no-plugin voice; uses dashboard session from Manage |
| Pairing (QR) | `POST /pairing/register` (loopback only) | Via `/hermes-relay-pair` or `hermes-pair` shim; accepts optional `endpoints` for multi-endpoint QRs |
| Pairing (multi-endpoint) | QR `endpoints` array (ADR 24) | `hermes: 3` schema; ordered `lan`/`tailscale`/`public`/... candidates; phone re-probes on network change |
| Pairing auth | WSS `auth.ok` payload | Includes `expires_at`, `grants`, `transport_hint` |
| Tailscale Serve (ADR 25) | `hermes-relay-tailscale enable\|disable\|status` CLI | Fronts loopback `:8767` with `tailscale serve --bg --https=<port>`; auto-retires on upstream PR #9295 |
| Inbound media (token) | `GET /media/{token}` | Bearer auth; 24h TTL |
| Inbound media (path) | `GET /media/by-path?path=<abs>` | Permissive by default; `RELAY_MEDIA_STRICT_SANDBOX=1` to restrict |
| Session management | `GET /sessions`, `DELETE /sessions/{prefix}`, `PATCH /sessions/{prefix}` | List/revoke/extend; RelayHttpClient |
| Voice transcribe | `POST /voice/transcribe` | multipart/form-data; bearer auth |
| Voice synthesize | `POST /voice/synthesize` | JSON → audio/mpeg; max 5000 chars |
| Voice config | `GET /voice/config` | Returns current tts/stt provider info |
| Plugin diagnostics | `hermes relay doctor --json` | Reports upstream route reachability, Relay loopback state, plugin layout, and legacy bootstrap state |
| Compat hook lifecycle | `hermes relay compat status/install/remove` | Optional legacy API compatibility hook; not required for the standard path |
| Notifications | `GET /notifications/recent?limit=N` | Loopback callers skip bearer |
| Relay health | `GET /health` on `:8767` | Used by `RelayHttpClient.probeHealth()` |
| Capabilities | `GET /v1/capabilities` plus targeted `HEAD` probes | Prefer capabilities when present; HEAD probes keep mixed-version fallback working |
| Desktop CLI (tui channel) | WSS `tui.attach` / `tui.rpc.request` / `tui.rpc.event` | Same channel + envelopes as the Ink TUI — the CLI just renders events as plain lines. Zero server changes. |
| Desktop CLI (terminal channel) | WSS `terminal.attach` / `terminal.input` / `terminal.output` / `terminal.resize` / `terminal.detached` | Existing channel (shared with Android). CLI `shell` subcommand attaches, injects `clear; exec hermes\n` 350ms after ack, pipes raw bytes. `Ctrl+A .` detaches (tmux preserved), `Ctrl+A k` kills. |
| Desktop CLI tool visibility | `tools.list` RPC on the shared tui channel | Returns `{toolsets: [{name, description, tool_count, enabled, tools:[]}]}`; surfaced by `hermes-relay tools` |
| Desktop CLI devices | HTTP `GET/DELETE/PATCH /sessions` on the relay's same port | Wrapped by `hermes-relay devices list | revoke <prefix> | extend <prefix> --ttl <s>`; bearer token from stored session; token prefix only (never full token) |
| Desktop tool routing (Phase B) | WSS `desktop.command` (s→c) + `desktop.response` (c→s) + `desktop.status` (c→s heartbeat) | New channel. Hermes calls `desktop_read_file(path)` → Python handler POSTs to `/desktop/desktop_read_file` → relay forwards over `desktop.command` → Node client's `DesktopToolRouter` runs the handler locally → response bubbles back. Mirror of Android's `bridge.command` pattern. |
| Desktop tool check_fn | HTTP `GET /desktop/_ping?tool=<name>` | Returns 200 if a client is connected AND advertises this tool; 503 otherwise. Hermes uses this to fail the tool quickly when no desktop client is live, instead of waiting 30s for the dispatch timeout. |
| Desktop health | HTTP `GET /desktop/health` | Returns full status snapshot — connected/host/platform/version/pid/uptime/advertised_tools/last_error/recent_commands. Loopback-only. Backs the `desktop_health` agent tool, which intentionally does NOT round-trip through the client so it remains callable when other tools are wedged. |
| Surface | Endpoint | Notes |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chat (gateway) | Dashboard `POST /api/auth/ws-ticket` -&gt; WS `/api/ws` | Vanilla Hermes dashboard/tui_gateway path; live thinking/reasoning; requires dashboard auth |
| Chat streaming | `POST /v1/runs` → `GET /v1/runs/{id}/events` | Structured tool events; async run-control path |
| Chat (sessions) | `POST /api/sessions/{id}/chat/stream` | Native upstream session-persisted SSE; preferred when capability probe finds it |
| Chat (compat) | `POST /v1/chat/completions` (stream=true) | Inline tool annotations only |
| Session CRUD | `GET/POST/PATCH/DELETE /api/sessions` | Native upstream (#33134); bootstrap fallback retired |
| Manage | Dashboard `/api/status`, `/api/auth/me`, `/api/config`, `/api/profiles/*`, `/api/env`, `/api/model/*`, `/api/mcp/*` | Vanilla Hermes dashboard surface; do not proxy through Relay |
| Vanilla Hermes voice | Dashboard `POST /api/audio/transcribe`, `POST /api/audio/speak` | Vanilla Hermes no-plugin voice; uses dashboard session from Manage |
| Pairing (QR) | `POST /pairing/register` (loopback only) | Via `/hermes-relay-pair` or `hermes-pair` shim; accepts optional `endpoints` for multi-endpoint QRs |
| Pairing (multi-endpoint) | QR `endpoints` array (ADR 24) | `hermes: 3` schema; ordered `lan`/`tailscale`/`public`/... candidates; phone re-probes on network change |
| Pairing auth | WSS `auth.ok` payload | Includes `expires_at`, `grants`, `transport_hint` |
| Tailscale Serve (ADR 25) | `hermes-relay-tailscale enable|disable|status` CLI | Fronts loopback `:8767` with `tailscale serve --bg --https=<port>`; auto-retires on upstream PR #9295 |
| Inbound media (token) | `GET /media/{token}` | Bearer auth; 24h TTL |
| Inbound media (path) | `GET /media/by-path?path=<abs>` | Permissive by default; `RELAY_MEDIA_STRICT_SANDBOX=1` to restrict |
| Session management | `GET /sessions`, `DELETE /sessions/{prefix}`, `PATCH /sessions/{prefix}` | List/revoke/extend; RelayHttpClient |
| Voice transcribe | `POST /voice/transcribe` | multipart/form-data; bearer auth |
| Voice synthesize | `POST /voice/synthesize` | JSON → audio/mpeg; max 5000 chars |
| Voice config | `GET /voice/config` | Returns current tts/stt provider info |
| Plugin diagnostics | `hermes relay doctor --json` | Reports upstream route reachability, Relay loopback state, plugin layout, and legacy bootstrap state |
| Compat hook lifecycle | `hermes relay compat status/install/remove` | Optional legacy API compatibility hook; not required for the standard path |
| Notifications | `GET /notifications/recent?limit=N` | Loopback callers skip bearer |
| Relay health | `GET /health` on `:8767` | Used by `RelayHttpClient.probeHealth()` |
| Capabilities | `GET /v1/capabilities` plus targeted `HEAD` probes | Prefer capabilities when present; HEAD probes keep mixed-version fallback working |
| Desktop CLI (tui channel) | WSS `tui.attach` / `tui.rpc.request` / `tui.rpc.event` | Same channel + envelopes as the Ink TUI — the CLI just renders events as plain lines. Zero server changes. |
| Desktop CLI (terminal channel) | WSS `terminal.attach` / `terminal.input` / `terminal.output` / `terminal.resize` / `terminal.detached` | Existing channel (shared with Android). CLI `shell` subcommand attaches, injects `clear; exec hermes\n` 350ms after ack, pipes raw bytes. `Ctrl+A .` detaches (tmux preserved), `Ctrl+A k` kills. |
| Desktop CLI tool visibility | `tools.list` RPC on the shared tui channel | Returns `{toolsets: [{name, description, tool_count, enabled, tools:[]}]}`; surfaced by `hermes-relay tools` |
| Desktop CLI devices | HTTP `GET/DELETE/PATCH /sessions` on the relay's same port | Wrapped by `hermes-relay devices list |
| Desktop tool routing (Phase B) | WSS `desktop.command` (s→c) + `desktop.response` (c→s) + `desktop.status` (c→s heartbeat) | New channel. Hermes calls `desktop_read_file(path)` → Python handler POSTs to `/desktop/desktop_read_file` → relay forwards over `desktop.command` → Node client's `DesktopToolRouter` runs the handler locally → response bubbles back. Mirror of Android's `bridge.command` pattern. |
| Desktop tool check_fn | HTTP `GET /desktop/_ping?tool=<name>` | Returns 200 if a client is connected AND advertises this tool; 503 otherwise. Hermes uses this to fail the tool quickly when no desktop client is live, instead of waiting 30s for the dispatch timeout. |
| Desktop health | HTTP `GET /desktop/health` | Returns full status snapshot — connected/host/platform/version/pid/uptime/advertised_tools/last_error/recent_commands. Loopback-only. Backs the `desktop_health` agent tool, which intentionally does NOT round-trip through the client so it remains callable when other tools are wedged. |
## Upstream References
| Topic | Upstream File |
|-------|--------------|
| API endpoints | `gateway/platforms/api_server.py` — all registered HTTP routes |
| Platform adapter interface | `gateway/platforms/base.py` — `BasePlatformAdapter` abstract class |
| Adding a platform | `gateway/platforms/ADDING_A_PLATFORM.md` — 16-step checklist |
| Platform registration | `gateway/run.py` → `_create_adapter()`, `gateway/config.py` → `Platform` enum |
| Channel directory | `gateway/channel_directory.py` — how platforms/channels are enumerated |
| Send message routing | `tools/send_message_tool.py` → `platform_map` dict |
| SSE streaming (runs) | `gateway/platforms/api_server.py` → runs endpoint, `_on_tool_progress` |
| Topic | Upstream File |
| -------------------------- | ----------------------------------------------------------------------------- |
| API endpoints | `gateway/platforms/api_server.py` — all registered HTTP routes |
| Platform adapter interface | `gateway/platforms/base.py` — `BasePlatformAdapter` abstract class |
| Adding a platform | `gateway/platforms/ADDING_A_PLATFORM.md` — 16-step checklist |
| Platform registration | `gateway/run.py` → `_create_adapter()`, `gateway/config.py` → `Platform` enum |
| Channel directory | `gateway/channel_directory.py` — how platforms/channels are enumerated |
| Send message routing | `tools/send_message_tool.py` → `platform_map` dict |
| SSE streaming (runs) | `gateway/platforms/api_server.py` → runs endpoint, `_on_tool_progress` |
## Related Projects
- **[hermes-agent](https://github.com/NousResearch/hermes-agent)** — the agent platform (gateway, WebAPI, plugin system)
- **[android-tools-mcp](https://github.com/Codename-11/android-tools-mcp)** — our fork of Android Studio MCP bridge (Compose previews, Gradle, docs)
- **[mobile-mcp](https://github.com/mobile-next/mobile-mcp)** — device control MCP server (ADB, tap/swipe, screenshots)
- [**hermes-agent**](https://github.com/NousResearch/hermes-agent) — the agent platform (gateway, WebAPI, plugin system)
- [**android-tools-mcp**](https://github.com/Codename-11/android-tools-mcp) — our fork of Android Studio MCP bridge (Compose previews, Gradle, docs)
- [**mobile-mcp**](https://github.com/mobile-next/mobile-mcp) — device control MCP server (ADB, tap/swipe, screenshots)
+26 -27
View File
@@ -1,64 +1,63 @@
# Hermes-Relay-CLI v__VERSION__
**Release Date:** <!-- YYYY-MM-DD -->
**Since the previous CLI release:** <!-- one line: the theme of this release -->
**Release Date:** 2026-07-13
<!-- One short paragraph: what this desktop/CLI release is about and who should care. -->
This alpha makes the desktop direction explicit: Hermes-Relay is a real CLI/TUI with an optional Windows right-click systray—not a second desktop application. The old Tauri/WebView dashboard and its embedded windows are gone. The installed CLI remains the single source of behavior for pairing, TUI, daemon management, grants, audit, diagnostics, chat, voice, and tools.
<!--
═══ RELEASE-PREP CHECKLIST (delete this comment block when done) ═══
• This file is the GitHub Release body for `cli-v*` tags. The release workflow
substitutes __VERSION__ (bare, e.g. 0.3.0) and __TAG__ (full, e.g. cli-v0.3.0) —
leave those tokens in the Install section; do NOT hardcode versions there.
• Rewrite the Summary + the Added/Changed/Fixed groups from the CLI/desktop-relevant
bullets in CHANGELOG.md's promoted version block.
• Keep-a-Changelog rules: include only the groups that have entries; delete empty ones.
• Keep the "Experimental phase" notice until the CLI reaches GA.
• Scrub for public distribution (RELEASE.md §2): no personal names, no private infra,
no fork-branch plumbing, no AI self-narration.
═══════════════════════════════════════════════════════════════════
-->
**Experimental phase.** Assets are unsigned — Windows SmartScreen and macOS Gatekeeper will warn on first launch. Windows ships a tray installer as the primary desktop surface; CLI binaries remain available for terminal/headless use and for macOS/Linux.
**Experimental phase.** Assets are unsigned, so Windows SmartScreen and macOS Gatekeeper may warn on first launch. Standalone CLI binaries ship for Windows x64, Linux x64, and macOS x64/arm64; the optional native systray is Windows-only.
## What's changed
### Added
-
- **Persistent desktop-use control.** `hermes-relay computer-use status|enable|disable|cancel` stores one local preference, reports daemon privilege and active/pending grants, and can end an active task-scoped grant without relying on a GUI.
- **Headless grant review.** `hermes-relay grants` lists pending local computer-use requests and supports interactive review plus explicit `approve`, `reject`, and JSON forms for scripts.
- **Typed Relay chat option.** `chat --relay-chat` sends `chat.send` over WSS and renders typed `stream.event` v1 assistant, tool, artifact, memory, skill, and error lifecycles while preserving the existing gateway path as the default.
- **Release-parity verification.** One version contract now keeps the npm package, compiled CLI, Rust tray, lockfile, and installer metadata aligned. The Windows verification target covers TypeScript, compiled-binary smoke tests, Rust formatting/lint/check/tests, and installer packaging.
### Changed
-
- **Menu-only Windows systray.** The optional tray is a small native Rust process with no application window, WebView, overlay, embedded terminal, chat view, voice view, or settings dashboard. Interactive actions open the installed CLI in a normal terminal.
- **State- and privilege-aware daemon control.** The menu reports PID-backed daemon state and User/Administrator privilege, disables invalid lifecycle actions, and requests UAC only when **Start/Restart daemon as Administrator…** is explicitly chosen. The tray itself remains unprivileged.
- **Visible desktop-use safety.** The tray shows enablement, active grant mode and expiry, warns when an Administrator control grant is active, raises a native alert for pending approvals, opens CLI grant review, and provides immediate cancellation and emergency stop.
- **Per-user Windows installation.** The default PowerShell installer downloads the checksum-verified NSIS package, installs the CLI and optional tray under `~/.hermes/bin`, adds Start-menu shortcuts and user PATH, and can start the tray at sign-in. CLI-only installation remains available with `HERMES_RELAY_INSTALL_SURFACE=cli`.
### Fixed
-
- **Installed-binary diagnostics.** `hermes-relay doctor` reports the physical Bun-compiled executable instead of a virtual embedded-module path, so PATH and install-directory checks describe the binary that actually launched.
- **Release guardrails.** CLI tag automation rejects version drift, tags not contained in `main`, oversized tray binaries, or a tray process that creates an application window.
## Install
**Windows tray app (PowerShell):**
**Windows CLI + optional systray (PowerShell):**
```powershell
irm https://raw.githubusercontent.com/Codename-11/hermes-relay/main/desktop/scripts/install.ps1 | iex
```
**Windows CLI only:**
```powershell
$env:HERMES_RELAY_INSTALL_SURFACE='cli'; irm https://raw.githubusercontent.com/Codename-11/hermes-relay/main/desktop/scripts/install.ps1 | iex
```
**macOS / Linux CLI:**
```bash
curl -fsSL https://raw.githubusercontent.com/Codename-11/hermes-relay/main/desktop/scripts/install.sh | sh
```
Pin this specific release with `HERMES_RELAY_VERSION=__TAG__`.
Pin this release with `HERMES_RELAY_VERSION=__TAG__`.
## Verify
```text
hermes-relay --version
hermes-relay pair --remote ws://<host>:8767
hermes-relay shell
hermes-relay pair --remote ws://<host>:8767 --grant-tools
hermes-relay daemon start
hermes-relay daemon status
```
Open **Hermes Relay Desktop** from the Windows Start menu for tray pairing, devices, task log, settings, pause, and emergency stop.
On Windows, open **Hermes Relay Systray** from the Start menu and right-click its notification-area icon. No separate desktop window is installed.
See [Desktop docs](https://codename-11.github.io/hermes-relay/desktop/) for full usage.
See the [CLI and systray guide](https://hermes-relay.dev/docs/desktop/) for installation, commands, desktop-use safety, and troubleshooting.
+78
View File
@@ -0,0 +1,78 @@
# Code of Conduct
Hermes-Relay adopts the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/),
version 2.1, as its code of conduct. The canonical, full text lives at that
link; the summary below states what it means for this project.
## Our Pledge
We as members, contributors, and maintainers pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity and
orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
## Our Standards
Behavior that helps create a positive environment includes:
- Showing empathy and kindness toward others.
- Being respectful of differing opinions, viewpoints, and experiences.
- Giving and gracefully accepting constructive feedback.
- Taking responsibility, apologizing to those affected by our mistakes, and
learning from the experience.
- Focusing on what is best for the overall community, not just ourselves.
Behavior that is not acceptable includes:
- Harassment, intimidation, or discrimination in any form.
- Personal or political attacks, insults, or derogatory comments.
- Unwelcome advances or attention, including of a romantic or sexual nature.
- Publishing others' private information (such as a physical or email address)
without their explicit permission.
- Other conduct that could reasonably be considered inappropriate in a
professional setting.
For the complete, canonical list of standards and examples, see the
[Contributor Covenant v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
## Enforcement Responsibilities
Project maintainers are responsible for clarifying and enforcing these standards
and will take appropriate and fair corrective action in response to any behavior
they deem inappropriate, threatening, offensive, or harmful.
Maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, issues, and other contributions that are not aligned
with this Code of Conduct, and will communicate reasons for moderation decisions
when appropriate.
## Scope
This Code of Conduct applies within all project spaces — the repository, issues,
pull requests, discussions, and the documentation site — and also applies when
an individual is officially representing the project in public spaces.
## Reporting & Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported privately to the maintainers at **`conduct@codename-11.dev`**. All
complaints will be reviewed and investigated promptly and fairly. Maintainers
are obligated to respect the privacy and security of the reporter of any
incident.
For the **Enforcement Guidelines** (the tiered Correction → Warning →
Temporary Ban → Permanent Ban ladder maintainers use to determine consequences),
see the corresponding section of the
[Contributor Covenant v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/#enforcement-guidelines).
## Attribution
This Code of Conduct is adapted from the
[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.
Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+71 -2
View File
@@ -92,9 +92,69 @@ After the plugin is in place, restart hermes and verify pairing with `hermes-pai
We follow [Conventional Commits](https://www.conventionalcommits.org/): `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`.
**Branching model (as of 2026-04-19): `main` + `dev`.** Feature branches — `feature/<name>`, `fix/<name>`, `docs/<name>`, `chore/<name>` — branch off `dev` and merge back into `dev` via `--no-ff` PRs. `main` is released state only; it receives release merges from `dev` and nothing else. There is no straight-to-main exemption — even single-file typos go through `dev`.
**Branching model: `main` + `dev`.** Feature branches — `feature/<name>`,
`fix/<name>`, `docs/<name>`, `chore/<name>` — branch off `dev` and merge back
into `dev` via merge-commit/no-ff PRs. This includes small documentation fixes.
`main` is release history, not the normal contribution target; it receives
approved release PRs from `dev` and focused hotfix PRs based on production tags.
Release-prep commits (version bump, changelog promotion) land on `dev` first, then a surface-specific release PR merges `dev` → `main` with `--no-ff`. Tags are cut from `main` after the merge: `android-vX.Y.Z`, `server-vX.Y.Z`, or `desktop-vX.Y.Z`. See [RELEASE.md](RELEASE.md) for the full release process.
Feature completion means merged and verified on `dev`; it does not mean the
change has been released. A separate Forge release issue/session owns release
preparation, the `dev` → `main` release PR, tagging, artifacts, rollout or
deployment, and live verification. Release-prep commits land on `dev`; tags are
cut from the resulting `main` tip as `android-vX.Y.Z`, `server-vX.Y.Z`, or
`desktop-vX.Y.Z`. See [RELEASE.md](RELEASE.md) for the full release and hotfix
procedures.
## Stale PR salvage and contributor credit
A valuable pull request can become unsafe to merge when `dev` has materially
changed around it. Maintainers may create a replacement **salvage PR** from the
current `dev` instead of resolving a stale branch by choosing whole conflict
sides.
A salvage PR must:
- Link the original PR and contributor in its title or opening summary.
- Recover only the intended feature; unrelated fork, release, signing, and
generated migration changes stay out.
- Preserve the original commit author when a substantive commit can be safely
cherry-picked.
- Use a verified `Co-authored-by: Name <email>` trailer when the implementation
must be reconstructed or substantially rewritten.
- Include a `Lineage` section listing source and superseded PRs, plus a concise
explanation of integration changes made for current `dev`.
- Run current verification rather than relying on checks from the stale branch.
- Leave a comment linking the replacement before the source PR is closed.
The maintainer remains the committer for integration commits. The original
contributor remains the author or co-author of the recovered work. Do not guess
an email address: use the source commit's verified address or ask the
contributor.
## Localization contributions
English resources are canonical and Android locale catalogs must retain exact
resource and format-argument parity. Read [docs/localization.md](docs/localization.md)
before changing user-facing strings or adding a language.
Translation PRs should cover one locale or one clear catalog refresh. They must
not include custom APK publishing, signing configuration, version bumps, or
fork-specific branding. Run:
```bash
python scripts/check-android-locales.py
./gradlew lint
```
Update `docs/localization-status.json` with the actual review level. AI-assisted
translations may ship as `ai-translated`; do not claim fluent review unless a
review reference is recorded. Focused correction PRs from fluent contributors
are the canonical way to improve wording and can advance a locale to
`community-reviewed` or `verified` under `docs/translation-playbook.md`.
Translated READMEs use separate `README.<locale>.md` files; `README.md` remains
the canonical project description. User docs may be added incrementally under
`user-docs/<locale>/`, with links back to canonical English reference material.
## Changelog & writing conventions
@@ -108,10 +168,19 @@ Release notes (`RELEASE_NOTES.md`, `app/src/main/assets/whats_new.txt`, `docs/pl
## Testing
- **Android pre-push gate:** `scripts\dev.bat prepush` on Windows or
`./scripts/dev.sh prepush` on macOS/Linux. This runs the Android repository
checks, Google Play debug lint, and the same focused unit-test shard used by
CI in one cached Gradle invocation. Run it before pushing Android PR updates
to catch common hosted failures without waiting for another full Actions
cycle; hosted CI remains the exhaustive all-variant gate.
- **Android unit tests:** `scripts/dev.bat test` (runs JUnit + MockK + Compose testing)
- **Python tests:** `python -m unittest plugin.tests.test_<name>` from the repo root with the hermes-agent venv active. `pytest` works too but the pre-existing `conftest.py` imports a module that isn't always installed — `unittest` avoids that entirely.
CI is split into path-filtered workflows: `.github/workflows/ci-android.yml` (lint + build + test on app/Gradle changes), `.github/workflows/ci-server.yml` (syntax check + focused server tests on plugin/Python changes), and `.github/workflows/ci-desktop.yml` (desktop type/build/smoke checks). They run on pushes to `main` and `dev` and on PRs targeting either when their paths are touched.
Superseded Android runs on `dev` and PR refs are canceled automatically; `main`
runs are never canceled because each release-branch commit must complete its
independent validation.
## Questions?
+2671 -1
View File
File diff suppressed because it is too large Load Diff
+20 -21
View File
@@ -1,39 +1,38 @@
# Hermes-Relay-Plugin v__VERSION__
**Release Date:** June 20, 2026
**Since the previous plugin release:** A new, removable **enhancement layer** that lets the relay teach the agent things only the relay knows — starting with sensitive-media classification — plus provider-aware enhanced voice and an isolated, TUI-tuned tmux for relay terminals.
**Release Date:** July 22, 2026
This release adds a clean way for the relay to extend the agent without forking or touching the user's soul/memory. The first use is **sensitive-media classification**: the relay appends a small, auditable system-prompt block teaching the agent to mark private/NSFW media so the paired phone can blur it — with sensitivity staying model-emitted. It's on by default for relay installs (installing the relay is the opt-in), reversible from the dashboard or an env flag, fully visible over a new audit route, and a complete no-op on vanilla upstream. Voice gains provider-aware controls for Gemini and xAI, and relay terminals now run on a dedicated, correctly-configured tmux.
This patch hardens Relay authorization, adds upstream-aware diagnostics, and keeps plugin bootstrap work off the Gateway event loop.
It can accompany Hermes-Relay-Android v1.5.0 for optional Relay diagnostics and power features. Standard chat and Vanilla Hermes voice remain upstream-owned and do not require this plugin.
## What's changed
### Added
- **Relay enhancement layer + agent-context injection.** A reusable, removable layer that injects auditable, fenced blocks into the agent's system prompt at plugin-load. Fail-open at every step (seam absent / block build throws ⇒ base prompt unchanged), config-gated, and a byte-for-byte no-op on vanilla upstream. Built to be retired per-surface as upstream adds a context hook — the same pattern as the bootstrap route shims. See `docs/plans/2026-06-20-relay-enhancement-layer.md`.
- **Sensitive-media classification (first block).** Teaches the agent to mark private/NSFW media with the client's spoiler convention so the phone blurs it per the user's setting. **On by default for relay installs**; opt out with `RELAY_AGENT_CONTEXT_ENABLED=0` or the dashboard toggle. Sensitivity stays model-emitted — no relay-side or on-device classifier. No soul/memory is touched.
- **`GET /context/injected` audit route.** The relay exposes exactly what it would inject (loopback-open, bearer-gated remotely), so the injection is never hidden — surfaced in the Android chat "What the agent sees" sheet as "Relay context (server-side)".
- **Dashboard Agent-context controls.** The Relay management tab gained a master toggle and per-block toggles (labeled experimental / server-side / removable), shown on-by-default for relay installs.
- **Provider-aware enhanced voice (Gemini + xAI).** `/voice/synthesize` accepts per-request overrides so a paired client can steer a Gemini voice/model with expressive tone tags, or an xAI voice with expressive speech tags, without changing the server's global voice config.
### Changed
- **Relay terminals run on an isolated, TUI-tuned tmux.** Sessions spawn on a dedicated tmux server/socket with a generated config — `escape-time 0`, truecolor `tmux-256color`, `mouse`/`focus-events` on, `status off` — so editors and full-screen tools behave correctly without touching the user's personal tmux.
- **Upstream-aware Gateway diagnostics.** Doctor and `/relay/info` expose optional health, configuration-route, and capability signals so clients can explain compatibility gaps without treating an older upstream install as a broken Relay.
### Fixed
- **Relay voice synthesis no longer leaves temporary audio files behind** on the server.
- **Clearer voice errors.** Standard voice rejects an over-long recording before uploading and returns a helpful message for audio the server can't read, instead of a generic HTTP error.
## Install
- **Privileged Relay paths enforce host authorization and active grants.** Pairing, Android bridge, terminal, session policy, remote profile configuration, and voice provider origins retain their intended trust boundaries.
- **Plugin bootstrap remains responsive.** Database initialization and compatibility inspection run outside the Gateway event loop while preserving compatibility with older upstream bootstrap contracts.
- **Windows Gateway detection is non-signalling.** Starting Relay and periodic profile rescans no longer risk terminating an existing Gateway process.
```bash
pip install hermes-relay==__VERSION__
```
## Install / update
# Native upstream plugin path:
hermes plugins install Codename-11/hermes-relay/plugin --enable
# Classic install / update on a systemd host:
curl -fsSL https://raw.githubusercontent.com/Codename-11/hermes-relay/main/install.sh | bash
# or, if already installed:
hermes-relay-update
## Verify
```bash
python -m relay_server --help
```
hermes relay doctor
python scripts/check-plugin-version-sync.py --expect __VERSION__
---
Tag prefixes: Android releases use `android-v*`, CLI releases use `cli-v*`. Historical
relay/plugin releases used `relay-v*` tags.
Tag prefixes: Android releases use android-v*, Server releases use server-v*, and Desktop releases use desktop-v*.
+63 -49
View File
@@ -21,7 +21,8 @@
</p>
<p align="center">
<a href="https://codename-11.github.io/hermes-relay/">Documentation</a> ·
<strong>English</strong> · <a href="README.zh-CN.md">简体中文</a><br>
<a href="https://hermes-relay.dev/docs/">Documentation</a> ·
<a href="https://github.com/Codename-11/hermes-relay/releases">Releases</a> ·
<a href="CHANGELOG.md">Changelog</a> ·
<a href="https://hermes-agent.nousresearch.com">Hermes Agent</a>
@@ -49,56 +50,52 @@ Install → connect → talk, in about two minutes.
### 1 · Install the app
- **Google Play** *(easiest — auto-updates)* — [**install from Google Play**](https://play.google.com/store/apps/details?id=com.axiomlabs.hermesrelay). Chat, voice, Manage, terminal/TUI, media, notifications, and relay sessions.
- **APK** *(full phone-control feature set)* — download the file ending in **`-sideload-release.apk`** from the newest `android-v*` release on [GitHub Releases](https://github.com/Codename-11/hermes-relay/releases) and open it (allow your browser to install unknown apps the first time). Integrity verification, signing fingerprint, and per-build details are in the [Sideload guide](https://codename-11.github.io/hermes-relay/guide/getting-started.html#sideload-apk).
- **APK** *(full phone-control feature set)* — download the file ending in **`-sideload-release.apk`** from the newest `android-v*` release on [GitHub Releases](https://github.com/Codename-11/hermes-relay/releases) and open it (allow your browser to install unknown apps the first time). Integrity verification, signing fingerprint, and per-build details are in the [Sideload guide](https://hermes-relay.dev/docs/guide/getting-started.html#sideload-apk).
Sideload builds check GitHub for updates and show a one-tap banner when you're behind; Play builds update through the Store. See [Release tracks](https://codename-11.github.io/hermes-relay/guide/release-tracks) for the capability matrix.
Sideload builds check GitHub for updates and show a one-tap banner when you're behind; Play builds update through the Store. See [Release tracks](https://hermes-relay.dev/docs/guide/release-tracks) for the capability matrix.
### 2 · Have Hermes running
### 2 · Have the Hermes Dashboard running
The app needs your Hermes **API server enabled and reachable from your phone**, plus an **API key** — the token the app sends to authenticate Chat (pick any value you like). Installing Hermes and choosing a provider is vanilla Hermes setup; the [full walkthrough](https://codename-11.github.io/hermes-relay/guide/getting-started) covers Windows, the dashboard for **Manage**, LAN scan, and QR setup.
The normal Android connection uses the upstream Hermes Dashboard/Gateway for
chat, sign-in, sessions, Manage, and voice. Installing Hermes and choosing a
provider is vanilla Hermes setup:
```bash
hermes setup --portal # install / log in / pick a provider — skip if already done
mkdir -p ~/.hermes
API_SERVER_KEY="$(openssl rand -hex 32)" # strong random key — or substitute your own memorable value
cat >> ~/.hermes/.env <<EOF
API_SERVER_ENABLED=true
API_SERVER_HOST=0.0.0.0
API_SERVER_PORT=8642
API_SERVER_KEY=$API_SERVER_KEY
EOF
chmod 600 ~/.hermes/.env
echo "Android API URL: http://<this-computer-ip>:8642 key: $API_SERVER_KEY"
hermes gateway
hermes setup --portal # install / log in / pick a provider — skip if already done
hermes dashboard # start the standard Dashboard/Gateway surface
```
`API_SERVER_ENABLED` turns the API server on; `API_SERVER_HOST=0.0.0.0` makes it reachable on your LAN (the default is localhost-only); `API_SERVER_KEY` is the bearer token the app sends — **your choice of value**.
> **Heads up on `0.0.0.0`:** that exposes the API to every device on your network — fine on a trusted home LAN, but off it keep the key set and front it with Tailscale or an HTTPS reverse proxy ([Remote access](https://codename-11.github.io/hermes-relay/guide/remote-access)) rather than exposing it directly. You don't have to type the key on your phone — **Scan for Hermes on LAN**, or have your agent make a setup QR (below). For **Manage** (skills, models, keys), also run the Hermes dashboard — see [Getting Started](https://codename-11.github.io/hermes-relay/guide/getting-started).
Make the dashboard reachable from your phone over a trusted LAN, Tailscale, or
an HTTPS reverse proxy. The [full walkthrough](https://hermes-relay.dev/docs/guide/getting-started)
covers Windows, remote access, and dashboard authentication. You do not need to
enable the separate API server or invent an API key for the standard path.
### 3 · Connect and talk
Open the app and pick how to connect — any of:
Open the app, choose **Connect to Hermes**, and enter or discover the dashboard
address (conventionally `http://<host>:9119`). Sign in through the dashboard's
configured provider when prompted. The app probes the available upstream
capabilities and finishes with a connection summary.
- **Vanilla Hermes** → tap **Scan for Hermes on LAN** to auto-find the server, then enter your key.
- **Vanilla Hermes** → type the address (`http://<host>:8642`) and key by hand.
- **Scan setup QR** → ask your Hermes agent to generate a QR with your URL + key (e.g. `{"api_url":"http://<host>:8642","api_key":"<key>","dashboard_url":"http://<host>:9119"}`) and scan it. `dashboard_url` is optional when the dashboard uses the conventional same-host `:9119` URL.
The separate API server can be discovered automatically or added later under
**Advanced** as a chat fallback or for a headless compatibility setup. Its API
key is requested only when that optional endpoint is configured. Existing
API-first setup QRs remain importable.
The wizard probes everything and finishes with a capability card:
| Line | What it means |
|------|---------------|
| **Chat** | API server reachable — you can talk |
| **Manage** | Dashboard found — models, keys, skills, profiles from the phone |
| **Chat** | Dashboard/Gateway ready — you can talk |
| **Manage** | Models, keys, skills, and profiles are available from the phone |
| **Voice** | Speech ready via your server (or one Manage sign-in away) |
| **Remote** | Fallback route configured — keeps working away from home |
| **Relay** | Optional power tools — fine to leave unpaired |
| **API fallback** | Optional API route available/unavailable |
| **Relay** | Optional extensions — fine to leave unpaired |
If your dashboard requires sign-in, do it once under the **Manage** tab — the same session unlocks voice. That's the whole Vanilla Hermes setup.
One dashboard sign-in unlocks Chat, Manage, sessions, and standard voice. That's
the whole Vanilla Hermes setup.
> **Going places?** Put your server's Tailscale URL in the setup form's *Remote access* field (or add a route any time under **Settings → Connections → Routes**). The app uses LAN at home and switches routes automatically when you leave. See [Remote access](https://codename-11.github.io/hermes-relay/guide/remote-access).
> **Going places?** Add the Dashboard's Tailscale address — for example `http://100.x.y.z:9119` or a separately published `https://host.ts.net` URL — under **Settings → Connections → Routes**. Android tests it as a Dashboard route; no API server or API key is required. The app uses LAN at home and switches routes automatically when you leave. See [Remote access](https://hermes-relay.dev/docs/guide/remote-access).
### 4 · Optional: install Relay for power tools
@@ -132,7 +129,7 @@ the QR from the phone's Connections screen — or use
Full server setup, TLS, and systemd details: [docs/relay-server.md](docs/relay-server.md).
**Requirements:** Android 8.0+ (SDK 26) · current upstream [hermes-agent](https://github.com/NousResearch/hermes-agent) with the API server and dashboard enabled · Python 3.11+ on the server.
**Requirements:** Android 8.0+ (SDK 26) · current upstream [hermes-agent](https://github.com/NousResearch/hermes-agent) with the Dashboard/Gateway enabled · Python 3.11+ on the server. The API server and Relay are optional.
## Screenshots
@@ -151,7 +148,22 @@ Full server setup, TLS, and systemd details: [docs/relay-server.md](docs/relay-s
</tr>
</table>
<p align="center"><sub>▶ <a href="https://codename-11.github.io/hermes-relay/guide/getting-started.html#see-it-working">Watch the demo</a> on the docs site</sub></p>
### Simplified Chinese
<table>
<tr>
<td align="center" width="33%"><img src="assets/screenshots/Zh01.jpg" alt="中文设置界面" width="100%"><br><sub><b>设置 — 全面汉化</b></sub></td>
<td align="center" width="33%"><img src="assets/screenshots/Zh02.jpg" alt="中文管理界面" width="100%"><br><sub><b>管理 — 仪表盘汉化</b></sub></td>
<td align="center" width="33%"><img src="assets/screenshots/Zh03.jpg" alt="中文导航界面" width="100%"><br><sub><b>导航菜单 — 简体中文</b></sub></td>
</tr>
</table>
The Android app ships complete AI-assisted catalogs for **Deutsch**, **Español**,
**日本語**, **Português (Brasil)**, and **简体中文**. Choose a language from
**Settings → Appearance → Language**; translation status and fluent review are
tracked independently so community corrections remain easy to contribute.
<p align="center"><sub>▶ <a href="https://hermes-relay.dev/docs/guide/getting-started.html#see-it-working">Watch the demo</a> on the docs site</sub></p>
## Features
@@ -167,11 +179,11 @@ Full server setup, TLS, and systemd details: [docs/relay-server.md](docs/relay-s
- **Security & pairing** — QR pairing, Android Keystore session storage (StrongBox-preferred), TOFU cert pinning, per-channel time-bound grants, user-chosen session TTL.
- **Stats for Nerds** — local-only analytics: TTFT, token usage, stream health, peak-time charts.
> Sideload builds add direct SMS, contact search, one-tap dialing, and location awareness — handy for fully hands-free intents like *"text Sam I'll be 10 minutes late."* See [Release tracks](https://codename-11.github.io/hermes-relay/guide/release-tracks).
> Sideload builds add direct SMS, contact search, one-tap dialing, and location awareness — handy for fully hands-free intents like *"text Sam I'll be 10 minutes late."* See [Release tracks](https://hermes-relay.dev/docs/guide/release-tracks).
## Hands on any machine — the Hermes-Relay CLI&nbsp;<sub>(alpha)</sub>
> **Alpha · Windows today** (macOS / Linux coming soon). A single self-contained binary — no Node required. Binaries are unsigned during the experimental phase, so SmartScreen / Gatekeeper warnings are expected.
> **Alpha.** Self-contained CLI binaries ship for Windows x64, Linux x64, and macOS x64/arm64 — no Node required. Windows also has an optional native, menu-only systray. Assets are unsigned during the experimental phase, so SmartScreen / Gatekeeper warnings are expected.
The agent's brain stays on the host; the CLI lets it call tools **on your machine** over the same WSS relay — `read_file`, `write_file`, `terminal`, `search_files`, `screenshot`, `clipboard`, `open_in_editor`, and more — behind a one-time consent gate, interactive diff approval for patches, and a `--no-tools` kill-switch.
@@ -181,13 +193,15 @@ irm https://raw.githubusercontent.com/Codename-11/hermes-relay/main/desktop/scri
```bash
hermes-relay pair --remote ws://<host>:8767 # once
hermes-relay daemon # headless tool router — agent reaches you anytime
hermes-relay daemon start # background tool router — agent reaches you anytime
hermes-relay update # self-update via GitHub Releases
```
It pairs against the **same relay and credential store** as the Android app — pair once from either, both work. Tagged on a separate `cli-v*` [release track](https://github.com/Codename-11/hermes-relay/releases?q=cli), with old alpha prereleases still visible under `desktop-v*`.
It pairs against the **same relay and credential store** as the Android app — pair once from either, both work. Tagged on the `desktop-v*` [release track](https://github.com/Codename-11/hermes-relay/releases?q=desktop), with historical releases still visible under `cli-v*`.
- **Docs:** [CLI guide](https://codename-11.github.io/hermes-relay/desktop/) · [`desktop/README.md`](desktop/README.md)
On Windows, the default installer adds the optional right-click-only systray: no dashboard or app window, just TUI launch, User/Administrator-aware daemon controls, pairing, local grant review, audit, diagnostics, logs, desktop-use status/cancellation, sign-in startup, and emergency stop.
- **Docs:** [CLI guide](https://hermes-relay.dev/docs/desktop/) · [`desktop/README.md`](desktop/README.md)
- **AI-agent setup recipe:** `/hermes-relay-desktop-setup`
## How It Works
@@ -211,14 +225,14 @@ configure API, dashboard, and relay routes without merging their auth models.
| | |
|---|---|
| **[User Guide](https://codename-11.github.io/hermes-relay/)** | **Quick start, features, configuration — start here** |
| [Android](https://codename-11.github.io/hermes-relay/guide/) | Android install + setup + features |
| [Hermes-Relay CLI](https://codename-11.github.io/hermes-relay/desktop/) | Pairing, subcommands, local tool routing |
| [Architecture](https://codename-11.github.io/hermes-relay/architecture/) | How the system works under the hood |
| [API Reference](https://codename-11.github.io/hermes-relay/reference/api.html) | Hermes API endpoints used by both surfaces |
| **[User Guide](https://hermes-relay.dev/docs/)** | **Quick start, features, configuration — start here** |
| [Android](https://hermes-relay.dev/docs/guide/) | Android install + setup + features |
| [Hermes-Relay CLI](https://hermes-relay.dev/docs/desktop/) | Pairing, subcommands, local tool routing |
| [Architecture](https://hermes-relay.dev/docs/architecture/) | How the system works under the hood |
| [API Reference](https://hermes-relay.dev/docs/reference/api.html) | Hermes API endpoints used by both surfaces |
| [Specification](docs/spec.md) | Full spec — protocol, UI, phases, dependencies |
| [Architecture Decisions](docs/decisions.md) | ADRs — framework, channels, auth, terminal |
| [Changelog](CHANGELOG.md) | Release history (`android-v*`, `plugin-v*`, `cli-v*`) |
| [Changelog](CHANGELOG.md) | Release history (`android-v*`, `server-v*`, `desktop-v*`; historical prefixes remain immutable) |
<details>
<summary><b>Install with an AI agent</b> — paste-ready prompt for Claude / GPT</summary>
@@ -311,7 +325,7 @@ docker build -t hermes-relay relay_server/ && docker run -d --network host --nam
ln -s "$PWD/plugin" ~/.hermes/plugins/hermes-relay
```
Then restart hermes and run `hermes pair` to verify. The 18 `android_*` and 9 `desktop_*` tools register regardless of hermes-agent version. See [docs/relay-server.md](docs/relay-server.md) for TLS, systemd, and full setup.
Then restart hermes and run `hermes pair` to verify. The 35 `android_*` and 25 `desktop_*` tools register regardless of hermes-agent version. See [docs/relay-server.md](docs/relay-server.md) for TLS, systemd, and full setup.
</details>
@@ -327,9 +341,9 @@ This is an indie project and every report helps shape where it goes next. If som
<a href="https://www.star-history.com/?repos=Codename-11%2Fhermes-relay&type=date&legend=top-left">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&theme=dark&legend=top-left" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&legend=top-left" />
<img alt="Star History Chart" src="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&legend=top-left" />
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&theme=dark&legend=top-left&sealed_token=LpoTO7nnGWAwvnRyEeMuKowbf1fe6tQP9n6EbjX-9HTG0uGPrSD_OaNkloMDIM5ugTCg_14LB3XpQTx7v4fBn7PAtMZhO87iIlK5lo42Z31x8myptmcmnQ" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&legend=top-left&sealed_token=LpoTO7nnGWAwvnRyEeMuKowbf1fe6tQP9n6EbjX-9HTG0uGPrSD_OaNkloMDIM5ugTCg_14LB3XpQTx7v4fBn7PAtMZhO87iIlK5lo42Z31x8myptmcmnQ" />
<img alt="Star History Chart" src="https://api.star-history.com/chart?repos=Codename-11/hermes-relay&type=date&legend=top-left&sealed_token=LpoTO7nnGWAwvnRyEeMuKowbf1fe6tQP9n6EbjX-9HTG0uGPrSD_OaNkloMDIM5ugTCg_14LB3XpQTx7v4fBn7PAtMZhO87iIlK5lo42Z31x8myptmcmnQ" />
</picture>
</a>
+104
View File
@@ -0,0 +1,104 @@
<p align="center">
<img src="assets/play-store-feature-1024x500.png" alt="Hermes-Relay — 随身携带您的 Hermes 代理" width="800">
</p>
<p align="center">
<strong>运行在您的电脑上,连接到您的设备。</strong><br>
Hermes-Relay 是 <a href="https://github.com/NousResearch/hermes-agent">Hermes Agent</a> 的原生 Android 客户端,提供流式聊天、免手动语音和代理管理;另有单文件 CLI,让代理在已配对的电脑上安全使用终端、文件和截图工具。
</p>
<p align="center">
<strong>简体中文</strong> · <a href="README.md">English</a><br>
<a href="https://hermes-relay.dev/docs/zh-CN/">中文文档</a> ·
<a href="https://github.com/Codename-11/hermes-relay/releases">版本下载</a> ·
<a href="CHANGELOG.md">更新日志</a>
</p>
> 英文 [README.md](README.md) 是最新、完整的项目说明。本页维护中文安装入口和核心功能摘要;协议、架构和维护者文档以英文版本为准。
## 功能简介
- **Android 应用**:流式聊天、会话历史、文件附件、Hermes 管理、语音模式、多连接和配置文件。
- **无需插件的标准路径**:聊天、管理和标准语音可直接连接未修改的上游 Hermes Agent。
- **可选 Relay 插件**:增加终端、手机控制、媒体传输、通知助手、Relay 语音和电脑工具。
- **安全连接**:二维码配对、Android Keystore、证书固定、按通道授权和可配置会话有效期。
- **远程使用**:可配置 Tailscale 或 HTTPS 地址,在家庭局域网和远程路由之间自动切换。
- **两种 Android 发行渠道**:Google Play 版本适合日常使用;sideload 版本包含完整手机控制能力。
## 快速开始
### 1. 安装 Android 应用
- [Google Play](https://play.google.com/store/apps/details?id=com.axiomlabs.hermesrelay):自动更新,包含聊天、语音、管理、终端、媒体和通知功能。
- [GitHub Releases](https://github.com/Codename-11/hermes-relay/releases):下载最新 `android-v*` 版本中以 `-sideload-release.apk` 结尾的文件,获得完整手机控制功能。
### 2. 启动 Hermes API 服务
手机需要能够访问 Hermes API 服务,并使用 API 密钥进行身份验证:
```bash
hermes setup --portal
mkdir -p ~/.hermes
API_SERVER_KEY="$(openssl rand -hex 32)"
cat >> ~/.hermes/.env <<EOF
API_SERVER_ENABLED=true
API_SERVER_HOST=0.0.0.0
API_SERVER_PORT=8642
API_SERVER_KEY=$API_SERVER_KEY
EOF
chmod 600 ~/.hermes/.env
echo "Android API URL: http://<电脑IP>:8642 key: $API_SERVER_KEY"
hermes gateway
```
`0.0.0.0` 会让同一网络中的设备访问 API。请保留强密钥;离开可信局域网时,应使用 Tailscale 或 HTTPS 反向代理,不要直接把端口暴露到互联网。
### 3. 在手机上连接
打开应用后,可以:
- 扫描局域网中的 Hermes;
- 手动输入 `http://<主机>:8642` 和 API 密钥;
- 扫描包含 API、Dashboard 和可选 Relay 地址的设置二维码。
如需在手机上管理模型、密钥、技能和配置文件,请运行 Hermes Dashboard,并在应用的 **管理** 页面登录一次。同一登录会话也会启用标准语音。
### 4. 可选:安装 Relay
仅在需要终端、手机控制、媒体路由、Relay 会话、实时语音或电脑工具时安装:
```bash
hermes plugins install Codename-11/hermes-relay/plugin --enable
hermes relay doctor
hermes relay start --no-ssl
hermes pair
```
完整说明请阅读[中文快速开始](https://hermes-relay.dev/docs/zh-CN/guide/quick-start);远程访问、协议和高级配置暂时链接到英文参考文档。
## 中文界面
<table>
<tr>
<td align="center" width="33%"><img src="assets/screenshots/Zh01.jpg" alt="中文设置界面" width="100%"><br><sub><b>设置</b></sub></td>
<td align="center" width="33%"><img src="assets/screenshots/Zh02.jpg" alt="中文管理界面" width="100%"><br><sub><b>管理</b></sub></td>
<td align="center" width="33%"><img src="assets/screenshots/Zh03.jpg" alt="中文导航界面" width="100%"><br><sub><b>导航</b></sub></td>
</tr>
</table>
## 参与翻译
Android 英文资源是规范来源。新增语言必须保持资源名称、类型和格式参数一致,并通过:
```bash
python scripts/check-android-locales.py
./gradlew lint
```
翻译规范、目录命名、复数和占位符规则见 [docs/localization.md](docs/localization.md)。
## 许可证
[MIT](LICENSE) — Copyright (c) 2026 [Axiom-Labs](https://codename-11.dev)
+283 -88
View File
@@ -13,23 +13,24 @@ with optional prerelease identifiers.
- `PATCH` — bug fixes, backwards compatible
- Prerelease suffixes: `-alpha`, `-beta`, `-rc.N` (e.g. `0.2.0-beta.1`)
Hermes-Relay now ships three independently versioned surfaces. Public GitHub
Release titles use product names (`Hermes-Relay-Android`,
`Hermes-Relay-Plugin`, `Hermes-Relay-CLI`); tag prefixes stay short and stable
for automation.
Hermes-Relay ships three independently versioned production surfaces. Public
GitHub Release titles use product names (`Hermes-Relay-Android`,
`Hermes-Relay-Server`, `Hermes-Relay-Desktop`); immutable tag prefixes select
the corresponding build and deployment lane.
| Surface | Tag prefix | Version source | Bump script | Release workflow |
|---|---|---|---|---|
| Hermes-Relay-Android | `android-v*` | `gradle/libs.versions.toml` | `scripts/bump-android-version.sh` | `.github/workflows/release-android.yml` |
| Hermes-Relay-Plugin | `plugin-v*` | `pyproject.toml` plus checked plugin/dashboard metadata | `scripts/bump-plugin-version.sh` | `.github/workflows/release-plugin.yml` |
| Hermes-Relay-CLI | `cli-v*` | `desktop/package.json` | `npm version` or manual package bump | `.github/workflows/release-cli.yml` |
| Hermes-Relay-Server | `server-v*` | `pyproject.toml` plus checked plugin/dashboard metadata | `scripts/bump-plugin-version.sh` | `.github/workflows/release-plugin.yml` |
| Hermes-Relay-Desktop | `desktop-v*` | `desktop/package.json` | `cd desktop && npm version --no-git-tag-version <version>` | `.github/workflows/release-cli.yml` |
This split is intentional. The plugin carries relay features for both Android
and CLI clients, so plugin fixes can ship without forcing an Android app
`versionCode` bump, and CLI alphas can continue on their own cadence. Historical
Android releases before this naming split used bare `v*` tags. Historical
plugin/server releases used `relay-v*` tags, and historical CLI prereleases used
`desktop-v*` tags. New releases use the explicit tag prefixes above.
plugin/server releases used `relay-v*` and `plugin-v*` tags. Historical
desktop/CLI releases also include `cli-v*` tags. Those tags remain immutable;
new releases use the canonical prefixes above.
### Android app versioning
@@ -87,7 +88,7 @@ lockstep:
| `plugin/dashboard/package.json` | `"version": "..."` | dashboard build/package metadata |
| `plugin/dashboard/package-lock.json` | `"version": "..."` | locked dashboard package metadata |
Always bump Plugin releases via:
Always bump Server releases via:
```bash
bash scripts/bump-plugin-version.sh 0.6.2
@@ -105,16 +106,50 @@ Check all release tracks at once with:
python scripts/check-version-tracks.py
```
This aggregate check reports Android, plugin, and CLI versions
This aggregate check reports Android, Server, and Desktop versions
side by side and validates that each track's own source files are internally
consistent. It deliberately does not require all three tracks to share the same
SemVer.
The `plugin-v*` release workflow validates the tag against the same metadata,
The `server-v*` release workflow validates the tag against the same metadata,
runs plugin tests, builds a wheel and sdist, generates checksums, and
publishes a `Hermes-Relay-Plugin vX.Y.Z` GitHub Release with the package
publishes a `Hermes-Relay-Server vX.Y.Z` GitHub Release with the package
artifacts.
### CLI / tray versioning
`desktop/package.json` is the Desktop/CLI release track's source of truth. Its version
must match the generated CLI and native Windows systray metadata. The systray is
a menu-only controller for the installed CLI; it has no application window,
WebView, embedded terminal, or separate desktop product surface. The public
release remains one `Hermes-Relay-Desktop` track containing CLI binaries plus the
optional Windows installer.
| File | Purpose |
|---|---|
| `desktop/package.json` | canonical CLI version |
| `desktop/package-lock.json` | npm root/workspace package metadata |
| `desktop/src/version.ts` | compiled CLI runtime version |
| `desktop/tray/Cargo.toml` | native systray package version |
| `desktop/tray/Cargo.lock` | locked systray package version |
Prepare a new CLI version on `dev` without creating a tag or npm-generated
commit:
```powershell
cd desktop
npm version --no-git-tag-version 0.4.0-alpha.2
npm run check:version-sync
npm run verify
```
The npm `version` lifecycle runs `sync:version`, which copies the canonical
version into the generated CLI and tray metadata. If `package.json` was edited
manually, run `npm run sync:version` before checking. `npm run verify` is the
single Windows release-parity gate: version sync, type-check, tests, TypeScript
build, compiled CLI smoke, and tray formatting, Clippy, check, and tests. CI runs
the portable portions on every desktop change and the Windows tray gates separately.
## Branching policy
> **Updated 2026-04-19:** moved from `main`-only to `main + dev`. See
@@ -132,12 +167,28 @@ the accumulator: every merged PR appends bullets there. A release is a
separate act, taken when the accumulated state on `dev` is worth shipping
(see "When to cut a release" below). Cutting a release means opening a
surface-specific release PR from `dev` into `main`, merging it `--no-ff`,
then tagging `main`.
then tagging `main`. Feature completion means merged and verified on `dev`; it
does not mean released.
**Server tracks `dev` for staging.** The hermes-host deployment pulls
`dev` so merged features get exercised against real data before they
reach a tag. Users (Play Store, sideload, `hermes-relay-update`) only
see state that lives on `main` and on release tags.
**Staging is an environment, not a branch.** Deploy an exact tested `dev` SHA or
an immutable release-candidate tag to staging. Record that source in the Forge
release issue/session. Never deploy a moving branch name as the source of record
and never create a staging branch. Production deploys only immutable
`android-v*`, `server-v*`, or `desktop-v*` tags cut from `main`.
### Normal contribution and release flow
1. Branch `feature/*`, `fix/*`, `docs/*`, or `chore/*` from `dev`.
2. Open the PR into `dev` and require CI to pass.
3. Merge with a merge commit/no-ff according to repository policy.
4. Accumulate user-facing work under `CHANGELOG.md` `[Unreleased]`.
5. Treat the feature as complete when it is merged and verified on `dev`.
6. Start a separate Forge release issue/session when a release train is approved.
7. Prepare the affected surface release on `dev`, including its version and notes.
8. Open and approve the release PR from `dev` into `main`.
9. Tag the new `main` tip with the affected surface prefix.
10. Build and publish that surface's artifacts, roll out or deploy from the
immutable tag, and verify the release and live environment.
### Branch names
@@ -177,23 +228,35 @@ version files and, for Android, on `appVersionCode` (which must be
monotonic).
Version-bump commits live on `dev` as the last commit of release-prep
work. Android commits use `release(android): android-vX.Y.Z`; plugin commits
use `release(plugin): plugin-vX.Y.Z`; CLI commits use
`release(cli): cli-vX.Y.Z`. A release PR then merges `dev` →
work. Android commits use `release(android): android-vX.Y.Z`; server commits
use `release(server): server-vX.Y.Z`; desktop commits use
`release(desktop): desktop-vX.Y.Z`. A release PR then merges `dev` →
`main` with `--no-ff`, and the matching tag is cut from the resulting
`main` tip.
### Branch protection
Light branch protection is enabled:
Repository files define the contract and CI, but GitHub owns the default branch,
branch protection, rulesets, allowed merge methods, and required-check settings.
Those settings require an operator or infrastructure automation.
- **`main`** — direct pushes blocked; only release PRs from `dev` merge
here. PR must pass CI (Android + Plugin) before merge. Force push and
branch deletion blocked.
- **`dev`** — direct pushes blocked for non-trivial work; feature
branches PR in. PR must pass CI. Force push and branch deletion
blocked.
- Signed commits + review approval NOT required (solo-dev overhead).
The intended settings are:
- **`main`** — PRs required; `Required checks` required and current; force push
and deletion blocked. Normal work does not target this branch.
- **`dev`** — PRs and `Required checks` required; force push and deletion
blocked. This is the normal contribution target.
- **Merge policy** — merge commits allowed; squash and rebase merges disabled so
the no-ff contract cannot be bypassed in the GitHub UI.
- **Default branch** — `main`, which remains the release-history branch and the
repository's canonical landing page. Normal contribution PRs must explicitly
target `dev`.
As of the 2026-07-15 repository audit, the default branch was correctly `main`.
The remaining GitHub-owned gaps were that `dev` had no protection, squash and
rebase merges were enabled, and `main` protection did not apply to
administrators. Those settings must be reconciled separately; this documentation
PR does not mutate them.
## One-time Setup
@@ -354,6 +417,15 @@ tag a **pre-release** (`android-vX.Y.Z-rc.N`). Users can opt in via
`hermes-relay-update --branch rc/vX.Y.Z-rc.N` without being auto-pushed
the unstable build.
## Release train ownership
Every release train gets its own Forge release issue/session. That owner records
the exact tested staging source, reconciles the affected surface version and
notes on `dev`, owns the `dev` → `main` PR, tags the new `main` tip, observes the
artifact workflow, performs the rollout or deployment, and captures live
verification. Feature implementation sessions stop at merged and verified on
`dev`; they do not inherit release authority.
## Release Process
### 1. Bump the Android app version
@@ -392,15 +464,36 @@ the new app version and a higher `appVersionCode`.
3. Skim the new versioned block and tighten / reorder if needed —
Keep-a-Changelog grouping (`Added` / `Changed` / `Fixed`) should
already be in place from the accumulator phase.
4. **Per-surface split.** `[Unreleased]` accumulates entries from *all
three* surfaces (Android + CLI + plugin), but releases are
per-surface. Move only the entries for the surface you're cutting into
the new versioned block, and leave the other surfaces' entries under
the fresh `[Unreleased]` for their own `desktop-v*` / `server-v*` cut.
(Those tracks' GitHub-Release bodies come from `CLI_RELEASE_NOTES.md` /
`PLUGIN_RELEASE_NOTES.md`, so the split here only governs this file's
historical record.)
- `RELEASE_NOTES.md` — body of the GitHub Release for this version
(rewritten each release; the workflow uses this as-is). This is the
operator-facing summary, not the CHANGELOG mirror. Keep the
**Download** section near the top — it should spell out which file
to grab by its `-sideload-release.apk` / `-googlePlay-release.aab`
suffix (every artifact is version-tagged as
**Download** section near the top, in the required format (#144):
1. A lead callout naming the **one file most people want** —
"Installing on your phone? Download
`hermes-relay-<version>-sideload-release.apk` and tap it"
(full feature set), with the Play Store link for the
conservative build.
2. One explicit line that the `.aab` is a Play Console upload
bundle and **cannot** be installed by tapping it on a phone.
3. The `SHA256SUMS.txt` verify line + sideload-guide link.
No download table, no parity/testing artifacts: releases attach
exactly **two** app artifacts — the sideload APK and the googlePlay
AAB — plus `SHA256SUMS.txt` covering exactly those two (the 2-asset
policy in `.github/workflows/release-android.yml`; the parity twins
stay reproducible from the tag via CI but are not attached).
Every artifact is version-tagged as
`hermes-relay-<version>-<flavor>-<buildType>` via `archivesName`
in `app/build.gradle.kts`) and link to the sideload guide.
The v0.3.0 body is a good template.
in `app/build.gradle.kts`. Never rename the sideload APK — the
in-app update checker matches assets by `.apk` + `sideload` in the
name, and user-docs verify steps cite the filename.
- `app/src/main/assets/whats_new.txt` — in-app "What's New" content
shown in the settings/about screen. Update with the version number
and a brief feature summary. Gets stale silently if forgotten
@@ -464,11 +557,41 @@ prefixed `hermes-relay-<version>-` via `archivesName` in
Optional device smoke test: `scripts\dev.bat release` then
`adb install -r app\build\outputs\apk\sideload\release\hermes-relay-*-sideload-release.apk`.
### 4. Commit on `dev`, merge to `main`, tag from `main`
### 4. Run the private Play preflight from `dev`
The release-prep commit lands on `dev` first. Then a release PR merges
`dev` → `main` with `--no-ff`, and the `android-v<version>` tag is cut from the
resulting merge commit on `main`:
The release-prep commit lands on `dev` first. Before any public tag or GitHub
Release exists, open **Actions → Play Preflight — Android**, choose **Run
workflow**, select the final `dev` branch, and enter the prepared version.
The preflight workflow:
1. requires the workflow to run from `dev` or untagged `main` with matching
version metadata;
2. runs the release metadata, locale, and Android collection-API checks;
3. builds and release-signs the same APK/AAB variants used by the public release;
4. scans the final minified APK DEX for unsupported collection calls;
5. uploads the Google Play AAB as a private **Production draft**; and
6. records a 30-day preflight proof keyed to the version and Git tree hash.
No sideload APK or GitHub Release is published by preflight. A successful signed
build, final DEX scan, and Production-draft upload is the automated Play release
gate. Play Console pre-review and pre-launch reports are informational and
non-blocking because their detailed results are not exposed through the release
automation API. If the release source changes after preflight, rerun it—the
approval workflow matches the complete Git tree, not just the version number.
GitHub exposes manual workflows only after their workflow file exists on the
default branch. For the first release that introduces this process, merge the
release PR without creating a tag, run preflight from untagged `main`, and then
use the approval workflow. This publishes no app artifacts before the automated
Play upload gate.
### 5. Merge to `main` and approve the public release
After Play preflight passes, merge the release PR from `dev` to `main`
with `--no-ff`. The merge commit may differ from the preflight commit, but its
tree must be identical. If the merge changes the tree, rerun private preflight
from untagged `main`:
```bash
# From a clean dev checkout:
@@ -480,29 +603,38 @@ git add gradle/libs.versions.toml RELEASE_NOTES.md CHANGELOG.md \
git commit -m "release(android): android-v0.6.2"
git push origin dev
# Run Play Preflight — Android from dev and require a successful workflow.
# Open the release PR (dev -> main) and merge with --no-ff.
# After merge, tag from the new main tip:
git checkout main
git pull --ff-only origin main
git tag android-v0.6.2
git push origin android-v0.6.2
```
Pushing a tag matching `android-v*` triggers `.github/workflows/release-android.yml`,
which builds, signs, checksums, and creates a GitHub Release. Watch the
run under the **Actions** tab.
Then open **Actions → Approve Android Release**, choose **Run workflow**, select
`main`, and enter the version. Starting the workflow is the release approval. It
verifies that `main` has the exact preflighted tree and creates the
`android-v<version>` tag. Because tags created with `GITHUB_TOKEN` do not trigger
another workflow, approval dispatches the current release workflow definition
from `main`; every release job explicitly checks out and verifies the immutable
`android-v<version>` tag. This lets release-workflow fixes apply without moving
an existing tag or changing its artifact tree. Manual stable tags are still
guarded by the same preflight proof in the tag workflow.
The tag-triggered `.github/workflows/release-android.yml` rebuilds and scans the
artifacts, changes the existing Play Production draft to `completed` (submitting
it for review), and only after Play accepts that operation creates the public
GitHub Release with the sideload APK. A missing preflight, changed release tree,
missing Play credential, or Play submission failure prevents public GitHub
publication.
Plugin/Python version files are intentionally not part of an Android app
release unless the plugin package itself is also being released.
### Plugin / Python package release
### Server / Python package release
Use this when plugin or relay behavior changes independently of Android app
delivery, for example CLI channel support, bridge routes, pairing server fixes,
voice auth, dashboard plugin UI, or packaging changes.
First **rewrite `PLUGIN_RELEASE_NOTES.md`** — it is the GitHub Release body for
`plugin-v*` tags (the same role `RELEASE_NOTES.md` plays for Android). Fill the
`server-v*` tags (the same role `RELEASE_NOTES.md` plays for Android). Fill the
Summary and the Added/Changed/Fixed groups from the plugin-relevant bullets in the
promoted `CHANGELOG.md` block, keep the `__VERSION__` token in the Install command
(the workflow substitutes it), and apply the same public-distribution scrub as §2.
@@ -513,40 +645,81 @@ git pull --ff-only origin dev
bash scripts/bump-plugin-version.sh 0.6.2
git add pyproject.toml plugin/relay/__init__.py plugin/plugin.yaml plugin/dashboard/manifest.json plugin/dashboard/package.json plugin/dashboard/package-lock.json CHANGELOG.md PLUGIN_RELEASE_NOTES.md
git commit -m "release(plugin): plugin-v0.6.2"
git commit -m "release(server): server-v0.6.2"
git push origin dev
# Open the release PR (dev -> main) and merge with --no-ff.
# After merge, tag from the new main tip:
git checkout main
git pull --ff-only origin main
git tag plugin-v0.6.2
git push origin plugin-v0.6.2
git tag server-v0.6.2
git push origin server-v0.6.2
```
Pushing `plugin-v*` triggers `.github/workflows/release-plugin.yml`, which
Pushing `server-v*` triggers `.github/workflows/release-plugin.yml`, which
validates all plugin-owned version metadata with
`scripts/check-plugin-version-sync.py`. Run
`python scripts/check-version-tracks.py` locally before tagging when a change
touches more than one release surface. The workflow also runs plugin tests,
builds a wheel and sdist, generates `SHA256SUMS.txt`, and creates a GitHub
Release named `Hermes-Relay-Plugin v<version>` for the plugin package.
Release named `Hermes-Relay-Server v<version>` for the server/plugin package.
### 5. Upload to Play Console
### CLI / Windows systray release
> **If `PLAY_SERVICE_ACCOUNT_JSON` is configured as a repo secret, this step is
> automated for stable tags.** The release workflow runs
> `publishGooglePlayReleaseBundle --track=production` and the build appears as a
> Production **draft** — skip to the Play Console, confirm the draft, and click
> **Start rollout**. The manual path below is the fallback when the secret is
> unset (or for staging on a non-production track).
Use this when the standalone CLI, daemon, desktop tools, or Windows tray changes.
Android and plugin versions do not need to move with it.
First rewrite `CLI_RELEASE_NOTES.md` for the new Desktop release and promote only
CLI/tray-relevant changelog bullets into the release block. Then:
```powershell
git switch dev
git pull --ff-only origin dev
cd desktop
npm version --no-git-tag-version 0.4.0-alpha.2
npm run verify
cd ..
git add desktop/package.json desktop/package-lock.json desktop/src/version.ts `
desktop/tray/Cargo.toml desktop/tray/Cargo.lock CHANGELOG.md CLI_RELEASE_NOTES.md
git commit -m "release(desktop): desktop-v0.4.0-alpha.2"
git push origin dev
# Open the release PR (dev -> main) and merge with --no-ff.
# After merge, tag from main:
git switch main
git pull --ff-only origin main
cd desktop
npm run check:version-sync -- --expect 0.4.0-alpha.2
cd ..
git tag desktop-v0.4.0-alpha.2
git push origin desktop-v0.4.0-alpha.2
```
The tag workflow rejects version drift and tags whose commit is not in
`origin/main`, reruns CLI tests, builds all four standalone binaries, tests and
packages the Windows tray, generates checksums, and publishes the GitHub Release.
### 6. Play review and publishing behavior
> **Stable Android releases require `PLAY_SERVICE_ACCOUNT_JSON`.** Preflight
> uploads the Production draft; approval promotes that same version code to
> `completed`. Play Console-only reports are informational and non-blocking.
> Stable releases do not fall back to publishing GitHub first when Play
> credentials or submission are unavailable.
>
> This automated tag path is intentionally bundle-only. It uploads the
> This automated path is intentionally bundle-only. It uploads the
> `googlePlayRelease` AAB and release-scoped "What's new" notes, but it does
> not republish static listing assets such as screenshots, title, description,
> icon, or feature graphic. Use the Play Store Listing workflow when those
> assets change.
If Play Console **Managed publishing** is enabled, an approved submission remains
under **Changes ready to publish** until a Play Console user publishes it. If it
is disabled, the production submission may become available after Google review.
Either behavior begins only after the public-release approval described above.
**Pick the track first.** The AAB is track-agnostic — the same
`-googlePlay-release.aab` goes to whichever track you publish on. Choose by intent,
not habit:
@@ -593,7 +766,7 @@ To promote an existing release between tracks without rebuilding:
gradlew promoteReleaseArtifact --from-track=internal --promote-track=alpha
```
### 6. Tracks (a menu, not a mandatory ladder)
### 7. Tracks (a menu, not a mandatory ladder)
The org account is exempt from the 14-day / 12-tester closed-testing rule, so a
stable GA publishes **straight to Production** — there is no required promotion
@@ -612,7 +785,7 @@ the Play Console UI or:
gradlew promoteReleaseArtifact --from-track=internal --promote-track=production
```
### 7. After release
### 8. After release
- Verify the GitHub Release has APK, AAB, and `SHA256SUMS.txt` attached.
- Confirm the release body includes the **Download** section that tells
@@ -637,39 +810,46 @@ plugin changes from forcing an Android app `versionCode` bump.
On every push of a tag matching `android-v*`, `.github/workflows/release-android.yml`:
1. Validates the tag matches `appVersionName` in
1. Verifies the stable tag resolves to a commit contained in `main` and that the
tag matches `appVersionName` in
`gradle/libs.versions.toml` (mismatches fail the workflow).
2. Runs the Android debug build and the stable sideload pairing/connection
regression slice with explicit timeouts.
3. Decodes `HERMES_KEYSTORE_BASE64` into `$RUNNER_TEMP/release.keystore`
and exports `HERMES_KEYSTORE_PATH` (skipped if the secret is unset).
4. Builds both Android release artifacts:
`./gradlew bundleRelease assembleRelease`.
5. Generates `SHA256SUMS.txt` covering both.
6. Creates a GitHub Release named `Hermes-Relay-Android v<version>` with `RELEASE_NOTES.md` as
4. Builds all four flavored release artifacts
(`./gradlew bundleRelease assembleRelease`); only the sideload APK and
googlePlay AAB are attached (see §Release assets).
5. Generates `SHA256SUMS.txt` covering the two attached files.
6. Promotes the exact preflighted Production draft to `completed`; a missing
credential or rejected Play edit fails before public GitHub publication.
7. Creates a GitHub Release named `Hermes-Relay-Android v<version>` with `RELEASE_NOTES.md` as
the body. Attaches the APK, AAB, and `SHA256SUMS.txt`. Tags any version
containing a dash (e.g. `android-v0.2.0-beta.1`) as a prerelease automatically.
7. Prints a `$GITHUB_STEP_SUMMARY` showing whether release signing
succeeded. If `HERMES_KEYSTORE_BASE64` is missing, the summary warns
that the artifacts are debug-signed and unsuitable for Play Store.
8. Prints a `$GITHUB_STEP_SUMMARY` with the release and Play result.
On every push of a tag matching `plugin-v*`,
On every push of a tag matching `server-v*`,
`.github/workflows/release-plugin.yml`:
1. Validates the tag matches all plugin-owned version metadata checked by
`scripts/check-plugin-version-sync.py`.
1. Verifies the tag commit is contained in `main`, validates the tag against
all server/plugin-owned version metadata checked by
`scripts/check-plugin-version-sync.py`, and requires the matching release
heading in `CHANGELOG.md`.
2. Runs plugin syntax checks and the focused route/auth/session test slice.
3. Builds the Python wheel and sdist with `python -m build`.
4. Generates `dist/SHA256SUMS.txt`.
5. Creates a GitHub Release named `Hermes-Relay-Plugin v<version>` with the wheel,
5. Creates a GitHub Release named `Hermes-Relay-Server v<version>` with the wheel,
sdist, and checksum file attached.
On every push of a tag matching `cli-v*`,
On every push of a tag matching `desktop-v*`,
`.github/workflows/release-cli.yml` builds and publishes the CLI binaries and
Windows tray installer. Its GitHub Release body comes from `CLI_RELEASE_NOTES.md`
(rewritten per release — the CLI counterpart of `RELEASE_NOTES.md`); the workflow
substitutes `__VERSION__` (bare, e.g. `0.3.0`) and `__TAG__` (full, e.g.
`cli-v0.3.0`) so the install/pin commands stay accurate. Fill its Summary and
`desktop-v0.3.0`) so the install/pin commands stay accurate. It rejects tags
whose commit is not contained in `main`, whose version differs from
`desktop/package.json`, or whose version has no `CHANGELOG.md` release heading.
Fill its Summary and
Added/Changed/Fixed groups at CLI release-prep and apply the §2 public scrub.
Dashboard-only changes are covered by
`.github/workflows/ci-dashboard.yml`, which builds the dashboard plugin,
@@ -684,19 +864,28 @@ in the built bundle.
| `HERMES_KEYSTORE_PASSWORD` | Store password | Password set during `keytool -genkey` |
| `HERMES_KEY_ALIAS` | Key alias | Alias set during `keytool -genkey` |
| `HERMES_KEY_PASSWORD` | Key password | Usually the same as the store password |
| `PLAY_SERVICE_ACCOUNT_JSON` | **Optional** — Play auto-upload | Paste the full Play Developer API service-account JSON (step 3) |
| `PLAY_SERVICE_ACCOUNT_JSON` | Stable Play submission | Paste the full Play Developer API service-account JSON (step 3) |
If `PLAY_SERVICE_ACCOUNT_JSON` is set, the `android-v*` release workflow uploads
the `googlePlay` AAB to the **Production track as a DRAFT** automatically (stable
tags only — prereleases are skipped). CI does the upload; you still click **Start
rollout** in Play Console. If the secret is unset, the workflow skips the upload
and you upload manually (§5) — nothing else changes.
Stable Android releases require `PLAY_SERVICE_ACCOUNT_JSON`. Preflight uploads
the Production draft and the tag workflow promotes that exact version code to
`completed`. The workflow does not fall back to manual upload or publish GitHub
first. With Play Managed Publishing off, an approved release publishes
automatically; with it on, Play holds the approved change for an operator action
that the Developer API does not expose.
## Hotfix Recipe
When production has a bug and you need to ship a fix without picking up
unreleased work from `dev`, branch from the affected release tag and only
bump the version source for the surface you are shipping.
When production has a bug, use the same invariant for every surface:
1. Branch from the affected immutable `android-v*`, `server-v*`, or `desktop-v*`
production tag, never from the moving `main` or `dev` branch.
2. Make the smallest safe fix and add focused verification.
3. Bump only the affected surface's patch version and release notes.
4. Open the focused hotfix PR into `main` and merge with a merge commit/no-ff.
5. Tag the new `main` tip with the affected surface's patch tag.
6. Verify the artifacts and production rollout or deployment.
7. Merge `main` back into `dev` immediately so integration inherits the fix and
version history.
For an Android app hotfix:
@@ -710,17 +899,23 @@ For an Android app hotfix:
5. Open a PR from `fix/short-name` into `main`, merge with `--no-ff`.
6. `git tag android-v0.6.2` from the new `main` tip and `git push origin android-v0.6.2`
so Android release CI builds and publishes.
7. Upload to Play Console as normal.
7. Verify the automated Play submission, GitHub artifacts, and rollout.
8. Merge `main` back into `dev` (`git checkout dev && git merge --no-ff main`)
so `dev` picks up the hotfix and the versionCode bump. Without this,
`dev`'s `appVersionCode` lags behind `main` and the next app release
bump collides.
For a Plugin hotfix, branch from the affected `plugin-v*` tag, apply
For a Server hotfix, branch from the affected `server-v*` tag, apply
the fix, run `bash scripts/bump-plugin-version.sh <next-version>`, merge to
`main`, and tag `plugin-v<next-version>`. Do not touch
`main`, tag `server-v<next-version>`, verify the package/deployment, and merge
`main` back to `dev`. Do not touch
`gradle/libs.versions.toml` unless an Android app release is also shipping.
For a Desktop hotfix, branch from the affected `desktop-v*` tag, update only
`desktop/package.json` and its generated lock/runtime/tray metadata, merge to
`main`, tag `desktop-v<next-version>`, verify all binaries and the installer,
then merge `main` back to `dev`.
## Troubleshooting
**`Tag version (X) does not match appVersionName (Y)` in CI validate step**
+16 -54
View File
@@ -1,66 +1,28 @@
# Hermes-Relay-Android v1.2.0
# Hermes-Relay-Android v1.5.2
**Release Date:** June 20, 2026
**Since v1.1.0:** A big personalization release — app themes, swappable sphere skins, and animated agent **pets** — paired with a transparency pass (see which transport you're on and exactly what the agent is told), a much faster cold start, in-app crash reporting, and a broad reliability sweep.
v1.2.0 is about making Hermes-Relay feel like *yours* and making it honest about what it's doing. Dress the app in one of eight themes, swap the agent orb for a hand-picked or AI-generated **pet** that reacts to what the agent is doing, and give each profile its own icon. At the same time, the chat status strip now names the actual streaming path (⚡ Gateway, 📡 Sessions, …), a "What the agent sees" sheet shows the exact extra context prepended to your next turn, and cold start is roughly three times faster. If something does go wrong, the app now catches the crash and offers a one-tap, pre-filled bug report.
---
**Release Date:** July 28, 2026
## Download
v1.2.0 ships in two Android build flavors. APK and AAB filenames are version-tagged:
> Installing on your phone? Download `hermes-relay-1.5.2-sideload-release.apk` and tap it for the full feature set, or install the conservative build from [Google Play](https://play.google.com/store/apps/details?id=com.axiomlabs.hermesrelay).
| Flavor | File | Who it's for |
|---|---|---|
| Google Play | `hermes-relay-1.2.0-googlePlay-release.aab` | Upload this Android App Bundle to Play Console. It has no AccessibilityService, screen reading, screenshots, gestures, SMS/calls, contacts/location, overlays, or unattended phone control. |
| sideload | `hermes-relay-1.2.0-sideload-release.apk` | Direct-install APK for full Device Control. Installs as `com.axiomlabs.hermesrelay.sideload`. |
| googlePlay APK | `hermes-relay-1.2.0-googlePlay-release.apk` | Parity/testing artifact. |
| sideload AAB | `hermes-relay-1.2.0-sideload-release.aab` | Parity/testing artifact. |
The `.aab` file is a Play Console upload bundle and cannot be installed by tapping it on a phone.
Verify integrity with `SHA256SUMS.txt` from the same release. See the [Sideload guide](https://codename-11.github.io/hermes-relay/guide/getting-started.html#sideload-apk) for APK install steps.
Verify the download against `SHA256SUMS.txt`. See the [sideload guide](https://hermes-relay.dev/docs/guide/sideload) for installation help.
---
## Summary
## Highlights
This patch restores reliable dashboard sign-in for self-hosted OIDC and Nous Portal connections, including private-LAN and Tailscale routes, and prevents replayed chat events from destabilizing the conversation list.
### Make it yours
## Fixed
- **App themes.** A theme picker in Settings → Appearance ships eight looks — the signature Hermes Relay brand (full light/dark) plus ports of the Nous Hermes baselines: Hermes Teal, Nous Blue, Midnight, Ember, Mono, Cyberpunk, and Rosé. The whole app follows your choice; Light/Dark/Auto applies to themes that ship both modes.
- **Agent pets — a living avatar.** Replace the orb with an animated pet that reacts to the agent: idle / thinking / writing / speaking / listening, a distinct **working** pose during tool calls, one-shot **greet** and **celebrate** reactions, and a loop that speeds up as output streams. Add or remove pets right in Appearance (no `adb`), preview each state, tune playback speed, and toggle frame auto-stabilization. Pets are pure data — an AI authoring kit and JSON schema let you generate one from sprite art.
- **Hot-swappable sphere skins + per-profile icons.** Keep the orb but reskin it (Adaptive, Classic, Aurora, Solar, Mono, or your own JSON skin), and give each agent profile its own small icon beside its name — all client-side, never sent to Hermes.
- Self-hosted OIDC returns through the dashboard cookie flow instead of a desktop-only loopback callback.
- Nous Portal authentication opens in the system browser so provider security challenges can complete.
- Native PKCE uses standards-compatible unpadded Base64URL and preserves the dashboard's canonical HTTPS callback origin while keeping tokens scoped to the active route.
- Full-screen in-app sign-in remains available for compatible dashboard providers.
- Replayed upstream chat events are coalesced before rendering, preventing duplicate message keys.
### See what's actually happening
## Install / Verify
- **Transport path is visible.** The chat status strip now shows which streaming path is in use — ⚡ Gateway (live thinking), 📡 Sessions, Completions, or Runs — and Chat Settings adds a basic→best tier ladder explaining the active path and its fallback.
- **"What the agent sees" sheet.** Tap the context meter to see the exact extra context prepended to your next turn — persona/profile, phone status, any per-turn voice hint, and (when paired) the relay's own server-side context. The audit is honest about what the phone sends versus what's applied on the server.
- **Spoken-turn badges + voice render-path visibility.** Voice and Realtime Agent replies carry a chip in the scrollback, and Voice Settings shows whether speech is rendering over the streaming or basic path.
### Privacy
- **Sensitive-media blur.** When paired to the relay, the agent can mark private/NSFW media and the phone blurs it per your setting — sensitivity stays model-emitted (no on-device or relay-side classifier), and the exact instruction is visible in the "What the agent sees" sheet. Vanilla Hermes (no plugin) is unaffected.
### Faster, calmer, more honest
- **~3× faster cold start.** The app was building several hardware-keystore-encrypted stores at launch, serializing on a process-global lock and stalling the chat header for seconds. It now builds a single keyset shared with the dashboard cookies, cutting measured time-to-connected from ~2.9 s to ~1 s. Existing sign-ins migrate automatically.
- **Honest loading, never stale.** Model, personality, and approvals show a brief "checking…" state and fade in once the server confirms them; standard controls (Model, YOLO, Fast, reasoning effort) always appear — live when ready, "checking…" while loading, or cleanly disabled with the reason — instead of being hidden or showing a maybe-wrong value.
### More reliable
- **In-app crash reporting.** A force-close now surfaces a clean dialog on next launch with the stack trace — Copy it, or **Report** to open a pre-filled GitHub issue from the bug template. The handler re-raises so Play vitals still record the crash.
- **QR pairing hardened for foldables.** On devices where the camera can't initialize, the scanner shows a "camera unavailable — pair manually" card instead of force-closing.
- **Crash fixes.** No more crash opening a chat with a server-local image, and the PDF viewer no longer crashes when a document closes mid-render.
- **Chat correctness.** In-chat model picks now actually apply — both on a new chat and mid-conversation — server-side turn errors stay on screen as an error bubble, per-reply token counts and provenance badges survive the post-turn reload, and server steering markers (`[System: …]`) no longer appear as chat bubbles.
### Voice & terminal polish
- **Enhanced voice control (Gemini & xAI).** When the relay uses a Gemini or xAI voice provider, Voice Settings can pick a voice/model and turn on expressive tone/speech tags. Vanilla Hermes voice stays configured server-side.
- **Leaner terminal.** A scrollable, fully-legible key bar, TUI-correct arrows and bracketed paste, a compact single-row header, and relay sessions on an isolated, TUI-tuned tmux so editors and full-screen tools behave.
---
## Upgrade notes
- Cold-start speedup migrates the encrypted credential and dashboard-cookie stores automatically on first launch; in rare cases Manage/voice may ask for a one-time re-login (cookies are re-obtainable).
- App themes, sphere skins, and pets are available on **both** flavors — they're client-side and need no Device Control.
- `appVersionCode` is **14**.
- App version: **1.5.2** (versionCode **35**).
- Standard Chat and Vanilla Hermes voice continue to work against unmodified upstream Hermes.
+2 -2
View File
@@ -101,7 +101,7 @@ Small follow-ons to v0.4 deliberately deferred to keep the v0.4.0 release surfac
**What the middleware can do (near-term, ships via install.sh).** New aiohttp middleware in `hermes_relay_bootstrap/_command_middleware.py`, installed at the same `_PatchedApplication.__setitem__` hook as the current route injection so it lands before `AppRunner.setup()` freezes the app. Filters by `request.path in ("/v1/runs", "/v1/chat/completions")` — zero-cost fast path for everything else. On chat paths: parses the body, lazy-imports `GATEWAY_KNOWN_COMMANDS` + `resolve_command()` + `gateway_help_lines()` from `hermes_cli.commands`, and splits on command type:
- **Stateless commands** (`/help`, `/commands`, and any others the upstream Option B PR ends up supporting without router state) — actually dispatch, emit a synthetic SSE stream matching the runs handler's existing event shape so the Android client at `HermesApiClient.kt:655-715` renders it as a normal assistant turn.
- **Stateful commands** (`/model`, `/new`, `/retry`, `/undo`, `/compress`, `/title`, `/resume`, `/branch`, `/rollback`, `/yolo`, `/reasoning`, `/personality`, etc. — most of the registry) — emit a synthetic SSE stream whose content is a short, helpful notice: *"The `/model` command requires a persistent session and isn't available on the stateless `/v1/runs` endpoint. Use `/api/sessions/{id}/chat/stream` (post-PR-#8556) or a channel with session state. For commands that work here, type `/help`."* This replaces the LLM hallucination with a deterministic, accurate message that points the user at the real fix.
- **Stateful commands** (`/model`, `/new`, `/retry`, `/undo`, `/compress`, `/title`, `/resume`, `/branch`, `/rollback`, `/yolo`, `/reasoning`, `/personality`, etc. — most of the registry) — emit a synthetic SSE stream whose content is a short, helpful notice: *"The `/model` command requires a persistent session and isn't available on the stateless `/v1/runs` endpoint. Use `/api/sessions/{id}/chat/stream` or a channel with session state. For commands that work here, type `/help`."* This replaces the LLM hallucination with a deterministic, accurate message that points the user at the real fix.
**On no match** (unknown command, cli-only command, or plain text): falls through to `handler(request)` unchanged. Fork-detects the same way the existing injection does — if the upstream preprocessor PR lands first, the middleware no-ops.
@@ -109,7 +109,7 @@ Small follow-ons to v0.4 deliberately deferred to keep the v0.4.0 release surfac
**Files.** New `hermes_relay_bootstrap/_command_middleware.py` (~150 LOC), one-line append in `_patch.py` inside `_maybe_register_routes`, stdlib `unittest` coverage in `plugin/tests/test_bootstrap_command_middleware.py` mirroring the existing `test_bootstrap_patch.py` harness. Mirrors the upstream Option B PR exactly so the two can be reviewed side-by-side.
**Phase 2 — stateful dispatch on the session chat stream endpoint (post PR #8556).** Once PR #8556 merges and `/api/sessions/{id}/chat/stream` ships natively in upstream, a separate middleware (or a follow-up upstream PR) can add a preprocessor **scoped to that endpoint only**, leveraging the `session_id` in the URL as the persistence handle. At that point stateful commands become a dict write against session-scoped state — `session.model_override = new_model` — without needing to refactor `GatewayRouter` or plumb api_server into the router. Much smaller than a full router refactor, and it matches upstream's partition: `/v1/*` stays stateless, statefulness lives on `/api/sessions/*`. Blocked on #8556 landing.
**Phase 2 — stateful dispatch on the session chat stream endpoint (unblocked by PR #33134).** Since `/api/sessions/{id}/chat/stream` now ships natively in upstream, a separate middleware (or a follow-up upstream PR) can add a preprocessor **scoped to that endpoint only**, leveraging the `session_id` in the URL as the persistence handle. At that point stateful commands become a dict write against session-scoped state — `session.model_override = new_model` — without needing to refactor `GatewayRouter` or plumb api_server into the router. Much smaller than a full router refactor, and it matches upstream's partition: `/v1/*` stays stateless and statefulness lives on `/api/sessions/*`.
## Future — v0.5+
+91
View File
@@ -0,0 +1,91 @@
# Security Policy
Hermes-Relay can give a remote AI agent real control of a phone and, via the
CLI, of a paired desktop. We take security reports seriously and welcome
responsible disclosure.
For the architecture, threat model, and the `googlePlay` vs. `sideload`
capability boundary, see [`docs/security.md`](docs/security.md). This document
covers **how to report a problem**.
## Reporting a Vulnerability
**Please do not open a public issue, discussion, or pull request for a security
vulnerability.** Public reports expose users before a fix is available.
Use one of these private channels instead:
1. **GitHub Private Vulnerability Reporting (preferred).** Go to the
repository's **Security** tab → **Report a vulnerability**, or
[open a draft advisory directly](https://github.com/Codename-11/hermes-relay/security/advisories/new).
This keeps the whole exchange private and threaded with the code.
2. **Email** — `security@codename-11.dev`. Use this if you can't use GitHub.
If you'd like to encrypt the report, say so in a first contact message and
we'll arrange a key.
### What to include
A good report lets us reproduce and assess impact quickly:
- The affected surface — **Android app** (and which flavor, `googlePlay` or
`sideload`), **relay plugin / server**, **desktop CLI**, or the **docs site**.
- Affected version(s) — app version/code, plugin version, or CLI version.
- A clear description of the issue and its security impact.
- Step-by-step reproduction, a proof of concept, or a minimal example.
- Any suggested remediation, if you have one.
> ⚠️ **Scrub secrets before sending.** Remove API keys, relay session tokens,
> pairing codes, real hostnames/IPs, and personal data from logs, traces, and
> screenshots.
## What to Expect
This is an indie, open-source project, so timelines are best-effort rather than
contractual:
- **Acknowledgement** of your report — typically within **5 business days**.
- An initial **assessment and severity triage** after we can reproduce it.
- **Coordinated disclosure:** we'll work with you on a fix and a disclosure
timeline, and credit you in the advisory and release notes if you'd like
(or keep you anonymous if you prefer).
- A public GitHub Security Advisory and a `CHANGELOG.md` entry once a fix ships.
## Scope
**In scope** — vulnerabilities in code this project ships:
- The Android app (`app/`) on either flavor.
- The relay plugin and server (`plugin/`).
- The desktop CLI (`desktop/`).
- The pairing, auth, transport, media, and tool-routing surfaces.
**Out of scope** — please report these to the right place instead:
- **Your own Hermes server configuration** (missing TLS, an exposed dashboard,
weak provider keys). The relay connects only to endpoints you configure; how
you deploy and secure your Hermes host is outside this app. See
[`docs/security.md`](docs/security.md) and the relay-server docs for hardening
guidance.
- **Upstream [hermes-agent](https://github.com/NousResearch/hermes-agent)**
issues — report those to the upstream project (a heads-up to us is welcome if
it affects how Hermes-Relay should behave).
- **Third-party dependencies** — report upstream; if a dependency issue affects
Hermes-Relay users, tell us so we can pin or patch.
- Findings that require a **rooted device, a physical-access attacker, or a
malicious app already granted Accessibility/overlay permissions** — these are
outside the model documented in `docs/security.md`, though we'll still read
the report.
## Safe Harbor
We consider security research conducted in good faith under this policy to be
authorized. We will not pursue or support legal action against researchers who:
- Make a good-faith effort to avoid privacy violations, data destruction, and
service disruption.
- Test only against **their own devices, installs, and Hermes servers** — never
another person's data or infrastructure.
- Report promptly and give us a reasonable chance to remediate before any
public disclosure.
Thank you for helping keep Hermes-Relay and its users safe.
+1059 -46
View File
File diff suppressed because it is too large Load Diff
+26 -6
View File
@@ -27,7 +27,7 @@ android {
// and `applicationId` is the runtime install identity; they don't have
// to match.
namespace = "com.hermesandroid.relay"
compileSdk = 36
compileSdk = 37
defaultConfig {
// Axiom-Labs, LLC Play Console listing. Changed from the original
@@ -37,7 +37,7 @@ android {
// exempt from Play's 14-day closed-testing rule. See RELEASE.md.
applicationId = "com.axiomlabs.hermesrelay"
minSdk = 26
targetSdk = 35
targetSdk = 36
versionCode = libs.versions.appVersionCode.get().toInt()
versionName = libs.versions.appVersionName.get()
@@ -182,7 +182,13 @@ android {
// [POC] Roborazzi runs without its Gradle plugin (the plugin needs AGP's
// removed TestedExtension). Force record mode via the test-JVM system
// property the plugin would otherwise inject, so captureRoboImage writes.
unitTests.all { it.systemProperty("roborazzi.test.record", "true") }
// Heap: the Roborazzi store renders (1080×2160 native graphics) share a
// worker JVM with the Robolectric suites; Gradle's 512m default OOMs
// once both are in the same run.
unitTests.all {
it.systemProperty("roborazzi.test.record", "true")
it.maxHeapSize = "2g"
}
}
}
@@ -239,6 +245,8 @@ dependencies {
// Activity
implementation(libs.activity.compose)
implementation(libs.browser)
implementation(libs.appcompat)
// Core
implementation(libs.core.ktx)
@@ -254,6 +262,15 @@ dependencies {
// Bundled ONNX Silero model (~2.2 MB); pulled from JitPack.
implementation(libs.android.vad.silero)
// Google Play In-App Update — googlePlay flavor ONLY (FLEXIBLE flow).
// Scoped via the `googlePlayImplementation` configuration so it never
// ships in the sideload APK, which updates via the GitHub-releases
// UpdateChecker instead. The `app/src/googlePlay/.../update/` impl
// references AppUpdateManager; the `app/src/sideload/.../update/` impl
// never touches this library.
"googlePlayImplementation"(libs.play.app.update)
"googlePlayImplementation"(libs.play.app.update.ktx)
// Markdown rendering
implementation(libs.markdown.renderer.m3)
implementation(libs.markdown.renderer.code)
@@ -281,6 +298,9 @@ dependencies {
// Security
implementation(libs.security.crypto)
// Force a Tink newer than security-crypto's transitive one — older Tink's
// HybridConfig removeFirst()/removeLast() trips the Android-15 crash lint.
implementation(libs.tink.android)
// DataStore
implementation(libs.datastore.preferences)
@@ -307,10 +327,10 @@ dependencies {
// [POC] Roborazzi host-side screenshot rendering (src/test, Robolectric).
// Renders real composables on the JVM at an exact canvas — no device, no
// status bar, no clipping. See StoreScreenshotTest.
testImplementation("io.github.takahirom.roborazzi:roborazzi:1.43.1")
testImplementation("io.github.takahirom.roborazzi:roborazzi-compose:1.43.1")
testImplementation("io.github.takahirom.roborazzi:roborazzi:1.70.0")
testImplementation("io.github.takahirom.roborazzi:roborazzi-compose:1.70.0")
testImplementation(libs.compose.ui.test.junit4)
testImplementation(libs.compose.ui.test.manifest)
testImplementation("androidx.test.ext:junit:1.2.1")
testImplementation("androidx.test.ext:junit:1.3.0")
}
@@ -0,0 +1,48 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.test.core.app.ApplicationProvider
import androidx.test.ext.junit.runners.AndroidJUnit4
import kotlinx.coroutines.flow.first
import kotlinx.coroutines.runBlocking
import org.junit.Test
import org.junit.runner.RunWith
/** Local device-review helper. Never runs in or ships with the application APK. */
@RunWith(AndroidJUnit4::class)
class ConnectionReviewSeedTest {
@Test
fun seedOfflineSecondaryConnection() = runBlocking {
val context = ApplicationProvider.getApplicationContext<Context>()
val store = ConnectionStore(context)
store.isHydrated.first { it }
if (store.connections.value.none { it.id == REVIEW_ID }) {
store.addConnection(
Connection(
id = REVIEW_ID,
label = "Lab NAS",
apiServerUrl = "",
relayUrl = "",
tokenStoreKey = Connection.buildTokenStoreKey(REVIEW_ID),
dashboardUrl = "http://192.0.2.10:9119",
lastUsedAt = System.currentTimeMillis() - 2L * 24L * 60L * 60L * 1_000L,
),
)
}
}
@Test
fun removeOfflineSecondaryConnection() = runBlocking {
val context = ApplicationProvider.getApplicationContext<Context>()
val store = ConnectionStore(context)
store.isHydrated.first { it }
if (store.connections.value.any { it.id == REVIEW_ID }) {
store.removeConnection(REVIEW_ID)
}
}
private companion object {
const val REVIEW_ID = "00000000-0000-4000-8000-000000000220"
}
}
@@ -121,42 +121,39 @@ class OnboardingFlowTest {
}
@Test
fun connectPage_showsStandardChoiceFirst() {
fun connectPage_showsNearbyFirst() {
setOnboardingContent()
navigateToPage(4)
composeTestRule
.onNodeWithText("Vanilla Hermes")
.onNodeWithText("Enter address instead")
.assertIsDisplayed()
}
@Test
fun standardSetup_showsApiFields() {
fun manualSetup_showsHermesAddressWithoutApiCredentials() {
setOnboardingContent()
navigateToPage(4)
composeTestRule.onNodeWithText("Vanilla Hermes").performClick()
composeTestRule.onNodeWithText("Enter address instead").performClick()
composeTestRule.waitForIdle()
composeTestRule
.onNodeWithText("API server URL")
.assertIsDisplayed()
composeTestRule
.onNodeWithText("API key")
.onNodeWithText("Hermes address")
.assertIsDisplayed()
}
@Test
fun standardSetup_connectButton_isEnabled_withDefaultUrl() {
fun manualSetup_findButton_isShown() {
setOnboardingContent()
navigateToPage(4)
composeTestRule.onNodeWithText("Vanilla Hermes").performClick()
composeTestRule.onNodeWithText("Enter address instead").performClick()
composeTestRule.waitForIdle()
composeTestRule
.onNodeWithText("Connect")
.assertIsEnabled()
.onNodeWithText("Find Hermes")
.assertIsDisplayed()
}
@Test
@@ -164,6 +161,9 @@ class OnboardingFlowTest {
setOnboardingContent()
navigateToPage(4)
composeTestRule.onNodeWithText("Other connection methods").performClick()
composeTestRule.waitForIdle()
composeTestRule
.onNodeWithText("Pair Relay by code")
.assertIsDisplayed()
+13
View File
@@ -0,0 +1,13 @@
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<application>
<activity
android:name="com.hermesandroid.relay.ui.screens.VoiceSettingsDesignQaActivity"
android:exported="true"
android:screenOrientation="portrait" />
<activity
android:name="com.hermesandroid.relay.ui.screens.ImageGenerationDesignQaActivity"
android:exported="true"
android:screenOrientation="portrait" />
</application>
</manifest>
@@ -0,0 +1,196 @@
package com.hermesandroid.relay.ui.screens
import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.foundation.layout.Arrangement
import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.Row
import androidx.compose.foundation.layout.aspectRatio
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.foundation.layout.fillMaxWidth
import androidx.compose.foundation.layout.padding
import androidx.compose.foundation.Image
import androidx.compose.foundation.background
import androidx.compose.foundation.shape.RoundedCornerShape
import androidx.compose.material3.Button
import androidx.compose.material3.ExperimentalMaterial3Api
import androidx.compose.material3.FilterChip
import androidx.compose.material3.Icon
import androidx.compose.material3.IconButton
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Scaffold
import androidx.compose.material3.Text
import androidx.compose.material3.TopAppBar
import androidx.compose.material.icons.Icons
import androidx.compose.material.icons.automirrored.filled.ArrowBack
import androidx.compose.runtime.Composable
import androidx.compose.runtime.getValue
import androidx.compose.runtime.key
import androidx.compose.runtime.mutableIntStateOf
import androidx.compose.runtime.remember
import androidx.compose.runtime.setValue
import androidx.compose.ui.Modifier
import androidx.compose.ui.draw.clip
import androidx.compose.ui.layout.ContentScale
import androidx.compose.ui.res.painterResource
import androidx.compose.ui.unit.dp
import com.hermesandroid.relay.R
import com.hermesandroid.relay.ui.components.ImageGenerationPlaceholder
import com.hermesandroid.relay.ui.components.ImageGenerationResultTransition
import com.hermesandroid.relay.ui.components.ImageGenerationVisualStyle
import com.hermesandroid.relay.ui.theme.HermesRelayTheme
/**
* Debug-build-only live host for fast image-generation motion tuning.
*
* Launch directly:
* adb shell am start -n <applicationId>/
* com.hermesandroid.relay.ui.screens.ImageGenerationDesignQaActivity
*/
class ImageGenerationDesignQaActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
val themePreference = intent.getStringExtra("theme") ?: "auto"
setContent {
HermesRelayTheme(themePreference = themePreference) {
ImageGenerationDesignQaScene(onBack = ::finish)
}
}
}
}
@OptIn(ExperimentalMaterial3Api::class)
@Composable
private fun ImageGenerationDesignQaScene(onBack: () -> Unit) {
var restartKey by remember { mutableIntStateOf(0) }
var durationMillis by remember { mutableIntStateOf(4_800) }
var visualStyle by remember { androidx.compose.runtime.mutableStateOf(ImageGenerationVisualStyle.LatentGrid) }
var showResult by remember { androidx.compose.runtime.mutableStateOf(false) }
Scaffold(
topBar = {
TopAppBar(
title = { Text("Image generation lab") },
navigationIcon = {
IconButton(onClick = onBack) {
Icon(
imageVector = Icons.AutoMirrored.Filled.ArrowBack,
contentDescription = "Back",
)
}
},
)
},
) { padding ->
Column(
modifier = Modifier
.fillMaxSize()
.padding(padding)
.padding(16.dp),
verticalArrangement = Arrangement.spacedBy(16.dp),
) {
Text(
text = "Live debug preview · no generation request",
style = MaterialTheme.typography.labelMedium,
color = MaterialTheme.colorScheme.onSurfaceVariant,
)
Row(
modifier = Modifier.fillMaxWidth(),
horizontalArrangement = Arrangement.spacedBy(8.dp),
) {
listOf(
ImageGenerationVisualStyle.LatentGrid to "Grid",
ImageGenerationVisualStyle.ParticleOrb to "Orb",
ImageGenerationVisualStyle.Constellation to "Nodes",
).forEach { (style, label) ->
FilterChip(
selected = visualStyle == style,
onClick = { visualStyle = style },
label = { Text(label) },
)
}
}
key(restartKey, durationMillis, visualStyle) {
val startedAtMillis = remember { System.currentTimeMillis() }
ImageGenerationResultTransition(
generating = !showResult,
startedAtMillis = startedAtMillis,
animationDurationMillis = durationMillis,
visualStyle = visualStyle,
) {
Column(
modifier = Modifier
.fillMaxWidth()
.clip(RoundedCornerShape(18.dp))
.background(MaterialTheme.colorScheme.surfaceVariant),
) {
Image(
painter = painterResource(R.drawable.image_generation_transition_preview),
contentDescription = "Generated landscape preview",
contentScale = ContentScale.Crop,
modifier = Modifier
.fillMaxWidth()
.aspectRatio(16f / 9f),
)
Row(
modifier = Modifier
.fillMaxWidth()
.padding(horizontal = 12.dp, vertical = 8.dp),
horizontalArrangement = Arrangement.SpaceBetween,
) {
Text(
text = "Generated image",
style = MaterialTheme.typography.labelSmall,
color = MaterialTheme.colorScheme.onSurfaceVariant,
)
Text(
text = "12.4s",
style = MaterialTheme.typography.labelSmall,
color = MaterialTheme.colorScheme.onSurfaceVariant,
)
}
}
}
}
Text(
text = "Cycle speed",
style = MaterialTheme.typography.labelMedium,
)
Row(
modifier = Modifier.fillMaxWidth(),
horizontalArrangement = Arrangement.spacedBy(8.dp),
) {
listOf(
7_200 to "Slow",
4_800 to "Normal",
3_200 to "Fast",
).forEach { (duration, label) ->
FilterChip(
selected = durationMillis == duration,
onClick = { durationMillis = duration },
label = { Text(label) },
)
}
}
Row(horizontalArrangement = Arrangement.spacedBy(8.dp)) {
Button(
onClick = {
showResult = true
},
enabled = !showResult,
) {
Text("Reveal result")
}
Button(
onClick = {
showResult = false
restartKey++
},
) {
Text("Restart")
}
}
}
}
}
@@ -0,0 +1,128 @@
package com.hermesandroid.relay.ui.screens
import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.foundation.layout.Arrangement
import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.foundation.layout.fillMaxWidth
import androidx.compose.foundation.layout.padding
import androidx.compose.foundation.rememberScrollState
import androidx.compose.foundation.verticalScroll
import androidx.compose.material3.Card
import androidx.compose.material3.CardDefaults
import androidx.compose.material3.ExperimentalMaterial3Api
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Scaffold
import androidx.compose.material3.Text
import androidx.compose.material3.TopAppBar
import androidx.compose.runtime.Composable
import androidx.compose.runtime.getValue
import androidx.compose.runtime.mutableStateOf
import androidx.compose.runtime.remember
import androidx.compose.runtime.setValue
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp
import com.hermesandroid.relay.network.relay.RealtimeProviderInfo
import com.hermesandroid.relay.ui.theme.HermesRelayTheme
import com.hermesandroid.relay.viewmodel.VoicePreviewUiState
/** Debug-build-only deterministic host for design QA screenshots. */
class VoiceSettingsDesignQaActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
val themePreference = intent.getStringExtra("theme") ?: "auto"
setContent { HermesRelayTheme(themePreference = themePreference) { VoiceSettingsDesignQaScene() } }
}
}
@OptIn(ExperimentalMaterial3Api::class)
@Composable
private fun VoiceSettingsDesignQaScene() {
val provider = remember {
RealtimeProviderInfo(
id = "xai_tts",
name = "xAI Grok TTS",
status = "ready",
models = listOf("grok-tts", "grok-tts-fast"),
voices = listOf("eve", "ara", "sal", "rex", "leo"),
model_labels = mapOf("grok-tts" to "Grok TTS"),
voice_labels = mapOf("eve" to "Eve", "ara" to "Ara", "sal" to "Sal"),
recommended_voices = listOf("eve", "ara"),
supports_tts = true,
)
}
var selectedSection by remember { mutableStateOf(VoiceSettingsSection.Output) }
var selectedVoice by remember { mutableStateOf("eve") }
var expanded by remember { mutableStateOf(false) }
val allVoices = remember {
listOf(
VoiceChoice("eve", "Eve", "Warm · expressive", recommended = true),
VoiceChoice("ara", "Ara", "Clear · balanced", recommended = true),
VoiceChoice("sal", "Sal", "Calm · grounded"),
VoiceChoice("rex", "Rex", "Direct · confident"),
VoiceChoice("leo", "Leo", "Bright · conversational"),
)
}
Scaffold(topBar = { TopAppBar(title = { Text("Voice") }) }) { padding ->
Column(
modifier = Modifier
.fillMaxSize()
.padding(padding)
.verticalScroll(rememberScrollState())
.padding(16.dp),
verticalArrangement = Arrangement.spacedBy(12.dp),
) {
Card(
modifier = Modifier.fillMaxWidth(),
colors = CardDefaults.cardColors(
containerColor = MaterialTheme.colorScheme.primaryContainer.copy(alpha = 0.58f),
),
) {
Column(modifier = Modifier.padding(16.dp)) {
Text("Hermes Chat + Voice Output", style = MaterialTheme.typography.titleMedium)
Text("Default profile · Profile voice", color = MaterialTheme.colorScheme.onSurfaceVariant)
}
}
VoiceSettingsTabs(selectedSection) { selectedSection = it }
VoiceProviderGroupCard(
provider = provider,
providerValue = provider.id,
enabled = true,
providerChoices = listOf(VoiceChoice(provider.id, provider.name.orEmpty())),
onEnabledChange = {},
onProviderChange = {},
controlsEnabled = true,
)
ModelAndVoiceGroupCard(
modelValue = "grok-tts",
modelChoices = listOf(VoiceChoice("grok-tts", "Grok TTS")),
voices = previewVoiceChoices(allVoices, selectedVoice),
allVoices = allVoices,
selectedVoice = selectedVoice,
previewState = VoicePreviewUiState(
selectionKey = "voice:eve",
isPlaying = true,
amplitude = 0.42f,
),
onModelChange = {},
onVoiceChange = { selectedVoice = it },
onPreviewVoice = {},
enabled = true,
)
LanguageQualityCard(
expanded = expanded,
onExpandedChange = { expanded = it },
language = "English",
languages = listOf(VoiceChoice("en", "English")),
onLanguageChange = {},
sampleRate = "24000",
sampleRates = listOf(VoiceChoice("24000", "24 kHz")),
onSampleRateChange = {},
enabled = true,
)
}
}
}
Binary file not shown.

After

Width:  |  Height:  |  Size: 2.0 MiB

@@ -0,0 +1,199 @@
package com.hermesandroid.relay.update
import android.app.Activity
import android.content.Context
import android.util.Log
import com.google.android.play.core.appupdate.AppUpdateInfo
import com.google.android.play.core.appupdate.AppUpdateManager
import com.google.android.play.core.appupdate.AppUpdateManagerFactory
import com.google.android.play.core.appupdate.AppUpdateOptions
import com.google.android.play.core.install.InstallState
import com.google.android.play.core.install.InstallStateUpdatedListener
import com.google.android.play.core.install.model.AppUpdateType
import com.google.android.play.core.install.model.InstallStatus
import com.google.android.play.core.install.model.UpdateAvailability
import kotlinx.coroutines.suspendCancellableCoroutine
import kotlin.coroutines.resume
/**
* === update (googlePlay flavor): factory ===
*
* Backs [UpdateAvailabilitySource] onto Google Play's In-App Update API,
* FLEXIBLE flow. Mirrors `voice/VoiceBridgeIntentFactory`'s flavor-split
* factory pattern: both flavors export this exact function signature +
* package, so the UI layer has one static call site and no reflection / no
* `#if` gating.
*/
fun createUpdateAvailabilitySource(context: Context): UpdateAvailabilitySource =
PlayUpdateAvailabilitySource(context.applicationContext)
private const val TAG = "PlayUpdate"
/**
* Google Play FLEXIBLE in-app update source.
*
* - [check] queries `AppUpdateManager.appUpdateInfo`. If Play reports
* `UPDATE_AVAILABLE` and FLEXIBLE is allowed, returns [UpdateStatus.Available]
* (or [UpdateStatus.Downloaded] / [UpdateStatus.Downloading] if a previously
* started flexible update is already mid-flight). Anything else →
* [UpdateStatus.UpToDate].
* - [startUpdate] launches Play's FLEXIBLE consent + background download and
* registers an [InstallStateUpdatedListener] so DOWNLOADED is reported back
* asynchronously via [onStatusChanged].
* - [completeUpdate] calls `AppUpdateManager.completeUpdate()` which restarts
* the app to install the staged APK.
*
* Robustness: every Play interaction is wrapped in try/catch. On any failure
* (no Play services, sideloaded "googlePlay" build on an AOSP device, RESULT
* errors) it degrades to [UpdateStatus.UpToDate] / [UpdateStatus.Unsupported]
* — the banner just never shows. Play is never a crash surface.
*/
private class PlayUpdateAvailabilitySource(
private val appContext: Context,
) : UpdateAvailabilitySource {
override var onStatusChanged: ((UpdateStatus) -> Unit)? = null
private val manager: AppUpdateManager? = runCatching {
AppUpdateManagerFactory.create(appContext)
}.getOrNull()
/** Cached label/code from the last [check] so async listener events can label themselves. */
@Volatile private var lastVersionCode: Long? = null
private val installListener = InstallStateUpdatedListener { state: InstallState ->
when (state.installStatus()) {
InstallStatus.DOWNLOADING ->
onStatusChanged?.invoke(
UpdateStatus.Downloading(
versionLabel = labelFor(lastVersionCode),
versionCode = lastVersionCode,
// bytesDownloaded()/totalBytesToDownload() are base
// app-update InstallState methods (Long); no ktx import.
bytesDownloaded = state.bytesDownloaded(),
totalBytes = state.totalBytesToDownload(),
)
)
InstallStatus.DOWNLOADED ->
onStatusChanged?.invoke(
UpdateStatus.Downloaded(
versionLabel = labelFor(lastVersionCode),
versionCode = lastVersionCode,
)
)
else -> Unit // INSTALLING / INSTALLED / FAILED / CANCELED → no banner change
}
}
@Volatile private var listenerRegistered = false
override suspend fun check(): UpdateStatus {
val mgr = manager ?: return UpdateStatus.Unsupported
return try {
val info = mgr.awaitAppUpdateInfo()
lastVersionCode = info.availableVersionCode().toLong()
when {
// A previously started FLEXIBLE update already finished downloading.
info.installStatus() == InstallStatus.DOWNLOADED -> {
ensureListener(mgr)
UpdateStatus.Downloaded(
versionLabel = labelFor(lastVersionCode),
versionCode = lastVersionCode,
)
}
info.updateAvailability() == UpdateAvailability.DEVELOPER_TRIGGERED_UPDATE_IN_PROGRESS ||
info.installStatus() == InstallStatus.DOWNLOADING -> {
ensureListener(mgr)
UpdateStatus.Downloading(
versionLabel = labelFor(lastVersionCode),
versionCode = lastVersionCode,
)
}
info.updateAvailability() == UpdateAvailability.UPDATE_AVAILABLE &&
info.isUpdateTypeAllowed(AppUpdateType.FLEXIBLE) ->
UpdateStatus.Available(
versionLabel = labelFor(lastVersionCode),
versionCode = lastVersionCode,
openUrl = null,
)
else -> UpdateStatus.UpToDate
}
} catch (t: Throwable) {
Log.w(TAG, "appUpdateInfo check failed; treating as up-to-date", t)
UpdateStatus.UpToDate
}
}
override fun startUpdate(activity: Activity?): Boolean {
val mgr = manager ?: return false
if (activity == null) return false
return try {
ensureListener(mgr)
mgr.appUpdateInfo
.addOnSuccessListener { info: AppUpdateInfo ->
val canStart = info.updateAvailability() == UpdateAvailability.UPDATE_AVAILABLE &&
info.isUpdateTypeAllowed(AppUpdateType.FLEXIBLE)
val resuming = info.updateAvailability() ==
UpdateAvailability.DEVELOPER_TRIGGERED_UPDATE_IN_PROGRESS
if (canStart || resuming) {
runCatching {
mgr.startUpdateFlow(
info,
activity,
AppUpdateOptions.newBuilder(AppUpdateType.FLEXIBLE).build(),
)
}.onFailure { Log.w(TAG, "startUpdateFlow failed", it) }
}
}
.addOnFailureListener { Log.w(TAG, "startUpdate appUpdateInfo failed", it) }
true
} catch (t: Throwable) {
Log.w(TAG, "startUpdate failed", t)
false
}
}
override fun completeUpdate() {
val mgr = manager ?: return
runCatching { mgr.completeUpdate() }
.onFailure { Log.w(TAG, "completeUpdate failed", it) }
}
override fun dispose() {
val mgr = manager ?: return
if (listenerRegistered) {
runCatching { mgr.unregisterListener(installListener) }
listenerRegistered = false
}
onStatusChanged = null
}
private fun ensureListener(mgr: AppUpdateManager) {
if (!listenerRegistered) {
runCatching { mgr.registerListener(installListener) }
.onSuccess { listenerRegistered = true }
.onFailure { Log.w(TAG, "registerListener failed", it) }
}
}
// Play exposes only the numeric versionCode, not a marketing version
// string, so the banner copy stays generic ("A new version"). The code is
// still carried on the status for per-version dismissal keying.
private fun labelFor(@Suppress("UNUSED_PARAMETER") code: Long?): String = "A new version"
}
// === END update (googlePlay) ===
/**
* `await()` for Play's [AppUpdateInfo] task without pulling in
* `kotlinx-coroutines-play-services`. Named `await…` (not the ktx
* `requestAppUpdateInfo`) to avoid any overload ambiguity with the
* `app-update-ktx` suspend extension. Resumable + cancels cleanly if the
* coroutine is torn down.
*/
private suspend fun AppUpdateManager.awaitAppUpdateInfo(): AppUpdateInfo =
suspendCancellableCoroutine { cont ->
appUpdateInfo
.addOnSuccessListener { info -> if (cont.isActive) cont.resume(info) }
.addOnFailureListener { e -> if (cont.isActive) cont.cancel(e) }
}
@@ -0,0 +1 @@
info@axiom-labs.dev
Binary file not shown.

Before

Width:  |  Height:  |  Size: 152 KiB

After

Width:  |  Height:  |  Size: 128 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 182 KiB

After

Width:  |  Height:  |  Size: 166 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 112 KiB

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 131 KiB

After

Width:  |  Height:  |  Size: 134 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 129 KiB

After

Width:  |  Height:  |  Size: 129 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 246 KiB

After

Width:  |  Height:  |  Size: 222 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 140 KiB

After

Width:  |  Height:  |  Size: 110 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 165 KiB

After

Width:  |  Height:  |  Size: 166 KiB

@@ -1,7 +1 @@
v1.2.0 — Make it yours.
• Eight app themes, swappable sphere skins, and animated agent "pets" that react to what your agent is doing.
• See which streaming path you're on, plus a "What the agent sees" sheet showing the agent's exact context.
• ~3× faster cold start and honest loading states.
• In-app crash reporting with one-tap bug reports.
• Fixes: QR pairing on foldables, server-image & PDF crashes, in-chat model picks now apply.
Dashboard sign-in now completes reliably for self-hosted OIDC and Nous Portal, including private-LAN and Tailscale routes. Nous opens securely in the system browser, while compatible providers retain full-screen in-app sign-in. Replayed chat updates no longer duplicate conversation rows.
@@ -0,0 +1 @@
Hermes 仪表板登录现在可为自托管 OIDC 和 Nous Portal 可靠完成认证,并支持私有局域网与 Tailscale 路由。Nous 会在系统浏览器中安全打开,兼容的提供商仍可使用应用内全屏登录。重放的聊天更新不再产生重复会话行。
+26 -6
View File
@@ -29,6 +29,7 @@
android:enableOnBackInvokedCallback="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:localeConfig="@xml/locales_config"
android:networkSecurityConfig="@xml/network_security_config"
android:supportsRtl="true"
android:theme="@style/Theme.HermesRelay">
@@ -39,7 +40,7 @@
android:launchMode="singleTask"
android:screenOrientation="portrait"
tools:ignore="LockedOrientationActivity"
android:configChanges="uiMode|fontScale|locale|density|orientation|screenSize|screenLayout|keyboardHidden"
android:configChanges="uiMode|fontScale|density|orientation|screenSize|screenLayout|keyboardHidden"
android:windowSoftInputMode="adjustResize"
android:theme="@style/Theme.HermesRelay.Splash">
<intent-filter>
@@ -48,6 +49,17 @@
</intent-filter>
</activity>
<!-- AppCompat persists in-app language choices on Android 12 and lower.
Android 13+ stores the same selection in the platform LocaleManager. -->
<service
android:name="androidx.appcompat.app.AppLocalesMetadataHolderService"
android:enabled="false"
android:exported="false">
<meta-data
android:name="autoStoreLocales"
android:value="true" />
</service>
<provider
android:name="androidx.core.content.FileProvider"
android:authorities="${applicationId}.fileprovider"
@@ -70,10 +82,18 @@
</service>
<!-- === END PHASE3-notif-listener === -->
<!-- Opt-in "Keep connected in background" — holds the gateway chat
socket open while backgrounded. In main so BOTH flavors ship it
(Home-Assistant-class persistent connection). Off by default; only
runs while the user has explicitly enabled the toggle. specialUse
<!-- Inline-reply receiver for proactive-message notifications
(Phase 2c — two-way phone messaging). Not exported: it is only
ever triggered by the app's own mutable RemoteInput PendingIntent
delivered by the system, never by a third party. -->
<receiver
android:name=".notifications.ProactiveReplyReceiver"
android:exported="false" />
<!-- Protects user-started active turns automatically; the optional
"Persistent connection" setting extends the same foreground
protection to idle/background connectivity (and relay-paired
device features). In main so BOTH flavors ship it. specialUse
needs a Play Console foreground-service declaration at submission. -->
<service
android:name=".network.upstream.GatewayKeepAliveService"
@@ -81,7 +101,7 @@
android:foregroundServiceType="specialUse">
<property
android:name="android.app.PROPERTY_SPECIAL_USE_FGS_SUBTYPE"
android:value="Keeps the user's chat connection to their Hermes agent open while the app is backgrounded, only when the user has explicitly enabled 'Keep connected in background'." />
android:value="Keeps user-started Hermes turns connected until they finish or need input, and optionally keeps idle connections responsive when the user enables Persistent connection." />
</service>
</application>
+578
View File
@@ -0,0 +1,578 @@
{
"versions": [
{
"version": "1.5.2",
"title": "Sign in without detours",
"date": "2026-07-28",
"sections": [
{
"header": "Provider-compatible sign-in",
"bullets": [
"Self-hosted OIDC returns through the dashboard callback, while Nous Portal opens securely in the system browser.",
"Private-LAN and Tailscale dashboard routes preserve the configured HTTPS callback and keep credentials scoped to the active connection."
]
},
{
"header": "Stable conversation updates",
"bullets": [
"Replayed upstream chat events are coalesced before rendering so duplicate message identifiers do not destabilize the conversation list."
]
}
]
},
{
"version": "1.5.1",
"title": "Voice and chat stay in place",
"date": "2026-07-26",
"sections": [
{
"header": "Voice at the right depth",
"bullets": [
"Use Voice Focus for a compact spoken-turn view or Conversation for the complete Chat renderer without leaving the active voice session.",
"Keep intermediate work visual while supported voice paths wait to speak the settled final response."
]
},
{
"header": "Reliable narration and background work",
"bullets": [
"Standard Voice now speaks valid completed replies after generation hands off to narration.",
"Realtime background tasks release foreground voice controls while their progress and results remain reachable."
]
},
{
"header": "Formatted answers stay readable",
"bullets": [
"Completed streams render headings, lists, emphasis, and code blocks without returning to the beginning of the answer.",
"Assistant text uses stronger theme contrast and a more comfortable chat reading scale."
]
}
]
},
{
"version": "1.5.0",
"title": "Hermes, always in reach",
"date": "2026-07-25",
"sections": [
{
"header": "One secure Hermes connection",
"bullets": [
"Connect through secure Dashboard sign-in while Chat, sessions, Manage, and Standard Voice follow the same active route.",
"Switch profiles and control personality, model, reasoning, approvals, and processing speed from the new Agent Passport."
]
},
{
"header": "Active work stays reachable",
"bullets": [
"Multiple user-started chats remain active in the background until every session settles.",
"Approval, question, elevated-permission, and secure-response alerts reopen the correct conversation."
]
},
{
"header": "Richer chat and voice",
"bullets": [
"Attachments, image generation, model routing, recovery, advisor progress, and upstream events are clearer and more reliable.",
"Browse and preview Standard and Realtime voices, and hear Standard replies begin speaking as completed segments arrive."
]
},
{
"header": "Setup without surprises",
"bullets": [
"Onboarding explains optional notification, camera, microphone, companion, and device permissions without blocking standard chat.",
"Tailscale, QR, and remote routes now move all Hermes surfaces together and recover the original session after connection loss."
]
}
]
},
{
"version": "1.4.9",
"title": "Clearer Hermes connections",
"date": "2026-07-19",
"sections": [
{
"header": "Dashboard-first setup",
"bullets": [
"Connect through the Hermes dashboard with one sign-in for Chat, sessions, Manage, and voice; API fallback and optional Relay remain available.",
"Onboarding and connection management now explain nearby, remote, Tailscale, custom-port, startup, route, and security choices."
]
},
{
"header": "Consistent identity",
"bullets": [
"Server default now displays Hermes' pinned active profile consistently across the app.",
"Successful local discovery adds useful hostname identity without replacing a custom connection label."
]
}
]
},
{
"version": "1.4.8",
"title": "Privacy policy restored",
"date": "2026-07-18",
"sections": [
{
"header": "Google Play compliance",
"bullets": [
"The privacy policy now lives at hermes-relay.dev and the historical store URL remains valid for compatibility.",
"The About screen opens the hosted policy directly, and releases verify it is publicly available before publishing."
]
}
]
},
{
"version": "1.4.7",
"title": "Smoother replies, more languages",
"date": "2026-07-18",
"sections": [
{
"header": "Smooth streaming",
"bullets": [
"Long replies grow at a display-paced cadence and stay anchored at the newest text through completion.",
"Scrolling into history preserves your reading position instead of forcing the conversation back to the bottom."
]
},
{
"header": "More languages",
"bullets": [
"Use German, Brazilian Portuguese, or Japanese throughout both Android product flavors.",
"Catalog freshness validation keeps every shipped translation aligned with the canonical English resources."
]
}
]
},
{
"version": "1.4.6",
"title": "Profiles stay together",
"date": "2026-07-15",
"sections": [
{
"header": "One Server-default profile",
"bullets": [
"Server default now keeps the selected agent, session drawer, transcript, and new messages in Hermes' sticky active profile.",
"Reorder or hide profiles per connection without changing server configuration."
]
},
{
"header": "Profile icons",
"bullets": [
"Choose an image through Android's file picker or import avatar.png/profile.jpg from an updated paired Relay.",
"Host import now distinguishes an outdated Relay from a genuinely missing profile image."
]
}
]
},
{
"version": "1.4.5",
"title": "Chats that keep running",
"date": "2026-07-15",
"sections": [
{
"header": "Keep moving between chats",
"bullets": [
"Switch to another chat, profile, draft, or Thread without stopping a running Gateway reply.",
"Return to the session and reattach to its live checkpoint and progress."
]
},
{
"header": "Cleaner live state",
"bullets": [
"Expired secret and sudo prompts collapse when Hermes reports their expiry, so stale actions no longer look usable.",
"Provider wait, reconnect, and continuation notices stay in Chat's live status line instead of cluttering the conversation."
]
}
]
},
{
"version": "1.4.4",
"title": "Spanish and clearer diagnostics",
"date": "2026-07-12",
"sections": [
{
"header": "Language that is ready to grow",
"bullets": [
"Use Spanish throughout the app from Settings → Appearance.",
"Translation freshness checks flag catalogs whenever the English source changes, while fluent verification remains tracked separately."
]
},
{
"header": "Know what is connected",
"bullets": [
"Refresh Diagnostics to see the Relay plugin version, protocol, capability count, profile status, and last-check time.",
"Open the complete release history directly from the cleaner What’s New modal."
]
}
]
},
{
"version": "1.4.3",
"title": "Language switching inside the app",
"date": "2026-07-11",
"sections": [
{
"header": "Language at your fingertips",
"bullets": [
"Choose System default, English, or Simplified Chinese from Settings → Appearance without leaving Hermes-Relay.",
"The picker stays synchronized with Android's per-app language setting and persists the choice on Android 12 and lower.",
"Release builds reject collection APIs that can crash on Android versions before API 35."
]
}
]
},
{
"version": "1.4.2",
"title": "Simplified Chinese and scalable localization",
"date": "2026-07-11",
"sections": [
{
"header": "Simplified Chinese throughout the app",
"bullets": [
"Use onboarding, connection setup, Chat, Manage, Voice, settings, diagnostics, notifications, and accessibility labels in Simplified Chinese across both product flavors.",
"Switch between English and Simplified Chinese through Android's per-app language settings on supported versions, or follow the device language elsewhere."
]
},
{
"header": "Localization built to grow",
"bullets": [
"Automated catalog checks protect resource, plural, and format-argument parity, while contributor docs and translated entry points make another language easier to add safely.",
"Connection scan and queued-message counts now use locale-aware Android plurals."
]
}
]
},
{
"version": "1.4.1",
"title": "Chat that keeps up",
"date": "2026-07-11",
"sections": [
{
"header": "Chat that stays with you",
"bullets": [
"Follow background terminal work from a compact process strip and expandable sheet. Its completed answer appears in the same conversation automatically.",
"Close and reopen while a reply runs: partial text, thinking, tool progress, background-task state, and pending approvals return in the same chat without repeating your prompt."
]
},
{
"header": "Voice you can direct",
"bullets": [
"Use spoken commands to pause or resume listening, stop speech, cancel background work, repeat a finished result, or start Standard voice chat.",
"Hands-free, Low latency, Careful tools, and Quiet presets tune existing voice behavior without changing your selected voice or route."
]
},
{
"header": "Clearer conversations",
"bullets": [
"Browse adjacent images as a gallery, read smoother streaming Markdown and wide tables, and see background-process completion as a compact process notice."
]
}
]
},
{
"version": "1.4.0",
"title": "Realtime voice that finishes the job",
"date": "2026-07-09",
"sections": [
{
"header": "Voice that keeps going",
"bullets": [
"Quick follow-ups can be answered while a long Hermes task runs, another long request can wait in a bounded queue, and the finished answer can stay in the selected realtime voice.",
"Voice route recovery now waits for relay confirmation, replays unacknowledged input without starting a second Hermes run, and rejects stale sockets or sessions before they can overwrite a healthy connection.",
"Listening, thinking, reconnecting, and cancellation states now settle cleanly after Stop, exit, route loss, or terminal retry failure."
]
},
{
"header": "Models and phone automation",
"bullets": [
"Realtime Agent model and voice choices apply to the next session, persist per connection/profile, and survive restart.",
"Chat and Manage can refresh dynamic provider model catalogs on demand.",
"Opt-in notification rules can offer a local Ask Hermes action, and Bridge tools can target a specific paired Android device."
]
},
{
"header": "Reliability and safety",
"bullets": [
"Long chat turns avoid premature transport fallback, and supported voice, card, and attachment context now reaches upstream Hermes through channels it consumes.",
"Malformed server addresses fail through normal connection errors, older Android versions avoid newer collection APIs, and relay media blocks credential and token paths.",
"Model management keeps unconfigured providers visible with key-setup guidance, and session cleanup gains export, prune preview/apply, archive, and restore plumbing."
]
}
]
},
{
"version": "1.3.0",
"title": "Voice that multitasks & sturdier chats",
"date": "2026-07-06",
"sections": [
{
"header": "Voice, hands-free",
"bullets": [
"Ask for something big and keep talking — long tasks hand off to the background with a live chip showing the current step, steps done, and a running timer, with a tap-to-cancel. The answer is spoken when it's ready, even after a brief disconnect — and if the voice session is gone, it arrives as a notification (the full answer is always in the chat).",
"Leaving voice mode (or tapping stop to interrupt speech) no longer cancels a running background task — the chip's ✕ is the one deliberate kill switch, and a delivered answer keeps its text instead of flipping to \"Cancelled.\"",
"Quieter and quicker: the agent speaks at milestones instead of narrating every step, clearly long tasks hand off to the background right away, and the first turn starts faster — the session warms up when you open voice mode."
]
},
{
"header": "Chats that keep their answers",
"bullets": [
"An answer is no longer lost when the connection drops mid-reply on a long turn (slow local models, delegating skills) — the app quietly re-checks the conversation and completes the turn when the server finishes, with the usual done-notification if you've switched away.",
"Markdown reads like chat: headings are proportionate instead of billboard-sized, lists and paragraphs share one size, links are clearly styled, and timestamps show once per message group."
]
},
{
"header": "Your agent can reach out",
"bullets": [
"Proactive messages: your Hermes agent can message your phone first (off by default, opt-in on both server and phone), and you can reply straight from the notification or the new Hermes inbox — the conversation continues like any other chat."
]
},
{
"header": "Make it yours",
"bullets": [
"Pick your app font — Inter (new default), Nunito, or your system font — applied instantly, everywhere.",
"The in-bubble working indicator can be a small animated dot-matrix (Wave, Pulse, Bounce, Sparkle) with a color of your choice.",
"Quick Controls at the top of Settings puts Persistent connection and Turn-complete alerts one tap away."
]
},
{
"header": "Setup & housekeeping",
"bullets": [
"Onboarding slides now scroll on small screens and large font sizes, so no setup guidance is cut off.",
"Reporting a diagnostic files the right kind of issue: informational entries ask what you expected and file as a question, and every report carries your actual connection mode.",
"Connections is a scannable list with a tabbed detail screen (Overview, Routes, Advanced, Security), and voice settings can now read and edit your server's voice engine (provider, voice, model) over the dashboard."
]
}
]
},
{
"version": "1.2.6",
"title": "Tidier chats & calmer status",
"date": "2026-06-27",
"sections": [
{
"header": "Tidier chats",
"bullets": [
"Chats no longer get stuck showing \"Untitled\" — your first message stands in as the title until the chat is named, titles refresh once a turn settles, and a new refresh button in the session drawer pulls the latest on demand. Renaming a chat now sticks when you're on a non-default agent profile."
]
},
{
"header": "Calmer status",
"bullets": [
"Connection status — reconnecting, checking, network handoffs — now shows as a thin banner at the top that gently slides the screen down, instead of a card floating over your chat; the floating alert is kept for persistent errors. Quick confirmations (copied, profiles updated, profile/personality switches) land in the same calm banner instead of a pop-up at the bottom."
]
}
]
},
{
"version": "1.2.5",
"title": "Stability + Try the demo",
"date": "2026-06-27",
"sections": [
{
"header": "Stability",
"bullets": [
"Fixed a crash that could close the app when a non-URL value — a UI label, or a line copied from the docs — was entered in the API server or Dashboard URL field. The setup fields now reject anything that isn't a valid host or http(s) URL with an inline error, and the dashboard and voice request paths treat a bad address as unreachable instead of crashing."
]
},
{
"header": "Try the demo",
"bullets": [
"A new \"Try the demo\" option on the setup screen — and on the empty chat screen if you skip setup — opens an offline preview of the real chat experience: a sample conversation with Markdown, a tool-progress card, and a rich card, with no server, account, or network. A banner shows it's a demo, with a one-tap Connect to set up for real."
]
}
]
},
{
"version": "1.2.4",
"title": "Stability + connection security",
"date": "2026-06-25",
"sections": [
{
"header": "Stability",
"bullets": [
"Fixed a crash that could close the app when the dashboard connection check hit a transient network failure — a pooled connection aborting or timing out over Tailscale. The check now reports the failure cleanly and the connection probe degrades gracefully instead of force-closing."
]
},
{
"header": "See if you're secure",
"bullets": [
"The chat status chip, connection card, and route picker now show at a glance whether your connection is encrypted — Encrypted · TLS, Encrypted · Tailscale (both secure), Mixed routes, or Not encrypted — and tapping it opens a per-transport breakdown (chat, API, relay tools). A Tailscale or WireGuard route is now correctly shown as encrypted rather than implied insecure."
]
}
]
},
{
"version": "1.2.3",
"title": "Connection crash fix",
"date": "2026-06-23",
"sections": [
{
"header": "Stability",
"bullets": [
"Fixed a crash that could close the app right after connecting over an encrypted link (Tailscale or HTTPS) — a live secure connection was being torn down on the main thread as it came up. Securing your connection no longer force-closes the app; plain-LAN connections were never affected."
]
}
]
},
{
"version": "1.2.2",
"title": "Multi-profile polish",
"date": "2026-06-22",
"sections": [
{
"header": "Profiles that behave",
"bullets": [
"Deleting a session while a non-default agent profile is active now sticks — it no longer reappears after the list refreshes.",
"On a cold start with a non-default profile selected, the session drawer opens on that profile's chats directly instead of briefly showing the default profile's."
]
},
{
"header": "Clearer diagnostics",
"bullets": [
"Diagnostics is now a full screen led by a top-to-bottom list of subsystem health checks — network, API server, chat transport, pairing, relay, and voice — each with a pass / warning / fail state and the reason when something's wrong; tap a failing check for full detail. The recent-activity log stays below."
]
},
{
"header": "Small touches",
"bullets": [
"The default connection is now simply \"Hermes\" (and the optional power features are labelled \"Relay\"), across setup, the switcher, voice, and permissions.",
"Distraction-free chat mode gives its text a taller, scrollable area."
]
}
]
},
{
"version": "1.2.1",
"title": "Polish & control",
"date": "2026-06-21",
"sections": [
{
"header": "Yours to control",
"bullets": [
"Lock the app to a single agent profile (Settings → Profile lock) and hide the rest from the pickers."
]
},
{
"header": "Find your way back",
"bullets": [
"A new \"What's New\" entry in Settings shows current and past release notes any time — not just after an update."
]
},
{
"header": "When something breaks",
"bullets": [
"Diagnostics show clean error titles — tap any entry for a detail view with Copy, Share, and a one-tap GitHub issue.",
"A tasteful in-app banner tells you when a newer version is live (Play or sideload) — dismissable, and it never nags."
]
},
{
"header": "Voice fixes",
"bullets": [
"Stop now halts realtime speech instantly, hold-to-talk is steadier, the voice overlay is easier to read, and a chosen voice applies in Auto mode.",
"Realtime turns that reach back to Hermes no longer drop with a session error."
]
}
]
},
{
"version": "1.2.0",
"title": "Make it yours",
"date": "2026-06-20",
"sections": [
{
"header": "Personalize",
"bullets": [
"Eight app themes in Settings → Appearance — the Hermes Relay brand plus ports of the Nous Hermes looks (Teal, Nous Blue, Midnight, Ember, Mono, Cyberpunk, Rosé), with light/dark.",
"Swap the agent orb for an animated pet that reacts to what the agent is doing — add, preview, and tune pets right in the app, or generate one from sprite art with the AI authoring kit.",
"Reskin the sphere, and give each agent profile its own icon."
]
},
{
"header": "See what's happening",
"bullets": [
"The chat status strip names the actual streaming path (Gateway, Sessions, Completions, Runs), with a basic→best tier ladder in Chat Settings.",
"Tap the context meter for a \"What the agent sees\" sheet — the exact extra context prepended to your next turn.",
"Voice and Realtime turns are badged in the scrollback."
]
},
{
"header": "Privacy",
"bullets": [
"When paired to the relay, the agent can mark private media and the phone blurs it per your setting — sensitivity stays model-emitted."
]
},
{
"header": "Faster & more reliable",
"bullets": [
"Cold start is about 3× faster, and model/personality/approvals load honestly instead of showing a maybe-wrong value.",
"In-app crash reporting offers a one-tap, pre-filled bug report.",
"QR pairing no longer force-closes on unusual cameras (foldables); fixed crashes opening server images and PDFs; in-chat model picks now apply."
]
},
{
"header": "Voice & terminal",
"bullets": [
"Enhanced voice control for Gemini and xAI providers.",
"Leaner terminal with TUI-correct input and an isolated, tuned tmux."
]
}
]
},
{
"version": "1.1.0",
"title": "Release plumbing & polish",
"date": "2026-06-16",
"sections": [
{
"header": "New",
"bullets": [
"Automated Play Console upload when a release tag ships (a human still starts the rollout).",
"/relay slash commands — status, devices, and pair from any platform — plus a relay-status badge in the dashboard header.",
"The relay plugin prompts for its optional voice-provider keys on install, and a tools-only native install path."
]
},
{
"header": "Improved",
"bullets": [
"Settings overhaul: status pills are now exception-only, Power tools shows a single Plugin active/required/offline badge, and Connections moved to the top.",
"Release names and notes are now split per surface (Android, plugin, CLI)."
]
},
{
"header": "Fixed",
"bullets": [
"No more force-close on connect when the stored credential keyset was corrupt — it now heals in place.",
"The installer works on uv-managed Hermes hosts, and the dashboard relay panel buttons are readable again."
]
}
]
},
{
"version": "1.0.0",
"title": "Stable launch",
"date": "2026-06-14",
"sections": [
{
"header": "Gateway chat with live thinking",
"bullets": [
"Chat can ride the upstream dashboard gateway — the only vanilla-upstream path that streams reasoning live, so the Thinking block and sphere light up during generation. \"Auto\" prefers it and falls back to the SSE endpoints per turn.",
"Desktop parity: native image/PDF/file attachments, mid-turn steering, edit & resend, approval/clarify/sudo/secret cards, live subagent lanes, a context-window meter, server slash commands, and turn-complete notifications.",
"Warm-start and an opt-in Keep connected in background toggle so long-backgrounded conversations resume instantly."
]
},
{
"header": "Agents, Manage & media",
"bullets": [
"Switch agent profiles per conversation — model, SOUL, personality, and skills — with the selection bound to the session, never changing the server default for other clients.",
"Manage parity with the desktop dashboard: change models, manage provider keys, edit profiles and SOUL.md, and browse/install skills.",
"Open and save chat images and attachments — full-screen viewer with pinch-zoom, plus an Open/Share/Save menu."
]
},
{
"header": "Standard path is first-class",
"bullets": [
"Chat, Manage, and voice all work against an unmodified upstream Hermes agent; the relay plugin is now purely additive.",
"Seamless connection UX — LAN↔Tailscale handoffs and reconnects no longer reload the chat, and status shows as in-theme slide-down toasts.",
"Persistent Realtime Agent voice that keeps one session across turns, with long runs promoted to tracked background tasks."
]
}
]
}
]
}
+5 -31
View File
@@ -1,32 +1,6 @@
v1.2.0 - Make it yours
v1.5.2 - Sign in without detours
Personalize
* Eight app themes in Settings → Appearance — the Hermes Relay brand plus
ports of the Nous Hermes looks (Teal, Nous Blue, Midnight, Ember, Mono,
Cyberpunk, Rosé), with light/dark.
* Swap the agent orb for an animated pet that reacts to what the agent is
doing — add, preview, and tune pets right in the app, or generate one
from sprite art with the AI authoring kit.
* Reskin the sphere, and give each agent profile its own icon.
See what's happening
* The chat status strip names the actual streaming path (Gateway, Sessions,
Completions, Runs), with a basic→best tier ladder in Chat Settings.
* Tap the context meter for a "What the agent sees" sheet — the exact extra
context prepended to your next turn.
* Voice and Realtime turns are badged in the scrollback.
Privacy
* When paired to the relay, the agent can mark private media and the phone
blurs it per your setting — sensitivity stays model-emitted.
Faster & more reliable
* Cold start is about 3× faster, and model/personality/approvals load
honestly instead of showing a maybe-wrong value.
* In-app crash reporting offers a one-tap, pre-filled bug report.
* QR pairing no longer force-closes on unusual cameras (foldables); fixed
crashes opening server images and PDFs; in-chat model picks now apply.
Voice & terminal
* Enhanced voice control for Gemini and xAI providers.
* Leaner terminal with TUI-correct input and an isolated, tuned tmux.
* Complete self-hosted OIDC sign-in through the dashboard callback.
* Open Nous Portal securely in the system browser.
* Sign in over private-LAN and Tailscale dashboard routes.
* Keep replayed chat updates from duplicating conversation rows.
@@ -8,23 +8,24 @@ import android.os.Bundle
import android.util.Log
import android.view.View
import android.view.animation.DecelerateInterpolator
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.activity.enableEdgeToEdge
import androidx.activity.result.contract.ActivityResultContracts
import androidx.activity.viewModels
import androidx.core.animation.doOnEnd
import androidx.core.splashscreen.SplashScreen.Companion.installSplashScreen
import androidx.appcompat.app.AppCompatActivity
import com.hermesandroid.relay.accessibility.ScreenCaptureRequester
import com.hermesandroid.relay.bridge.BridgeForegroundService
import com.hermesandroid.relay.bridge.UnattendedAccessManager
import com.hermesandroid.relay.data.BuildFlavor
import com.hermesandroid.relay.notifications.TurnCompleteNotifier
import com.hermesandroid.relay.notifications.InteractionRequestNotifier
import com.hermesandroid.relay.ui.RelayApp
import com.hermesandroid.relay.util.NavRouteRequest
import com.hermesandroid.relay.viewmodel.ConnectionViewModel
class MainActivity : ComponentActivity() {
class MainActivity : AppCompatActivity() {
private val connectionViewModel: ConnectionViewModel by viewModels()
@@ -142,6 +143,10 @@ class MainActivity : ComponentActivity() {
// Returning to the app clears the one-slot "Hermes finished
// responding" notification — the chat surface is the answer.
TurnCompleteNotifier.cancel(this)
// Action-required notifications are durable across process death.
// Once the authenticated chat surface is visible it owns presentation;
// unresolved asks are re-posted if the app returns to the background.
InteractionRequestNotifier.cancelAll(this)
// v0.4.1 — register this activity as the host for
// KeyguardManager.requestDismissKeyguard. Cleared in onPause so
// we don't leak the Activity past its lifecycle. The unattended-
@@ -15,6 +15,7 @@ import android.os.HandlerThread
import android.util.DisplayMetrics
import android.util.Log
import android.view.WindowManager
import kotlinx.coroutines.delay
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.sync.withLock
import kotlinx.coroutines.withContext
@@ -114,8 +115,27 @@ class ScreenCapture(
*/
private const val MAX_IMAGES = 2
/** Capture timeout — if no frame arrives in this window, fail loudly. */
private const val CAPTURE_TIMEOUT_MS = 2_500L
/**
* Capture timeout — if no frame arrives in this window, fail loudly.
*
* BOOX / e-ink devices can take several seconds before a
* VirtualDisplay-backed ImageReader emits its first frame, especially
* after a fresh MediaProjection grant or when the display is idle. Keep
* the default generous enough for those devices while still bounded so
* a dead capture pipeline reports a clear error.
*/
private const val DEFAULT_CAPTURE_TIMEOUT_MS = 10_000L
/** Optional JVM/system-property override for local QA and OEM tuning. */
private const val CAPTURE_TIMEOUT_PROPERTY =
"hermes.relay.screen_capture_timeout_ms"
private const val MIN_CAPTURE_TIMEOUT_MS = 2_500L
private const val MAX_CAPTURE_TIMEOUT_MS = 30_000L
/** One retry covers stale VirtualDisplay/ImageReader pipelines. */
private const val MAX_CAPTURE_ATTEMPTS = 2
private const val CAPTURE_RETRY_DELAY_MS = 350L
}
// === PHASE3-bridge-ui-followup: MediaProjection reuse fix ===
@@ -211,7 +231,27 @@ class ScreenCapture(
// mutex keeps us honest if anything ever parallelizes.
val pngBytes = try {
captureMutex.withLock {
captureFrame(projection)
var lastTimeout: CaptureTimeoutException? = null
for (attempt in 1..MAX_CAPTURE_ATTEMPTS) {
try {
return@withLock captureFrame(projection)
} catch (e: CaptureTimeoutException) {
lastTimeout = e
Log.w(
TAG,
"screen capture timed out on attempt " +
"$attempt/$MAX_CAPTURE_ATTEMPTS: ${e.message}"
)
if (attempt < MAX_CAPTURE_ATTEMPTS) {
// A timeout can leave an OEM VirtualDisplay path
// wedged without invalidating the MediaProjection
// grant. Rebuild our pipeline once before giving up.
releaseCache()
delay(CAPTURE_RETRY_DELAY_MS)
}
}
}
throw lastTimeout ?: IOException("screen capture timed out")
}
} catch (e: Exception) {
Log.w(TAG, "captureFrame failed: ${e.message}")
@@ -286,16 +326,28 @@ class ScreenCapture(
}
return try {
kotlinx.coroutines.withTimeout(CAPTURE_TIMEOUT_MS) { deferred.await() }
val timeoutMs = captureTimeoutMs()
kotlinx.coroutines.withTimeout(timeoutMs) { deferred.await() }
} catch (e: kotlinx.coroutines.TimeoutCancellationException) {
pendingCaptureRef.compareAndSet(deferred, null)
throw IOException("screen capture timed out")
throw CaptureTimeoutException(
"screen capture timed out after ${captureTimeoutMs()}ms"
)
} catch (t: Throwable) {
pendingCaptureRef.compareAndSet(deferred, null)
throw t
}
}
private fun captureTimeoutMs(): Long {
val configured = System.getProperty(CAPTURE_TIMEOUT_PROPERTY)
?.toLongOrNull()
?.coerceIn(MIN_CAPTURE_TIMEOUT_MS, MAX_CAPTURE_TIMEOUT_MS)
return configured ?: DEFAULT_CAPTURE_TIMEOUT_MS
}
private class CaptureTimeoutException(message: String) : IOException(message)
/**
* Build (or reuse) the cached VirtualDisplay + ImageReader + HandlerThread
* for this projection. Rebuilds when:
@@ -489,7 +541,7 @@ class ScreenCapture(
fastClient.newCall(request).execute().use { response ->
when (response.code) {
200 -> {
val raw = response.body?.string().orEmpty()
val raw = response.body.string()
val token = extractToken(raw)
if (token.isNullOrBlank()) {
Result.failure(
@@ -9,6 +9,7 @@ import android.media.AudioTrack
import android.os.Build
import android.os.SystemClock
import android.util.Log
import com.hermesandroid.relay.R
import com.hermesandroid.relay.diagnostics.DiagnosticCategory
import com.hermesandroid.relay.diagnostics.DiagnosticSeverity
import com.hermesandroid.relay.diagnostics.DiagnosticsLog
@@ -25,7 +26,7 @@ import kotlin.math.sqrt
* writes them directly to an AudioTrack so the Android Studio dev build can
* hear provider output without waiting for an encoded file.
*/
class RealtimePcmPlayer(context: Context? = null) {
class RealtimePcmPlayer(private val context: Context? = null) {
private val trackLock = Any()
private val writeLock = Any()
private val audioManager =
@@ -225,7 +226,7 @@ class RealtimePcmPlayer(context: Context? = null) {
// is the chunk's end frame. The cursor reaches this amplitude once
// playbackHeadPosition passes the previous end frame.
playbackAmpQueue.addLast(FrameAmp(endFrame = totalFramesWritten, rms = rms))
while (playbackAmpQueue.size > MAX_AMP_QUEUE) playbackAmpQueue.removeFirst()
while (playbackAmpQueue.size > MAX_AMP_QUEUE) playbackAmpQueue.removeAt(0)
}
/**
@@ -240,7 +241,7 @@ class RealtimePcmPlayer(context: Context? = null) {
val head = readHeadFrames(track).toLong()
// Drop fully-played chunks so the head of the queue is the one playing now.
while (playbackAmpQueue.size > 1 && playbackAmpQueue.first().endFrame <= head) {
playbackAmpQueue.removeFirst()
playbackAmpQueue.removeAt(0)
}
amplitudeAtHead(playbackAmpQueue, head)
}
@@ -449,7 +450,7 @@ class RealtimePcmPlayer(context: Context? = null) {
DiagnosticsLog.record(
category = DiagnosticCategory.Voice,
severity = DiagnosticSeverity.Info,
title = "Realtime audio started",
title = context?.getString(R.string.audio_diag_started) ?: "Realtime audio started",
detail = "First sample reached the speaker after ${ttfaMs}ms.",
)
}
@@ -489,7 +490,7 @@ class RealtimePcmPlayer(context: Context? = null) {
DiagnosticsLog.record(
category = DiagnosticCategory.Voice,
severity = DiagnosticSeverity.Warning,
title = "Realtime audio not starting",
title = context?.getString(R.string.audio_diag_not_starting) ?: "Realtime audio not starting",
detail = "Playback running ${stuckMs}ms but no audio reached the speaker " +
"(${mediaVolumeSummaryLocked()}).",
)
@@ -587,7 +588,7 @@ class RealtimePcmPlayer(context: Context? = null) {
DiagnosticsLog.record(
category = DiagnosticCategory.Voice,
severity = DiagnosticSeverity.Warning,
title = "Realtime audio stream gap",
title = context?.getString(R.string.audio_diag_stream_gap) ?: "Realtime audio stream gap",
detail = reason,
)
}
@@ -603,7 +604,7 @@ class RealtimePcmPlayer(context: Context? = null) {
DiagnosticsLog.record(
category = DiagnosticCategory.Voice,
severity = DiagnosticSeverity.Warning,
title = "Realtime voice volume muted",
title = context?.getString(R.string.audio_diag_volume_muted) ?: "Realtime voice volume muted",
detail = "Media volume is 0/${maxVolume ?: "?"}.",
)
}
@@ -5,6 +5,8 @@ import android.media.audiofx.Visualizer
import android.util.Log
import androidx.annotation.OptIn
import androidx.core.net.toUri
import androidx.media3.common.AudioAttributes
import androidx.media3.common.C
import androidx.media3.common.MediaItem
import androidx.media3.common.Player
import androidx.media3.common.util.UnstableApi
@@ -425,9 +427,25 @@ class VoicePlayer(
* Production ExoPlayer factory — used as the default for [VoicePlayer].
* Split out as a top-level function so unit tests can swap it for a
* MockK mock without touching Media3's `Builder` class loader.
*
* Audio attributes (USAGE_MEDIA + CONTENT_TYPE_SPEECH) with
* `handleAudioFocus = true` are set so ExoPlayer requests audio focus when
* the first TTS clip starts, which warms the audio HAL output path before
* playback begins. Without them the very first turn of a cold voice session
* could lose its opening syllables to the AudioTrack/HAL allocation window —
* the standard-path twin of the deep-buffer cold-start the relay PCM player
* already mitigates. SPEECH also lets the system duck other audio
* appropriately for a spoken assistant reply.
*/
@OptIn(UnstableApi::class)
private fun defaultExoPlayer(context: Context): ExoPlayer =
ExoPlayer.Builder(context)
.setAudioAttributes(
AudioAttributes.Builder()
.setUsage(C.USAGE_MEDIA)
.setContentType(C.AUDIO_CONTENT_TYPE_SPEECH)
.build(),
/* handleAudioFocus = */ true,
)
.setHandleAudioBecomingNoisy(true)
.build()
@@ -5,6 +5,8 @@ import android.content.Context
import android.media.AudioFormat
import android.media.AudioRecord
import android.media.MediaRecorder
import android.media.audiofx.AcousticEchoCanceler
import android.media.audiofx.NoiseSuppressor
import android.util.Log
import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.flow.StateFlow
@@ -55,6 +57,8 @@ class VoiceRecorder(
private val bufferLock = Any()
private val stopRequested = AtomicBoolean(false)
private var audioRecord: AudioRecord? = null
private var echoCanceler: AcousticEchoCanceler? = null
private var noiseSuppressor: NoiseSuppressor? = null
private var currentOutputFile: File? = null
private var readThread: Thread? = null
private var readDone: CountDownLatch? = null
@@ -117,6 +121,7 @@ class VoiceRecorder(
throw e
}
attachVoiceEffects(recorder.audioSessionId)
audioRecord = recorder
val done = CountDownLatch(1)
readDone = done
@@ -136,6 +141,9 @@ class VoiceRecorder(
fun stopRecording(): File {
val file = currentOutputFile
?: throw IllegalStateException("stopRecording called with no active recording")
// Claim the capture exactly once. A stale UI stop must not repackage
// the previous PCM as a second voice turn.
currentOutputFile = null
val record = audioRecord
stopRequested.set(true)
@@ -202,8 +210,15 @@ class VoiceRecorder(
}
}
updateAmplitude(buffer, read)
} else if (read < 0) {
Log.w(TAG, "AudioRecord.read ended with error code $read")
break
}
}
// Android can terminate capture while the app is backgrounded without
// stopRecording() running. Reflect that loss in isRecording() so the
// foreground UI can recover instead of remaining stuck on Listening.
stopRequested.set(true)
}
private fun updateAmplitude(buffer: ByteArray, read: Int) {
@@ -224,7 +239,44 @@ class VoiceRecorder(
_amplitude.value = sqrt(floored)
}
/**
* Engage the platform's hardware echo-cancellation and noise-suppression
* on the [AudioRecord] capture session when the device exposes them —
* parity with hermes-desktop's `getUserMedia({echoCancellation,
* noiseSuppression})`. Both are best-effort: many mid-range and older
* devices report [AcousticEchoCanceler.isAvailable] / [NoiseSuppressor.isAvailable]
* false, in which case capture proceeds raw (the same behaviour as before
* this change). AEC in particular keeps the device's own TTS playback from
* bleeding into the next captured utterance during back-to-back voice turns.
*/
private fun attachVoiceEffects(sessionId: Int) {
if (AcousticEchoCanceler.isAvailable()) {
echoCanceler = try {
AcousticEchoCanceler.create(sessionId)?.apply { enabled = true }
} catch (e: Exception) {
Log.w(TAG, "AcousticEchoCanceler unavailable: ${e.message}")
null
}
}
if (NoiseSuppressor.isAvailable()) {
noiseSuppressor = try {
NoiseSuppressor.create(sessionId)?.apply { enabled = true }
} catch (e: Exception) {
Log.w(TAG, "NoiseSuppressor unavailable: ${e.message}")
null
}
}
}
private fun releaseRecorder() {
echoCanceler?.let { fx ->
try { fx.release() } catch (_: Exception) { }
}
echoCanceler = null
noiseSuppressor?.let { fx ->
try { fx.release() } catch (_: Exception) { }
}
noiseSuppressor = null
audioRecord?.let { record ->
try { record.release() } catch (_: Exception) { }
}
@@ -22,6 +22,7 @@ import kotlinx.serialization.Serializable
import kotlinx.serialization.json.Json
import kotlinx.serialization.json.JsonArray
import kotlinx.serialization.json.JsonObject
import kotlinx.serialization.json.JsonObjectBuilder
import kotlinx.serialization.json.JsonPrimitive
import kotlinx.serialization.json.buildJsonObject
import kotlinx.serialization.json.booleanOrNull
@@ -702,6 +703,18 @@ class AuthManager(
pendingEndpoints = endpoints?.takeIf { it.isNotEmpty() }
}
/**
* Capability negotiation advertised in the first system/auth envelope.
* Older relays ignore this object; newer relays use it to send versioned
* `chat:stream.event` payloads instead of flattening Hermes SSE into text.
*/
private fun JsonObjectBuilder.putRelayClientSupports() {
put("supports", buildJsonObject {
put("typed_stream_events", true)
put("event_schema_version", 1)
})
}
/**
* Send auth envelope when connection is established.
*
@@ -737,6 +750,7 @@ class AuthManager(
}
put("device_id", deviceId)
put("device_name", android.os.Build.MODEL)
putRelayClientSupports()
}
}
else -> {
@@ -752,6 +766,7 @@ class AuthManager(
put("pairing_code", codeToSend)
put("device_id", deviceId)
put("device_name", android.os.Build.MODEL)
putRelayClientSupports()
pendingTtlSeconds?.let { put("ttl_seconds", it) }
pendingGrants?.let { grants ->
val obj = buildJsonObject {
@@ -883,6 +898,18 @@ class AuthManager(
val profilesUpdatedEvents: kotlinx.coroutines.flow.SharedFlow<Unit> =
_profilesUpdatedEvents.asSharedFlow()
/**
* Emits once per successful `auth.ok` — i.e. on every (re)connect, not
* just the first pair. Lets connection-scoped consumers re-establish
* per-socket state. The proactive subscription is tracked per-WebSocket
* on the relay, so [com.hermesandroid.relay.viewmodel.ConnectionViewModel]
* collects this to re-send `proactive.subscribe` after each reconnect.
*/
private val _authOkEvents =
kotlinx.coroutines.flow.MutableSharedFlow<Unit>(extraBufferCapacity = 4)
val authOkEvents: kotlinx.coroutines.flow.SharedFlow<Unit> =
_authOkEvents.asSharedFlow()
fun regeneratePairingCode() {
_pairingCode.value = generatePairingCode()
}
@@ -950,6 +977,9 @@ class AuthManager(
}
_authState.value = AuthState.Paired(token)
Log.i(TAG, "handleAuthOk: Paired(token=${token.take(8)}…)")
// Per-connection signal for socket-scoped consumers (e.g.
// re-sending proactive.subscribe). Fires on every auth.ok.
_authOkEvents.tryEmit(Unit)
// Server-issued code is one-shot — drop it once the
// upgrade to a long-lived session token has landed.
serverIssuedCode = null
@@ -89,8 +89,8 @@ class AutoDisableWorker(private val context: Context) {
val builder = NotificationCompat.Builder(context, CHANNEL_ID)
.setSmallIcon(R.mipmap.ic_launcher)
.setContentTitle("Bridge auto-disabled")
.setContentText("Paused after idle — tap to re-enable in the Bridge tab.")
.setContentTitle(context.getString(R.string.bridge_notification_auto_disabled_title))
.setContentText(context.getString(R.string.bridge_notification_auto_disabled_body))
.setStyle(NotificationCompat.BigTextStyle().bigText(
"Hermes bridge was idle for too long, so device control has been turned off " +
"automatically. Open the Bridge tab to turn it back on if you still need it."
@@ -373,8 +373,8 @@ class BridgeForegroundService : Service() {
return NotificationCompat.Builder(this, CHANNEL_ID)
.setSmallIcon(R.mipmap.ic_launcher)
.setContentTitle("Hermes agent has device control")
.setContentText("Bridge is active — tap Disable to stop at any time.")
.setContentTitle(getString(R.string.bridge_notification_control_title))
.setContentText(getString(R.string.bridge_notification_control_body))
.setStyle(NotificationCompat.BigTextStyle().bigText(
"The Hermes agent can currently read the screen and perform " +
"actions on your behalf through the accessibility service. " +
@@ -31,7 +31,16 @@ object AgentDisplay {
fun effectiveDisplayProfile(
selectedProfile: Profile?,
profiles: List<Profile>,
): Profile? = selectedProfile ?: profiles.firstOrNull { isServerDefaultAlias(it.name) }
serverDefaultProfileName: String? = null,
): Profile? {
selectedProfile?.let { return it }
val resolvedServerDefault = profileRequestName(serverDefaultProfileName)
return resolvedServerDefault
?.let { activeName ->
profiles.firstOrNull { it.name.equals(activeName, ignoreCase = true) }
}
?: profiles.firstOrNull { isServerDefaultAlias(it.name) }
}
// The NAME goes in the name slot. Non-default profiles use their profile
// name first. The synthetic default profile uses its description only when
@@ -137,6 +146,24 @@ object AgentDisplay {
?.trim()
?.takeIf { it.isNotEmpty() && !isServerDefaultAlias(it) }
/**
* The profile name that owns chat sessions for the current UI selection.
*
* [selectedProfileName] is null (or the synthetic `default` alias) for the
* "Server default" row. That UI sentinel must remain distinct from the
* server's sticky active profile: a dashboard launched under the root home
* may still report `active=victor`, in which case upstream Gateway and
* dashboard session calls must explicitly target `victor`. The resolved
* server value deliberately keeps the literal `default` name so a dashboard
* launched under another profile can still address the root profile.
*/
fun effectiveSessionProfileName(
selectedProfileName: String?,
serverDefaultProfileName: String?,
): String? =
profileRequestName(selectedProfileName)
?: serverDefaultProfileName?.trim()?.takeIf { it.isNotEmpty() }
fun profileSessionKey(profileName: String?): String =
profileRequestName(profileName) ?: SERVER_DEFAULT_PROFILE_KEY
@@ -0,0 +1,49 @@
package com.hermesandroid.relay.data
import androidx.core.os.LocaleListCompat
import java.util.Locale
/** Languages exposed by the in-app picker and Android's per-app language UI. */
enum class AppLanguage(val languageTag: String) {
SYSTEM_DEFAULT(""),
ENGLISH("en"),
GERMAN("de"),
BRAZILIAN_PORTUGUESE("pt-BR"),
JAPANESE("ja"),
SIMPLIFIED_CHINESE("zh-Hans"),
SPANISH("es"),
;
fun toLocaleList(): LocaleListCompat = if (languageTag.isEmpty()) {
LocaleListCompat.getEmptyLocaleList()
} else {
LocaleListCompat.forLanguageTags(languageTag)
}
companion object {
fun fromLanguageTags(languageTags: String): AppLanguage {
val primaryTag = languageTags
.substringBefore(',')
.trim()
.takeIf { it.isNotEmpty() }
?: return SYSTEM_DEFAULT
val locale = Locale.forLanguageTag(primaryTag)
return when (locale.language.lowercase(Locale.ROOT)) {
"de" -> GERMAN
"en" -> ENGLISH
"es" -> SPANISH
"ja" -> JAPANESE
"pt" -> BRAZILIAN_PORTUGUESE
"zh" -> {
val simplified = locale.script.equals("Hans", ignoreCase = true) ||
locale.script.isEmpty() ||
locale.country.equals("CN", ignoreCase = true) ||
locale.country.equals("SG", ignoreCase = true)
if (simplified) SIMPLIFIED_CHINESE else SYSTEM_DEFAULT
}
else -> SYSTEM_DEFAULT
}
}
}
}
@@ -82,9 +82,9 @@ class BargeInPreferencesRepository(
constructor(context: Context) : this(context.relayDataStore)
companion object {
private val KEY_ENABLED = booleanPreferencesKey("barge_in_enabled")
private val KEY_SENSITIVITY = stringPreferencesKey("barge_in_sensitivity")
private val KEY_RESUME_AFTER_INTERRUPTION =
internal val KEY_ENABLED = booleanPreferencesKey("barge_in_enabled")
internal val KEY_SENSITIVITY = stringPreferencesKey("barge_in_sensitivity")
internal val KEY_RESUME_AFTER_INTERRUPTION =
booleanPreferencesKey("barge_in_resume_after_interruption")
}
@@ -111,8 +111,79 @@ data class ChatMessage(
* reconcile normally. Only [clientOnly] gates orphan preservation.
*/
val clientOnly: Boolean = false,
/**
* Delivery state for a message the user sends into an agent **Thread** over
* the relay proactive channel ([com.hermesandroid.relay.viewmodel.ChatViewModel]
* routes `source=phone` sessions here instead of the normal chat send).
* `SENDING` until the relay acks (`proactive.reply.ack`) → `DELIVERED`;
* `FAILED` on a send error. Null for ordinary chat messages — those render
* no status affix.
*/
val deliveryStatus: MessageDeliveryStatus? = null,
/**
* Client-side lifecycle for a promoted/durable Hermes run that belongs to
* this assistant turn. The same message owns the state from promotion
* through delivery so Chat never needs a separate system notice and final
* reply for one task. On the normal post-turn history reconcile this field
* is carried forward with the rest of the client-only enrichment whenever
* the live message can be matched to its server row.
*/
val backgroundTask: BackgroundTaskState? = null,
/**
* Stable identity for Compose list rendering.
*
* Gateway/user rows start with client UUIDs, then post-turn history
* reconciliation adopts the server message id into [id]. That server-id
* adoption must not make a visible bubble look removed and reinserted to
* LazyColumn: doing so discards its scroll anchor, which is especially
* disruptive when the row is a long answer occupying the viewport.
*
* New rows default to their current [id]. Reconciled rows retain this key
* through `copy`, while [id] remains the authoritative lookup/wire id.
*/
val uiKey: String = id,
/**
* Mixture-of-Agents advisor responses surfaced during the live turn.
* Unavailable advisors retain only neutral state, never their raw failure
* body. A sanitized bounded copy may enter the local in-flight checkpoint,
* but server history never owns these presentation blocks.
*/
val moaReferences: List<MoaReference> = emptyList(),
)
data class MoaReference(
val index: Int,
val count: Int?,
val label: String,
val text: String,
val available: Boolean = true,
)
/** One Chat-visible identity for a promoted/durable realtime Hermes run. */
data class BackgroundTaskState(
/** Relay run id when supplied; otherwise a stable id derived from the message. */
val id: String,
/** Short objective derived from the associated user turn. */
val title: String,
/** ADR 33 tier: `promoted` or `durable`. */
val tier: String = "promoted",
val phase: BackgroundTaskPhase = BackgroundTaskPhase.RUNNING,
/** Latest meaningful progress line, deliberately not a raw event trace. */
val statusLine: String? = null,
val completedToolCount: Int = 0,
val queuedCount: Int = 0,
val startedAt: Long = System.currentTimeMillis(),
)
enum class BackgroundTaskPhase {
RUNNING,
WAITING,
DELIVERING,
COMPLETE,
FAILED,
CANCELLED,
}
/**
* Structured details about a phone-local voice intent that was dispatched
* in-process via [com.hermesandroid.relay.network.relay.BridgeCommandHandler.handleLocalCommand].
@@ -295,7 +366,13 @@ data class ToolCall(
* goal truncated to 60 chars. Carried on each child call so the lane
* header can render without a separate lane registry.
*/
val taskLabel: String? = null
val taskLabel: String? = null,
/** Deterministic non-low output risk reported by upstream for this call. */
val outputRisk: String? = null,
/** Human-readable deterministic findings; rendered as untrusted metadata. */
val outputRiskFindings: List<String> = emptyList(),
/** Upstream removed sensitive spans before emitting the findings. */
val outputRiskRedacted: Boolean = false,
)
enum class MessageRole {
@@ -304,6 +381,17 @@ enum class MessageRole {
SYSTEM
}
/**
* Delivery state of a user reply sent into an agent Thread over the relay
* proactive channel. Only set on Thread replies; ordinary chat messages leave
* it null and show no status affix.
*
* - [SENDING] handed to the relay; awaiting the per-reply ack.
* - [DELIVERED] the relay acked (`proactive.reply.ack`) — buffered for the agent.
* - [FAILED] the send errored (e.g. relay disconnected).
*/
enum class MessageDeliveryStatus { SENDING, DELIVERED, FAILED }
data class ChatSession(
val sessionId: String,
val title: String?,
@@ -311,7 +399,16 @@ data class ChatSession(
val messageCount: Int = 0,
val updatedAt: Long = 0L,
val startedAt: Long = 0L,
val lastActivityAt: Long = 0L
val lastActivityAt: Long = 0L,
/**
* Originating gateway platform/source for this session (upstream `sessions.source`):
* `tui`/`api_server` for ordinary app chats, `phone` for an agent **Thread**, and
* `discord`/`slack`/… for other platforms. Null when the server didn't supply it or
* for locally-created optimistic rows. Drives the drawer's Thread tag (see ADR 12).
*/
val source: String? = null,
/** Server reports a persisted session runtime/model binding. */
val hasModelConfig: Boolean = false,
) {
val activityTimestamp: Long
get() = firstPositive(lastActivityAt, updatedAt, startedAt)
@@ -0,0 +1,286 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.core.DataStore
import androidx.datastore.preferences.core.Preferences
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringPreferencesKey
import kotlinx.coroutines.flow.first
import kotlinx.serialization.Serializable
import kotlinx.serialization.encodeToString
import kotlinx.serialization.json.Json
/**
* Durable, client-owned snapshot of one in-flight chat turn.
*
* Hermes history is authoritative once a turn finishes, but it cannot recreate
* transient UI that existed before persistence (live reasoning, a running tool,
* an interactive ask, or the latest lifecycle line). This checkpoint bridges
* that gap across Activity recreation and process death. It deliberately stores
* no entered secret/approval response; only the server-issued ask is retained.
*/
@Serializable
data class ChatTurnCheckpoint(
val schemaVersion: Int = CURRENT_SCHEMA,
val contextKey: String,
val sessionId: String,
val liveSessionId: String? = null,
val transport: String,
val user: ChatTurnUserCheckpoint,
val assistant: ChatTurnAssistantCheckpoint,
val turnStatus: String? = null,
val priorUserMessageCount: Int,
val baselineAssistantCount: Int,
val pendingAsk: ChatTurnAskCheckpoint? = null,
val startedAt: Long,
val updatedAt: Long,
) {
companion object {
const val CURRENT_SCHEMA = 1
const val MAX_AGE_MS = 24L * 60L * 60L * 1_000L
}
}
@Serializable
data class ChatTurnUserCheckpoint(
val id: String,
val content: String,
val timestamp: Long,
)
@Serializable
data class ChatTurnAssistantCheckpoint(
val id: String,
val content: String = "",
val timestamp: Long,
val isStreaming: Boolean = true,
val thinkingContent: String = "",
val isThinkingStreaming: Boolean = false,
val inputTokens: Int? = null,
val outputTokens: Int? = null,
val totalTokens: Int? = null,
val estimatedCost: Double? = null,
val agentName: String? = null,
val badges: List<String> = emptyList(),
val cards: List<HermesCard> = emptyList(),
val cardDispatches: List<HermesCardDispatch> = emptyList(),
val toolCalls: List<ChatTurnToolCheckpoint> = emptyList(),
val backgroundTask: ChatTurnBackgroundTaskCheckpoint? = null,
/** Sanitized, bounded live-only MoA presentation state; never server transcript data. */
val moaReferences: List<ChatTurnMoaReferenceCheckpoint> = emptyList(),
)
@Serializable
data class ChatTurnMoaReferenceCheckpoint(
val index: Int,
val count: Int? = null,
val label: String,
val text: String = "",
val available: Boolean = true,
)
@Serializable
data class ChatTurnToolCheckpoint(
val id: String? = null,
val name: String,
val result: String? = null,
val success: Boolean? = null,
val isComplete: Boolean = false,
val error: String? = null,
val runId: String? = null,
val provenance: String? = null,
val startedAt: Long,
val completedAt: Long? = null,
val isGenerating: Boolean = false,
val taskIndex: Int? = null,
val taskLabel: String? = null,
val outputRisk: String? = null,
val outputRiskFindings: List<String> = emptyList(),
val outputRiskRedacted: Boolean = false,
)
@Serializable
data class ChatTurnBackgroundTaskCheckpoint(
val id: String,
val title: String,
val tier: String,
val phase: String,
val statusLine: String? = null,
val completedToolCount: Int = 0,
val queuedCount: Int = 0,
val startedAt: Long,
)
@Serializable
data class ChatTurnAskCheckpoint(
val kind: String,
val requestId: String? = null,
val text: String,
val choices: List<String>? = null,
val smartDenied: Boolean = false,
val envVar: String? = null,
val timeoutSeconds: Int,
val messageId: String,
val cardKey: String,
/** Original receive time, used to preserve an ask's expiry after reopen. */
val receivedAt: Long,
)
interface ChatTurnCheckpointStore {
suspend fun read(): ChatTurnCheckpoint?
suspend fun readAll(): List<ChatTurnCheckpoint> = listOfNotNull(read())
suspend fun read(contextKey: String, sessionId: String): ChatTurnCheckpoint? =
readAll()
.filter { it.contextKey == contextKey && it.sessionId == sessionId }
.maxByOrNull(ChatTurnCheckpoint::updatedAt)
suspend fun write(checkpoint: ChatTurnCheckpoint)
suspend fun remove(contextKey: String, sessionId: String) {
if (read()?.let { it.contextKey == contextKey && it.sessionId == sessionId } == true) {
clear()
}
}
suspend fun clear()
}
class DataStoreChatTurnCheckpointStore(
private val dataStore: DataStore<Preferences>,
private val now: () -> Long = System::currentTimeMillis,
) : ChatTurnCheckpointStore {
constructor(context: Context) : this(context.applicationContext.relayDataStore)
private val json = Json {
ignoreUnknownKeys = true
encodeDefaults = true
isLenient = true
}
override suspend fun read(): ChatTurnCheckpoint? =
readAll().maxByOrNull(ChatTurnCheckpoint::updatedAt)
override suspend fun readAll(): List<ChatTurnCheckpoint> {
val preferences = runCatching { dataStore.data.first() }.getOrNull() ?: return emptyList()
val decoded = decode(preferences)
val valid = decoded.filter(::isValid)
.distinctBy { it.contextKey to it.sessionId }
if (valid.size != decoded.size ||
(preferences[KEY_CHECKPOINT_SET] == null && preferences[KEY_CHECKPOINT] != null)
) {
// Cleanup/migration is best-effort. A read must still return the
// valid subset if DataStore's atomic rewrite is briefly unavailable.
runCatching { replaceAll(valid) }
}
return valid
}
override suspend fun read(contextKey: String, sessionId: String): ChatTurnCheckpoint? =
readAll().firstOrNull { it.contextKey == contextKey && it.sessionId == sessionId }
override suspend fun write(checkpoint: ChatTurnCheckpoint) {
dataStore.edit { preferences ->
val merged = mergeChatTurnCheckpoints(
existing = decode(preferences),
checkpoint = checkpoint,
now = now(),
limit = MAX_CHECKPOINTS,
)
preferences[KEY_CHECKPOINT_SET] = json.encodeToString(
ChatTurnCheckpointSet(checkpoints = merged),
)
preferences.remove(KEY_CHECKPOINT)
}
}
override suspend fun remove(contextKey: String, sessionId: String) {
dataStore.edit { preferences ->
val remaining = removeChatTurnCheckpoint(
decode(preferences),
contextKey,
sessionId,
)
if (remaining.isEmpty()) {
preferences.remove(KEY_CHECKPOINT_SET)
} else {
preferences[KEY_CHECKPOINT_SET] = json.encodeToString(
ChatTurnCheckpointSet(checkpoints = remaining),
)
}
preferences.remove(KEY_CHECKPOINT)
}
}
override suspend fun clear() {
dataStore.edit { preferences ->
preferences.remove(KEY_CHECKPOINT)
preferences.remove(KEY_CHECKPOINT_SET)
}
}
private fun decode(preferences: Preferences): List<ChatTurnCheckpoint> {
val current = preferences[KEY_CHECKPOINT_SET]?.let { raw ->
runCatching { json.decodeFromString<ChatTurnCheckpointSet>(raw) }.getOrNull()
}
if (current?.schemaVersion == ChatTurnCheckpointSet.CURRENT_SCHEMA) {
return current.checkpoints
}
return preferences[KEY_CHECKPOINT]?.let { raw ->
listOfNotNull(runCatching { json.decodeFromString<ChatTurnCheckpoint>(raw) }.getOrNull())
}.orEmpty()
}
private fun isValid(checkpoint: ChatTurnCheckpoint): Boolean =
checkpoint.schemaVersion == ChatTurnCheckpoint.CURRENT_SCHEMA &&
now() - checkpoint.updatedAt <= ChatTurnCheckpoint.MAX_AGE_MS
private suspend fun replaceAll(checkpoints: List<ChatTurnCheckpoint>) {
dataStore.edit { preferences ->
if (checkpoints.isEmpty()) {
preferences.remove(KEY_CHECKPOINT_SET)
} else {
preferences[KEY_CHECKPOINT_SET] = json.encodeToString(
ChatTurnCheckpointSet(checkpoints = checkpoints),
)
}
preferences.remove(KEY_CHECKPOINT)
}
}
private companion object {
const val MAX_CHECKPOINTS = 16
val KEY_CHECKPOINT = stringPreferencesKey("chat_inflight_turn_checkpoint_v1")
val KEY_CHECKPOINT_SET = stringPreferencesKey("chat_inflight_turn_checkpoints_v2")
}
}
internal fun mergeChatTurnCheckpoints(
existing: List<ChatTurnCheckpoint>,
checkpoint: ChatTurnCheckpoint,
now: Long,
limit: Int = 16,
): List<ChatTurnCheckpoint> =
(existing.filterNot {
it.contextKey == checkpoint.contextKey && it.sessionId == checkpoint.sessionId
} + checkpoint)
.filter {
it.schemaVersion == ChatTurnCheckpoint.CURRENT_SCHEMA &&
now - it.updatedAt <= ChatTurnCheckpoint.MAX_AGE_MS
}
.sortedByDescending(ChatTurnCheckpoint::updatedAt)
.take(limit)
internal fun removeChatTurnCheckpoint(
existing: List<ChatTurnCheckpoint>,
contextKey: String,
sessionId: String,
): List<ChatTurnCheckpoint> = existing.filterNot {
it.contextKey == contextKey && it.sessionId == sessionId
}
@Serializable
private data class ChatTurnCheckpointSet(
val schemaVersion: Int = CURRENT_SCHEMA,
val checkpoints: List<ChatTurnCheckpoint>,
) {
companion object {
const val CURRENT_SCHEMA = 1
}
}
@@ -0,0 +1,31 @@
package com.hermesandroid.relay.data
/**
* Pure, persisted-state-derived availability for a Hermes connection.
*
* This deliberately describes configured surfaces, not live reachability or
* authentication. Runtime layers can combine it with their probe/auth state
* without treating a missing optional API server or Relay as a broken Hermes
* connection.
*/
data class ConnectionCapabilities(
val dashboardGatewayConfigured: Boolean,
val apiServerConfigured: Boolean,
val relayConfigured: Boolean,
) {
val gatewayChatAvailable: Boolean get() = dashboardGatewayConfigured
val manageAvailable: Boolean get() = dashboardGatewayConfigured
val standardVoiceAvailable: Boolean get() = dashboardGatewayConfigured
val apiChatFallbackAvailable: Boolean get() = apiServerConfigured
val relayFeaturesAvailable: Boolean get() = relayConfigured
val chatConfigured: Boolean get() = gatewayChatAvailable || apiChatFallbackAvailable
val anySurfaceConfigured: Boolean
get() = dashboardGatewayConfigured || apiServerConfigured || relayConfigured
}
val Connection.capabilities: ConnectionCapabilities
get() = ConnectionCapabilities(
dashboardGatewayConfigured = resolvedDashboardUrl.isNotBlank(),
apiServerConfigured = apiServerUrl.isNotBlank(),
relayConfigured = relayUrl.isNotBlank(),
)
@@ -13,13 +13,16 @@ data class DashboardConnectionStatus(
val authProvider: String? = null,
val gatewayTicketAvailable: Boolean? = null,
val message: String? = null,
val gatewayMode: String? = null,
val profiles: List<String> = emptyList(),
)
/**
* A "connection" = a distinct Hermes server connection the app can switch between.
*
* Each connection has its own:
* - API server URL + relay URL
* - One or more independently-configured Hermes surfaces. Dashboard/Gateway
* is the standard primary path; API server and Relay are optional.
* - EncryptedSharedPreferences file (keyed by [tokenStoreKey]) holding the
* session token, device ID, API key, and paired-session metadata.
* - Cert pin (already host-keyed in [com.hermesandroid.relay.auth.CertPinStore]
@@ -73,17 +76,34 @@ data class Connection(
val preferredRouteRole: String? = null,
/** Epoch milliseconds. Pass `System.currentTimeMillis()`; do not pass seconds. */
val pairedAt: Long? = null,
/** Last time the user explicitly selected this connection. */
val lastUsedAt: Long? = null,
val lastActiveSessionId: String? = null,
val transportHint: String? = null,
/** Epoch milliseconds. The auth.ok `expires_at` field is seconds — multiply by 1000 at the call site. */
val expiresAt: Long? = null,
) {
/**
* Effective Dashboard/Gateway endpoint. Legacy records did not persist a
* dashboard URL, so they retain the conventional same-host `:9119`
* derivation from the API server. Dashboard-only records persist an
* explicit URL and may leave [apiServerUrl] and [relayUrl] blank.
*/
val resolvedDashboardUrl: String
get() = dashboardUrl
?.trim()
?.takeIf { it.isNotBlank() }
?: deriveDefaultDashboardUrl(apiServerUrl).orEmpty()
/** Stable display/host identity that does not depend on the API surface. */
val primaryEndpointUrl: String
get() = resolvedDashboardUrl.takeIf { it.isNotBlank() }
?: apiServerUrl.trim().takeIf { it.isNotBlank() }
?: relayUrl.trim()
val primaryHost: String
get() = extractHost(primaryEndpointUrl).orEmpty()
companion object {
/**
* The pre-multi-connection EncryptedSharedPreferences filename. Matches
@@ -94,6 +114,8 @@ data class Connection(
const val LEGACY_TOKEN_STORE_KEY: String = "hermes_companion_auth_hw"
const val DEFAULT_DASHBOARD_PORT: Int = 9119
const val DEFAULT_API_PORT: Int = 8642
const val DEFAULT_RELAY_PORT: Int = 8767
/**
* Derive a stable per-connection EncryptedSharedPreferences filename
@@ -111,12 +133,40 @@ data class Connection(
* user typed a malformed value — better to show something recognizable
* than to crash).
*/
fun extractDefaultLabel(apiServerUrl: String): String {
return try {
URI(apiServerUrl).host ?: apiServerUrl
} catch (_: Exception) {
apiServerUrl
}
fun extractDefaultLabel(apiServerUrl: String): String =
extractHost(apiServerUrl) ?: apiServerUrl
/** Preserve explicit labels while upgrading an auto-generated IP label to a discovered host name. */
fun chooseDiscoveredLabel(
currentLabel: String,
primaryHost: String,
discoveredHostname: String?,
): String {
val current = currentLabel.trim()
val discovered = discoveredHostname?.trim()?.takeIf { it.isNotBlank() }
val isAutomatic = current.isBlank() || current.equals(primaryHost.trim(), ignoreCase = true)
return if (isAutomatic && discovered != null) discovered else currentLabel
}
/**
* Dashboard-first label for a connection whose surfaces are optional.
* The one-argument overload above remains for source compatibility.
*/
fun extractDefaultLabel(
dashboardUrl: String?,
apiServerUrl: String,
relayUrl: String,
): String {
val primary = dashboardUrl?.trim()?.takeIf { it.isNotBlank() }
?: apiServerUrl.trim().takeIf { it.isNotBlank() }
?: relayUrl.trim()
return extractHost(primary) ?: primary
}
private fun extractHost(url: String): String? = try {
URI(url).host
} catch (_: Exception) {
null
}
fun deriveDefaultDashboardUrl(
@@ -141,6 +191,29 @@ data class Connection(
return "$scheme://$hostPart:$dashboardPort"
}
/** Derive the conventional same-host direct API fallback from a Dashboard URL. */
fun deriveDefaultApiUrl(
dashboardUrl: String,
apiPort: Int = DEFAULT_API_PORT,
): String? {
val trimmed = dashboardUrl.trim().trimEnd('/')
if (trimmed.isEmpty()) return null
val uri = runCatching { URI(trimmed) }.getOrNull() ?: return null
val scheme = when (uri.scheme?.lowercase()) {
"http" -> "http"
"https" -> "https"
else -> return null
}
val host = uri.host?.takeIf { it.isNotBlank() } ?: return null
val hostPart = if (host.contains(":") && !host.startsWith("[")) {
"[$host]"
} else {
host
}
return "$scheme://$hostPart:$apiPort"
}
fun isAutoManagedDashboardUrl(dashboardUrl: String?, apiServerUrl: String): Boolean {
val trimmed = dashboardUrl?.trim()?.trimEnd('/').orEmpty()
if (trimmed.isEmpty()) return true
@@ -150,7 +223,7 @@ data class Connection(
fun deriveDefaultRelayUrl(
apiServerUrl: String,
relayPort: Int = 8767,
relayPort: Int = DEFAULT_RELAY_PORT,
): String? {
val trimmed = apiServerUrl.trim().trimEnd('/')
if (trimmed.isEmpty()) return null
@@ -174,6 +247,7 @@ data class Connection(
apiServerUrl: String,
relayUrl: String,
extraApiUrls: List<Pair<String, String>> = emptyList(),
dashboardUrl: String? = null,
): List<EndpointCandidate> {
val routes = buildList {
endpointCandidateFromApiUrl(
@@ -182,6 +256,7 @@ data class Connection(
apiServerUrl = apiServerUrl,
relayUrl = relayUrl.takeIf { it.isNotBlank() }
?: deriveDefaultRelayUrl(apiServerUrl).orEmpty(),
dashboardUrl = dashboardUrl,
)?.let(::add)
extraApiUrls
@@ -193,13 +268,14 @@ data class Connection(
priority = index + 1,
apiServerUrl = url,
relayUrl = deriveDefaultRelayUrl(url).orEmpty(),
dashboardUrl = dashboardUrl,
)?.let(::add)
}
}
return routes
.distinctBy {
"${it.role.lowercase()}|${it.api.host.lowercase()}:${it.api.port}"
"${it.role.lowercase()}|${it.routeAuthority()}"
}
.sortedWith(compareBy<EndpointCandidate> { it.priority }.thenBy { it.role })
}
@@ -222,13 +298,13 @@ data class Connection(
existing: List<EndpointCandidate>,
): List<EndpointCandidate> {
val rebuiltHostPorts = rebuilt
.map { "${it.api.host.lowercase()}:${it.api.port}" }
.mapNotNull { it.mergeAuthority() }
.toSet()
val preserved = existing
.filter { it.priority > 0 }
.filterNot { "${it.api.host.lowercase()}:${it.api.port}" in rebuiltHostPorts }
.filterNot { it.mergeAuthority() in rebuiltHostPorts }
return (rebuilt + preserved)
.distinctBy { "${it.role.lowercase()}|${it.api.host.lowercase()}:${it.api.port}" }
.distinctBy { "${it.role.lowercase()}|${it.routeAuthority()}" }
.sortedWith(compareBy<EndpointCandidate> { it.priority }.thenBy { it.role })
}
@@ -267,6 +343,7 @@ data class Connection(
priority: Int,
apiServerUrl: String,
relayUrl: String,
dashboardUrl: String? = null,
): EndpointCandidate? {
val uri = runCatching { URI(apiServerUrl.trim().trimEnd('/')) }.getOrNull()
?: return null
@@ -290,12 +367,141 @@ data class Connection(
role = role.ifBlank { inferRouteRole(apiServerUrl) },
priority = priority,
api = ApiEndpoint(host = host, port = port, tls = tls),
dashboard = deriveDefaultDashboardUrl(apiServerUrl)
dashboard = dashboardUrl
?.trim()
?.trimEnd('/')
?.takeIf { it.isNotBlank() && urlsShareHost(it, apiServerUrl) }
?.let { DashboardEndpoint(url = it) }
?: deriveDefaultDashboardUrl(apiServerUrl)
?.let { DashboardEndpoint(url = it) },
relay = RelayEndpoint(url = resolvedRelayUrl, transportHint = transportHint),
)
}
/**
* Reconcile stored API-derived routes with the Dashboard origin that
* was actually verified during setup. Older app versions synthesized
* `:9119` for every API route, even when the same host was reached
* through an HTTPS reverse proxy on 443. Replace only that conventional
* synthesized value (or a missing value); preserve explicit and
* different-host LAN/Tailscale routes.
*/
fun reconcileDashboardRoutes(
dashboardUrl: String?,
candidates: List<EndpointCandidate>,
): List<EndpointCandidate> {
val explicitDashboard = dashboardUrl
?.trim()
?.trimEnd('/')
?.takeIf { it.isNotBlank() }
?: return candidates
return candidates.map { candidate ->
val apiUrl = candidate.api?.url ?: return@map candidate
if (!urlsShareHost(explicitDashboard, apiUrl)) return@map candidate
val currentDashboard = candidate.dashboard?.url
val derivedDashboard = deriveDefaultDashboardUrl(apiUrl)
val canReplace = currentDashboard.isNullOrBlank() ||
(
derivedDashboard != null &&
currentDashboard.trim().trimEnd('/')
.equals(derivedDashboard, ignoreCase = true)
)
if (canReplace) {
candidate.copy(dashboard = DashboardEndpoint(url = explicitDashboard))
} else {
candidate
}
}
}
fun urlsShareHost(leftUrl: String, rightUrl: String): Boolean {
val leftHost = runCatching { URI(leftUrl.trim()) }.getOrNull()?.host
val rightHost = runCatching { URI(rightUrl.trim()) }.getOrNull()?.host
return !leftHost.isNullOrBlank() &&
!rightHost.isNullOrBlank() &&
leftHost.equals(rightHost, ignoreCase = true)
}
/**
* De-duplication identity for rebuilding stored routes. Prefer the
* legacy API authority when present so an older API-only candidate and
* its dashboard-enriched replacement still collide. Dashboard-only
* candidates fall back to their primary route authority.
*/
private fun EndpointCandidate.mergeAuthority(): String? =
api?.let { endpoint -> "api|${endpoint.host.lowercase()}:${endpoint.port}" }
?: routeAuthority()?.let { authority -> "route|$authority" }
/**
* Build a Dashboard/Gateway-primary route from a remote host or URL.
* API and Relay are retained only when explicitly configured; callers
* no longer need to invent an API key or legacy surface URL.
*/
fun endpointCandidateFromDashboardUrl(
role: String,
priority: Int,
dashboardUrl: String,
apiServerUrl: String? = null,
relayUrl: String? = null,
): EndpointCandidate? {
val normalizedDashboard = normalizeDashboardUrlInput(dashboardUrl)
val dashboardUri = runCatching { URI(normalizedDashboard) }.getOrNull() ?: return null
if (dashboardUri.scheme?.lowercase() !in setOf("http", "https") ||
dashboardUri.host.isNullOrBlank()
) return null
val api = apiServerUrl
?.trim()
?.takeIf { it.isNotBlank() }
?.let { apiUrl ->
val apiUri = runCatching { URI(apiUrl.trimEnd('/')) }.getOrNull()
?: return@let null
val tls = when (apiUri.scheme?.lowercase()) {
"http" -> false
"https" -> true
else -> return@let null
}
val host = apiUri.host?.takeIf { it.isNotBlank() } ?: return@let null
ApiEndpoint(host, if (apiUri.port > 0) apiUri.port else 8642, tls)
}
val relay = relayUrl
?.trim()
?.takeIf { it.isNotBlank() }
?.let { url ->
val hint = when {
url.startsWith("wss://", ignoreCase = true) -> "wss"
url.startsWith("ws://", ignoreCase = true) -> "ws"
else -> null
}
RelayEndpoint(url, hint)
}
return EndpointCandidate(
role = role.ifBlank { inferRouteRole(normalizedDashboard) },
priority = priority,
dashboard = DashboardEndpoint(normalizedDashboard),
api = api,
relay = relay,
)
}
fun normalizeDashboardUrlInput(
raw: String,
defaultPort: Int = DEFAULT_DASHBOARD_PORT,
): String {
val trimmed = raw.trim().trimEnd('/')
if (trimmed.isEmpty()) return trimmed
if (SCHEME_REGEX.containsMatchIn(trimmed)) return trimmed
val withScheme = "http://$trimmed"
val uri = runCatching { URI(withScheme) }.getOrNull()
val canAppendPort = uri != null &&
!uri.host.isNullOrBlank() &&
uri.port <= 0 &&
uri.rawPath.isNullOrEmpty() &&
uri.rawQuery == null
return if (canAppendPort) "$withScheme:$defaultPort" else withScheme
}
fun inferRouteRole(apiServerUrl: String): String {
val host = runCatching { URI(apiServerUrl.trim().trimEnd('/')).host }
.getOrNull()
@@ -0,0 +1,156 @@
package com.hermesandroid.relay.data
/**
* Single source of truth for "is this connection encrypted, and by what?"
*
* Security is **per-surface**: a single paired connection fans out to several
* transports (chat/gateway + Manage over the dashboard, API/sessions, relay
* tools) and each can independently be TLS, overlay-encrypted, or plain (see
* [computeConnectionSecurity]). Every UI surface — the chat status chip, the
* connection header, the route picker, the detail sheet — renders the same
* derived [ConnectionSecurity] so no two places disagree about what "secure"
* means.
*
* Crucially, **"encrypted" includes overlay transports** (Tailscale/WireGuard,
* the plugin secure proxy), not just TLS. A `ws://` link over a tailnet is
* WireGuard-encrypted end-to-end — genuinely secure, just not TLS — so it is
* never labelled "insecure". Only a plain scheme with no overlay warns.
*/
enum class SurfaceSecurityKind { Tls, Overlay, Plain }
/** Connection-level rollup across the surfaces actually in use. */
enum class ConnectionSecurityLevel { Tls, Overlay, Mixed, Plain, Unknown }
/** Security verdict for one transport surface of a connection. */
data class SurfaceSecurity(
val label: String,
val kind: SurfaceSecurityKind,
/** Human mechanism: "TLS", "Tailscale", "WireGuard", "Proxy", "Plain". */
val mechanism: String,
val url: String,
)
data class ConnectionSecurity(
val level: ConnectionSecurityLevel,
/** Dominant mechanism for the at-a-glance label. */
val mechanism: String,
val surfaces: List<SurfaceSecurity>,
) {
/** True when every in-use surface is encrypted (TLS or overlay). */
val isEncrypted: Boolean
get() = level == ConnectionSecurityLevel.Tls || level == ConnectionSecurityLevel.Overlay
companion object {
val UNKNOWN = ConnectionSecurity(ConnectionSecurityLevel.Unknown, "", emptyList())
}
}
/** True when the URL scheme is TLS (`wss://` / `https://`). */
fun isTlsUrl(url: String?): Boolean {
if (url.isNullOrBlank()) return false
val lower = url.trim().lowercase()
return lower.startsWith("wss://") || lower.startsWith("https://")
}
/**
* True when the active route is encrypted by an overlay network (Tailscale /
* WireGuard) or the plugin secure proxy, even if its scheme is plain. Mirrors
* the logic that previously lived privately in `ActiveConnectionSections`.
*/
fun EndpointCandidate?.isEncryptedOverlayRoute(isTailscaleDetected: Boolean): Boolean {
if (this == null) return false
val r = role.lowercase()
val hint = security.orEmpty().lowercase()
return r == "tailscale" ||
(isTailscaleDetected && hint.contains("tailscale")) ||
r == "plugin_proxy" ||
r == "plugin-proxy" ||
hasSecureProxy() ||
hint.contains("wireguard") ||
hint.contains("https") ||
hint.contains("tls")
}
/** Human label for the overlay mechanism encrypting a route. */
fun EndpointCandidate?.overlayMechanism(isTailscaleDetected: Boolean): String {
if (this == null) return "Encrypted"
val r = role.lowercase()
val hint = security.orEmpty().lowercase()
return when {
r == "tailscale" || (isTailscaleDetected && hint.contains("tailscale")) -> "Tailscale"
r == "plugin_proxy" || r == "plugin-proxy" || hasSecureProxy() -> "Proxy"
hint.contains("wireguard") -> "WireGuard"
hint.contains("https") || hint.contains("tls") -> "TLS"
else -> "Encrypted"
}
}
/** Classify a single surface URL against the active route. */
fun classifySurfaceSecurity(
label: String,
url: String,
activeEndpoint: EndpointCandidate?,
isTailscaleDetected: Boolean,
): SurfaceSecurity {
val (kind, mechanism) = when {
isTlsUrl(url) -> SurfaceSecurityKind.Tls to "TLS"
activeEndpoint.isEncryptedOverlayRoute(isTailscaleDetected) ->
SurfaceSecurityKind.Overlay to activeEndpoint.overlayMechanism(isTailscaleDetected)
else -> SurfaceSecurityKind.Plain to "Plain"
}
return SurfaceSecurity(label = label, kind = kind, mechanism = mechanism, url = url)
}
/**
* Roll up the per-surface verdicts into one connection-level [ConnectionSecurity].
* Pure + side-effect free so it is unit-testable without Android.
*/
fun computeConnectionSecurity(
apiUrl: String,
dashboardUrl: String,
relayUrl: String,
relayConfigured: Boolean,
activeEndpoint: EndpointCandidate?,
isTailscaleDetected: Boolean,
): ConnectionSecurity {
val surfaces = buildList {
dashboardUrl.trim().takeIf { it.isNotBlank() }?.let {
add(classifySurfaceSecurity("Chat & Manage", it, activeEndpoint, isTailscaleDetected))
}
apiUrl.trim().takeIf { it.isNotBlank() }?.let {
add(classifySurfaceSecurity("API / sessions", it, activeEndpoint, isTailscaleDetected))
}
if (relayConfigured) {
relayUrl.trim().takeIf { it.isNotBlank() }?.let {
add(classifySurfaceSecurity("Relay tools", it, activeEndpoint, isTailscaleDetected))
}
}
}
if (surfaces.isEmpty()) return ConnectionSecurity.UNKNOWN
val kinds = surfaces.map { it.kind }.toSet()
val hasPlain = SurfaceSecurityKind.Plain in kinds
val hasSecure = kinds.any { it != SurfaceSecurityKind.Plain }
val level = when {
!hasSecure -> ConnectionSecurityLevel.Plain
hasPlain -> ConnectionSecurityLevel.Mixed
kinds == setOf(SurfaceSecurityKind.Tls) -> ConnectionSecurityLevel.Tls
else -> ConnectionSecurityLevel.Overlay
}
val mechanism = when (level) {
ConnectionSecurityLevel.Tls -> "TLS"
ConnectionSecurityLevel.Overlay ->
surfaces.firstOrNull { it.kind == SurfaceSecurityKind.Overlay }?.mechanism ?: "Encrypted"
ConnectionSecurityLevel.Mixed -> "Mixed"
ConnectionSecurityLevel.Plain -> when (activeEndpoint?.role?.lowercase()) {
"lan" -> "LAN"
"public" -> "Public"
null, "" -> "Plain"
else -> activeEndpoint.role
}
ConnectionSecurityLevel.Unknown -> ""
}
return ConnectionSecurity(level = level, mechanism = mechanism, surfaces = surfaces)
}
@@ -60,6 +60,7 @@ import kotlinx.serialization.json.Json
class ConnectionStore private constructor(
private val dataStore: DataStore<Preferences>,
private val context: Context?,
private val scope: CoroutineScope,
) {
/**
@@ -71,6 +72,7 @@ class ConnectionStore private constructor(
constructor(context: Context) : this(
dataStore = context.relayDataStore,
context = context.applicationContext,
scope = CoroutineScope(Dispatchers.Default + SupervisorJob()),
)
/**
@@ -81,9 +83,13 @@ class ConnectionStore private constructor(
internal constructor(dataStore: DataStore<Preferences>) : this(
dataStore = dataStore,
context = null,
scope = CoroutineScope(Dispatchers.Default + SupervisorJob()),
)
private val scope = CoroutineScope(Dispatchers.Default + SupervisorJob())
internal constructor(
dataStore: DataStore<Preferences>,
scope: CoroutineScope,
) : this(dataStore = dataStore, context = null, scope = scope)
private val json = Json {
ignoreUnknownKeys = true
@@ -100,6 +106,13 @@ class ConnectionStore private constructor(
private val _activeConnectionId = MutableStateFlow<String?>(null)
val activeConnectionId: StateFlow<String?> = _activeConnectionId.asStateFlow()
/**
* Optional cold-start pin. `null` means restore the last connection the
* user actively selected, which remains the recommended default.
*/
private val _startupConnectionId = MutableStateFlow<String?>(null)
val startupConnectionId: StateFlow<String?> = _startupConnectionId.asStateFlow()
/**
* Flips to `true` once the initial DataStore hydrate completes (success OR
* failure). Until then [connections] / [activeConnection] hold their empty
@@ -128,6 +141,7 @@ class ConnectionStore private constructor(
val oldJson = prefs[KEY_LEGACY_PROFILES]
val activeNew = prefs[KEY_ACTIVE_CONNECTION_ID]
val activeOld = prefs[KEY_LEGACY_ACTIVE_PROFILE_ID]
val startupId = prefs[KEY_STARTUP_CONNECTION_ID]
// Prefer the new key. If absent and the old key has data,
// migrate it once: write to the new key and clear the old ones
@@ -143,15 +157,21 @@ class ConnectionStore private constructor(
p.remove(KEY_LEGACY_ACTIVE_PROFILE_ID)
}
}
_connections.value = decodeConnections(oldJson)
_activeConnectionId.value = activeOld
val restored = decodeConnections(oldJson)
val validStartupId = startupId?.takeIf { id -> restored.any { it.id == id } }
_connections.value = restored
_startupConnectionId.value = validStartupId
_activeConnectionId.value = validStartupId ?: activeOld
Log.i(
TAG,
"Migrated legacy DataStore keys (profiles_v1 → connections_v1)",
)
} else {
_connections.value = decodeConnections(newJson)
_activeConnectionId.value = activeNew
val restored = decodeConnections(newJson)
val validStartupId = startupId?.takeIf { id -> restored.any { it.id == id } }
_connections.value = restored
_startupConnectionId.value = validStartupId
_activeConnectionId.value = validStartupId ?: activeNew
}
} catch (e: Exception) {
Log.w(TAG, "Initial hydrate failed: ${e.message}")
@@ -229,6 +249,10 @@ class ConnectionStore private constructor(
prefs.remove(KEY_ACTIVE_CONNECTION_ID)
_activeConnectionId.value = null
}
if (prefs[KEY_STARTUP_CONNECTION_ID] == id) {
prefs.remove(KEY_STARTUP_CONNECTION_ID)
_startupConnectionId.value = null
}
}
removed?.let { deleteTokenStoresFor(it) }
}
@@ -247,10 +271,12 @@ class ConnectionStore private constructor(
removed = decodeConnections(prefs[KEY_CONNECTIONS])
prefs.remove(KEY_CONNECTIONS)
prefs.remove(KEY_ACTIVE_CONNECTION_ID)
prefs.remove(KEY_STARTUP_CONNECTION_ID)
prefs.remove(KEY_LEGACY_PROFILES)
prefs.remove(KEY_LEGACY_ACTIVE_PROFILE_ID)
_connections.value = emptyList()
_activeConnectionId.value = null
_startupConnectionId.value = null
}
removed.forEach { deleteTokenStoresFor(it) }
}
@@ -259,6 +285,7 @@ class ConnectionStore private constructor(
suspend fun replaceConnections(
connections: List<Connection>,
activeConnectionId: String? = null,
startupConnectionId: String? = null,
) {
writeMutex.withLock {
var removed: List<Connection> = emptyList()
@@ -266,6 +293,8 @@ class ConnectionStore private constructor(
val normalizedActiveId = activeConnectionId
?.takeIf { id -> normalizedConnections.any { it.id == id } }
?: normalizedConnections.firstOrNull()?.id
val normalizedStartupId = startupConnectionId
?.takeIf { id -> normalizedConnections.any { it.id == id } }
dataStore.edit { prefs ->
removed = decodeConnections(prefs[KEY_CONNECTIONS])
@@ -281,8 +310,14 @@ class ConnectionStore private constructor(
}
prefs.remove(KEY_LEGACY_PROFILES)
prefs.remove(KEY_LEGACY_ACTIVE_PROFILE_ID)
if (normalizedStartupId == null) {
prefs.remove(KEY_STARTUP_CONNECTION_ID)
} else {
prefs[KEY_STARTUP_CONNECTION_ID] = normalizedStartupId
}
_connections.value = normalizedConnections
_activeConnectionId.value = normalizedActiveId
_activeConnectionId.value = normalizedStartupId ?: normalizedActiveId
_startupConnectionId.value = normalizedStartupId
}
removed.forEach { deleteTokenStoresFor(it) }
}
@@ -315,12 +350,44 @@ class ConnectionStore private constructor(
suspend fun setActiveConnection(id: String) {
writeMutex.withLock {
dataStore.edit { prefs ->
val current = decodeConnections(prefs[KEY_CONNECTIONS])
if (current.any { it.id == id }) {
val next = current.map { connection ->
if (connection.id == id) {
connection.copy(lastUsedAt = System.currentTimeMillis())
} else {
connection
}
}
prefs[KEY_CONNECTIONS] = encodeConnections(next)
_connections.value = next
}
prefs[KEY_ACTIVE_CONNECTION_ID] = id
_activeConnectionId.value = id
}
}
}
/** Set a specific cold-start connection, or `null` to restore last used. */
suspend fun setStartupConnection(id: String?) {
writeMutex.withLock {
dataStore.edit { prefs ->
val validId = id?.takeIf { candidate ->
decodeConnections(prefs[KEY_CONNECTIONS]).any { it.id == candidate }
}
if (validId == null) {
prefs.remove(KEY_STARTUP_CONNECTION_ID)
_activeConnectionId.value?.let { activeId ->
prefs[KEY_ACTIVE_CONNECTION_ID] = activeId
}
} else {
prefs[KEY_STARTUP_CONNECTION_ID] = validId
}
_startupConnectionId.value = validId
}
}
}
/**
* Update just the `lastActiveSessionId` on the identified connection.
* Called whenever the user picks a chat session so connection-switch can
@@ -476,34 +543,12 @@ class ConnectionStore private constructor(
}
}
private fun Connection.withDashboardDefaults(): Connection {
val derivedDashboardUrl = Connection.deriveDefaultDashboardUrl(apiServerUrl)
val normalizedRoutes = routeCandidates.ifEmpty {
Connection.buildRouteCandidates(apiServerUrl, relayUrl)
}
val normalizedPreferredRouteRole = preferredRouteRole?.takeIf { preferred ->
normalizedRoutes.any { it.role.equals(preferred, ignoreCase = true) }
}
return if (
(dashboardUrl.isNullOrBlank() && derivedDashboardUrl != null) ||
normalizedRoutes != routeCandidates ||
normalizedPreferredRouteRole != preferredRouteRole
) {
copy(
dashboardUrl = dashboardUrl?.takeIf { it.isNotBlank() } ?: derivedDashboardUrl,
routeCandidates = normalizedRoutes,
preferredRouteRole = normalizedPreferredRouteRole,
)
} else {
this
}
}
companion object {
private const val TAG = "ConnectionStore"
private val KEY_CONNECTIONS = stringPreferencesKey("connections_v1")
private val KEY_ACTIVE_CONNECTION_ID = stringPreferencesKey("active_connection_id")
private val KEY_STARTUP_CONNECTION_ID = stringPreferencesKey("startup_connection_id")
// Pre-rename DataStore keys — read once in init on first launch after
// the rename, then wiped. See the init block above.
@@ -517,3 +562,40 @@ class ConnectionStore private constructor(
private const val DEFAULT_RELAY_URL = "ws://localhost:8767"
}
}
/**
* Restore route defaults after loading a serialized connection. This remains
* internal so focused persistence tests can exercise the same normalization
* path used by [ConnectionStore].
*/
internal fun Connection.withDashboardDefaults(): Connection {
val derivedDashboardUrl = Connection.deriveDefaultDashboardUrl(apiServerUrl)
val effectiveDashboardUrl = dashboardUrl?.takeIf { it.isNotBlank() } ?: derivedDashboardUrl
val storedOrDefaultRoutes = routeCandidates.ifEmpty {
Connection.buildRouteCandidates(
apiServerUrl = apiServerUrl,
relayUrl = relayUrl,
dashboardUrl = effectiveDashboardUrl,
)
}
val normalizedRoutes = Connection.reconcileDashboardRoutes(
dashboardUrl = effectiveDashboardUrl,
candidates = storedOrDefaultRoutes,
)
val normalizedPreferredRouteRole = preferredRouteRole?.takeIf { preferred ->
normalizedRoutes.any { it.role.equals(preferred, ignoreCase = true) }
}
return if (
dashboardUrl != effectiveDashboardUrl ||
normalizedRoutes != routeCandidates ||
normalizedPreferredRouteRole != preferredRouteRole
) {
copy(
dashboardUrl = effectiveDashboardUrl,
routeCandidates = normalizedRoutes,
preferredRouteRole = normalizedPreferredRouteRole,
)
} else {
this
}
}
@@ -52,6 +52,45 @@ object ConnectionValidation {
kind = "relay URL",
)
/** Dashboard/Gateway URL must be HTTP(S) when configured. */
fun validateDashboardUrl(raw: String): String? = validateOptionalUrl(
raw = raw,
allowedSchemes = setOf("http", "https"),
kind = "Dashboard URL",
)
/** A blank API server means the optional SSE fallback is not configured. */
fun validateOptionalApiServerUrl(raw: String): String? = validateOptionalUrl(
raw = raw,
allowedSchemes = setOf("http", "https"),
kind = "API server URL",
)
/** A blank Relay URL means Relay-only power features are not configured. */
fun validateOptionalRelayUrl(raw: String): String? = validateOptionalUrl(
raw = raw,
allowedSchemes = setOf("ws", "wss"),
kind = "relay URL",
)
/**
* Validate the independently optional connection surfaces. A connection
* needs at least one endpoint, but Dashboard-only, API-only, and
* Relay-only records are all structurally valid.
*/
fun validateConnectionEndpoints(
dashboardUrl: String?,
apiServerUrl: String,
relayUrl: String,
): String? {
if (dashboardUrl.isNullOrBlank() && apiServerUrl.isBlank() && relayUrl.isBlank()) {
return "Configure at least one Hermes endpoint"
}
return validateDashboardUrl(dashboardUrl.orEmpty())
?: validateOptionalApiServerUrl(apiServerUrl)
?: validateOptionalRelayUrl(relayUrl)
}
/**
* Catches the "added the same server twice" mistake. Matches when the
* candidate's api + relay URLs exactly match an existing connection
@@ -67,12 +106,33 @@ object ConnectionValidation {
apiServerUrl: String,
relayUrl: String,
excludeId: String? = null,
dashboardUrl: String? = null,
): Connection? = connections.firstOrNull { c ->
c.id != excludeId &&
c.apiServerUrl.equals(apiServerUrl, ignoreCase = true) &&
c.relayUrl.equals(relayUrl, ignoreCase = true)
if (c.id == excludeId) {
false
} else {
val legacyExactMatch =
(apiServerUrl.isNotBlank() || relayUrl.isNotBlank()) &&
urlsEqual(c.apiServerUrl, apiServerUrl) &&
urlsEqual(c.relayUrl, relayUrl)
val candidateDashboard = dashboardUrl
?.takeIf { it.isNotBlank() }
?: Connection.deriveDefaultDashboardUrl(apiServerUrl)
val dashboardMatch = !candidateDashboard.isNullOrBlank() &&
urlsEqual(c.resolvedDashboardUrl, candidateDashboard)
legacyExactMatch || dashboardMatch
}
}
private fun validateOptionalUrl(
raw: String,
allowedSchemes: Set<String>,
kind: String,
): String? = if (raw.isBlank()) null else validateUrl(raw, allowedSchemes, kind)
private fun urlsEqual(first: String, second: String): Boolean =
first.trim().trimEnd('/').equals(second.trim().trimEnd('/'), ignoreCase = true)
private fun validateUrl(raw: String, allowedSchemes: Set<String>, kind: String): String? {
val trimmed = raw.trim()
if (trimmed.isEmpty()) return "$kind can't be blank"
@@ -72,10 +72,11 @@ class DataManager(
* - v5 (2026-06-08): full connection backups. Adds active connection id
* and `connectionSecrets`, including API keys, relay tokens, device id,
* paired metadata, and dashboard cookies.
* - v6 (2026-07-19): preserves the optional pinned startup connection.
*/
@Serializable
data class AppBackup(
val version: Int = 5,
val version: Int = 6,
val serverUrl: String? = null, // legacy (v1 compat)
val apiServerUrl: String? = null,
val relayUrl: String? = null,
@@ -83,6 +84,7 @@ class DataManager(
val onboardingCompleted: Boolean = false,
val connections: List<Connection> = emptyList(),
val activeConnectionId: String? = null,
val startupConnectionId: String? = null,
val containsSensitiveData: Boolean = true,
val connectionSecrets: List<ConnectionSecretBackup> = emptyList(),
val exportedAt: Long = System.currentTimeMillis(),
@@ -160,6 +162,7 @@ class DataManager(
onboardingCompleted = onboardingCompleted,
connections = connectionsSnapshot,
activeConnectionId = connectionStore?.activeConnectionId?.value,
startupConnectionId = connectionStore?.startupConnectionId?.value,
containsSensitiveData = true,
connectionSecrets = connectionSecrets,
exportedAt = System.currentTimeMillis(),
@@ -173,6 +176,7 @@ class DataManager(
store.replaceConnections(
connections = backup.connections,
activeConnectionId = backup.activeConnectionId,
startupConnectionId = backup.startupConnectionId,
)
val connectionsById = backup.connections.associateBy { it.id }
@@ -251,9 +255,11 @@ class DataManager(
suspend fun writeBackupToUri(uri: Uri, backup: String): Boolean {
return withContext(Dispatchers.IO) {
try {
context.contentResolver.openOutputStream(uri)?.use { outputStream ->
outputStream.write(backup.toByteArray(Charsets.UTF_8))
outputStream.flush()
val outputStream = context.contentResolver.openOutputStream(uri)
?: return@withContext false
outputStream.use {
it.write(backup.toByteArray(Charsets.UTF_8))
it.flush()
}
true
} catch (e: Exception) {
@@ -284,9 +290,10 @@ class DataManager(
* - Clear DataStore preferences
* - Clear EncryptedSharedPreferences (auth tokens)
* - Clear any cached data
* Does NOT clear the onboarding flag (that's separate via [resetOnboarding]).
* Preserves the onboarding flag. Use [resetOnboarding] when the next launch
* should show onboarding again.
*/
suspend fun resetAppData() {
suspend fun resetAppData(): Boolean =
try {
// Preserve onboarding state before clearing
val onboarding = isOnboardingCompleted()
@@ -316,10 +323,11 @@ class DataManager(
}
Log.d(TAG, "App data reset complete")
true
} catch (e: Exception) {
Log.e(TAG, "Failed to reset app data", e)
false
}
}
private suspend fun deleteSensitivePreferenceFiles() {
withContext(Dispatchers.IO) {
@@ -380,16 +388,17 @@ class DataManager(
* Reset only the onboarding completion flag.
* Next app launch will show onboarding again.
*/
suspend fun resetOnboarding() {
suspend fun resetOnboarding(): Boolean =
try {
context.relayDataStore.edit { preferences ->
preferences.remove(KEY_ONBOARDING_COMPLETED)
}
Log.d(TAG, "Onboarding flag reset")
true
} catch (e: Exception) {
Log.e(TAG, "Failed to reset onboarding flag", e)
false
}
}
/**
* Check if onboarding has been completed.
@@ -408,13 +417,14 @@ class DataManager(
/**
* Mark onboarding as completed.
*/
suspend fun setOnboardingCompleted(completed: Boolean) {
suspend fun setOnboardingCompleted(completed: Boolean): Boolean =
try {
context.relayDataStore.edit { preferences ->
preferences[KEY_ONBOARDING_COMPLETED] = completed
}
true
} catch (e: Exception) {
Log.e(TAG, "Failed to set onboarding completed", e)
false
}
}
}
@@ -0,0 +1,164 @@
package com.hermesandroid.relay.data
/**
* Curated, offline sample conversation for **Demo mode** — the zero-setup,
* zero-network "Try the demo" path surfaced on the Connect screen.
*
* Why this exists: Hermes-Relay is a client for a *user-run* Hermes server, so
* a fresh install with no connection has nothing to show. Google Play review
* (and any curious first-run user) hits an empty Connect wall. Demo mode feeds
* this canned transcript through the **real** chat pipeline
* ([com.hermesandroid.relay.network.upstream.ChatHandler] →
* [com.hermesandroid.relay.viewmodel.ChatViewModel] → `ChatScreen`), so the app
* showcases streaming chat, Markdown, a tool-progress card, and a rich
* [HermesCard] without a single network call. See [DemoMode] for the state
* holder and `docs/play-store-listing.md` (App access) for the reviewer note.
*
* Content contract (keep it this way):
* - **Obviously fictional, English, no real personal/server data** — public
* repo hygiene. "Aurora Bay" is a made-up city; "Hermes" is the agent.
* - **Fully self-contained / renders with zero network** — every message is
* terminal (not streaming), every attachment is [AttachmentState.LOADED]
* with no `relayToken` (which would trigger a relay fetch), and no inline
* `http(s)` image needs to be fetched. The unit test asserts this.
* - **Deterministic timestamps** ([DEMO_BASE_TIME] + offsets) so the demo
* looks the same every launch and the content is unit-testable.
*/
object DemoContent {
/**
* Fixed base wall-clock for demo timestamps (≈ mid-2025). Constant rather
* than `System.currentTimeMillis()` so the transcript is deterministic and
* the unit tests don't flake on timing.
*/
const val DEMO_BASE_TIME: Long = 1_750_000_000_000L
/** Stable session id for the demo conversation. */
const val DEMO_SESSION_ID: String = "demo-session"
/** Display name used on the assistant bubbles in the demo. */
const val DEMO_AGENT_NAME: String = "Hermes"
/**
* The canned conversation, oldest-first (the order `ChatScreen` renders).
* Two short exchanges: a capability tour that runs a tool and emits a rich
* card, then a quick "can you code?" follow-up showing a Markdown code
* block. 1–2 exchanges is enough to convey what the app does.
*/
fun transcript(): List<ChatMessage> = listOf(
ChatMessage(
id = "demo-user-1",
role = MessageRole.USER,
content = "Hey Hermes — what can this app do? And what's the weather in Aurora Bay?",
timestamp = DEMO_BASE_TIME,
clientOnly = true,
),
ChatMessage(
id = "demo-assistant-1",
role = MessageRole.ASSISTANT,
content = ASSISTANT_TOUR,
timestamp = DEMO_BASE_TIME + 3_000L,
agentName = DEMO_AGENT_NAME,
badges = listOf("Demo"),
toolCalls = listOf(
ToolCall(
id = "demo-tool-1",
name = "web_search",
args = "{\"query\":\"weather in Aurora Bay today\"}",
result = "Aurora Bay — 18°C, partly cloudy, wind 12 km/h NW.",
success = true,
isComplete = true,
provenance = "demo",
startedAt = DEMO_BASE_TIME + 800L,
completedAt = DEMO_BASE_TIME + 2_300L,
),
),
cards = listOf(
HermesCard(
type = HermesCard.BuiltInTypes.WEATHER,
title = "Aurora Bay",
subtitle = "Partly cloudy",
accent = HermesCard.Accents.INFO,
fields = listOf(
HermesCardField("Now", "18°C · feels like 17°C"),
HermesCardField("Wind", "12 km/h NW"),
HermesCardField("Sunset", "8:42 PM"),
),
footer = "Sample data — demo mode",
id = "demo-weather",
),
),
clientOnly = true,
),
ChatMessage(
id = "demo-user-2",
role = MessageRole.USER,
content = "Nice! Can you write code too?",
timestamp = DEMO_BASE_TIME + 9_000L,
clientOnly = true,
),
ChatMessage(
id = "demo-assistant-2",
role = MessageRole.ASSISTANT,
content = ASSISTANT_CODE,
timestamp = DEMO_BASE_TIME + 12_000L,
agentName = DEMO_AGENT_NAME,
badges = listOf("Demo"),
clientOnly = true,
),
)
/**
* Assistant reply appended when the user sends a message INSIDE demo
* mode. The composer must not be a silent no-op (it reads as broken —
* see the demo-polish TODO), but there is no server to answer, so the
* "reply" is an honest notice pointing at the exit path. Same content
* contract as the transcript: clientOnly, terminal, zero network.
*
* @param id unique message id supplied by the caller (UUID-based; two
* rapid sends must not collide on LazyColumn keys).
* @param nowMs wall-clock timestamp for the bubble.
*/
fun composerReply(id: String, nowMs: Long): ChatMessage = ChatMessage(
id = id,
role = MessageRole.ASSISTANT,
content = COMPOSER_REPLY,
timestamp = nowMs,
agentName = DEMO_AGENT_NAME,
badges = listOf("Demo"),
clientOnly = true,
)
// --- Message bodies (Markdown). Kept as constants so the content is easy
// to scan and the [transcript] builder stays readable. ---
private val COMPOSER_REPLY: String = """
This is the offline demo, so I can't answer for real — nothing here talks to a server.
Connect your own Hermes server to chat live: tap **Connect** in the demo banner above.
""".trimIndent()
private val ASSISTANT_TOUR: String = """
I'm **Hermes**, the agent running on *your* server. Here's a quick tour of what this app surfaces:
- **Live streaming chat** with Markdown, code blocks, and reasoning
- **Tool calls** rendered as progress cards — watch me work in real time
- **Rich cards** for structured results like the one below
- Optional **Terminal**, **Bridge**, and **Voice** once you connect a server
I just looked up the forecast for you:
""".trimIndent()
private val ASSISTANT_CODE: String = """
Absolutely — code blocks render with syntax-aware styling. For example:
```kotlin
fun greet(name: String): String = "Hello, ${'$'}name!"
println(greet("Aurora Bay"))
// -> Hello, Aurora Bay!
```
Connect your Hermes server to chat for real, run tools, and pick up where this demo leaves off.
""".trimIndent()
}
@@ -0,0 +1,48 @@
package com.hermesandroid.relay.data
import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.flow.StateFlow
import kotlinx.coroutines.flow.asStateFlow
/**
* Offline **Demo / Explore mode** state holder.
*
* Plain Kotlin (no Android, no network, no coroutines side-effects) so it can
* be unit-tested on the pure JVM and owned by the Activity-scoped
* [com.hermesandroid.relay.viewmodel.ConnectionViewModel] without dragging
* framework dependencies into the demo path. The ViewModel delegates
* `isDemoMode` to [active] and pushes [transcript] into the real `ChatHandler`
* so the canned conversation renders through the production chat UI.
*
* Lifecycle: [enter] flips [active] true and loads the canned [DemoContent]
* transcript; [exit] flips it false and clears the transcript. Entering demo
* must **never** mark onboarding complete or start a connection — the
* ViewModel's network entry points early-return while [active] is true (see
* `reconnectIfStale` / `revalidate` / `connectRelay`).
*
* @param transcriptFactory source of the demo transcript. Defaults to
* [DemoContent.transcript]; overridable in tests.
*/
class DemoMode(
private val transcriptFactory: () -> List<ChatMessage> = DemoContent::transcript,
) {
private val _active = MutableStateFlow(false)
/** True while the offline demo is active. Drives the banner + network gates. */
val active: StateFlow<Boolean> = _active.asStateFlow()
private val _transcript = MutableStateFlow<List<ChatMessage>>(emptyList())
/** The canned conversation while [active]; empty otherwise. */
val transcript: StateFlow<List<ChatMessage>> = _transcript.asStateFlow()
/** Enter demo: load the canned transcript, then mark active. Idempotent. */
fun enter() {
_transcript.value = transcriptFactory()
_active.value = true
}
/** Exit demo: clear active, then drop the transcript. Idempotent. */
fun exit() {
_active.value = false
_transcript.value = emptyList()
}
}
@@ -2,6 +2,7 @@ package com.hermesandroid.relay.data
import kotlinx.serialization.SerialName
import kotlinx.serialization.Serializable
import java.net.URI
/**
* One entry in a pairing payload's `endpoints` array (ADR 24 — multi-endpoint
@@ -38,8 +39,10 @@ import kotlinx.serialization.Serializable
data class EndpointCandidate(
val role: String,
val priority: Int = 0,
val api: ApiEndpoint,
val relay: RelayEndpoint,
/** Optional legacy/API-server surface. Dashboard-only routes omit it. */
val api: ApiEndpoint? = null,
/** Optional Hermes-Relay bridge surface. Standard upstream routes omit it. */
val relay: RelayEndpoint? = null,
val dashboard: DashboardEndpoint? = null,
val proxy: ProxyEndpoint? = null,
val security: String? = null,
@@ -137,13 +140,42 @@ fun EndpointCandidate.displayLabel(): String {
return when (role.lowercase()) {
"lan" -> "LAN"
"tailscale" -> "Tailscale"
"public" -> if (api.tls) "HTTPS" else "Public"
"public" -> if (primaryRouteUrl()?.startsWith("https://", ignoreCase = true) == true) {
"HTTPS"
} else {
"Public"
}
"https" -> "HTTPS"
"plugin_proxy", "plugin-proxy" -> "Plugin proxy"
else -> "Custom VPN ($role)"
}
}
/** Dashboard-first URL identity for routing, diagnostics, and UI labels. */
fun EndpointCandidate.primaryRouteUrl(): String? =
dashboard?.url?.trim()?.trimEnd('/')?.takeIf { it.isNotBlank() }
?: api?.url
?: relay?.url?.trim()?.trimEnd('/')?.takeIf { it.isNotBlank() }
?: proxy?.url?.trim()?.trimEnd('/')?.takeIf { it.isNotBlank() }
/** Stable host/port identity without assuming that an API surface exists. */
fun EndpointCandidate.routeAuthority(): String? {
val rawUrl = primaryRouteUrl() ?: return null
val httpUrl = when {
rawUrl.startsWith("ws://", ignoreCase = true) -> "http://${rawUrl.substringAfter("://")}"
rawUrl.startsWith("wss://", ignoreCase = true) -> "https://${rawUrl.substringAfter("://")}"
else -> rawUrl
}
val uri = runCatching { URI(httpUrl) }.getOrNull() ?: return null
val host = uri.host?.lowercase()?.takeIf { it.isNotBlank() } ?: return null
val port = when {
uri.port > 0 -> uri.port
uri.scheme.equals("https", ignoreCase = true) -> 443
else -> 80
}
return "$host:$port"
}
fun EndpointCandidate.hasSecureProxy(): Boolean =
proxy?.url?.startsWith("https://", ignoreCase = true) == true ||
proxy?.url?.startsWith("wss://", ignoreCase = true) == true ||
@@ -10,7 +10,8 @@ import kotlinx.coroutines.flow.map
/**
* Feature flags with compile-time defaults and runtime overrides.
*
* In debug builds, all features are unlocked by default.
* In debug builds, Developer Options are unlocked by default until the user
* explicitly locks them.
* In release builds, experimental features are hidden unless the user
* enables Developer Options (tap version 7 times in Settings > About).
*
@@ -21,7 +22,6 @@ object FeatureFlags {
// DataStore keys
private val KEY_DEV_OPTIONS_UNLOCKED = booleanPreferencesKey("dev_options_unlocked")
private val KEY_RELAY_ENABLED = booleanPreferencesKey("feature_relay_enabled")
/** Whether the app is running a debug build. */
val isDevBuild: Boolean get() = BuildConfig.DEV_MODE
@@ -29,13 +29,7 @@ object FeatureFlags {
/** Observe whether Developer Options have been unlocked. */
fun devOptionsUnlocked(context: Context): Flow<Boolean> =
context.relayDataStore.data.map { prefs ->
if (isDevBuild) true else prefs[KEY_DEV_OPTIONS_UNLOCKED] ?: false
}
/** Observe whether relay features (settings, pairing, onboarding pages) are enabled. */
fun relayEnabled(context: Context): Flow<Boolean> =
context.relayDataStore.data.map { prefs ->
if (isDevBuild) true else prefs[KEY_RELAY_ENABLED] ?: false
prefs[KEY_DEV_OPTIONS_UNLOCKED] ?: isDevBuild
}
/** Unlock Developer Options. */
@@ -45,18 +39,10 @@ object FeatureFlags {
}
}
/** Lock Developer Options and disable all experimental features. */
/** Lock Developer Options, including in debug builds. */
suspend fun lockDevOptions(context: Context) {
context.relayDataStore.edit { prefs ->
prefs[KEY_DEV_OPTIONS_UNLOCKED] = false
prefs[KEY_RELAY_ENABLED] = false
}
}
/** Toggle relay features (terminal/bridge settings, pairing, onboarding relay page). */
suspend fun setRelayEnabled(context: Context, enabled: Boolean) {
context.relayDataStore.edit { prefs ->
prefs[KEY_RELAY_ENABLED] = enabled
}
}
@@ -5,7 +5,7 @@ import androidx.datastore.preferences.core.booleanPreferencesKey
import androidx.datastore.preferences.core.edit
/**
* Single source of truth for the opt-in "keep the gateway chat connection
* Single source of truth for the opt-in "keep the app's connection to Hermes
* alive in the background" preference. Off by default.
*
* Shared by [com.hermesandroid.relay.viewmodel.ConnectionViewModel] (the
@@ -246,4 +246,9 @@ data class HermesCardDispatch(
* passes.
*/
val syncedToServer: Boolean = false,
)
) {
companion object {
/** Local-only stamp used when Hermes expires an interactive ask. */
const val EXPIRED_STAMP = "expired"
}
}
@@ -0,0 +1,69 @@
package com.hermesandroid.relay.data
/**
* A process event that upstream Hermes injected into transcript history as a
* synthetic user message.
*
* Hermes intentionally persists these events with role=user so the agent can
* react to them without breaking message-role alternation. UI code should use
* [ChatMessage.hermesProcessNotificationOrNull] to present them as process
* notices without changing their canonical role or content.
*/
data class HermesProcessNotification(
val processId: String,
val headline: String,
val detail: String?,
)
/**
* Recognizes the exact envelope emitted by upstream
* `tools.process_registry.format_process_notification` for background-process
* completion and watch events.
*
* The parser deliberately excludes other `[IMPORTANT: ...]` messages. Those
* can carry unrelated agent instructions and must continue through the normal
* transcript renderer.
*/
object HermesProcessNotificationParser {
private const val ENVELOPE_PREFIX = "[IMPORTANT: Background process "
private const val HEADLINE_PREFIX = "Background process "
fun parse(content: String): HermesProcessNotification? {
val normalized = content.trim()
if (!normalized.startsWith(ENVELOPE_PREFIX) || !normalized.endsWith(']')) {
return null
}
val body = normalized
.removePrefix("[IMPORTANT: ")
.dropLast(1)
val headline = body.substringBefore('\n').trim()
if (!headline.startsWith(HEADLINE_PREFIX)) return null
val identityAndStatus = headline.removePrefix(HEADLINE_PREFIX)
val processId = identityAndStatus.substringBefore(' ')
val status = identityAndStatus.substringAfter(' ', missingDelimiterValue = "")
if (processId.isBlank() || status.isBlank()) return null
val detail = body
.substringAfter('\n', missingDelimiterValue = "")
.trim()
.ifBlank { null }
return HermesProcessNotification(
processId = processId,
headline = headline,
detail = detail,
)
}
}
/**
* Returns the upstream process-notification presentation model only for the
* canonical synthetic user-row shape. The original [ChatMessage.role] remains
* [MessageRole.USER].
*/
fun ChatMessage.hermesProcessNotificationOrNull(): HermesProcessNotification? =
takeIf { it.role == MessageRole.USER }
?.content
?.let(HermesProcessNotificationParser::parse)
@@ -0,0 +1,84 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.core.DataStore
import androidx.datastore.preferences.core.Preferences
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringPreferencesKey
import androidx.datastore.preferences.preferencesDataStore
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
import kotlinx.serialization.Serializable
import kotlinx.serialization.decodeFromString
import kotlinx.serialization.encodeToString
import kotlinx.serialization.json.Json
/**
* One agent-initiated message as persisted in the Hermes inbox.
*
* Deliberately separate from the wire model
* ([com.hermesandroid.relay.network.relay.ProactiveMessage]) so the on-disk
* shape doesn't track protocol changes — only the user-facing fields persist.
*/
@Serializable
data class ProactiveInboxEntry(
val id: String,
val title: String,
val text: String,
/** Epoch millis the message was received (server `sent_at` when present). */
val receivedAt: Long,
/**
* Conversation the message belongs to (server `chat_id`). Carried so an
* inbox reply (Phase 2c) continues the same thread. Nullable + defaulted
* so blobs persisted before 2c still decode (kotlinx tolerates the absent
* field).
*/
val chatId: String? = null,
)
private val Context.proactiveInboxStore: DataStore<Preferences> by
preferencesDataStore(name = "proactive_inbox")
private val INBOX_JSON = stringPreferencesKey("entries_json")
/** Bound the inbox so a chatty agent can't grow the on-disk blob without limit. */
private const val MAX_ENTRIES = 100
/**
* DataStore-backed durable log of agent-initiated messages. Entries are kept
* newest-first, deduped by id (so a re-delivered message doesn't double up), and
* capped at [MAX_ENTRIES]. Survives app restart.
*
* Demoted (2026-06-29): the agent conversation now lives as a Thread in Chat (the
* gateway session is the durable history), so the in-app inbox view is retired.
* This store is only fed for messages NOT shown in an open Thread; it currently
* has no viewer and is fully retireable — see TODO.
*/
class ProactiveInboxRepository(private val context: Context) {
private val json = Json { ignoreUnknownKeys = true }
val entries: Flow<List<ProactiveInboxEntry>> =
context.proactiveInboxStore.data.map { prefs -> decode(prefs[INBOX_JSON]) }
suspend fun add(entry: ProactiveInboxEntry) {
context.proactiveInboxStore.edit { prefs ->
val current = decode(prefs[INBOX_JSON]).toMutableList()
current.removeAll { it.id == entry.id }
current.add(0, entry)
while (current.size > MAX_ENTRIES) current.removeAt(current.lastIndex)
prefs[INBOX_JSON] = json.encodeToString(current.toList())
}
}
suspend fun clear() {
context.proactiveInboxStore.edit { it.remove(INBOX_JSON) }
}
private fun decode(raw: String?): List<ProactiveInboxEntry> {
if (raw.isNullOrBlank()) return emptyList()
return runCatching {
json.decodeFromString<List<ProactiveInboxEntry>>(raw)
}.getOrDefault(emptyList())
}
}
@@ -0,0 +1,33 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.preferences.core.booleanPreferencesKey
import androidx.datastore.preferences.core.edit
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
/**
* "Let Hermes message me" — the off-by-default opt-in that lets the agent
* proactively push messages to this phone (the `phone` Hermes platform).
*
* This is the app half of a two-sided gate: the server-side adapter is gated
* on `PHONE_ENABLED`, and the relay can only push when the app has sent
* `proactive.subscribe` — which the app only does when this flag is on. So
* nothing is delivered unless BOTH sides opt in.
*
* Shared by [com.hermesandroid.relay.viewmodel.ConnectionViewModel] (the
* StateFlow + subscribe/unsubscribe wiring) and the Settings switch that
* flips it. Phase 3 expands this into a fuller `ProactivePreferences`
* (quiet hours, per-profile scope, rate limiting); the enablement flag is
* the foundational gate and lives here next to the other shared pref keys.
*/
val KEY_PROACTIVE_ENABLED = booleanPreferencesKey("proactive_messages_enabled")
/** Persist the "Let Hermes message me" preference. */
suspend fun Context.setProactiveEnabled(enabled: Boolean) {
relayDataStore.edit { it[KEY_PROACTIVE_ENABLED] = enabled }
}
/** Reactive read of the enablement flag — defaults to false (off). */
fun Context.proactiveEnabledFlow(): Flow<Boolean> =
relayDataStore.data.map { it[KEY_PROACTIVE_ENABLED] ?: false }
@@ -0,0 +1,95 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.core.DataStore
import androidx.datastore.preferences.core.Preferences
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringPreferencesKey
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
/**
* Per-connection persisted "profile lock" — pins the app to ONE Hermes
* profile so the profile pickers/switchers across the app collapse to a
* single locked state. A dedicated Settings control is the only surface that
* still lists every profile (to choose the lock target or unlock).
*
* Twin of [ProfileSelectionStore]: this deliberately rides the SAME
* [profileSelectionsDataStore] ("profile_selections") so the lock and the
* selection clear and migrate together — a per-connection wipe or a wholesale
* reset takes out both, and there is no second DataStore file to keep in sync.
*
* Value semantics (distinct from "selection", which is just a name or absent):
* - **absent key** → unlocked. The flow emits `null`. This is distinct from
* "locked to Server default", so we can tell "no lock" apart from "lock to
* the server's own default profile".
* - [AgentDisplay.SERVER_DEFAULT_PROFILE_KEY] sentinel → locked to **Server
* default** (the null-profile context). Reusing the existing sentinel keeps
* the server-default identity consistent with [AgentDisplay.profileSessionKey].
* - any other string → locked to that profile `name`.
*
* The caller ([com.hermesandroid.relay.viewmodel.connection.ProfileController])
* resolves the locked name against the current server-advertised profile list;
* if the locked profile no longer exists it HOLDS (selection null) and surfaces
* a banner rather than silently switching.
*/
class ProfileLockStore(
private val dataStore: DataStore<Preferences>,
) {
constructor(context: Context) : this(context.profileSelectionsDataStore)
companion object {
/**
* Preference-key factory. Per-connection so every connection gets its
* own lock slot — profiles are server-scoped, so a lock pinned on one
* server must not leak onto another.
*/
private fun keyFor(connectionId: String) =
stringPreferencesKey("locked_profile_$connectionId")
}
/**
* Persist the lock for [connectionId].
* - `null` → **unlock**: removes the key (converges with fresh-install
* "no key" state).
* - any non-null [profileName] → lock to that profile name. Callers lock
* to Server default by passing [AgentDisplay.SERVER_DEFAULT_PROFILE_KEY].
*/
suspend fun setLockedProfile(connectionId: String, profileName: String?) {
dataStore.edit { prefs ->
val key = keyFor(connectionId)
if (profileName == null) {
prefs.remove(key)
} else {
prefs[key] = profileName
}
}
}
/**
* Emits the locked profile name for [connectionId], or `null` when no lock
* is stored (unlocked). The sentinel
* [AgentDisplay.SERVER_DEFAULT_PROFILE_KEY] means "locked to Server default".
*/
fun lockedProfileFlow(connectionId: String): Flow<String?> {
val key = keyFor(connectionId)
return dataStore.data.map { prefs -> prefs[key] }
}
/**
* Remove the persisted lock for [connectionId]. Called from the connection
* removal path alongside the selection clear so a removed connection's lock
* pointer goes with it.
*/
suspend fun clear(connectionId: String) {
dataStore.edit { prefs ->
prefs.remove(keyFor(connectionId))
}
}
suspend fun clearAll() {
dataStore.edit { prefs ->
prefs.clear()
}
}
}
@@ -0,0 +1,21 @@
package com.hermesandroid.relay.data
/** User-facing availability of one Hermes profile from this connection. */
enum class ProfilePresence {
/** Its dedicated gateway is running, so channels and proactive work can stay reachable. */
ONLINE,
/** The host can create/resume profile-bound sessions on demand, but no profile gateway is running. */
AVAILABLE,
/** The host/profile cannot currently be reached from this connection. */
OFFLINE,
}
object ProfilePresenceResolver {
fun resolve(profile: Profile, hostReachable: Boolean = true): ProfilePresence = when {
!hostReachable -> ProfilePresence.OFFLINE
profile.gatewayRunning -> ProfilePresence.ONLINE
else -> ProfilePresence.AVAILABLE
}
}
@@ -0,0 +1,99 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.core.DataStore
import androidx.datastore.preferences.core.Preferences
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringPreferencesKey
import androidx.datastore.preferences.preferencesDataStore
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
import kotlinx.serialization.builtins.ListSerializer
import kotlinx.serialization.builtins.serializer
import kotlinx.serialization.json.Json
/** Per-connection local display preferences for the profile picker. */
data class ProfilePresentation(
val order: List<String> = emptyList(),
val hidden: Set<String> = emptySet(),
)
/**
* Applies saved presentation preferences without changing the server profile catalog.
* Unknown saved names are dropped and newly-discovered profiles append in server order.
*/
object ProfilePresentationPolicy {
fun availableKeys(profiles: List<Profile>): List<String> = buildList {
add(AgentDisplay.SERVER_DEFAULT_PROFILE_KEY)
profiles.asSequence()
.filterNot { AgentDisplay.isServerDefaultAlias(it.name) }
.map(Profile::name)
.distinct()
.forEach(::add)
}
fun orderedKeys(
profiles: List<Profile>,
presentation: ProfilePresentation,
): List<String> {
val available = availableKeys(profiles)
val availableSet = available.toSet()
return presentation.order.filter { it in availableSet }.distinct() +
available.filterNot(presentation.order.toSet()::contains)
}
fun visibleKeys(
profiles: List<Profile>,
presentation: ProfilePresentation,
selectedKey: String,
): List<String> = orderedKeys(profiles, presentation).filter { key ->
key == selectedKey || key !in presentation.hidden
}
}
class ProfilePresentationStore(
private val dataStore: DataStore<Preferences>,
) {
constructor(context: Context) : this(context.profilePresentationDataStore)
private val json = Json { ignoreUnknownKeys = true }
private val listSerializer = ListSerializer(String.serializer())
private fun orderKey(connectionId: String) = stringPreferencesKey("order_$connectionId")
private fun hiddenKey(connectionId: String) = stringPreferencesKey("hidden_$connectionId")
fun presentationFlow(connectionId: String): Flow<ProfilePresentation> = dataStore.data.map { prefs ->
ProfilePresentation(
order = decode(prefs[orderKey(connectionId)]),
hidden = decode(prefs[hiddenKey(connectionId)]).toSet(),
)
}
suspend fun setOrder(connectionId: String, order: List<String>) {
dataStore.edit { it[orderKey(connectionId)] = json.encodeToString(listSerializer, order.distinct()) }
}
suspend fun setHidden(connectionId: String, hidden: Set<String>) {
dataStore.edit { it[hiddenKey(connectionId)] = json.encodeToString(listSerializer, hidden.sorted()) }
}
suspend fun clear(connectionId: String) {
dataStore.edit {
it.remove(orderKey(connectionId))
it.remove(hiddenKey(connectionId))
}
}
suspend fun clearAll() {
dataStore.edit { it.clear() }
}
private fun decode(raw: String?): List<String> = if (raw == null) {
emptyList()
} else {
runCatching { json.decodeFromString(listSerializer, raw) }.getOrDefault(emptyList())
}
}
internal val Context.profilePresentationDataStore: DataStore<Preferences>
by preferencesDataStore(name = "profile_presentation")
@@ -0,0 +1,36 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringSetPreferencesKey
import androidx.datastore.preferences.preferencesDataStore
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
private val Context.sessionSourceDataStore by preferencesDataStore(name = "session_sources")
private val KEY_HIDDEN = stringSetPreferencesKey("hidden_sources")
/**
* Session `source`s hidden from the drawer by default — the agent's noisiest
* automation lanes. Everything else (your chats, Threads, discord, telegram, …)
* shows. The user can hide/reveal more from the drawer source filter or Chat
* settings; both edit the same persisted set.
*/
val DEFAULT_HIDDEN_SOURCES = setOf("cron", "webhook")
/** DataStore for which gateway sources the drawer hides. */
class SessionSourcePrefs(private val context: Context) {
val hiddenSources: Flow<Set<String>> = context.sessionSourceDataStore.data.map { prefs ->
prefs[KEY_HIDDEN] ?: DEFAULT_HIDDEN_SOURCES
}
suspend fun setHidden(source: String, hidden: Boolean) {
val key = source.trim().lowercase()
if (key.isBlank()) return
context.sessionSourceDataStore.edit { prefs ->
val cur = prefs[KEY_HIDDEN] ?: DEFAULT_HIDDEN_SOURCES
prefs[KEY_HIDDEN] = if (hidden) cur + key else cur - key
}
}
}
@@ -0,0 +1,43 @@
package com.hermesandroid.relay.data
import android.content.Context
import androidx.datastore.preferences.core.edit
import androidx.datastore.preferences.core.stringPreferencesKey
import androidx.datastore.preferences.preferencesDataStore
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.map
import kotlinx.serialization.builtins.MapSerializer
import kotlinx.serialization.builtins.serializer
import kotlinx.serialization.json.Json
private val Context.threadNameDataStore by preferencesDataStore(name = "thread_names")
private val KEY_NAMES = stringPreferencesKey("names_json")
/**
* Persists user-chosen agent **Thread** names (`sessionId` → name) so a named
* Thread keeps its name across app restarts — the user's name is authoritative
* (Discord-style), overriding the gateway's async auto-title which would
* otherwise clobber it. Applied to the drawer via
* [com.hermesandroid.relay.network.upstream.ChatHandler.setUserThreadNames].
*/
class ThreadNameStore(private val context: Context) {
private val json = Json { ignoreUnknownKeys = true }
private val ser = MapSerializer(String.serializer(), String.serializer())
private fun decode(raw: String?): Map<String, String> =
raw?.let { runCatching { json.decodeFromString(ser, it) }.getOrNull() } ?: emptyMap()
val names: Flow<Map<String, String>> = context.threadNameDataStore.data.map { prefs ->
decode(prefs[KEY_NAMES])
}
suspend fun setName(sessionId: String, name: String) {
val id = sessionId.trim()
val value = name.trim()
if (id.isBlank() || value.isBlank()) return
context.threadNameDataStore.edit { prefs ->
prefs[KEY_NAMES] = json.encodeToString(ser, decode(prefs[KEY_NAMES]) + (id to value))
}
}
}
@@ -0,0 +1,191 @@
package com.hermesandroid.relay.data
/**
* One-tap bundles over voice settings that already exist in the app and relay.
*
* Presets intentionally do not own voice identity or routing: engine, audio
* route, provider, model, voice, enhanced-voice overrides, and background-run
* concurrency all remain exactly as the user configured them. A preset only
* coordinates interaction ergonomics, barge-in, Realtime trace/session
* behavior, and the existing ADR 33 background-delivery controls.
*/
enum class VoiceModePreset(
val displayName: String,
val shortLabel: String,
val description: String,
internal val localSettings: VoicePresetLocalSettings,
internal val bargeInUpdate: VoicePresetBargeInUpdate,
val promotionUpdate: VoicePresetPromotionUpdate,
) {
HandsFree(
displayName = "Hands-free",
shortLabel = "Hands-free",
description =
"Continuous listening, exact answers, detailed trace, and low-noise " +
"spoken progress after 15 seconds. Your barge-in choice is preserved.",
localSettings = VoicePresetLocalSettings(
interactionMode = "continuous",
silenceThresholdMs = 1250L,
realtimeTraceDetails = true,
realtimePersistentSession = true,
),
// Barge-in remains an explicit experimental opt-in until echo and
// self-recording hardening is complete. Never enable it via a preset.
bargeInUpdate = VoicePresetBargeInUpdate(),
promotionUpdate = VoicePresetPromotionUpdate(
enabled = true,
promoteAfterMs = 6000,
backgroundDefaultMode = "promote",
spokenHandoff = true,
progressSpokenAfterMs = 15000,
progressRepeatMs = 90000,
resultDelivery = "speak_verbatim",
),
),
LowLatency(
displayName = "Low latency",
shortLabel = "Fast",
description =
"Tap capture, the shortest supported silence window, a persistent " +
"session, and a fast visual handoff for long work.",
localSettings = VoicePresetLocalSettings(
interactionMode = "tap",
silenceThresholdMs = 750L,
realtimeTraceDetails = false,
realtimePersistentSession = true,
),
bargeInUpdate = VoicePresetBargeInUpdate(enabled = false),
promotionUpdate = VoicePresetPromotionUpdate(
enabled = true,
promoteAfterMs = 2500,
backgroundDefaultMode = "promote",
spokenHandoff = false,
progressSpokenAfterMs = 0,
resultDelivery = "speak_when_idle",
),
),
CarefulTools(
displayName = "Careful tools",
shortLabel = "Careful",
description =
"Hold-to-talk, uninterrupted foreground tool runs, a detailed trace, and exact result delivery.",
localSettings = VoicePresetLocalSettings(
interactionMode = "hold",
silenceThresholdMs = 1750L,
realtimeTraceDetails = true,
realtimePersistentSession = true,
),
bargeInUpdate = VoicePresetBargeInUpdate(enabled = false),
promotionUpdate = VoicePresetPromotionUpdate(
enabled = false,
backgroundDefaultMode = "foreground",
spokenHandoff = false,
progressSpokenAfterMs = 0,
resultDelivery = "speak_verbatim",
),
),
QuietVisualOnly(
displayName = "Quiet / visual-only",
shortLabel = "Quiet",
description =
"Manual capture with visual long-task handoffs and results. Normal short voice replies still speak.",
localSettings = VoicePresetLocalSettings(
interactionMode = "tap",
silenceThresholdMs = 1250L,
realtimeTraceDetails = true,
realtimePersistentSession = true,
),
bargeInUpdate = VoicePresetBargeInUpdate(enabled = false),
promotionUpdate = VoicePresetPromotionUpdate(
enabled = true,
promoteAfterMs = 6000,
backgroundDefaultMode = "promote",
spokenHandoff = false,
progressSpokenAfterMs = 0,
resultDelivery = "visual_only",
),
);
/** Apply only fields owned by this preset; every other value is preserved. */
fun applyTo(current: VoiceModePresetState): VoiceModePresetState =
current.copy(
voiceSettings = current.voiceSettings.copy(
interactionMode = localSettings.interactionMode,
silenceThresholdMs = localSettings.silenceThresholdMs,
realtimeTraceDetails = localSettings.realtimeTraceDetails,
realtimePersistentSession = localSettings.realtimePersistentSession,
),
bargeInPreferences = current.bargeInPreferences.copy(
enabled = bargeInUpdate.enabled ?: current.bargeInPreferences.enabled,
sensitivity =
bargeInUpdate.sensitivity ?: current.bargeInPreferences.sensitivity,
resumeAfterInterruption = bargeInUpdate.resumeAfterInterruption
?: current.bargeInPreferences.resumeAfterInterruption,
),
promotion = current.promotion?.let(promotionUpdate::applyTo),
)
/** A preset is active only when every field it owns still matches. */
fun matches(current: VoiceModePresetState): Boolean =
current.promotion != null && applyTo(current) == current
}
/** Snapshot used by the pure preset reducer and active-preset detector. */
data class VoiceModePresetState(
val voiceSettings: VoiceSettings,
val bargeInPreferences: BargeInPreferences,
val promotion: VoicePresetPromotionSettings?,
)
/** Relay promotion values mirrored without introducing a data -> network dependency. */
data class VoicePresetPromotionSettings(
val enabled: Boolean = true,
val promoteAfterMs: Int = 6000,
val backgroundDefaultMode: String = "promote",
val spokenHandoff: Boolean = true,
val progressSpokenAfterMs: Int = 0,
val progressRepeatMs: Int = 90000,
val resultDelivery: String = "speak_verbatim",
val maxBackgroundRuns: Int = 1,
)
/** Nullable fields map directly to RelayVoiceClient's partial PATCH contract. */
data class VoicePresetPromotionUpdate(
val enabled: Boolean? = null,
val promoteAfterMs: Int? = null,
val backgroundDefaultMode: String? = null,
val spokenHandoff: Boolean? = null,
val progressSpokenAfterMs: Int? = null,
val progressRepeatMs: Int? = null,
val resultDelivery: String? = null,
val maxBackgroundRuns: Int? = null,
) {
internal fun applyTo(current: VoicePresetPromotionSettings): VoicePresetPromotionSettings =
current.copy(
enabled = enabled ?: current.enabled,
promoteAfterMs = promoteAfterMs ?: current.promoteAfterMs,
backgroundDefaultMode = backgroundDefaultMode ?: current.backgroundDefaultMode,
spokenHandoff = spokenHandoff ?: current.spokenHandoff,
progressSpokenAfterMs = progressSpokenAfterMs ?: current.progressSpokenAfterMs,
progressRepeatMs = progressRepeatMs ?: current.progressRepeatMs,
resultDelivery = resultDelivery ?: current.resultDelivery,
maxBackgroundRuns = maxBackgroundRuns ?: current.maxBackgroundRuns,
)
}
internal data class VoicePresetLocalSettings(
val interactionMode: String,
val silenceThresholdMs: Long,
val realtimeTraceDetails: Boolean,
val realtimePersistentSession: Boolean,
)
internal data class VoicePresetBargeInUpdate(
val enabled: Boolean? = null,
val sensitivity: BargeInSensitivity? = null,
val resumeAfterInterruption: Boolean? = null,
)
/** Null means the current manual values are Custom. */
fun detectVoiceModePreset(current: VoiceModePresetState): VoiceModePreset? =
VoiceModePreset.entries.firstOrNull { it.matches(current) }
@@ -19,19 +19,31 @@ import kotlinx.coroutines.flow.distinctUntilChanged
*
* - [interactionMode] how the mic button behaves: "tap" | "hold" | "continuous".
* Drives the VoiceViewModel's InteractionMode enum at startup.
* - [silenceThresholdMs] auto-stop threshold for listening: after this many
* ms of amplitude below the silence floor, stopListening() is called.
* - [autoTts] future — read TTS on every non-voice assistant message.
* - [language] STT language hint. Stored; not yet wired to /voice/transcribe
* (V1 doesn't accept a language param).
* - [silenceThresholdMs] end-of-speech threshold for listening: after this many
* ms of amplitude below the silence floor (once speech has been heard),
* stopListening() is called. Default 1250 ms matches hermes-desktop
* voice_mode `silenceMs`. (Idle/no-speech 12 s and a 60 s hard turn cap are
* fixed in VoiceViewModel, not user-tunable — see startSilenceWatchdog.)
*
* Note: the standard path has no client-side auto-TTS or STT-language pref.
* hermes-desktop only speaks responses during an active voice conversation
* (no "read every typed message"), and STT language is a server-side
* `stt.*.language` config edited via the Server voice config card, not a
* client param — so neither is faked here.
*/
data class VoiceSettings(
val engineMode: String = VoiceEngineMode.HermesVoiceOutput.storageValue,
val audioRoute: String = VoiceAudioRoute.Auto.storageValue,
val interactionMode: String = "tap",
val silenceThresholdMs: Long = 3000L,
val autoTts: Boolean = false,
val language: String = "",
val silenceThresholdMs: Long = 1250L,
/**
* When true, voice keeps progress visual and waits for the settled Hermes
* answer before speaking. Tool status, service updates, and intermediate
* assistant commentary are not narrated.
*/
val finalAnswerOnly: Boolean = false,
/** Presentation only; changing this never restarts or interrupts voice. */
val presentationMode: String = VoicePresentationMode.Focus.storageValue,
val realtimeTraceDetails: Boolean = false,
/**
* When true (default), Realtime Agent keeps one provider session/socket open
@@ -40,6 +52,9 @@ data class VoiceSettings(
* docs/plans/2026-05-24-realtime-persistent-session.md.
*/
val realtimePersistentSession: Boolean = true,
/** Per-profile Realtime Agent session overrides; blank uses relay config. */
val realtimeModel: String = "",
val realtimeVoice: String = "",
/**
* Enhanced-voice overrides for the relay TTS path, mapped onto the active
* provider (Gemini / xAI). Empty string / false means "use the server's
@@ -115,6 +130,16 @@ enum class VoiceAudioRoute(val storageValue: String) {
}
}
enum class VoicePresentationMode(val storageValue: String) {
Focus("focus"),
Conversation("conversation");
companion object {
fun fromStorage(value: String?): VoicePresentationMode =
values().firstOrNull { it.storageValue == value } ?: Focus
}
}
/**
* Active scope for per-profile voice prefs.
*
@@ -150,9 +175,9 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
// over the hard default — see [scopedName] / [resolveString].
//
// Why these are per-profile: engine mode, audio route, and the
// enhanced-voice overrides describe *which voice the agent speaks
// with*, which is a property of the profile (the relay already
// persists `voice_output:`/`realtime_voice:` per profile and
// enhanced-voice and realtime-session overrides describe *which voice
// the agent speaks with*, which is a property of the profile (the relay
// already persists `voice_output:`/`realtime_voice:` per profile and
// `RelayVoiceClient` already sends `?profile=`). Keeping them global
// leaked one profile's voice onto every other profile.
private const val KEY_ENGINE_MODE = "voice_engine_mode"
@@ -162,20 +187,21 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
private const val KEY_ENH_AUDIO_TAGS = "voice_enh_audio_tags"
private const val KEY_ENH_PERSONA = "voice_enh_persona"
private const val KEY_ENH_LANGUAGE = "voice_enh_language"
private const val KEY_REALTIME_MODEL = "voice_realtime_model"
private const val KEY_REALTIME_VOICE = "voice_realtime_voice"
// --- Global keys (shared across profiles; never namespaced) ----------
// Why these stay global: interaction-mode and silence-threshold are
// ergonomic input preferences about *how the user drives the mic*, not
// about the agent's voice — a user wants the same tap/hold/continuous
// habit regardless of which profile is active. auto-tts and the STT
// language hint are dead/experimental controls today, and the two
// realtime diagnostic toggles (trace details, persistent session) are
// habit regardless of which profile is active. The two realtime
// diagnostic toggles (trace details, persistent session) are
// engine-behaviour switches that aren't profile-specific. Keeping them
// un-namespaced means switching profiles never churns these.
private val KEY_INTERACTION_MODE = stringPreferencesKey("voice_interaction_mode")
private val KEY_SILENCE_THRESHOLD_MS = longPreferencesKey("voice_silence_threshold_ms")
private val KEY_AUTO_TTS = booleanPreferencesKey("voice_auto_tts")
private val KEY_LANGUAGE = stringPreferencesKey("voice_language")
private val KEY_FINAL_ANSWER_ONLY = booleanPreferencesKey("voice_final_answer_only")
private val KEY_PRESENTATION_MODE = stringPreferencesKey("voice_presentation_mode")
private val KEY_REALTIME_TRACE_DETAILS = booleanPreferencesKey("voice_realtime_trace_details")
private val KEY_REALTIME_PERSISTENT_SESSION =
booleanPreferencesKey("voice_realtime_persistent_session")
@@ -183,9 +209,10 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
const val DEFAULT_ENGINE_MODE = "hermes_voice_output"
const val DEFAULT_AUDIO_ROUTE = "auto"
const val DEFAULT_INTERACTION_MODE = "tap"
const val DEFAULT_SILENCE_THRESHOLD_MS = 3000L
const val DEFAULT_AUTO_TTS = false
const val DEFAULT_LANGUAGE = ""
// 1250 ms matches hermes-desktop voice_mode `silenceMs` end-of-speech.
const val DEFAULT_SILENCE_THRESHOLD_MS = 1250L
const val DEFAULT_FINAL_ANSWER_ONLY = false
const val DEFAULT_PRESENTATION_MODE = "focus"
const val DEFAULT_REALTIME_TRACE_DETAILS = false
const val DEFAULT_REALTIME_PERSISTENT_SESSION = true
@@ -214,8 +241,8 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
/**
* Point the repository at a (connection, profile) scope. Per-profile reads
* and writes (engine/route/enhanced) re-target the namespaced keys for that
* profile; global prefs are unaffected. Passing a null/blank profile name
* and writes (engine/route/enhanced/realtime) re-target the namespaced keys
* for that profile; global prefs are unaffected. Passing a null/blank profile name
* reverts per-profile reads/writes to the global base layer (the default
* profile). Idempotent — a no-op when the normalized scope is unchanged.
*/
@@ -248,11 +275,15 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
enhancedAudioTags = resolveBoolean(prefs, KEY_ENH_AUDIO_TAGS, scope, false),
enhancedPersona = resolveString(prefs, KEY_ENH_PERSONA, scope, ""),
enhancedLanguage = resolveString(prefs, KEY_ENH_LANGUAGE, scope, ""),
realtimeModel = resolveString(prefs, KEY_REALTIME_MODEL, scope, ""),
realtimeVoice = resolveString(prefs, KEY_REALTIME_VOICE, scope, ""),
// --- global (shared across profiles) ---
interactionMode = prefs[KEY_INTERACTION_MODE] ?: DEFAULT_INTERACTION_MODE,
silenceThresholdMs = prefs[KEY_SILENCE_THRESHOLD_MS] ?: DEFAULT_SILENCE_THRESHOLD_MS,
autoTts = prefs[KEY_AUTO_TTS] ?: DEFAULT_AUTO_TTS,
language = prefs[KEY_LANGUAGE] ?: DEFAULT_LANGUAGE,
finalAnswerOnly = prefs[KEY_FINAL_ANSWER_ONLY] ?: DEFAULT_FINAL_ANSWER_ONLY,
presentationMode = VoicePresentationMode.fromStorage(
prefs[KEY_PRESENTATION_MODE] ?: DEFAULT_PRESENTATION_MODE,
).storageValue,
realtimeTraceDetails = prefs[KEY_REALTIME_TRACE_DETAILS]
?: DEFAULT_REALTIME_TRACE_DETAILS,
realtimePersistentSession = prefs[KEY_REALTIME_PERSISTENT_SESSION]
@@ -329,6 +360,29 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
dataStore.edit { it[key] = language.trim() }
}
/** "" clears the override so new sessions use the relay's saved model. */
suspend fun setRealtimeModel(model: String) {
val key = stringPreferencesKey(scopedName(KEY_REALTIME_MODEL, _scope.value))
dataStore.edit { it[key] = model.trim() }
}
/** "" clears the override so new sessions use the relay's saved voice. */
suspend fun setRealtimeVoice(voice: String) {
val key = stringPreferencesKey(scopedName(KEY_REALTIME_VOICE, _scope.value))
dataStore.edit { it[key] = voice.trim() }
}
/** Persist a compatible model/voice pair without exposing a half-updated snapshot. */
suspend fun setRealtimeSelection(model: String, voice: String) {
val scope = _scope.value
val modelKey = stringPreferencesKey(scopedName(KEY_REALTIME_MODEL, scope))
val voiceKey = stringPreferencesKey(scopedName(KEY_REALTIME_VOICE, scope))
dataStore.edit {
it[modelKey] = model.trim()
it[voiceKey] = voice.trim()
}
}
// --- global setters (always the un-namespaced key) -----------------------
suspend fun setInteractionMode(mode: String) {
@@ -339,12 +393,12 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
dataStore.edit { it[KEY_SILENCE_THRESHOLD_MS] = ms.coerceAtLeast(500L) }
}
suspend fun setAutoTts(enabled: Boolean) {
dataStore.edit { it[KEY_AUTO_TTS] = enabled }
suspend fun setFinalAnswerOnly(enabled: Boolean) {
dataStore.edit { it[KEY_FINAL_ANSWER_ONLY] = enabled }
}
suspend fun setLanguage(language: String) {
dataStore.edit { it[KEY_LANGUAGE] = language }
suspend fun setPresentationMode(mode: VoicePresentationMode) {
dataStore.edit { it[KEY_PRESENTATION_MODE] = mode.storageValue }
}
suspend fun setRealtimeTraceDetails(enabled: Boolean) {
@@ -354,4 +408,31 @@ class VoicePreferencesRepository(private val dataStore: DataStore<Preferences>)
suspend fun setRealtimePersistentSession(enabled: Boolean) {
dataStore.edit { it[KEY_REALTIME_PERSISTENT_SESSION] = enabled }
}
/**
* Atomically apply the phone-side portion of [preset]. Only fields owned by
* the preset are written, so route/provider/model/voice overrides and other
* preferences remain untouched. Barge-in shares this DataStore and is
* updated in the same transaction so observers never see a half-applied
* local preset.
*/
suspend fun applyModePreset(preset: VoiceModePreset) {
val local = preset.localSettings
val bargeIn = preset.bargeInUpdate
dataStore.edit { prefs ->
prefs[KEY_INTERACTION_MODE] = local.interactionMode
prefs[KEY_SILENCE_THRESHOLD_MS] = local.silenceThresholdMs.coerceAtLeast(500L)
prefs[KEY_REALTIME_TRACE_DETAILS] = local.realtimeTraceDetails
prefs[KEY_REALTIME_PERSISTENT_SESSION] = local.realtimePersistentSession
bargeIn.enabled?.let {
prefs[BargeInPreferencesRepository.KEY_ENABLED] = it
}
bargeIn.sensitivity?.let {
prefs[BargeInPreferencesRepository.KEY_SENSITIVITY] = it.name
}
bargeIn.resumeAfterInterruption?.let {
prefs[BargeInPreferencesRepository.KEY_RESUME_AFTER_INTERRUPTION] = it
}
}
}
}
@@ -28,12 +28,50 @@ data class DiagnosticLogEntry(
val endpointRole: String? = null,
val url: String? = null,
val elapsedMs: Long? = null,
/**
* Full (multi-KB) redacted stacktrace for the detail page. Kept OUT of the
* 180-char [detail] truncation — the list still shows the short title/detail,
* the detail view shows this. Null for non-error / manually-recorded entries.
*/
val stacktrace: String? = null,
)
/**
* Current health of a single subsystem on the Diagnostics status timeline.
*
* Distinct from [DiagnosticSeverity], which classifies a *logged event* after
* the fact. A [CheckStatus] is the *live* state of a subsystem, derived
* read-only from connection state + the recent [DiagnosticsLog]. [Unknown] is
* a first-class, honest state — "not checked / not applicable" — never an
* implied pass or fail.
*/
enum class CheckStatus { Pass, Warn, Fail, Unknown }
/**
* One row on the Diagnostics status timeline: a named subsystem check with its
* current [status] and, when not [CheckStatus.Pass], a human [reason] — the
* whole point of the screen is answering "why is this failing?".
*
* [category] links the check back to a [DiagnosticCategory]; when [timestampMs]
* is non-null the reason came from a concrete [DiagnosticLogEntry], so the row
* is tappable and the UI can open that entry's full detail.
*/
data class StatusCheck(
val name: String,
val status: CheckStatus,
val reason: String? = null,
val category: DiagnosticCategory? = null,
val timestampMs: Long? = null,
val durationMs: Long? = null,
)
object DiagnosticsLog {
private const val MAX_ENTRIES = 200
private const val MAX_TEXT_LENGTH = 180
/** Cap for the full stacktrace kept on an error entry — a few KB is plenty. */
private const val MAX_TRACE_LENGTH = 8000
private val lock = Any()
private val _entries = MutableStateFlow<List<DiagnosticLogEntry>>(emptyList())
val entries: StateFlow<List<DiagnosticLogEntry>> = _entries.asStateFlow()
@@ -46,6 +84,7 @@ object DiagnosticsLog {
endpointRole: String? = null,
url: String? = null,
elapsedMs: Long? = null,
stacktrace: String? = null,
) {
val entry = DiagnosticLogEntry(
timestampMs = System.currentTimeMillis(),
@@ -56,12 +95,51 @@ object DiagnosticsLog {
endpointRole = clean(endpointRole),
url = sanitizeUrl(url),
elapsedMs = elapsedMs,
stacktrace = redactTrace(stacktrace),
)
synchronized(lock) {
_entries.value = (_entries.value + entry).takeLast(MAX_ENTRIES)
}
}
/**
* Record an [DiagnosticSeverity.Error] entry from a classified failure. The
* list keeps showing the clean [title] (+ short [detail]); the detail page
* shows the full redacted stacktrace.
*
* Called centrally from [com.hermesandroid.relay.util.classifyError] as a
* side effect, so every classified error lands here with no per-call-site
* churn. The flow is one-way (classify -> record); nothing here re-enters
* the classifier, so there is no recursion.
*
* @param title clean, human title (e.g. [com.hermesandroid.relay.util.HumanError.title]).
* @param detail short one-line summary shown in the list row (truncated to 180).
* @param throwable source error — its stacktrace is captured, redacted, and capped.
*/
fun recordError(
category: DiagnosticCategory,
title: String,
detail: String? = null,
throwable: Throwable? = null,
endpointRole: String? = null,
url: String? = null,
elapsedMs: Long? = null,
) {
record(
category = category,
severity = DiagnosticSeverity.Error,
title = title,
detail = detail ?: throwable?.message,
endpointRole = endpointRole,
url = url,
elapsedMs = elapsedMs,
stacktrace = throwable?.let { stackTraceText(it) },
)
}
private fun stackTraceText(t: Throwable): String =
java.io.StringWriter().also { t.printStackTrace(java.io.PrintWriter(it)) }.toString().trim()
fun recent(
categories: Set<DiagnosticCategory>? = null,
limit: Int = 30,
@@ -99,12 +177,36 @@ object DiagnosticsLog {
return noUserInfo.take(MAX_TEXT_LENGTH)
}
/**
* Public secret redaction for user-composed report text (e.g. the "what
* were you expecting?" answer embedded in a GitHub issue body). Same
* redaction + cap as the stored stacktraces — entry fields are already
* sanitized at record time; this covers text added after the fact.
*/
fun redactReportText(value: String?): String? = redactTrace(value)
private fun clean(value: String?): String? {
val trimmed = value?.trim()?.takeIf { it.isNotBlank() } ?: return null
return trimmed
.replace(Regex("""(?i)(bearer|token|api[_-]?key|session[_-]?token)\s*[:=]\s*\S+""")) {
"${it.groupValues[1]}=[hidden]"
}
.take(MAX_TEXT_LENGTH)
return redact(trimmed).take(MAX_TEXT_LENGTH)
}
/**
* Same secret redaction as [clean] but WITHOUT the 180-char list truncation —
* for the full stacktrace shown on the detail page. Still capped at
* [MAX_TRACE_LENGTH] so a runaway trace can't bloat the ring.
*/
private fun redactTrace(value: String?): String? {
val trimmed = value?.trim()?.takeIf { it.isNotBlank() } ?: return null
val redacted = redact(trimmed)
return if (redacted.length > MAX_TRACE_LENGTH) {
redacted.take(MAX_TRACE_LENGTH) + "\n… (truncated)"
} else {
redacted
}
}
private fun redact(value: String): String =
value.replace(Regex("""(?i)(bearer|token|api[_-]?key|session[_-]?token)\s*[:=]\s*\S+""")) {
"${it.groupValues[1]}=[hidden]"
}
}

Some files were not shown because too many files have changed in this diff Show More