OpenAlly: Local AI Assistant for Android with Phone Control
OpenAlly is a public beta Android app that runs an AI assistant entirely locally on your device. Instead of sending data to external servers like most AI apps, OpenAlly processes everything on your phone through an embedded Node.js process, with the AI gateway ported to Rust for mobile performance.
Core Architecture
The app bundles a large binary containing the OpenClaw AI gateway ported to Rust. All agent runtime, memory, session state, and skills run locally on your Android device. When you interact with the AI, only your device is involved—no internet connection required for core functionality.
Key Features
- Messaging Integration: Connects to 19+ platforms including WhatsApp, Telegram, Discord, Slack, and Signal
- 51 Built-in Skills: Notion, GitHub, Spotify, Image Generation, Coding Agent, smart lights, web search, and more
- Model Support: 18 model providers including Claude, GPT-4o, Gemini, Grok, Groq, and local LLMs—bring your own API keys with zero lock-in
- Aster Companion: Gives the AI actual phone control capabilities: calls, SMS, camera, notifications, files—all over local connections
- SMS Analyser: On-device phishing detection and spend tracking
- Flare: AI-driven notification automation with auto-reply rules, smart muting, and per-app triggers
Privacy Implementation
- API keys stored in Android hardware secure enclave
- Zero analytics and zero telemetry
- No cloud servers operated by the developers
- Encrypted Google Drive backup with end-to-end encryption on-device before upload
- Open source (MIT) for some packages
Current Limitations
This is a public beta release with expected bugs as the team stabilizes the software. The app is not plug-and-play—setup requires bringing your own API keys and takes 1-2 minutes. It's not designed for simple chatbot queries like "ask ChatGPT something quickly."
The developers are actively seeking feedback on crashes, missing features, and bugs through Reddit comments or Aster's GitHub repository.
📖 Read the full source: r/clawdbot
👀 See Also
Replacing Kafka, Redis, and RabbitMQ with NATS: A Developer's Experience
A developer replaced Kafka, Redis, and RabbitMQ with NATS in their architecture, sharing specific implementation details and lessons learned from consolidating multiple messaging systems into one tool.
Custom WhatsApp Channel Plugin for Claude Code Using Baileys
A developer built a custom channel plugin that adds WhatsApp support to Claude Code 2.1.80+ using Baileys v7, implementing the WhatsApp Web Multi-Device protocol as an MCP server with the experimental claude/channel capability.
Claude Code Prompt Architecture Reverse-Engineered for Local Models
A clean-room reimplementation of Claude Code's 26-prompt architecture is now available on GitHub, offering system prompts, tool prompts, safety rules, memory compression, and verification patterns for building coding agents on local models like Ollama, llama.cpp, or vLLM.
AI Ate the Translation Layer: The Org Chart After Agents
Ajey Gore argues AI didn't replace job titles — it ate the translation task. The middle of the org chart (engineering managers, scrum masters, tech leads) is shrinking as agents convert requirements to code directly.