Native Android chat client for ConnectOnion
agents, built with Kotlin and Jetpack Compose. Connect to an agent by its 0x…
address and talk to it — the same protocol the
web client speaks.
This is a starting point, not a finished product you are meant to use as-is.
If you are running ConnectOnion agents and your users want a native Android app rather than a browser tab, fork this, change the four things under Make it yours, and ship it. The web client is the default answer; this exists for when the default is not enough.
Type / in the composer and the agent's published skills appear as a list, each
with the description the agent gave it. The list comes from the agent itself — an
agent that publishes nothing shows an empty palette rather than a stale or
invented one.
Speak instead of typing and the transcript arrives in the text field, where you can fix a misheard word before anything is sent. A recogniser that mishears a name no longer costs you a message.
The composer stays usable while a reply is streaming, so a follow-up or a correction can be sent mid-run. The agent picks it up as part of the same turn.
This needs runtime_input on the agent, which is opt-in
(Agent(plugins=[runtime_input])). Without it the relay acknowledges the
mid-run message and queues it, and nothing drains the queue.
Failed sends are marked and can be retried, rather than disappearing into the transcript as though they had gone.
A notification arrives when a reply lands and the app is in the background.
- Multiple sessions per agent, in a drawer, renameable
- Agent discovery and invite-code onboarding
- BIP39 recovery phrase — generated the same way as the web client, so a phrase created in one restores the identical identity in the other
- Ed25519 signing via lazysodium; credentials in EncryptedSharedPreferences (AES256-GCM)
- Room-backed history: agents, sessions, messages, session state
- No tablet-specific layout — it runs on tablets, but the layout is the phone one
- Mid-run input needs the agent to opt in (see above)
- Instrumented UI tests need an attached device; CI does not run them
| Android | 8.0 (API 26) or later |
| Build | JDK 17, Android SDK with the API 36 platform |
| Android Studio | Hedgehog (2023.1.1) or newer |
| An agent | See connectonion — pip install connectonion, then co init |
git clone https://github.com/openonion/oochat-android.git
cd oochat-android
./gradlew :app:assembleDebug # build
./gradlew :app:installDebug # install on a connected device or emulator
./gradlew :app:testDebugUnitTest # unit tests
./gradlew :app:jacocoTestReport # coverageInstrumented and Compose UI tests need a device attached:
./gradlew :app:connectedDebugAndroidTestScreenshot baselines are checked with Roborazzi:
./gradlew :app:verifyRoborazziDebugThe committed baselines are stale and CI does not check them. A fixture in
SettingsScreenshotTestwas changed during the rebrand, so the baseline images no longer match what the test renders, andverifyRoborazziDebugis not run in CI. Nothing else covers this either — baselines are PNGs, and the pre-publication audit does not read images. Regenerate them with./gradlew :app:recordRoborazziDebugon a machine with the Android SDK before relying on screenshot coverage.
See INSTALL.md for a clean-machine walkthrough and USER_GUIDE.md for the app itself.
| What | Where | Default |
|---|---|---|
| Relay endpoint | In-app settings | oo.openonion.ai |
| Agent address | Added in-app by 0x… address |
— |
| # | What | Where |
|---|---|---|
| 1 | Application ID | app/build.gradle.kts — currently ai.openonion.oochat |
| 2 | Display name | app/src/main/res/values/strings.xml |
| 3 | Icon | app/src/main/res/mipmap-* |
| 4 | Relay endpoint | In-app settings, or the default in Constants.kt |
Compose UI over view models over a repository layer, with the WebSocket protocol
client underneath. ui/ renders, domain/ holds the models, data/ owns Room
and the preference stores, network/ owns the relay connection, and crypto/
owns the Ed25519 identity and BIP39 recovery.
An architecture test (ArchitectureGuardTest) enforces the layering: UI code
cannot import repository implementations, DAOs, or the WebSocket factory
directly. If you restructure, that test is where the rules are written down.
See docs/architecture.md and docs/protocol.md.
Installable debug-signed APKs are published from semantic version tags. See the release guide for the version bump, dry-run and tagging procedure, and INSTALL.md for installation and checksum verification.
Issues and pull requests are welcome at https://github.com/openonion/oochat-android.
MIT — see LICENSE.
Copyright (c) 2026 ConnectOnion PTY LTD.




