Skip to content

A tiny friend in your Mac's notch and on your iPhone that keeps an eye on your AI coding agents: Claude Code, Codex, Cursor, Gemini CLI, Antigravity and more. Approve from the notch or your Lock Screen.

Android: remove three working notes that were not meant to ship

Rhytam Biswasf6101045706a
diff --git a/android/DEMO_VIDEO.md b/android/DEMO_VIDEO.md
deleted file mode 100644
index 8c592974..00000000
--- a/android/DEMO_VIDEO.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# Demo video for Louis (about 90 seconds)
-
-Louis asked for a short screen recording of the main flow. Nothing is published: the file goes to Louis only.
-
-## Before recording
-
-- Phone: Coucou for Android from the latest `android` branch, Wi-Fi on, same network as the PC, notification volume up.
-- PC: the portable `coucou.exe` (no other Coucou running), Settings > Android phone > Phone link on, phone paired.
-- Claude Code (the command-line tool, not the Desktop app) in a folder you trust, started with `claude.cmd --permission-mode default`.
-- Phone: Do Not Disturb off, "Show Mochi over other apps" on if you want the island in the video.
-- Use a test folder and a harmless command (`echo hello > demo.txt`). No real secrets on screen.
-
-## Shot list
-
-1. Home, connected, Mochi and the agent card (5 s).
-2. Lock the phone. In the terminal, ask Claude Code to write `demo.txt` (10 s).
-3. The screen lights up with the notification: "Approval needed / Unlock to see the request" (8 s).
-4. Unlock and tap Allow with the fingerprint. The phone screen is black here, so cut to the PC with the caption "Request sent for approval", then the terminal continuing (20 s).
-5. A second request: the PC shows it waiting, Deny on the phone, the terminal says it was denied, caption "Denied on the phone" (15 s).
-6. Plan usage and the Chat tab, if switched on (15 s).
-7. Settings > About and Licences: the attribution to Louis (10 s).
-
-## The one catch: secure screens record black
-
-The pairing, chat and approval screens are marked secure on purpose, so a screen recording of them is black. The video
-does not remove that protection. During those seconds it shows the request from the other side instead:
-
-- Record the PC screen at the same time (the terminal waiting on the permission, and Coucou's island or card on the PC).
-- Put a caption over the black part: **"Request sent for approval"**, then **"Approved on the phone (fingerprint)"** or
- **"Denied on the phone"**. Add the captions when editing (any video editor, or the Windows Clipchamp).
-- Cut between the phone (notification, Home, Settings, About) and the PC (terminal and island), so the viewer always sees
- something real. Use the other phone as a camera only if Louis wants to see the approval sheet itself.
-
-## How to record
-
-Wireless or USB, from the PC: `adb shell screenrecord --time-limit 180 /sdcard/coucou-demo.mp4`, then
-`adb pull /sdcard/coucou-demo.mp4`. Or use Android's own screen recorder (swipe down twice, Screen recorder).
-Trim to about 90 seconds. Check the file for notifications from other apps before sending it.
diff --git a/android/HANDOFF.md b/android/HANDOFF.md
deleted file mode 100644
index c2b8e462..00000000
--- a/android/HANDOFF.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Handoff: Coucou for Android (read this first)
-
-For a new coding session with no memory of the earlier work.
-
-## What this is
-
-**Coucou** (https://github.com/Louis-CFM/coucou, by Louis Raillé) is a macOS app, with a Windows/Linux Tauri port in `windows/`, where
-**Mochi** shows the state of AI coding agents and lets the user approve their permission requests. **Our project** is the
-Android port in `android/` (Kotlin + Compose), built by Rhytam Biswas (`Rhytam23`) with Claude on branch `android` of the fork
-`Rhytam23/coucou` (`upstream` = Louis-CFM/coucou, read-only for us).
-
-## Rules that must never be broken
-
-Louis agreed by email (`PERMISSION.md`): Mochi, the sounds, visuals, icon and the name "Coucou for Android" for this Android app only, and
-only if it is **free (no ads, paid features or analytics; CI greps for them)**, credits him in the app (About and Licences) with a link to his
-repo, keeps the MIT notice, and **he approves the build and the store listing BEFORE anything is published**. Pushing source to the fork is fine.
-Never create a release, upload an APK, submit to a store, or open a PR to `upstream` without the user saying so.
-
-Repo rules (`CLAUDE.md`): no third-party dependency unless unavoidable; secrets in the keystore; no telemetry; never block the agent; never
-approve a permission without an explicit click; don't restyle Louis's shipped desktop views; pill IDs are never renamed. Don't touch
-`NotchBuddy/`, `relay/` (Louis's APNs relay) or the Mac docs. Android app: English only, dark only. Commit messages end with
-`Co-Authored-By: Claude Sonnet 5.5 <[email protected]>`; push only to `origin android`; `change log.md` stays local.
-
-## Where things are
-
-- `android/app/src/main/kotlin/com/coucou/android`: `mochi/` (engine, painter, `outfit/`), `link/` (protocol, pairing, TLS client, discovery,
- `WebSocket.kt`, `RelayLink.kt`, `RelayCrypto.kt`, `Transport.kt`, `LinkHealth.kt` (what Home says, the alarm and battery rules), `Reconnect.kt`, `Diagnostics.kt`), `core/` (pure rules), `ui/` (Compose), `app/` (`AppModel`, notifications,
- `LinkService`, `SecureStore`, biometric gate), `scan/` (QR), `sound/`. Overview and features: `android/README.md`.
-- Desktop side: `windows/src-tauri/src/phone_link/` (hub = rules, server = TLS, pairing, admission, discovery, chat, `relay_client.rs`,
- `relay_crypto.rs`), front end `windows/src/island/phone-link.ts` and `windows/src/settings/phone.ts`. Protocol: `docs/ANDROID_LINK.md`.
-- Internet relay: `android/relay/` (Worker + Node twin, test vectors), wire `docs/RELAY_LINK.md`, plan and decisions `android/RELAY_PLAN.md`,
- threat check `android/RELAY_THREAT_CHECK.md`, deploy and test with a phone on mobile data `docs/RELAY_DEPLOY.md`, end to end `android/relay/tools/e2e.sh`.
-- `android/tools/dev-desktop.mjs`: a pretend computer for trying the app (fake data, test tool). `android/PROPOSAL_FOR_LOUIS.md`: draft for the user to send; nothing is opened upstream.
-- CI: `.github/workflows/phone-link.yml` ("Phone link": Windows tests, Linux interop, relay, relay end to end, Android build/tests/lint).
-
-## Checks
-
-```
-cd android && ./gradlew test assembleDebug lint
-node android/scripts/gen-strings.mjs --check # English strings in sync
-cd windows && cargo test --workspace --locked && npm test && npx tsc --noEmit
-cd android/relay && npm ci && npm test && npm run vectors
-```
-
-The Kotlin suite is about 640 tests (some need `node`/`cargo` and skip without them: set `COUCOU_RUST_INTEROP=1` and `COUCOU_NODE_RELAY=1`).
-Gradle and Compose compile only in CI in a cloud session; the pure Kotlin files can be compiled with kotlinc and JUnit.
-
-## What has and has not been seen on a real phone
-
-Seen (Samsung Galaxy A12s, Android 13, earlier stages): Mochi renders, demo mode, pairing over Wi-Fi, Allow reaches the computer.
-**Not seen on a device**: a release (R8) build, which has never been installed (CI builds it unsigned and checks the logs are gone, nothing more); the keep-alive alarm and "Can't connect?" (the Galaxy A12s with the screen off for 10+ minutes is the test), the redesigned screens, the island and its motion, the widget/tile/notification, QR scan, chat, answers,
-file changes, the relay path (and Doze/battery with it), anything on real Cloudflare. CI proves compilation, lint and the unit and
-interop tests, not how it looks or feels.
-
-## Still open
-
-- The user tests each feature on the phone; Louis has not approved a build or a listing.
-- Not built: stage I (send the next instruction to an agent), FCM push, a Play Store listing. Stage G (a VPN) was built and removed.
diff --git a/android/PROPOSAL_FOR_LOUIS.md b/android/PROPOSAL_FOR_LOUIS.md
deleted file mode 100644
index f3492e7c..00000000
--- a/android/PROPOSAL_FOR_LOUIS.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Draft message to Louis (the user sends it; nothing is opened on his repo)
-
-Subject: Coucou for Android: an optional phone link in the Windows/Linux app (your call)
-
-Hi Louis,
-
-The Android port you allowed needs something from the desktop app to show real sessions: today Android
-has no CloudKit or APNs, so the phone connects straight to the computer over the local network.
-I wrote that desktop side for the Windows/Linux app, as a separate module, and I'd like to know if you
-want it in Coucou. It's your app and your decision; I'll keep it on my fork if you don't.
-
-What it is
-- Settings gets an "Android phone" section. The switch is **off by default**. When it's on, the app
- listens for the Android app on the local network only; when it's off, nothing listens, nothing is
- published and no timer runs.
-- The phone sees the agent sessions and the pending permission request. Allow/Deny from the phone is
- applied only if it matches the request that is still pending (same fingerprint as the Mac's
- ApprovalRelay), once, and not after 115 s. Allow asks for the fingerprint or screen lock on the phone.
- It never blocks the agent: the card on the island keeps working, and the phone is just another way to click.
-- The code is in `windows/src-tauri/src/phone_link/` (about 900 lines with tests) plus a small publisher
- (`src/island/phone-link.ts`) and the settings section. Existing views are not restyled; the only edits to
- your code are a `phoneLink` setting, `dropPendingCard` exported from hooks.ts, and the secrets module
- gaining entries the webview can't reach.
-
-Security choices
-- TLS 1.2/1.3 with a self-signed certificate made once. The phone pins its SHA-256 from the pairing QR.
-- The certificate key and the pairing token are in the OS keystore, never on disk. No keystore, no link.
-- Only private/loopback/link-local peers are accepted; 64 KiB line limit; 8 connections; constant-time
- token check; "Pair again" revokes the old phone. The pairing code is shown only after a click.
-- No telemetry, no cloud, no relay.
-
-Cost
-- Two new crates: `rcgen` (certificate, plus its `yasna` dependency) and `qrcode` (pairing QR). rustls,
- tokio-rustls and ring were already in the tree via reqwest. If you'd rather not have the QR, the link can
- be pasted and `qrcode` goes away.
-
-Tested
-- 38 cargo tests (wrong token, fingerprint mismatch, oversize line, late decision, answered at the desk,
- pairing again, local-network filter...), 9 front-end tests, and the real Android client against the
- real server. Not yet verified on a real phone with real sessions. The Settings texts are translated
- by me in the nine languages and need a native read.
-
-The Mac app is untouched; if you ever want the same on macOS, `docs/ANDROID_LINK.md` is the protocol.
-Nothing from the Android app is published until you've approved the build and the listing.
-
-Thanks,
-Rhytam
diff --git a/android/RELAY_PLAN.md b/android/RELAY_PLAN.md
index fe55a1b7..c483a562 100644
--- a/android/RELAY_PLAN.md
+++ b/android/RELAY_PLAN.md
@@ -24,7 +24,7 @@ Status: **approved by the user on 2026-10-10**, with the decisions and two addit
asserts "no (key, nonce) twice" over thousands of frames, both directions and two sessions; R2 repeats it in Rust and Kotlin.
- **Stage R0 (done):** `docs/RELAY_LINK.md` (the wire spec) and `android/relay/test-vectors.json` with its generator.
-Sources read: `android/HANDOFF.md`, `docs/ANDROID_LINK.md`, `relay/README.md` and `relay/src/index.ts` (Louis's APNs
+Sources read: `docs/ANDROID_LINK.md`, `relay/README.md` and `relay/src/index.ts` (Louis's APNs
relay, for style), the former parity plan (stage G, row 16; deleted in the cleanup, it is in the git history), `CLAUDE.md`, and the phone-link code on both sides.
## 1. Goal and non-goals
@@ -260,7 +260,6 @@ The relay transport lives inside the same service. Design:
small, self-contained, reviewed change, and no PR is opened without the user's decision.
- No telemetry, no accounts, no third party in the data path except the user's own Cloudflare account, and the payload is
end-to-end encrypted, so even that account cannot read it.
-- `android/PROPOSAL_FOR_LOUIS.md` would get a short section with the above after you approve; nothing is sent.
## 11. Stages