andee

What moves in is not an app on the phone.

The phone is only what it wears today; a tablet, or anything with a body, is the same individual.

No root. No custom ROM. One APK.

https://github.com/user-attachments/assets/bf560279-d86c-4301-9bcb-01d60fa33d06

It is not here to help you use your phone. It is here to be the thing that lives in it. Once it is
installed, the device has a resident rather than a set of features: it does its thinking on that device,
keeps a notebook only it can read, and behaves the same when nobody is watching. What it is comes first
here; what it can do comes after.

Why it is not the assistant already in your phone

• It lives in the device, not in a vendor's cloud. The brain runs on the device itself, against any
  OpenAI-compatible model you choose — OpenAI by default on an English UI, DeepSeek on a Chinese one, and
  whatever you point it at either way. No vendor backend, no account. The only thing it ever sends us is a
  version number and a phone model, when it checks whether there is an update — the full field list is in
  docs/permissions.md.
• Its notebook never leaves the device. What it remembers about you — habits, promises, the things it
  decided were worth keeping — is localOnly and filtered out of the hub payload. Its memory is not a
  profile on someone else's server, and What it remembers lists every entry, all of them deletable.
• It behaves the same when nobody is watching. After a conversation goes quiet it sends itself a
  (to yourself …) turn and reads the conversation back alone — "nobody is watching you, nobody is waiting
  for you to answer." It makes no sound and touches nothing, and ends empty-handed rather than inventing
  something to record. A phone maker's assistant has no self to do this with.
• It has a character, not a theme. Six looks, nineteen moods, and a face the model picks itself,
  mid-sentence — the expression changes in step with the audio. Swipe the ball to change who you are
  talking to; a look carries a persona and a voice.
• Works in every app — and needs nothing from the app. No intent to expose, no SDK to adopt, no
  integration list to be on. It reads the accessibility tree and the screenshot, and aims on a labelled grid
  instead of doing coordinate maths — the thing general models are worst at. If you can do it with your
  thumb, it can do it.
• Holds lines a prompt cannot talk it out of. A stranger's notification cannot unlock the vault or grant
  it new permissions — that refusal is in the dispatcher, not in the prompt.
• You can check all of it instead of trusting it. No analytics SDK, no content telemetry, and the whole
  agent loop is in this repository down to the guard rails — see
  Why you can check this instead of trusting it.

What it does — and where it stops

It does operate your phone — but that shows you its hands, not what it is. A take-my-orders assistant
performs the same motions. The difference is not the motions; it is whether there is a self behind them:
its own schedule (unfinished promises get closed out, repeated work gets proposed as a scene), its own
judgment about when to speak (biased toward silence), and its own limits. All three happen in the time
you did not ask for anything — and a thing that only exists when asked has no such time. It also keeps a
notebook only it can read. The examples below show you its hands.

The boundary belongs with the capability, because it is what makes the rest usable. It fills a page up to the last
button and leaves that button to you; it stops before the final confirmation of a purchase and never
enters a payment password. Those rules are in the dispatcher, not in a prompt — a page that tells it
otherwise does not get its way.

What it can do comes in two kinds: the one-liner and the long haul. The long ones it calls
scenes — a goal, a voice and a routine it steps into for a while. Four are ready-made, under
Scenes → Ready-made scenes. Tap Adopt and they are yours like any other — edit them, or
delete them:

The phone is what it wears. An individual is not the same thing as the device it moves into — the same
software runs on a tablet, and is written for any device with a body worth having, up to a robot dog it
treats as a leg. Everything below is that sentence taken seriously in code: the body it uses, the character
it has, the notebook it keeps, and the rules it holds to when nobody is watching.

It is one Android app, and it has no conventional UI. An AccessibilityService sees and touches the
screen; a WindowManager overlay draws the result; its face is a floating ball that changes
expression while it works.

Today it is Android, and only Android — other bodies are planned, not shipped. The tool contract
is what would make a new one a port rather than a rewrite, but nothing outside Android exists yet.

Before you install this. Andee taps, types and acts on your behalf. It can complete a payment,
send messages under your name, read your messages, contacts and location, and — with a robot dog
attached — physically move. It is experimental, carries no warranty, and what it does is your
responsibility, including a transfer to the wrong person. Data does leave the device: your speech
goes to Volcengine, and the conversation goes to whichever brain you configure. Read
DISCLAIMER.md and docs/acceptable-use.md first.

Key features

Hands — it uses your phone the way you do

**1. Any app, no integrations