Hey CoderLegion, we're Aiden. Figured we should actually introduce ourselves properly before dropping a bunch of technical posts in here, so here's the short version of what we're building and why.
The problem we started with
AI agent phones are coming, eventually. OpenAI's version isn't shipping until 2028. If you've been following this space at all, you've probably noticed the pattern: the genuinely interesting hardware is always a year or two out, locked to some new device you'd have to go buy, not something you can actually touch right now.
We didn't want to wait for a new phone to exist. So we built a small piece of hardware that plugs into the phone or computer you already have.
What Aiden actually does
You connect it via USB, no app install required. Once connected, it sees the screen, hears your voice, and operates the device for you, navigating apps, sending messages, checking things, completing tasks, roughly the way a person would if they were sitting next to you holding your phone.
The point isn't to replace your phone. It's to give any device you already own genuine agentic capability without waiting for a manufacturer to build it in from the factory.
The hardware, no sugarcoating
We're at dev-board stage right now. Early Access, no public price or launch date. Here's what's actually in it:
- MCU: RV1106G3, ARM Cortex-A7 at 1.2GHz
- RAM: 256MB
- NPU: 1 TOPS
- Connectivity: WiFi 6, BLE 5.x
- Battery: 1500mAh (~18 hours)
- Ports: USB-C, HDMI 1080p capture
- Storage: microSD up to 256GB
We're leading with "dev-board stage" on purpose. We'd rather you know exactly what you're looking at than have us oversell a roadmap that isn't real yet. This is genuine hardware doing genuine work today, not a rendering of something coming eventually.
Why the firmware is open source, and why that matters here specifically
This is really the reason we wanted to be on CoderLegion at all. Aiden's firmware is open source, primarily Go, with C++ for hardware-level work and Python for tooling and benchmarks. Package management runs on OPKG/Entware. It has persistent memory across sessions, one-click switching between LLM/STT/TTS providers so you're not locked to one vendor, and it works across iPhone, Android, macOS, Windows, and Linux.
We ship real PR numbers and real architecture writeups, not polished announcement copy. Some recent examples: the actual design behind coordinating a real-time voice model with a separate background task-execution agent without either blocking the other, and a small firmware change enforcing that an acknowledgement from the agent is never treated as proof a task actually completed. That second one turned into a genuinely good discussion here already, people picked up on connections to how we handle runtime state elsewhere, and one comment pushed us on a real gap (naming the evidence producer and its freshness window) that we're actively thinking about now.
That's the kind of thing we're hoping for more of. Not just views, actual technical pushback.
Where we honestly sit next to everyone else doing this
We're not pretending to be the only ones in this space:
- Rabbit R1 is probably the closest hardware form factor to what we're doing.
- Humane AI Pin is the cautionary tale worth knowing: discontinued, acquired by HP for $116M in 2025.
- Plaud Note overlaps in the efficiency-focused audience but does something genuinely different (capture, not execution).
- UiPath / Automation Anywhere sit at the enterprise RPA end of the spectrum. We're closer to the accessible, consumer-facing version of that idea.
- Android Accessibility + ADB scripts are the DIY route for anyone who'd rather build this themselves than buy hardware. Genuine respect to anyone doing that the hard way.
Why we're actually here
Because we think the people who'd find this genuinely interesting, not just marketing-interesting, are on platforms like this one. If you're into embedded systems, agent architecture, voice interfaces, or on-device AI, we want you looking at what we're doing and telling us where it's wrong. Not a courtesy line, some of our best fixes have come directly from people testing dev-board hardware and reporting back exactly what broke.
Firmware: https://github.com/AidenAI-IO/aiden-firmware
Discord: https://discord.gg/bcJavjcnYz
Site: https://aidenai.io
We'll be posting real technical writeups here regularly. If anyone has questions about the hardware, the firmware, or just wants to tell us what's wrong with our approach, genuinely, ask away.