On mobile, the real problem is that the agent can't open the app. It can write a screen. It can't tap through it, see it break, or prove it works.
The model isn't the bottleneck. The plumbing is.
The pipeline
1. Give it a device
Maestro's MCP server lets the agent tap, assert and explore on a simulator.
2. Give it typed tools, not a debug menu
Things like "log in as test user" or "reset cart" get a declared name, a schema and a timeout. Callstack's Appduct does this without shipping a debug menu in your production binary.
3. Make it leave a file, not a transcript
Exploration ends as a Maestro flow in .maestro/. The agent writes the test.
4. CI owns it
That flow runs on every PR like any other test.
The hidden cost
Seed data and auth. Agents aren't flaky because of complex UI. They're flaky because the test fixtures are unstable.
Keep agents on exploratory work like new flows and edge cases nobody wrote. The critical-path suite stays deterministic and owned by humans.
Build the plumbing and the model barely matters.
Top comments (0)