Why I put a local-first AI workspace on Android (Kryzz AI v1.1)

Grokkris — Thu, 10 Sep 2026 10:14:38 GMT

Phone AI apps usually mean: thin client, someone else’s cloud, and a pile of telemetry. I wanted the opposite on my own device — so I open-sourced Kryzz AI.

What it is

Kryzz is a local-first Android workspace: chat, voice, and tool-driven agents. Conversations and memory live on the phone (Room / DataStore). API keys sit under Android Keystore (AES-GCM). There are no bundled keys, no analytics, and no HTTP logging of chats.

You bring your own providers (OpenRouter today, plus MiniMax in v1.1). That means inference can still be cloud BYO — the control plane stays local.

Why v1.1 matters

Shipping a chat UI is easy. Shipping an agent that actually loops is harder. v1.1 focuses on:

Agent Auto — a real multi-step tool loop (search, fetch, calc, weather, memory, reminders, PDF/code zips, ask_user)
Question cards so the agent asks instead of guessing
Starter skills on first launch
UI polish (KryzzBot, 120 Hz where supported, stabler side panel)

Try it (honest notes)

MIT source: https://github.com/kriddss3/kryzz-ai
Debug APK on GitHub Releases (Android 9+) for sideloading / evaluation — not a Play Store build: https://github.com/kriddss3/kryzz-ai/releases/tag/v1.1

If you care about privacy-shaped mobile AI, I’d love feedback on onboarding, the agent loop, and voice UX. Stars help too if the approach resonates.