If you do not want a SaaS browser farm holding the account, the subagents run on a Pi you own. Sessions stay on hardware you physically hold, cost is a one-time purchase rather than a per-instance subscription, and stopping does not require anyone’s cooperation.
The boundary
Microphone on your phone stays the voice agent that decides what is worth saying and when the claim should change. The Pi runs the subagents that execute the schedule. Judgment upstream, repetition downstream — and the repetition happens somewhere you can reach.
Self-hosted Pi, then set it up and connect it to Microphone.
Frequently asked questions
- What is wrong with a cloud browser farm?
- It is shared infrastructure holding your authenticated sessions so something can act on your accounts while you sleep. That is the largest concentration of trust in the workflow, sitting with a vendor whose incentives are not yours.
- What happens if I unplug the Pi?
- The routines stop. Being able to end the activity physically and immediately is the point, not a fallback.
- Is setup complicated?
- Flash a card, boot the Pi, run one install command, and pair the device with your account. After that you work in Microphone rather than on the device.