Skip to content

armgit / andee

Public Imported from GitHub
0

Andee lives on your phone or Mac and uses any app like you do—no integrations, no root, any model; memory and passwords never leave your device | Andee 住进你的手机或 Mac,像你一样操作任何 App——无需集成、无需 Root、支持任意模型,记忆和密码绝不离开设备。

chore(release): v0.1.0

booboosui0cac8aab2f99
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2997210..450a20a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,28 +4,53 @@ Notable changes to Andee. The format follows [Keep a Changelog](https://keepacha
## Versioning policy
-**No release has been tagged yet.** In 207 commits the version has never moved off the values the
-Android template shipped with. Rather than pretend otherwise, this file records the policy going
-forward and states plainly where the project is:
-
-- `versionCode` / `versionName` live in `app/build.gradle` and are currently **`1` / `"1.0.0"`**.
-- The first tagged release should be **`v1.0.0`**, matching the `versionName` already in the file.
-- Thereafter: releases are tagged `vMAJOR.MINOR.PATCH`, `versionName` mirrors the tag without the
- leading `v`, and `versionCode` increases by one per release. `versionCode` must increase
- **monotonically** or Android refuses the upgrade; the same number must never be reused for
- two different builds.
+- `versionCode` / `versionName` live in `app/build.gradle` and are currently **`1` / `"0.1.0"`**.
+- Releases are tagged `vMAJOR.MINOR.PATCH`, `versionName` mirrors the tag without the leading `v`,
+ and `versionCode` increases by one per release. `versionCode` must increase **monotonically** or
+ Android refuses the upgrade; the same number must never be reused for two different builds.
- MAJOR for a change that breaks the wire protocol or an existing configuration; MINOR for a new
capability; PATCH for fixes.
-**A version number does not currently identify a build.** Because `versionCode` has always been `1`,
-"which build is this?" cannot be answered from the installed app. Until a release exists, identify
-builds by the short commit hash they were built from. (Embedding the hash into `versionName` at
-build time would close this hole; it is not implemented yet.)
+**The project starts at `0.x`, and that is the accurate number rather than a modest one.** Nothing is
+frozen. The tool-schema contract a hub brain speaks has been rewritten repeatedly
+(`net/ToolSchemas.kt` alone has changed in seven commits since the first), the `local.properties`
+build flags that decide the first-install language, the thinking default and whether CodeFlying is
+compiled in have all been added since, and a saved scene is a shape that only appeared in this
+release. Each of those is something a user or a second implementation would have to rebuild against,
+so `0.x` is being honest that MINOR may break. The release that moves off `0` should be the one where
+the wire contract is written down well enough that a second implementation could be built from it.
+
+**A version number does not identify a build yet.** `versionCode` is `1` and will stay `1` until a
+second release exists, so "which build is this?" still cannot be answered from the installed app.
+Until then, identify builds by the short commit hash they were built from. (Embedding the hash into
+`versionName` at build time would close this hole; it is not implemented yet.)
## [Unreleased]
+## [0.1.0] - 2026-10-09
+
+The first tagged release. Because nothing was tagged before it, this section is the whole project
+rather than a delta from a previous version — it reads as a long list of *Added* for that reason, not
+because a release this size is the norm.
+
### Added
+- **`docs/architecture.svg` + `docs/architecture.zh-CN.svg`, and a `## Architecture` section in both
+ READMEs.** The README described pieces — the ball, the vault, the dog — and never showed how a turn
+ actually moves. Drawing it forced two corrections to the diagram before it was right, both of them
+ worth recording. The first was factual: the draft showed "two brains" when there are **three
+ mutually exclusive backends**, and it marked the hosted one as the default when an unconfigured
+ device reads as `BRAIN_LOCAL`. The second was structural and worse: the draft stopped at the
+ backend and drew nothing after it — no agent loop, no outputs, which is most of the interesting
+ half. No class is named after the harness; it is `LocalBrain` itself. The picture now shows the
+ system prompt held constant with the volatile parts (clock, notebook index, scenes, photos)
+ deliberately inlined into the user message so the provider's prefix cache still hits, the tool
+ table rebuilt every turn, and the non-streaming step loop with its guards. Outputs come back
+ through six channels, none of which had been drawn: speech, text, a full-screen page, saved
+ artifacts, long text, and the dog. Both files are hand-built SVG with hardcoded colours, because
+ GitHub renders a README image through `<img>` and `var(--color-*)` resolves to black there; both
+ were rendered at 1:1 and read back to check for overflow, which caught three layout faults that
+ reading the source alone would not have shown.
- **Both READMEs now ask for your use case (`## Showcase` / `## 好玩的用法`).** The
README described what the thing can do and never asked anyone to show what they did with it,
which is how a project ends up with no idea whether the odd corners work. The section is an
diff --git a/DISCLAIMER.md b/DISCLAIMER.md
index 202e157..22725a9 100644
--- a/DISCLAIMER.md
+++ b/DISCLAIMER.md
@@ -46,7 +46,7 @@ The second row needs spelling out: **tool results are part of the conversation.*
**So "local mode" does not mean "processed locally."** Local mode swaps the hub for whichever provider you typed in. It does not keep a single byte on the device.
Therefore:
-- *"We do not monitor or store your data"* — **mostly true, but do not overclaim it.** No database, no behavioural analysis, and no reading of anything you send; the one exception is the version check, which tells us that some device of some model on some IP is running 1.0.0.
+- *"We do not monitor or store your data"* — **mostly true, but do not overclaim it.** No database, no behavioural analysis, and no reading of anything you send; the one exception is the version check, which tells us that some device of some model on some IP is running 0.1.0.
- *"Your data never leaves the device"* — **false. Do not claim it.**
## 3. What it can actually do (not hypotheticals — current state of the code)
diff --git a/DISCLAIMER.zh-CN.md b/DISCLAIMER.zh-CN.md
index 61974c5..2eac636 100644
--- a/DISCLAIMER.zh-CN.md
+++ b/DISCLAIMER.zh-CN.md
@@ -45,7 +45,7 @@
**因此"本机模式"不等于"本地处理"** —— 本机模式只是把大脑从 hub 换成了你填的那个服务商。它没有让数据留在设备上,一个字都没有。
所以:
-- 「我们不会监控和存储您的数据」——**基本成立,但别把话说满**。不落库、不做行为分析、不看你发的内容;唯一的例外是版本自检,它让我们知道"某个 IP 上,有一台某个型号的设备在跑 1.0.0"。
+- 「我们不会监控和存储您的数据」——**基本成立,但别把话说满**。不落库、不做行为分析、不看你发的内容;唯一的例外是版本自检,它让我们知道"某个 IP 上,有一台某个型号的设备在跑 0.1.0"。
- 「您的数据不会离开设备」——**不成立,而且不要说**。
## 3. 它真的能做什么(以下都不是危言耸听,是代码里的现状)
diff --git a/README.md b/README.md
index ec93591..23b7eaf 100644
--- a/README.md
+++ b/README.md
@@ -523,7 +523,7 @@ Pure Kotlin, no Compose; the whole thing hangs off two pillars, `WindowManager`
| minSdk | 30 | Android 11 — `AccessibilityAction.ACTION_IME_ENTER` and `takeScreenshot` are both API 30+ |
| Java / Kotlin JVM target | 1.8 | `sourceCompatibility` 1.8, `jvmTarget = '1.8'` |
| **Build JDK** | **17–20** | see [Which JDK](#which-jdk) — this is the step people get stuck on |
-| versionCode / versionName | 1 / 1.0 | no release management yet |
+| versionCode / versionName | 1 / 0.1.0 | see [CHANGELOG.md](CHANGELOG.md) for the policy |
| applicationId / namespace | `net.kuafuai.andee` | never changed from the template. It affects nothing |
**Runtime dependencies** (`app/build.gradle`):
@@ -943,8 +943,8 @@ Bundled third-party components are inventoried in [THIRD_PARTY_NOTICES.md](THIRD
Read it before redistributing: **the ML Kit barcode SDK and the `play-services-*` stubs are not
open-source**, and the barcode model is fetched from Google at runtime.
-See [CHANGELOG.md](CHANGELOG.md) for what changed, and for the versioning policy — no release has
-been tagged yet, and version numbers do not currently identify a build.
+See [CHANGELOG.md](CHANGELOG.md) for what changed and for the versioning policy. The first release is
+**`v0.1.0`** — pre-1.0 on purpose, because the wire contract and the build flags are still moving.
## Related documents
diff --git a/README.zh-CN.md b/README.zh-CN.md
index ba3043e..fe537df 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -379,7 +379,7 @@ OpenAI 兼容端点(`llm_api_key`,默认 `https://api.deepseek.com`)。**
| minSdk | 30 | Android 11 —— 因为要用 `AccessibilityAction.ACTION_IME_ENTER`(API 30+)和 `takeScreenshot`(API 30+) |
| Java / Kotlin JVM target | 1.8 | `sourceCompatibility` 1.8、`jvmTarget = '1.8'` |
| **构建用 JDK** | **17–20** | 见[配 JDK](#配-jdk),这是最容易卡住的一步 |
-| versionCode / versionName | 1 / 1.0 | 还没做发版管理 |
+| versionCode / versionName | 1 / 0.1.0 | 策略见 [CHANGELOG.md](CHANGELOG.md) |
| applicationId / namespace | `net.kuafuai.andee` | 从模板里没改,不影响功能 |
**运行库依赖**(`app/build.gradle`):
@@ -837,8 +837,8 @@ CLAUDE.md 给 AI 编码助手看的架构说明(英文)
随包分发的第三方组件清单在 [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md)。再分发之前请先看:
**ML Kit 扫码 SDK 和 `play-services-*` 不是开源许可**,而且扫码模型是运行时从 Google 拉的。
-改了什么、以及版本号策略见 [CHANGELOG.md](CHANGELOG.md) —— 目前还没有打过 tag,版本号也不能
-用来辨认是哪次构建。
+改了什么、以及版本号策略见 [CHANGELOG.md](CHANGELOG.md) —— 首个版本是 **`v0.1.0`**,故意停在
+pre-1.0:线上协议和构建开关都还在动。
## 相关文档
diff --git a/app/build.gradle b/app/build.gradle
index ecd36a0..068d569 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -35,7 +35,7 @@ android {
minSdk 30
targetSdk 34
versionCode 1
- versionName "1.0.0"
+ versionName "0.1.0"
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
diff --git a/docs/releases/v0.1.0.md b/docs/releases/v0.1.0.md
new file mode 100644
index 0000000..c427e07
--- /dev/null
+++ b/docs/releases/v0.1.0.md
@@ -0,0 +1,133 @@
+# v0.1.0
+
+**The first tagged release.** Andee is an individual with a body, not an assistant app: one
+`AccessibilityService` is the entry point, there is no main UI, and the tablet is what it wears.
+
+`0.x` is the honest number rather than a modest one — the wire contract a hub brain speaks, the
+`local.properties` build flags and the shape of a saved scene all changed inside the first weeks of
+work. Treat MINOR versions as able to break. See the [versioning policy](../../CHANGELOG.md#versioning-policy).
+
+> **No APK is attached to this release, on purpose.** The release build type has no `signingConfig`
+> and there is no keystore in this repository, so `assembleRelease` emits
+> `app-<abi>-release-unsigned.apk`, which will not install until you sign it. Shipping a binary that
+> a reader cannot install would be worse than shipping none. Build it yourself —
+> see [Install](#install) below.
+
+## Highlights
+
+- **Any app, no integrations.** It reads the screen as a compact element outline and falls back to
+ the screenshot when an app draws its own pixels. Every screenshot carries a labelled 8×12 grid and
+ it taps by *cell + which third of it* — it never computes coordinates, because general-purpose
+ models are bad at that and good at reading them.
+- **It types like a keyboard without being one.** On Android 13+ it types through the accessibility
+ service's own input channel, into the focused field, **while your own keyboard stays active**.
+- **It logs in as you without ever holding your password.** The on-device vault lists accounts and
+ has the password *typed* into the focused field; no tool returns it, not even masked.
+- **Scenes — ways of working, ready-made or learned.** Four ship under **Scenes → Ready-made
+ scenes**, saved only when you tap Adopt. Beyond those it proposes one after the same kind of
+ session comes up a few times, and nothing is saved until you say yes.
+- **It reads your notifications before they interrupt you**, and stays quiet for groups, newsletters
+ and ads.
+- **The brain is detachable from the body.** Three mutually exclusive backends: on-device with your
+ own key (the out-of-box default), the hosted CodeFlying API market when it is compiled in, or a
+ hub reached over a WebSocket.
+- **The APK went from ~39 MB to ~8 MB** — an ABI split, `minifyEnabled` + `shrinkResources` on
+ release, and deflated native libs. ML Kit's `libbarhopper_v3.so` alone is ~4 MB and the old fat
+ APK carried four copies of it.
+- **A robot dog counts as a leg.** Through a USB OTG dongle on the same body, so one request can
+ move a physical object and look through a camera in a single task.
+
+## What's Changed
+
+### Added
+
+- `docs/architecture.svg` and `docs/architecture.zh-CN.svg`, plus a `## Architecture` section in
+ both READMEs — a turn in, the agent loop, six ways out. Drawing it corrected two claims: there are
+ three backends rather than two, and an unconfigured device reads as `BRAIN_LOCAL` rather than the
+ hosted one.
+- A **版本 row in the self-check list** — the first thing this app ever sends anywhere. It asks a
+ version service whether a newer build exists: one row, one renderer, no second settings page.
+- `LICENSE` — Apache-2.0 with additional conditions. GitHub reports it as `NOASSERTION`; that is
+ expected, not a misconfiguration.
+- `SECURITY.md`, `CODE_OF_CONDUCT.md`, `CONTRIBUTING.md` + `CONTRIBUTING.zh-CN.md`,
+ `DISCLAIMER.md` + `DISCLAIMER.zh-CN.md`, `docs/acceptable-use.md` + `docs/acceptable-use.zh-CN.md`,
+ `docs/permissions.md` + `docs/permissions.zh-CN.md`, `THIRD_PARTY_NOTICES.md`.
+- A `Signed-off-by:` sign-off is required on every commit, enforced by
+ `.github/workflows/dco.yml`.
+- Both READMEs now ask for your use case (`## Showcase` / `## 好玩的用法`).
+
+### Changed
+
+- **`assembleRelease` builds again** — it had been failing in `lintVitalRelease` on
+ `res/xml/backup_rules.xml` and `res/xml/data_extraction_rules.xml`, both of which exclude
+ `domain="device_root"`. A false positive against AGP 8.3's outdated domain list; both lines now
+ carry a scoped `tools:ignore`.
+- **`SECURITY.md` no longer claims a safeguard the software does not have.** It stated that
+ destructive actions are *"gated behind `ask_user` / `confirm` flows"*, which is not true — `ask_user`
+ is an ordinary tool the model chooses to call, and nothing forces a confirmation before
+ `tap_by_coordinates`. The checks are instructions to the model rather than enforcement.
+- **The blanket "no telemetry at all" claim is gone, because the version row made it false.** What
+ survives is the half that is still checkable: no analytics SDK, no crash reporting, no event
+ tracking, no advertising ID.
+- **Positioning corrected throughout the docs** — they described "the body side of a Physical Agent
+ system", which contradicts the project's own first instruction: *you are not a tablet's assistant,
+ you are an individual, and the tablet is only what carries you.* No code changed; the prose did.
+- `README.md` is now the English front page, `README.zh-CN.md` the Chinese one. Every bilingual
+ document follows one file per language, and each language links only to its own counterparts.
+- `LICENSE` Part A gained a fourth condition: shipping the software inside another product now needs
+ written authorisation. Running it yourself, forking it, and charging to support a client who runs
+ it themselves all remain permitted.
+- `gradle.properties` no longer pins `org.gradle.java.home` to a machine-specific path.
+
+### Fixed
+
+- **A failed voice turn crashed the app with `StackOverflowError` instead of reporting the failure.**
+ `AsrController`'s listener implemented `onError(msg)` by calling `onError(msg)` — which resolved to
+ *itself*, not the constructor's callback. One recognizer error became infinite recursion. Now
+ qualified `[email protected](msg)`.
+
+### Removed
+
+- `brain/andee-system-prompt.md` — an unused mirror of the cloud brain's prompt with no runtime role.
+ The cloud brain mode itself is not retired.
+- The `## 从哪里开始看` section in `README.zh-CN.md`, which held nothing but three rows announcing
+ that the demo video and screenshots do not exist yet.
+
+## Known issues
+
+- `tools/verify_faces_lab.py` reports **7/16 assertions passing** against the committed
+ `reports/ball-faces-lab.html`. Pre-existing, unrelated to the release; worth resolving before
+ contributors are pointed at the ball-face lab.
+- The debug WebSocket server (`net/BodyWsServer`) binds `0.0.0.0:9008` **with no authentication**.
+ Documented in `SECURITY.md`. Not fixed.
+
+## Before you install
+
+Read **[DISCLAIMER.md](../../DISCLAIMER.md)** and **[docs/acceptable-use.md](../acceptable-use.md)**
+first. The uncomfortable part is worth stating plainly here rather than burying it: this app asks for
+accessibility, overlay, notification access, SMS and call log, and it can complete a payment by
+tapping. The only guardrail on that path is Android's `FLAG_SECURE`. The prompt-level checks on risky
+actions are instructions to the model, not enforcement. Assume the device should not be left in a
+state where that matters.
+
+## Install
+
+Android 11+ (`minSdk 30`), arm64-v8a for anything bought in the last several years. There is no
+binary in this release; build one:
+
+```bash
+git clone https://github.com/kuafuai/andee
+cd andee
+./gradlew :app:assembleDebug # installs as-is, signed with the debug certificate
+```
+
+`assembleRelease` needs your own keystore — the repo has none, so it produces an unsigned APK. The
+debug variant ships un-shrunk dex and is larger, which is the price of it installing without you
+signing anything. Either way the APK is **per-ABI** (`splits` in `app/build.gradle`), so pick the file
+that matches the device.
+
+Full from-scratch setup — the JDK traps, the Android SDK two ways, and a table of the errors you are
+likely to hit — is in the README's **Provisioning** section. Then, in this order: grant Overlay → enable
+Accessibility → tap the ball → put in your own keys under ⚙.
+
+**Full Changelog**: https://github.com/kuafuai/andee/commits/v0.1.0