Andee Android Agent 设置与调试

安装指南

1. ClawHub CLI 从源直接安装技能的最快方式。
   npx clawhub@latest install andee-skill
2. 手动安装 将技能文件夹复制到以下位置之一
   全局模式
   ~/.openclaw/skills/
   工作区
   /skills/
   优先级：工作区 > 本地 > 内置
3. 提示词安装 将此提示词复制到 OpenClaw 即可自动安装。
   请帮我使用 Clawhub 安装 andee-skill。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。
   更倾向于下载？
   获取包含原生技能文件的ZIP压缩包。
   下载技能 (.zip)

什么是

Andee 将 Android 手机变成 AI agent 的身体：无障碍服务读取并操作屏幕，悬浮层显示 agent，而 LLM 提供智能。它以单个 APK 运行，无需 root 或自定义 ROM，目标平台为 Android 11（API 30）或更高版本。建议使用真实手机，因为该应用的大多数行为在模拟器中没有实际意义。
本 Openclaw Skills 指南帮助用户在两种方式之间进行选择：通过独立的 CodeFlying 服务免构建试用，或自行托管并克隆、构建、安装和调试 Andee。核心原则是一次只进行一个步骤，并在继续之前确认预期结果。

应用场景

使用 CodeFlying 方式，无需配置 Android 开发工具链即可在手机上试用 Andee。
克隆 Andee 仓库以检查源代码、修改代码或修复 bug。
在本地构建并安装 debug APK，然后在真实 Android 设备上验证应用。
诊断由不兼容的 JDK、缺失的 Android SDK 配置或 APK 选择错误导致的构建失败。
使用 ADB、logcat 和 Andee 设备端 WebSocket 工具端口调试设备行为。
为他人准备 APK，同时了解签名、设备凭据和隐私方面的注意事项。

工作原理

询问用户是想试用 Andee，还是要处理其源代码。试用时建议使用 CodeFlying；需要修改源代码和调试时选择自行托管。
对于 CodeFlying 方式，说明 CodeFlying 是一项拥有自身条款、定价和数据处理方式的独立服务。它可以构建并配置软件包，但生成的 APK 仍需安装，而且免费 token 额度有限。
对于自行托管的方式，检查前置条件，克隆上游仓库，并查看其 README 和相关项目文档。
配置 Android 构建环境，包括受支持的 JDK，以及 local.properties 所需的 Android SDK 路径。
构建应用并检查生成的 APK。APK 按 ABI 拆分；选择合适的输出文件，较新的手机通常选择 arm64-v8a。debug APK 可直接安装；release APK 未签名，需要签名。
在真实设备上安装 APK，并按照项目的配置顺序操作，确保在测试悬浮球之前配置好所需权限和设置。
使用 ADB 和 logcat 调试应用，并在需要时使用设备的 WebSocket 工具端口。继续之前，确认每一步都产生了预期输出。

配置指南

