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.6.2 — name and order the download list for the reader

booboosui89fee9f011a8
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 931d7c7..06e7440 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,7 +4,7 @@ Notable changes to Andee. The format follows [Keep a Changelog](https://keepacha
## Versioning policy
-- `versionCode` / `versionName` live in `app/build.gradle` and are currently **`14` / `"0.6.1"`**. The
+- `versionCode` / `versionName` live in `app/build.gradle` and are currently **`15` / `"0.6.2"`**. The
Mac's product version is read from that same `versionName`, so both bodies carry one number.
- 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
@@ -29,6 +29,39 @@ hash into `versionName` at build time would close this hole; it is not implement
## [Unreleased]
+## [0.6.2] - 2026-10-26
+
+**The download list now says what each file is for, and lists them in the order you would want them.**
+Every asset carries a label naming its platform and device — `Andee 0.6.2 · Android-arm64-v8a`,
+`Andee 0.6.2 中文版 · Mac-Apple 芯片` — and the list reads Android before Mac, most common device first,
+English group before Chinese.
+
+No behaviour changed in the app itself. This is a packaging release: the same ten builds as 0.6.1,
+named and ordered better.
+
+### Changed
+
+- **Asset file names gained a platform field**: `andee-<version>-<lang>-<platform>-<device>.<ext>`, so
+ `andee-0.6.2-en-android-arm64-v8a.apk`. Three things depend on that shape, and each was decided by
+ measuring rather than by preference:
+ - **The order a reader sees is the alphabetical order of these names.** GitHub sorts the asset list by
+ name and the upload order is discarded, so the display order has to be encoded in the names —
+ `en` < `zh`, `android` < `mac`, `arm64-v8a` < `armeabi-v7a` < `x86_64`, `arm64` < `x64`. All four
+ comparisons were checked before the shape was chosen.
+ - **No Han characters.** GitHub deletes them from asset names, so a file named with the Chinese
+ wording arrives with it removed and two separators left touching. So the name is ASCII and the
+ Chinese wording goes in the label.
+ - **The name is now stable across the three scripts** (build, verify, publish) that parse it.
+- **Every asset has a label, both languages.** The Chinese ones carry the Chinese wording, which only
+ survives in the label; the English ones carry a matching one so the two groups read as a set instead of
+ the second half of the list looking bare.
+
+### Fixed
+
+- **`verify_variants.py` and `publish_variants.sh` followed the new naming.** Both parse file names to
+ decide what a package is; both were updated in the same change, because a name change that lands in
+ only one of them produces a release that either fails verification or publishes the wrong pairing.
+
## [0.6.1] - 2026-10-26
**One checkout now produces every shipping variant, and the packages cannot contain a key.** Four
diff --git a/DISCLAIMER.md b/DISCLAIMER.md
index 90e715f..06ccf23 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 0.6.1.
+- *"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.6.2.
- *"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 250b42a..b586289 100644
--- a/DISCLAIMER.zh-CN.md
+++ b/DISCLAIMER.zh-CN.md
@@ -45,7 +45,7 @@
**因此"本机模式"不等于"本地处理"** —— 本机模式只是把大脑从 hub 换成了你填的那个服务商。它没有让数据留在设备上,一个字都没有。
所以:
-- 「我们不会监控和存储您的数据」——**基本成立,但别把话说满**。不落库、不做行为分析、不看你发的内容;唯一的例外是版本自检,它让我们知道"某个 IP 上,有一台某个型号的设备在跑 0.6.1"。
+- 「我们不会监控和存储您的数据」——**基本成立,但别把话说满**。不落库、不做行为分析、不看你发的内容;唯一的例外是版本自检,它让我们知道"某个 IP 上,有一台某个型号的设备在跑 0.6.2"。
- 「您的数据不会离开设备」——**不成立,而且不要说**。
## 3. 它真的能做什么(以下都不是危言耸听,是代码里的现状)
diff --git a/README.md b/README.md
index c167771..f53bd93 100644
--- a/README.md
+++ b/README.md
@@ -700,7 +700,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 | 14 / 0.6.1 | see [CHANGELOG.md](CHANGELOG.md) for the policy |
+| versionCode / versionName | 15 / 0.6.2 | 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`):
@@ -1133,7 +1133,7 @@ Read it before redistributing: **the ML Kit barcode SDK and the `play-services-*
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. The latest release is
-**`v0.6.1`** — pre-1.0 on purpose, because the wire contract and the build flags are still moving.
+**`v0.6.2`** — 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 8da9013..91e7a28 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -525,7 +525,7 @@ Google),再填该服务商的密钥。这是两个独立的服务,条款
| 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 | 14 / 0.6.1 | 策略见 [CHANGELOG.md](CHANGELOG.md) |
+| versionCode / versionName | 15 / 0.6.2 | 策略见 [CHANGELOG.md](CHANGELOG.md) |
| applicationId / namespace | `net.kuafuai.andee` | 从模板里没改,不影响功能 |
**运行库依赖**(`app/build.gradle`):
@@ -992,7 +992,7 @@ CLAUDE.md 给 AI 编码助手看的架构说明(英文)
随包分发的第三方组件清单在 [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md)。再分发之前请先看:
**ML Kit 扫码 SDK 和 `play-services-*` 不是开源许可**,而且扫码模型是运行时从 Google 拉的。
-改了什么、以及版本号策略见 [CHANGELOG.md](CHANGELOG.md) —— 当前版本是 **`v0.6.1`**,故意停在
+改了什么、以及版本号策略见 [CHANGELOG.md](CHANGELOG.md) —— 当前版本是 **`v0.6.2`**,故意停在
pre-1.0:线上协议和构建开关都还在动。
## 相关文档
diff --git a/app/build.gradle b/app/build.gradle
index caf7306..adfb979 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -130,8 +130,8 @@ android {
applicationId "net.kuafuai.andee"
minSdk 30
targetSdk 34
- versionCode 14
- versionName "0.6.1"
+ versionCode 15
+ versionName "0.6.2"
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
diff --git a/docs/releases/v0.6.2.md b/docs/releases/v0.6.2.md
new file mode 100644
index 0000000..de4783f
--- /dev/null
+++ b/docs/releases/v0.6.2.md
@@ -0,0 +1,180 @@
+# v0.6.2
+
+**The download list now says what each file is for.** Every package carries a label naming its platform
+and device — **Andee 0.6.2 · Android-arm64-v8a**, **Andee 0.6.2 中文版 · Mac-Apple 芯片** — so you can
+tell which file to take without knowing what an `ABI` is.
+
+The list is also ordered the way you would want it: **Android first, Mac second; the most common device
+in each platform first; the English group before the Chinese group.**
+
+Nothing changed inside the app. This is the same ten builds as v0.6.1, named and ordered better.
+
+> **These binaries carry no credentials.** No CodeFlying key, no voice-provider key, and no Google key.
+> **You supply your own**: sign up from the link inside the app, then paste the key into
+> **Settings → Backend**. Starting is free and the free allowance is finite.
+>
+> Each package already points at the right server for its language — the English ones at
+> `myapp.codeflying.app`, the Chinese at `baas.kuafuai.net`. You do not choose this.
+>
+> **The macOS packages are signed with a local identity, not an Apple Developer ID**, so Gatekeeper
+> refuses the first launch. On macOS 15 the old "right-click → Open" trick no longer exists; see
+> **[Opening the Mac app](#opening-the-mac-app)**.
+
+## Download
+
+### English packages
+
+**Android** (Android 11 / API 30 or later). Take the one that matches your device's processor:
+
+| Label shown on the page | File name | Take it if |
+|---|---|---|
+| Andee 0.6.2 · Android-arm64-v8a | `andee-0.6.2-en-android-arm64-v8a.apk` | **any phone from the last several years** — almost everyone |
+| Andee 0.6.2 · Android-armeabi-v7a | `andee-0.6.2-en-android-armeabi-v7a.apk` | an older 32-bit device |
+| Andee 0.6.2 · Android-x86_64 | `andee-0.6.2-en-android-x86_64.apk` | an emulator on a computer |
+
+*Not sure? Take `arm64-v8a`. If it refuses to install because no architecture matches, try
+`armeabi-v7a` — the two do not conflict, and only one of them can be right.*
+
+**macOS** (macOS 14 or later). Not a universal binary — take the one matching your Mac's chip:
+
+| Label shown on the page | File name | Take it if |
+|---|---|---|
+| Andee 0.6.2 · Mac-Apple 芯片 | `andee-0.6.2-en-mac-arm64.dmg` | an Apple silicon Mac (M1 or later) — **most Macs** |
+| Andee 0.6.2 · Mac-Intel 芯片 | `andee-0.6.2-en-mac-x64.dmg` | an Intel Mac |
+
+*To check: Apple menu → About This Mac. "Chip: Apple M1/M2/M3/M4" means Apple silicon; "Processor:
+Intel Core" means Intel.*
+
+### Chinese packages
+
+The Chinese packages are the `-zh-` files, and each displays a Chinese label on the Release page:
+
+| Label shown on the page | File name |
+|---|---|
+| Andee 0.6.2 中文版 · Android-arm64-v8a | `andee-0.6.2-zh-android-arm64-v8a.apk` |
+| Andee 0.6.2 中文版 · Android-armeabi-v7a | `andee-0.6.2-zh-android-armeabi-v7a.apk` |
+| Andee 0.6.2 中文版 · Android-x86_64 | `andee-0.6.2-zh-android-x86_64.apk` |
+| Andee 0.6.2 中文版 · Mac-Apple 芯片 | `andee-0.6.2-zh-mac-arm64.dmg` |
+| Andee 0.6.2 中文版 · Mac-Intel 芯片 | `andee-0.6.2-zh-mac-x64.dmg` |
+
+Which one to take is the same question as above. The only other difference is the server, which is
+already baked in.
+
+The **file names** are ASCII because GitHub deletes Han characters from release asset names — a file
+named with the Chinese wording would arrive with it removed and two separators left touching. So the
+Chinese wording lives in the label, where it survives, and the downloaded file name stays ASCII, which
+also means it survives every filesystem it is copied onto.
+
+### Opening the Mac app
+
+The `.dmg`s are signed with a local identity, not an Apple Developer ID, so Gatekeeper refuses the first
+launch of a downloaded copy.
+
+⚠️ **On macOS 15 (Sequoia) and later, "right-click → Open" no longer works** — Apple removed that
+override, and most advice online still recommends it. The current route:
+
+1. Double-click the app. It will be refused. Dismiss the dialog.
+2. Open **System Settings → Privacy & Security** and scroll to **Security**.
+3. There is a line naming Andee as blocked, with an **Open Anyway** button beside it.
+4. Confirm, and authenticate.
+
+That button **only appears for about an hour** after the failed launch. If it is missing, launch the app
+again and go straight back to Settings.
+
+One more thing worth knowing: the app **inside** the mounted dmg carries no quarantine flag, so it may
+launch straight from the dmg — and then be blocked once you drag it to Applications, which does attach
+one. Both behaviours are normal; neither means a damaged download.
+
+### What you supply
+
+No package has a key. After installing, open **Settings → Backend** and either paste a CodeFlying key
+(sign up from the link in that panel) or switch to **on-device** and give it an OpenAI-compatible
+endpoint and model. A voice key is optional — without one the assistant is silent but still works on
+screen.
+
+> **Would you rather not configure keys at all?** Use the one-click page instead —
+> **[codeflying.app/andee](https://www.codeflying.app/andee)**, or
+> **[codeflying.net/andee](https://www.codeflying.net/andee)** in mainland China. Describe what you want,
+> tap the build button, and you get a package with the **tokens already configured** plus a QR code to
+> scan. Starting is free and the free token allowance is **finite — once it runs out, tokens must be
+> bought.** It is a separate service with no direct relationship to this project, with its own terms,
+> pricing and data handling. Note it produces **an Android APK, not a Mac app** — macOS packages can
+> only be built on macOS.
+
+## What's Changed
+
+### Changed
+
+- **Asset file names gained a platform field** — `andee-<version>-<lang>-<platform>-<device>.<ext>`, so
+ `andee-0.6.2-en-android-arm64-v8a.apk`. Three constraints decided that shape, and each was measured
+ rather than assumed:
+ - **The order a reader sees is the alphabetical order of these names.** GitHub sorts the asset list by
+ name and discards the upload order, so the display order has to be encoded in the names:
+ `en` < `zh`, `android` < `mac`, `arm64-v8a` < `armeabi-v7a` < `x86_64`, `arm64` < `x64`. All four
+ comparisons were checked before the shape was chosen — an earlier attempt put the language tag at
+ the end, which interleaved the two languages instead of grouping them.
+ - **No Han characters**, per above.
+ - The name is now parsed the same way by all three scripts that touch it (build, verify, publish).
+- **Every asset has a label, in both languages.** The Chinese wording only survives in a label; labelling
+ the English assets too makes the two groups read as a set rather than half the list looking bare.
+
+### Fixed
+
+- **`verify_variants.py` and `publish_variants.sh` follow the new naming.** Both decide what a package is
+ by parsing its file name, so a rename that lands in only one of them produces a release that either
+ fails verification or publishes the wrong pairing. Changed together, on purpose.
+
+## Known issues
+
+- **The Mac still falls back silently when no server is configured.** Every package here carries one, so
+ it does not arise for these downloads — but a locally built app with an empty domain resolves to the
+ local backend and sends whatever key it has to `api.deepseek.com`, while the self-check reports
+ "Configured". The fix would be to make the Mac behave like the phone, which has nowhere to send and
+ says so; still not in this release.
+- **Nothing verifies that a key is accepted by the server it is sent to.** These packages are checked for
+ the right server and the absence of credentials; whether a given CodeFlying key works against
+ `baas.kuafuai.net` versus `myapp.codeflying.app` has not been exercised end-to-end.
+- **A Mac build made on another machine without its signing keychain is ad-hoc signed** — its identity
+ locks to the build hash, so installing it over an existing copy makes macOS treat it as a **different
+ app**: Accessibility and Screen Recording must be granted again. User data is unaffected; it lives in
+ `~/Library/Application Support/Andee`.
+- **The wake threshold's margin is thin**, carried from `v0.3.2`: the eight measured judgements sit in
+ 1.47–2.05 with the line landing in the gap between 1.69 and 1.77 — 0.08 wide.
+- **A light generated page still fades in over a dark stage.** Carried from `v0.3.1`; the app's own
+ default has been light since `v0.4.1`.
+- **`assets/andee_key.txt` is tracked by git and is not in `.gitignore`.** It ships with a single
+ newline, which reads as empty. A key written into it would outrank every build setting.
+- The two issues `v0.1.0` listed are **unchanged and untouched**: `tools/verify_faces_lab.py` still
+ reports 7/16 assertions passing, and the debug WebSocket server (`net/BodyWsServer`) still binds
+ `0.0.0.0:9008` with no authentication (documented in `SECURITY.md`).
+
+## Before you install
+
+Read **[DISCLAIMER.md](../../DISCLAIMER.md)** and
+**[docs/acceptable-use.md](../acceptable-use.md)** first. On Android the app asks for accessibility,
+overlay, notification access, SMS and call log, and it can complete a payment by tapping; on the Mac it
+asks for accessibility, screen recording and notifications. 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.
+
+## Install from source
+
+```bash
+git clone https://github.com/kuafuai/andee
+cd andee
+git checkout v0.6.2
+
+# one variant, by hand:
+./gradlew :app:assembleDebug -PdefaultLang=en -PcodeflyingDomain=myapp.codeflying.app -PcodeflyingSsl=true
+
+# or all ten files, the way the release was built:
+bash ~/.workbuddy/skills/andee-release-ship/scripts/build_variants.sh
+```
+
+`-PcodeflyingKey=` and `-PgoogleVoiceKey=` are refused on purpose — a published package carries no
+credential.
+
+**Upgrading:** `versionCode` moves `14 → 15`, so the Android package installs over v0.6.1 normally. The
+Mac app's version string follows the same number. Nothing about your settings, memory or notebook is
+migrated or touched, because nothing about them changed.
+
+**Full Changelog**: https://github.com/kuafuai/andee/compare/v0.6.1...v0.6.2