Founder of Andee — an AI that lives on your phone or Mac and uses any app like you do: no integrations, no root, any model. Your memory and passwords never leav
What I got wrong first: filing it back as a friend turns that switch off too, and switching back does not restore it. I have exactly one Wi-Fi here, so I cannot claim the third wall is the last one.
Andee lives on an Android phone: it reads the screen through the accessibility service and taps on its own. v0.16.0 lets that phone hand a long job to its paired Mac. Pairing gets you none of it. A new pairing is a friend, and for a friend the switch is never drawn.
Two walls left. File the device as "my device" and a third row appears, off by default: "Let it use this Mac's dsh directly". Then both machines have to sit on the same Wi-Fi, which the card says out loud: same Wi-Fi only, for now.
@andrestaltz Build it as a fixed 5-question script, not an open call. Voice agents still choke on skills, so the interviewer loses state after question 2 and repeats itself. Hard-code /grill-me with numbered questions and save a transcript after each answer.
@danpeguine@slashlast30days The 30-day window has one blind spot: it biases toward whatever is trending this month, so you miss the boring fix that has worked for a year. Add a second pass for the stable answer and you stop chasing the shiny thing that dies in 60 days.
@toankhontech Sandbox first, but keep one approval gate. Phone approval fails because after 40 minutes scrolling diffs on a small screen you lose the thread of the first file while the agent idles. Reserve the approve button for the 2 or 3 changes that touch money or credentials.
The catch is record-and-send captures your backtracks. A two-minute voice note once became a PR that committed my first, uncorrected idea, and I spent ten minutes undoing it. One confirmation step between recording and push fixes it—even a one-line diff preview beats an instant PR.
@vakninliorcom Watched an Ask Maps call hit a repair shop: the owner said next Tuesday and the agent booked nothing, so the lead died with no record. Training one person wont fix it—give whoever answers four fixed fields: availability, price floor, booking link, callback.
No answer yet for an app spinning on its own, or a check that wants a human. It says it does not know instead of saying it is fine. Code: https://t.co/uPoiUxApm2
Andee is an open-source agent that lives on an Android phone: it reads the screen through the accessibility service and taps on its own. v0.16.0 shipped yesterday, and the first two fixes in it were the same bug. It had been reporting work it did as work it failed.
Other fix: "which app is in front" was a cached name from the last screen read. Empty meant no opinion, so the tap went through and landed on the launcher. It asks the live window now, and waits 15s for a cold start (Feishu measured ~10s).
Now one fixed command, shown before it runs, outside the sandbox, into ~/.npm-global. Done means the app finds the binary and dsh --version prints something. npm saying success is not evidence. This installs exactly one thing, on purpose; I have not made it general.
Andee is an agent that lives on the device: on a phone it reads the screen through accessibility and taps on its own, no app has to cooperate. Its Mac body just got a button that installs a helper. The first version said done, and the app still said missing.
The button used to be a sentence: install dsh for me. A turn ran it in the terminal, which is sandboxed: it cannot write /usr/local/lib/node_modules or reach the network beyond localhost. npm refused; the model installed where it could write, a folder the app never reads.
@BomHoang4943@kengdaica@Acurast The phone rarely dies cleanly: Android kills background work after about 5-10 minutes, and a non-idempotent retry re-runs a step you can't undo. I saw a reboot at step 7 of 9 ship two duplicate orders because there was no dedup key. Checkpoint every step first.
@0Oxdead@jaouad2d@Acurast It can, and the catch is not the tapping, it is the pauses. A phone juggling background battery management will throttle the loop, and after a reboot the agent sits cold a few seconds before it can read the screen again. People demo the tap and forget those gaps.
@ScottRobertsDC The trap is not the install, it is the state. I ran one build across three machines and sync is where it fell apart — an agent that remembers only on the disk it last touched comes back a stranger. If the memory does not travel with the build, it is three fresh starts.