Zero-Assist is an open-source Android platform for building, running, and managing autonomous AI agents only using your phone . Connect cloud or local models, install tools and skills, schedule jobs, manage memory, execute actions, and deploy agents through channels, APIs, and IoT integrations — all from a native Android device.
Zero-Assist just got a major upgrade.
What if instead of one AI assistant, you had an entire team of AI specialists working together?
That’s exactly what I’ve built.
Zero-Assist now supports multiple specialized agents, each optimized for a specific role and workflow.
The brain of the operation.
Your personal information hunter.
Built for developers.
Turns chaos into clarity.
The most exciting feature in this update.
You can now create your own specialized AI agents with just a few clicks.
Customize:
Want an AI Startup Advisor?
Create one.
Want a Bug-Hunting Expert?
Create one.
Want a Cybersecurity Specialist?
Create one.
The possibilities are endless.
Most AI applications rely on a single model trying to do everything.
Zero-Assist takes a different approach.
Instead of one assistant, you get an entire ecosystem of AI specialists that can collaborate, delegate tasks, and work together to solve problems more efficiently.
Each agent has:
This creates a more scalable and intelligent workflow compared to traditional AI assistants.
The long-term goal isn’t just to build another chatbot.
It’s to build an AI Operating System where users can create, orchestrate, and manage teams of intelligent agents that work together to accomplish complex tasks.
And this is only the beginning.
Screenshot attached below.
#Devlog 6 -Zero-Assist
Shipped a big update today. The app can now handle complex tasks much more reliably, and tools run in parallel instead of sequentially — so heavy workloads finish noticeably faster without the app choking midway.
The smarter behavior actually came from Trimming down the soul.md, longterm-memory.md, agents.md, and user.md files reduced token usage significantly, and the model started reasoning better almost immediately. I tested it across several complex tasks and the output quality genuinely caught me off guard — results I didn’t expected!!!
Voice has been a pain point for a while. Dug into the Piper latency issues, restructured the integration, and the pipeline is much smoother now. Still sounds robotic — that’s a problem I haven’t cracked yet — but the lag that made it frustrating to use is mostly gone.
Overall the app feels like a different version of itself. More capable, leaner, and faster. Dropping Demo vid of the test runs below so you can see what it’s actually doing now. here is demo video too :https://youtube.com/shorts/F8sLD21dcWo
Today I spent most of my time working on one of the biggest features of the project so far: Channel Integration.
The channels system already supports multiple platforms such as Telegram, WhatsApp, Slack, Discord, and several others. My goal was to connect these channels with the assistant so that it can interact with users across different platforms while still having access to the tools and capabilities available on the phone.
To achieve this, I worked on properly connecting the Rust bridge with the Kotlin application. Once the communication layer was working correctly, I was able to expose several powerful capabilities to the assistant, including:
This was a fairly complex task because multiple systems needed to communicate reliably. I also used AI assistance throughout the development process to help debug issues, validate approaches, and speed up implementation. In total, this work took roughly 12 hours.
At the moment, I have not pushed the code to the repository because the feature still requires extensive testing. Since it touches storage access, tool execution, and communication across multiple services, I want to ensure everything is stable before making it public. Once I complete the testing phase, I will push the implementation to the repository.
This feature significantly expands what the application can do. Instead of being just a chatbot, it is evolving into a full assistant platform capable of interacting with external services, managing files, controlling parts of the device, and communicating through multiple messaging platforms. The long-term vision is to create a system where users can build highly capable personal assistants that can perform real tasks rather than simply generate text.
There is still a lot more work ahead, but today’s progress was a major step toward that goal. Stay tuned—some very exciting features are currently in development.
Zero-Assist Devlog #4 — The Phone Is Now a Personal Chat Server
so Devlog 4 is here.
The main thing i fixed this time is the channels section of the app. channels are basically how Zero-Assist can gets input or give output to other app — like Telegram, WhatsApp, and other messaging apps. once you connect them, the app starts listening.
but whats different now that channels are working, the phone isn’t just an AI assistant anymore. it’s your personal home server that you can message like a real in-person.
what this actually means in practice:
say you’re away and you message your own Telegram bot: “water the plants” — Zero-Assist picks that up, figures out what you mean, and either goes with an MQTT signal to your smart home setup or directly talks to your microcontroller over USB or BLE , whichever is available. no extra apps, no cloud, just your phone doing the work.
same idea works for your homelab. you can message “ping my website” and the app will run the actual shell command on your phone and report back. this does need a one-time manual connection to set up, but after that it just works.
basically the phone becomes a chat-controlled home automation that you own fully here is no cloud included except the llm , which you can also use the local llm .
what i’m planning to add next:
i’m planning a live dashboard screen for this — not raw logs, but a simplified readable feed. something like:
“message received via Telegram → running plant watering command → sent MQTT signal ✓”
the idea is it’s useful for people who like seeing what’s happening here, but written in plain language instead of technical stuff for the normal users .
the hard part this time was :
most of the time on this devlog went into connecting the Rust backend (which handles all the channel logic) to the Kotlin front-end of the app , so getting them to work together cleanly took a lot of debugging and was honestly the most frustrating part of this whole update. got it working though.
more soon.
devlog -3
added a new shared folder option int the app so that the app can share the storage from phone , it can open files edit files , manipulate the files and do lots of stuff with it , added the screenshot below
Devlog #2 is here!!
so after the piper TTS update in devlog #1, I’ve been working on something
way bigger — I added Composio integration to Zero-Assist
for those who don’t know what composio is — it’s basically a platform that
connects AI agents to over 1,000 apps like Gmail, Slack, GitHub, Notion,
Salesforce, Google Drive and a lot more. think of it as the bridge between
your AI and the rest of the internet.
so now Zero-Assist can actually do things for you like —
→ send and read messages (if you give it the right permissions)
→ make notes in Notion automatically
→ send mails on your behalf
→ store your files to Google Drive
→ and a lot more depending on which apps you connect
the best part is this feature was already there inside ZeroClaw (which is
what Zero-Assist is built on), so it wasn’t built from scratch — it was
more about bringing it properly into the Android app and making it actually
usable.
check out the video (https://drive.google.com/file/d/1ZO56Ekrq7fu205Epqx8fH-Vkt_E5xc16/view?usp=sharing) for a small demo of how it works
ZERO-ASSIST devlog 1
IM working on Zero-Assist voice assistant app on which im already working from March , the app has lots of features , i completely vibe coded the app but now im working on the finishing part of the app so today i improve the voice assist mode , the voice was really slow on cheaper Android phones. When you spoke to it, you’d wait 10+ seconds before hearing the voice response.
What I fixed today
1️⃣ Made It Stop Waiting So Long
Before: App waited up to 2.5-5 seconds to make sure the TTS Engine was ready
Now: Only waits 0.9-1.8 seconds
Result: Faster feedback !!
You can also check the app here (https://github.com/Tanmay-1122/Zero-Assist)