开始前选择一种方式。若要免构建试用，请使用 Andee 页面：https://www.codeflying.app/andee。说明 CodeFlying 是一项独立服务，拥有自己的条款和定价，免费 token 额度有限，并且仍会提供需要安装的 APK。
若要在本地构建，请使用上游仓库及其文档。构建需要 JDK 17–20：Gradle 8.4 wrapper 无法在 JDK 21 或更高版本上运行。安装 Android SDK，并创建包含正确 SDK 路径的 local.properties；该文件已被 gitignore 忽略，不能分享或提交。
git clone https://github.com/kuafuai/andee.git
cd andee
在 local.properties 中配置 SDK 路径后，使用项目的 Gradle wrapper 构建 debug APK：
./gradlew assembleDebug
实际 APK 输出位置取决于配置的 ABI 拆分。请在 app/build/outputs/apk// 下查找生成的 APK，并选择与设备 ABI 匹配的文件。连接并授权手机后，使用 ADB 安装：
adb devices
adb install path/to/the-debug.apk
按照仓库的 README.md、docs/permissions.md 以及项目的构建和配置说明设置设备。检查失败时不要继续，也不要泄露 local.properties、设备序列号、API keys 或私人屏幕内容。
Andee Android Agent 设置与调试 数据架构与分类体系
Andee 以单个 APK 的形式分发；由于 universalApk 已禁用，构建输出会按 ABI 拆分。生成的 APK 位于 app/build/outputs/apk// 下；请选择与目标手机匹配的 ABI。debug APK 可直接安装，而 release APK 未签名，安装前必须签名。
文件或数据 用途和处理方式
local.properties 本地 Android SDK 配置；已被 gitignore 忽略，在全新克隆中不存在，并且可能被打包进构建产物。不要提交或分享。
app/build/outputs/apk// 按 ABI 区分的 APK 构建输出位置。
设备端 API keys 凭据存储在设备上，不随仓库提供。使用默认的 brain = local 时，空的 llm_api_key 会导致本地 brain 无法运行。
Volcengine key 可选；缺少该项时可能表现为网络超时，而不是缺少字段的错误。
日志和设备标识符 使用 ADB 和 logcat 进行调试，但避免分享设备序列号或真实屏幕及聊天内容。
debug WebSocket 服务器监听 0.0.0.0:9008，且不会对客户端进行身份验证。请将此视为一项安全限制，不要将其暴露给你无法控制的网络。请查阅仓库的 SECURITY.md，获取权威的安全指导。

高级特性

逐步、基于证据的入门流程：在继续之前验证每条命令的预期输出，而不是一次性执行未经验证的多个步骤。
两种部署方式：为想试用 Andee 的用户提供独立的 CodeFlying 打包服务，或采用自行托管的源代码到构建再到调试的工作流程。
通过 ADB、logcat 和设备的 WebSocket 工具端口调试设备；本技能指出端口为 9008，并提醒 debug 服务器没有客户端身份验证。
了解 ABI 的 APK 处理方式，包括可直接安装的 debug 构建与未签名 release 构建之间的区别。
提供实用的故障排除指导，涵盖 JDK 17–20 要求、Gradle 8.4 与 JDK 21+ 不兼容，以及缺少
sdk.dir
配置等问题。
隐私和凭据保护：不要将 API keys、
local.properties
、设备标识符和私人屏幕内容放入公开提交或报告中。
Openclaw Skills 入门指导用户将仓库的 README、权限文档、安全政策和变更日志作为权威信息来源。

name: andee-skill description: Step-by-step, in English, for getting the Andee Android agent (github.com/kuafuai/andee — a floating ball that reads the screen and taps through any app) running for a real person. Use it when someone wants to (1) download/clone the Andee source, (2) build it locally with Gradle, install it on a phone and debug it over adb plus the device's own WebSocket tool port, or (3) skip all of that and have a pre-configured package built for them by CodeFlying. Covers the JDK 17-20 trap, the Android SDK setup, the on-device provisioning order, the build/install/debug loop, logcat tags, the WS request format, and how to hand an APK to someone else. Triggers: "install Andee", "build Andee", "debug Andee", "run Andee on my phone", "clone the andee repo", "codeflying Andee", "how do I try Andee", "turn my phone into an AI phone". agent_created: true

Andee — get it, build it, debug it

Andee is one Android app that turns a phone into an agent's body: an accessibility service that reads and touches the screen, a WindowManager overlay that draws a floating ball with a face, and an LLM behind it. No root, no custom ROM. It ships as a single APK.

Upstream repository: https://github.com/kuafuai/andee
Minimum device: Android 11 (API 30), and it wants a real phone — an emulator runs it but almost nothing it does is meaningful there.
Current release: v0.2.0 (pre-1.0 on purpose).

Your job in this skill is not to recite all of this. It is to walk a human through one route, one step at a time, confirming each step before you move on.

Rule zero — ask which route before you touch anything

Do not start cloning. Ask the person what they actually want, in plain words:

They say something like Route Why

