Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Rust acpagent-client-protocolai-agentsai-assistantclaudeclaude-codecodexcoding-agentscursorgeminigemini-cligrok-bot-alternativeiosiphonelinuxmacosmcpopen-sourcerustself-hosted
docs: note Android device records work on main too
leepokaiaafa5e064ef2
diff --git a/docs/plans/android-app.md b/docs/plans/android-app.mdindex 15bffec1..71c68393 100644--- a/docs/plans/android-app.md+++ b/docs/plans/android-app.md@@ -56,8 +56,8 @@ included, is connected to that computer).Every row is ported. On 2026-11-01 the owner put off the remaining checks: OpenAI until a valid key is saved,Speech mode until a phone can speak into its microphone (no sound from the Mac), the physical-device rows until-device acceptance, and the account flows on main (they were walked on dev, and main only lacks the-`0004_android_devices` migration, applied by hand after the next `dev` → `main` merge).+device acceptance, and the account flows on main (they were walked on dev; main has had the same+`0004_android_devices` migration since the 2.34.0 merge, but no Android phone has signed in against it yet).| What | Code | What it needs || --- | --- | --- |@@ -132,9 +132,9 @@ the Dynamic Island) with its feature graphic, per language.The host accepts Android pairing (older hosts refuse it, and the app asks to updateCodync on the computer) and counts Android event streams as connected phones, sopushes are held while one is open. The cloud accepts Android device records through-the `0004_android_devices.sql` migration, applied to dev on 2026-11-01. Main gets it only when it is applied there by hand-(`wrangler d1 migrations apply codync --remote` after a restore point; the merge and `deploy:main` run no migrations, [migration log](../guides/environments-and-deployment.md#migration-log)).-Until then, signed-in Android phones can't register with the production account. The push Worker needs the matching Firebase+the `0004_android_devices.sql` migration, applied by hand to dev and, right after the 2.34.0 merge, to main on 2026-11-01+(the merge and `deploy:main` run no migrations, [migration log](../guides/environments-and-deployment.md#migration-log)).+The push Worker needs the matching Firebaseservice account as an external secret; the client configuration contains no private key.