Show HN: QCCBot – 在浏览器标签页中运行的 Android 系统，由 AI 智能体控制
5 分•作者: Eastra•4 天前
八个月前，我看到一个朋友为了跨境电商业务，要管理三面墙的手机——充电、更换IP、还要时刻担心被封。
我问自己：人们真正需要的是这些手机盒子，还是里面的安卓环境？
我们为此构建了 QCCBot 来解答这个问题。它在 ARM 服务器上运行完整的安卓实例，然后将画面流式传输到浏览器。打开一个标签页，你就能获得一部手机。无需硬件，无需线缆，无需轮流给 100 台机器充电。
我们现在已经有了真正的用户——跨境电商、TikTok 运营、应用测试、远程办公。说实话，我们的用户比我们自己更早发现了这些用例。
我们接下来要构建的是：
AI 智能体，它们不仅能查看安卓环境，还能在其中操作。打开应用、执行任务、监控状态、反馈报告。日常操作无需人工干预。
我们刚刚发布的底层基础设施：
• 任务执行 API (OpenAPI)
• 脚本模板库 (~30 个模板，选择一个行为并部署)
• AgentV2 在私有部署中运行
• 基于 ADB 的智能体控制，通过 OpenClaw 集成
目前的真实局限性：
• 流媒体延迟仍在改进中
• 指纹模拟不够完美
• 完全自主操作仍在构建中
• 我们在重新设计用户界面时被高级用户吐槽了（应该的）
我们获得的“伤痕”比功能还要多。还处于早期阶段。但真实用户每天都在告诉我们哪些地方不好用——这比赞美更有价值。
试用一下：qccbot.com
很乐意深入探讨 ARM 虚拟化方法、智能体控制层或流媒体架构。也真诚地想知道，是否有正在构建 AI 智能体的人遇到了“需要一个持久的移动环境”的问题。
查看原文
Eight months ago I watched a friend manage three walls of phones for his cross-border e-commerce operation — charging, swapping IPs, constantly worrying about bans.
I asked myself: do people actually want the boxes, or just the Android environment inside?
We built QCCBot to answer that. Full Android instances running on ARM servers, streamed to a browser. Open a tab, you get a phone. No hardware, no cables, no charging 100 machines on rotation.
We have real users now — cross-border e-commerce, TikTok ops, app testing, remote work. Honestly, our users found the use cases before we did.
What we're building toward next:
AI agents that don't just view the Android environment — they operate inside it. Open apps, execute tasks, monitor state, report back. No human in the loop for routine operations.
The infrastructure piece we just shipped:
• Task execution API (OpenAPI)
• Script template store (~30 templates, pick a behavior and deploy it)
• AgentV2 running in private deployment
• ADB-based agent control via OpenClaw integration
Current honest limitations:
• Streaming latency is still a work in progress
• Fingerprint simulation isn't perfect
• Full autonomous operation is still being built out
• We got roasted by power users when we redesigned the UI (fair)
We've collected more scars than features. Still early. But real users are telling us what sucks every day — that's worth more than praise.
Try it: qccbot.com
Happy to go deep on the ARM virtualization approach, the agent control layer, or the streaming architecture. Also genuinely interested in whether anyone building AI agents has hit the "need a persistent mobile environment" problem.