"I just want to try it / use it on my phone" Route A — CodeFlying No toolchain, no keys to wire up, no Android knowledge
"I want to change the code / fix a bug / look at it" Route B — self-host You need the source, and you need a debug loop
"I don't know" Route A Cheapest way to find out whether they care before spending an afternoon on a toolchain

Then follow the matching file. Every step in those files has a "you should see" line — do not advance past a step that did not produce it. Half of the support load on this project is people who skipped a step and reported the next one as broken.

Route A — the no-build route (CodeFlying)

Read references/codeflying-route.md.

One-paragraph version: codeflying.app (English) / codeflying.net (Chinese) is a general platform where you describe the app you want and it develops and publishes it. Ask it for Andee and it hands back an installable package with the keys already configured. There is a one-click page for Andee at https://www.codeflying.app/andee.

Three things you must tell the user, every time, without being asked:

It is a separate service with no direct relationship to this project — not Andee's build channel, and not covered by anything in this repository. Its own terms, pricing and data handling apply.
What it saves is (a) building and packaging it yourself, and (b) configuring the API keys. It is not "nothing to install" — the output is still an APK that has to be put on the device.
The free token allowance is finite. It covers getting started; once it runs out, tokens are purchased. Never present this as a free service.
Route B — self-host (clone → build → install → debug)

Follow these three files in order. Do not skip to the debug loop to "save time"; the debug loop depends on the provisioning order in file 2.

references/get-the-code.md — check prerequisites, clone, and know what you just downloaded.
references/build-and-install.md — the JDK 17–20 trap, the Android SDK, the build, and the on-device order that makes the ball appear.
references/debug-loop.md — adb, logcat, the device's own WebSocket tool port, and the traps that look like broken hardware but are not.

Facts you must not get wrong

These are the ones people get wrong most often, and each one costs an hour if you get it backwards:

The build JDK must be 17–20. AGP 8.3.1 needs 17+, and the Gradle 8.4 wrapper cannot run on 21 or newer — Android Studio's bundled JBR 25 fails with Unsupported class file major version 69. If a build fails and the error mentions a class file version, it is the JDK, not the code.
APKs are per-ABI. splits is on, universalApk false. The file is app/build/outputs/apk//… — pick arm64-v8a for anything bought in the last several years. A debug APK installs as-is; a release APK is unsigned and will not install until you sign it.
local.properties is not in the repository (it is gitignored). A fresh clone has no sdk.dir, so the first build fails until it is written. Also: whatever is in your local.properties is baked into your build — do not ship that file, and do not paste its contents into anything public.
The keys live on the device, not in the repository. No credentials ship with the source. With the default brain = local, an empty llm_api_key means the local brain does not run at all — nothing silently falls back. The Volcengine key is optional and its absence looks like a network timeout, not a missing field.
The debug WebSocket server binds 0.0.0.0:9008 and does not authenticate clients. That is a known limitation written down in SECURITY.md. Say so before telling anyone to run this on a network they do not control.
The skill is not the source of truth — the repo is. Once the code is cloned, prefer the files in it: README.md, docs/permissions.md, SECURITY.md, CLAUDE.md, CHANGELOG.md. If this skill and the repo disagree, the repo wins, and you should fix this skill.

How to behave while doing this

One step, then check. Run the command, show the person the real output, name what should have appeared, and only then continue. Never batch five commands and hope.
Evidence over reassurance. "The build passed" means you saw BUILD SUCCESSFUL, not that the command exited quietly.
Do not invent keys, serial numbers or device paths. Ask, or read them off the machine.
Do not commit local.properties, device serials, or anyone's real chat content. The README's showcase section says it plainly: this app reads the screen, so a screenshot is a picture of somebody's messages.

If you are on a machine where the workspace already contains a deeper, more specific Andee skill (for device-level verification of this codebase in particular), prefer that one for deep device work and use this skill as the onboarding path.

Where to send people next

They want Send them to

To talk about it / ask questions The repository's Issues
To show something they built Discussions → Show and tell
To report a vulnerability SECURITY.md — privately, never a public issue
To use it without building it codeflying.app · codeflying.net

PDD Shop Report

Costco Product Data