Opposable is computer use for phones. It gives AI agents thumbs: Claude Code, Codex, Cursor, any MCP client, or the free agent built into the app can see, tap and type across every app you are already signed into on a real Android phone, the one in your pocket or a private phone rented in the cloud. The agent reads a screenshot and the screen as a list of labelled elements, opens apps, taps, swipes and types, and every call reports what it actually did. Everyday tasks like alarms, calendar, calls and texts run on the phone with no model at all, payments always stop and wait for your Approve tap, and iPhones work in beta through Opposable for Mac.
Most of your life runs through phone apps, and none of them have an API. Banking, rides, delivery, messaging and the two-factor prompt in the middle of every workflow are exactly where agents cannot currently go, which is why handing work to an AI usually ends with you copying a code between two screens. Reval Labs is building the layer that lets agents use those apps, on the phone you own and on phones the company runs for you, so an agent can open the banking app, check the amount, read the verification text and stop only for the one tap a person has to make.
Getting an agent onto a phone is deliberately small. The Android app shows its address and a token, and the phone becomes a tool in your next session with one command, for example claude mcp add --transport http phone https://.p1.getopposable.com/mcp with a bearer token header. Codex takes a few lines in ~/.codex/config.toml, and Cursor or any other MCP client works the same way. Opposable also ships as a connector for the Claude and ChatGPT apps: install the Android app, turn it on in Settings Accessibility, paste https://getopposable.com/mcp into a custom connector, then sign in, pick your phone and allow access. It is free for 14 days per phone, then part of Pro. No model API key is needed, because Claude Code or Codex think on the subscription you already pay for.
Most phone agents send your screen to a model in a data centre. Opposable's own agent runs on the phone it operates, so it keeps working with the laptop closed or with no signal, and the screen never leaves the device. About 40 tasks, including alarms, reminders, calendar, calls and texts, camera, settings, volume, maps and conversions, run with no model at all in 0 to 15 seconds each, and each one checks its own result on the screen. Everything else uses a 1.4 GB screen model that looks at the screen and taps like you do, plus a 0.7 GB answer model that answers questions from web results. On recent Snapdragon phones the vision step runs on the NPU; on a Galaxy S25 it was measured at about a quarter of a second, roughly 16 times faster than on a laptop CPU. Whatever Claude does once on your phone can be saved as a routine and replayed by the phone on its own in seconds.
The screen is exposed as both a screenshot and a structured list of labelled elements with their positions, cheap enough to read on every step. The agent acts with simple tool calls such as tap_element, swipe, type_text in any language, launch_app and press_key, and every call reports what it actually did. Alongside MCP there is a plain REST endpoint and webhooks: posting a task to /api/do returns a status, a result and a duration in seconds, which makes Opposable callable from cron jobs, n8n and Zapier. Tasks can be scheduled daily or every few minutes, so the phone wakes, does the work and messages you the outcome. Connections run over USB, over the same Wi-Fi, or from anywhere through the hosted relay, where the phone keeps one outbound connection and there is no port to forward. Money never moves on its own: payments and purchases stop and wait for your Approve tap on every plan, and Pro lets you approve or deny from the phone's notification.
The approach is model-neutral and phone-local. The same surface, one Android app with its own MCP server, a REST API, and a relay that reaches any phone, can be driven by Claude, Codex, OpenAI-compatible endpoints or the on-device agent, so you choose the brain without changing the hands. Because the phone's model runs locally, inference keeps working with no network and no screen data leaving the device, and because the phone only dials out, it can be operated on mobile data without exposing it to the internet. Pricing follows the same split: everything that runs on your phone is free, and you pay for what is annoying to host yourself, namely the relay, approvals and sync.
The practical benefit is that you can close the laptop instead of carrying it around half-open. A task handed to the phone is done locally and only the result comes back, so agents keep working on routines, scheduled checks and app-only workflows that were previously out of reach. You keep control of the consequential moments: the agent does the twenty taps, you make the one that matters. Pro adds an audit log of everything your agents did, and recipes backed up and shared across up to three phones, with automatic recipe repair when apps update listed as coming. Power covers up to ten phones with an audit log across phones, a shared recipe library for a small team and priority recipe repair, both coming.
Recorded, unedited runs show what this looks like in practice. In one demo, Claude Code over MCP turns on dark theme and sets a five-minute timer in 50 seconds across 17 tool calls. In another, the agent opens Chrome, goes to Wikipedia, reads the Apollo 11 launch date and crew, and returns 16 July 1969 with Armstrong, Collins and Aldrin for $0.44 and 118 seconds. A third run uses the on-device model to open Clock and the Stopwatch tab with no network calls for inference. Day-to-day examples from the site include reading the two-factor text the moment it lands and typing it where it is needed, opening the banking app to check the amount and stopping before paying, replying in chat apps in your voice with the whole thread in mind, booking a ride and sending the driver's ETA, reordering last week's grocery basket, and clearing the morning inbox by archiving, replying and moving invites into your calendar.
Opposable is built for people who already run agents: Claude Code, Codex and Cursor users, anyone with an MCP client, and teams running agents on several phones. The Android app is a 43 MB APK and needs Android 11 or later; iPhones work in beta when paired with a Mac, and on Windows or Linux a small Opposable Stick, about $8 to $13 with firmware installable from the browser, does the Bluetooth part. The Free plan covers the phone app, its MCP server and REST API, common no-model tasks, USB or same-Wi-Fi use, unlimited tasks and recipe replays, and the free on-device agent. Pro is $8/mo, $79 a year with founding members at $5/mo for life, and adds the hosted relay, scheduled tasks and webhooks while your laptop is closed, payment approvals from notifications, an audit log, and recipes backed up and shared across up to three phones. Power is $29/mo for up to ten phones. If you have no spare phone, cloud phones start at $19/mo with Cloud Starter, $49/mo for an always-on phone and $149/mo for three; some banking apps refuse to run on virtual phones, while your own phone has no such limits.
The takeaway: Opposable gives AI agents thumbs on a real phone, so the apps that never had an API become part of the workflow, free where it runs on your device and paid where you want remote access, approvals and control.
Publisher
A
admin
Launch Date2026-10-10
Platformweb
Pricingfreemium
Tech Stack
#MCP#REST API#Android#On-device model#Snapdragon NPU