Opposable

• Letting Claude Code read the 2FA text that arrives mid-task and type the code into the app or site that asked for it
• Asking an agent to open a banking app, check a bill amount, and prepare the payment, with the final step waiting for your Approve tap
• Having a coding agent build an Android app and then exercise it on a real phone instead of an emulator
• Scheduling a daily phone task, such as checking whether a parcel has arrived, that runs while the laptop is closed and messages you the result
• Turning an old phone from a drawer into a dedicated agent phone with its own apps and accounts
• Renting a cloud Android phone so an always-on agent can use mobile-only apps without tying up your own device

Opposable is a practical answer to a real gap: coding agents can drive browsers and desktops, but the jobs that stall them, such as a 2FA code, a banking app, or a ride booking, live on the phone. Its design choices are sensible for that job. It gives the agent a labelled element list instead of only pixels, holds an outbound connection instead of opening ports, runs common tasks with no model, and requires an Approve tap for payments. The free tier is genuinely useful if your agent and phone share a network. The costs are trust and maturity. You sideload an accessibility app, keep the phone unlocked, guard a token that is effectively a password to your phone, and route screen contents through a relay if you want remote access, all from a team that launched in October 2026 and has not published developer docs or certifications. Start with a spare phone or a cloud phone and low-stakes apps, and keep payment approvals on before you point it at accounts that matter.

About Opposable

Most computer-use tools stop at the browser or the desktop, while banking, rides, messaging, and the one-time code in the middle of every sign-in live on the phone. Opposable fills that gap. On Android 11 or newer you sideload a 16 MB APK, switch it on as an accessibility service, and pair it with your computer; one `claude mcp add --transport http` command (or a few lines in Codex's config.toml) turns the phone into a tool in your next agent session. The agent gets each screen as a list of labelled elements with positions plus a screenshot when it needs one, and calls tools such as tap_element, swipe, type_text, launch_app, and press_key, each of which reports what it actually did. The phone keeps one outbound connection, so it works over USB, the same Wi-Fi, or from anywhere through Opposable's hosted relay without port forwarding. There is also a delegation mode: a REST call or MCP request hands the whole task to the phone, which runs it locally and returns done or not done, can run on a schedule (a Pro feature), and saves repeated tasks as recipes that replay without a model. About 40 everyday tasks (alarms, calendar, texts, settings) run with no model at all, and an on-device screen model handles the rest offline, so you can use it without any API key. Anything that looks like a payment pauses for an Approve tap on the phone, and actions are written to an audit log. iPhone support is a beta that needs no app on the phone: the Opposable Mac app (Apple silicon, macOS 14+) pairs with the iPhone as a Bluetooth keyboard and pointer and sees the screen over a cable or AirPlay, and on Windows or Linux a small ESP32-S3 stick flashed with Opposable's firmware does the Bluetooth part. If you have no spare phone, Opposable rents private virtual Android 15 phones from $19 a month. The phone app, its MCP server, and the REST API are free; Pro ($8/month) and Power ($29/month) pay for the relay, scheduled tasks, payment approvals from notifications, and recipe sync. The tradeoffs are real: the Android app is not on the Play Store, unattended runs need the phone charging and unlocked, the bearer token is effectively a password to your phone, relay traffic (which can include screen contents) passes through Opposable's servers, some banking apps refuse to run on the cloud phones, and the product launched on October 7, 2026, with the iPhone path explicitly in beta.