How Mobster connects
Mobster for Mac, the terminal and your coding agent all reach the phone through Mobster on your Mac. Nothing goes through a Mobster server, unless you turn on Mobster Remote so that an assistant in the cloud can reach this Mac.- WebDriverAgent is an open-source test runner, built on Apple’s XCTest, that Xcode signs with your Apple Account and installs on the phone. The Mac app calls it Mobster’s helper. It listens on the phone’s own loopback, and Mobster reaches it over USB.
- Your coding agent drives the phone with its own model through
mobster mcp, or hands a whole task to Mobster’s agent withphone_task. - The model sees only what Mobster’s agent sends it, on your own key or a plan you already pay for. A check’s verdict never comes from a model.
One task, step by step
- Read. Mobster reads the screen’s tree: labels, values, roles and state. A step starts only once the screen has stopped changing.
- Decide. Mobster’s agent picks an action on a control in the tree, or a visible spot in its screenshot. Taps on unlabelled spots pass additional approval checks.
- Check. Before anything reaches the phone, the action is compared with your request, a ledger refuses to repeat a side effect, and a fresh read refuses a decision made on a screen that has since changed.
- Approve. A tap or submit that can send, buy, post, delete or submit waits for you. Approvals and safety has the rules.
- Act. The action is written to the journal before it’s sent, and an action whose outcome is unknown is never retried before a fresh read of the screen shows it didn’t happen. A consequential one asks you again.
- Finish. When the agent says the goal is met, Mobster reads the screen again and checks the task’s required receipts before reporting what it observed. A check file’s assertions give a verdict independently of the model.