Community Remote Gateway edition for Android (source + test APK)

[CristianGCiocoi]

Hi @rusty4444,

Thank you for building and publishing Hermes Android. I have published a public fork based on the latest upstream 1.0.13, focused on using the Android app with Hermes Desktop in Remote Gateway mode:

• source: https://github.com/CristianGCiocoi/hermes-android
• prerelease / ARM64 test APK: https://github.com/CristianGCiocoi/hermes-android/releases/tag/v1.0.13-hermesapk.13
• full changelog: https://github.com/CristianGCiocoi/hermes-android/blob/main/CHANGELOG.md

The edition adds a unified Desktop Gateway JSON-RPC session for text and arbitrary attachments, Copy/select text, Read aloud, Stop, Edit and resend, Regenerate, export, per-chat model and thinking effort, Search/Rename/Branch/Delete, and native handling for approvals, masked sudo/secrets, clarifications, reasoning, tool activity, notifications, background results, reviews, and subagents.

Validation currently includes 110 passing Flutter tests, a synthetic Desktop Gateway contract suite, and successful physical Android testing for Remote Gateway chat, Branch, model selection, and thinking effort.

The attached APK is deliberately marked as a debug prerelease; production signing still requires a real private keystore. The fork preserves upstream history and attribution. Because the change set is broad, I have not opened a large unsolicited PR, but I would be happy to align it with your roadmap or split useful pieces into reviewable contributions.

Thanks again for the original application.

[AI-Guru]

Big endorsement from me for this fork — I took a close look at the Remote Gateway edition today. The unified Desktop Gateway JSON-RPC transport is exactly the path the official Hermes Desktop app uses, which among other things means sessions get server-side LLM-generated titles for free (the REST /v1/chat/completions path the upstream app uses never triggers the server's auto-title hook — something we ran into ourselves). The synthetic gateway contract suite under tools/fake_gateway is a great addition too.

One heads-up from our review: the fork inherits a scroll bug from upstream PR #71. The saved scroll offset (_savedPositions in chat_screen.dart) is restored in the streaming completion handler, so once a session has been left and reopened, the chat jumps to a stale mid-history position whenever an answer finishes instead of scrolling to the bottom. I'm about to open an upstream PR with a fix — should be easy to pick up here as well.

Would love to see pieces of this land upstream. Thanks for building and documenting it so carefully.

[grunjol]

Just curious (because its a big patch and i didnt review it) do this patch removed all the /v1/* API calls? I was looking for time (and resources) to do that and move the chat part to the dashboard protocol (which the app uses for a lot of things), so if that's the case kudos fo you!

[AI-Guru]

Yes. It uses the Dashboard API calls. I have been testing the patch for a while. Works like a charm. Definitely an improvement over the other API calls.

[CristianGCiocoi]

Thanks @AI-Guru and @grunjol — I really appreciate the detailed review and independent testing.

@AI-Guru, good catch on the scroll issue inherited from PR #71. I verified that the stale _savedPositions restoration is still present in the legacy REST completion path. Remote Gateway turns do not use that completion block, but the compatibility REST mode can still reproduce the issue. I’ll follow the upstream fix and add a regression test before incorporating it into the fork.

@grunjol, the patch does not remove every /v1/* call globally. For Remote Gateway profiles, chat has been migrated: text, images, and files all use the same Dashboard WebSocket/JSON-RPC session, and /v1/chat/completions is not used on that path. The app still retains /v1/models and /v1/chat/completions for non-Desktop/legacy REST compatibility.

If the upstream direction is a complete Dashboard-only migration, I’d be happy to separate the transport work into smaller, reviewable contributions. Thanks again for taking the time to test it.