ZeroLog Mobile
Your AI. Anywhere.
A native Android app for your chats, Compute, jobs and container files. An agent works on the phone itself and asks before each action.
Android 8.0 or later · needs a sign-in
- /goal every test in ~/budget passes
- Ran pytest: 2 of 31 fail, both in parse_amount(). Fixed the comma handling.
- Check on the server: goal not met yet, test_negative_amount still fails.
- Negative values lost their sign. 31 of 31 pass.
- Goal met: pytest reports 31 passed.
What is in the app
The chat, built in
Chat, chat list, Compute, jobs and container files are drawn by the app, not by a web page inside it. The session key stays in Android's encrypted storage.
An agent on the phone
Python 3.11, a shell and app control on the device. Each action asks first unless you turn approvals off.
A folder in step with /work
Pick a folder and it syncs with your container. Files over 400 KB and binary files are left out, never cut short.
Your container in the Files app
It appears as a storage location, so any "choose a file" dialog can reach it.
/goal
Name the finish line. The model keeps going until a separate check on the server says it is reached, or that it cannot be.
Your own CLIs
Claude Code and Codex run in Termux inside a small Ubuntu, about 1 GB. You sign in to them yourself; the app never sees the code.
Install in four steps
Download the APK
On the phone, tap Download APK and sign in if asked. Chrome warns about every app from outside the Play Store; that is its standard text.
Allow installs from your browser
Settings → Apps → Special app access → Install unknown apps → Chrome → Allow. You can switch it off again afterwards.
Open the file
It installs over earlier 1.x versions and keeps settings. The old web-only ZeroLog app is separate; keep it until sign-in here works. For 2.0.0-a1, follow the signing-key migration below.
Sign in
The first start guides you. On Android 13 and later, tap the greyed-out accessibility switch once, then App info → ⋮ → Allow restricted settings.
What it does not do
It does not read your sign-ins
A command-line tool's login page opens in Chrome; the tool's own callback gets the code.
Its local bridge needs a key
Tools reach the app over 127.0.0.1 with a key that is new at every start. Other apps are turned away.
Crash reports without you
The error type and the line in the app's own code. No account, no chat, no device ID.
The file
Version
Build 2102, released 20.10.2026.
Needs Android 8.0 or later
Installs over earlier 1.x versions.
Download size
The download needs a sign-in.
- SHA-256
- 32763c602b1c0e22caf4824df01a97cc6259488b9015686ea9aac20e547e4f2f
- Signing key (SHA-256)
- b91705edac2204c9c301d383669bd5423717e41c84ee52bc44aa3e64280c8edb
- Previous version
- zerolog-1.21.7.apk
On a computer, sha256sum zerolog-2.0.0-a3.apk must print the same line.
Coming from 2.0.0-a1? This build is signed with a new key. Uninstall 2.0.0-a1 once before you install it. Later updates install over it.
Termux, migration and support
Use Termux from F-Droid or its GitHub releases, not the Play Store build. Settings → CLI sign-in shows the setup line. The app prepares a small Ubuntu; allow about 1 GB. Complete each CLI’s own sign-in in Chrome.
The package is ch.zerolog.zerocode.debug, a pre-release. The Android guide covers setup, migration and phone jobs. For help, write to info@zerolog.ch with your Android version and last step. Remove tokens and private content from log excerpts.
