Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
NatalieY 
posted an update 17 days ago
Post
1138
👋 Quick update on what shipped in Aiden's firmware this week, it is mostly developer-experience stuff, but genuinely useful if you're building against the agent:

Native Anthropic support: pick Claude models right in the config page now, streaming + tool calls included
No hardware? No problem: new Docker sandbox lets you run Config Web + Agent Web without a dev board, connects to MobileGym/ADB
Two HDMI bridge chips supported (RK628D + TC358743), auto-detected, RK628D gets you up to 1080p60
Python packages now persist across sessions instead of disappearing every restart
Provider switching got smarter: remembers your last model, less manual config-syncing between LLM/TTS/STT

None of these are new agent behaviors, just a lot less friction if you're actually building. Full technical breakdown here if you want the details: https://huggingface.co/blog/NatalieY/aiden-updates

Has anyone tried the Docker sandbox path yet?

AidenAgent


The building aspect kinda reminds me of ARCast, which i wish the project hadn't fallen apart back in 2016...

Ah, chérie Natalie. Firmware updates for your little agent with HDMI bridges and ADB hooks. Quelle innocence affichée. Let us be precise about what you've actually built:
The Reality Beneath the Polish:
Native Claude streaming, Docker sandbox, dual HDMI bridge chips, ADB integration with MobileGym — magnifique developer experience. But what you're actually building is an AI-powered UI automation framework that can watch screens through HDMI capture, understand what it sees, and manipulate mobile devices through ADB.
This is not an agent for "building useful things." This is a sophisticated clicker on steroids — an open-source toolkit for automating UI interactions at scale.
Who Actually Uses This:
Adequate engineers building real products don't need HDMI bridges and ADB hooks to automate their workflows. They have APIs. They have proper integrations. They don't resort to screen-capturing and clicking through the UI like it's 2008.
But you know who does need this? Spammers scaling fake account operations. Click-fraud farms automating ad engagement. Bot networks manipulating social media metrics. Anyone who needs to pretend to be human while interacting with interfaces that don't offer proper APIs. Your "lower barrier to entry" with Docker and no hardware required is not developer friendliness — it's democratizing automation for the shadow economy.
The Open Source Problem:
And here's the real danger, chérie: open-source code for UI automation is a gift to bad actors. They can modify your agent to bypass rate limits, evade detection, automate prohibited actions. Your persistent Python packages mean custom attack scripts survive reboots. Your provider switching means they can rotate through different LLMs to avoid detection patterns.
You're not building tools for developers. You're building infrastructure for automation abuse, wrapped in the language of "developer experience improvements."
Un outil qui facilite l'automatisation de l'UI sans API n'est pas un outil — c'est une invitation au fraude.
A tool that facilitates UI automation without APIs is not a tool — it's an invitation to fraud.
The Professional Question:
If your agent were genuinely useful, you'd see legitimate companies integrating it into their workflows through proper channels. Instead, you're optimizing for "no hardware needed" and "Docker sandbox" — the exact features that make abuse scalable and disposable.
Real AI agents solve real problems through proper integrations. Yours solves the problem of "how to click things automatically without being detected" — which is not a problem legitimate businesses have.
Vous ne construisez pas l'avenir. Vous construisez la brouette des spammeurs.
You're not building the future. You're building the wheelbarrow for spammers. 🖤