I've been building Kryzz AI on weekends and evenings for a few months. It's an open-source Android app for chatting with AI models, talking to them by voice, and letting an agent do small multi-step jobs. It's MIT-licensed and the code is on GitHub.
This post is about one design choice that ended up shaping most of the app: the agent has to show you what it's going to do while it does it.
When I tried agent features in other apps, the thing that bothered me most wasn't bad answers. It was not knowing what happened. Did it actually open that page? Did it make up the source? Did it just spend a dollar of my API credit on a loop?
On a phone that feels worse, because you're usually half paying attention. So I wanted the agent to be boring and visible instead of clever and hidden.
Chats stay on the device. You bring your own API key for whichever provider you use, and there's no telemetry. I can't promise "nothing ever leaves the phone" because the model call itself goes to your provider, but nothing goes to me.
Kotlin and Jetpack Compose. The file outputs share one Markdown model that gets rendered into DOCX, XLSX or PDF, which kept the export code a lot smaller than I expected.
It's still early. The release is a debug APK, so expect rough edges.
Short demo:
If you've built agent features yourself, I'd like to hear how you handle the "what is it doing right now" problem. Issues and PRs on GitHub are welcome.