Repository navigation
v0.6.2
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 atbaas.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.
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 .dmgs are signed with a local identity, not an Apple Developer ID, so Gatekeeper refuses the first
launch of a downloaded copy.
override, and most advice online still recommends it. The current route:
- Double-click the app. It will be refused. Dismiss the dialog.
- Open System Settings → Privacy & Security and scroll to Security.
- There is a line naming Andee as blocked, with an Open Anyway button beside it.
- 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, or
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).
- The order a reader sees is the alphabetical order of these names. GitHub sorts the asset list by
- 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.pyandpublish_variants.shfollow 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 toapi.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.netversusmyapp.codeflying.apphas 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 sincev0.4.1. assets/andee_key.txtis 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.0listed are unchanged and untouched:tools/verify_faces_lab.pystill
reports 7/16 assertions passing, and the debug WebSocket server (net/BodyWsServer) still binds
0.0.0.0:9008with no authentication (documented inSECURITY.md).
Before you install
Read DISCLAIMER.md and
docs/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
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: v0.6.1...v0.6.2