Coding agents changed what a working session looks like. You describe a change, the agent works for a few minutes, and then it either finishes or stops to ask something: may I run this command, which of these two approaches do you want, does this plan look right? If you have stepped away from the desk, the work waits for you.
Clawdex is our answer to that. It is a phone app that connects to the agents running on your own computer, so you can follow a run, answer its questions, and approve its actions from wherever you are. It supports Codex, Cursor, and OpenCode, and it is free to download on the App Store (opens in a new tab) and Google Play (opens in a new tab).
Two parts: the app and the bridge
Clawdex is deliberately not a cloud service. The agents keep running where they already run, on your Mac, Linux machine, or private server, next to your code and your tools. What Clawdex adds is a small program on that machine, the bridge, and the app on your phone that talks to it.
The bridge ships on npm as clawdex-mobile. Setting it up is two commands:
npm install -g clawdex-mobile@latest
clawdex initclawdex init asks which agents you want to use, writes its configuration, starts the bridge in the background, and prints a URL, a token, and a QR code. You scan the code with the app and you are paired. The package includes prebuilt bridge binaries for supported macOS, Linux, and Windows hosts, so normal setup does not compile anything.
The bridge itself is written in Rust. For Codex, it starts codex app-server as a child process and talks to it over standard input and output. The phone connects to the bridge over a WebSocket, authenticated with the bridge token. The same bridge can run Codex, OpenCode, and Cursor side by side, and the app switches between them.
Private by default
Because the bridge can run commands on your machine, where it listens matters. Clawdex is built for a trusted private network: your local network, a VPN, or Tailscale. The bridge requires its auth token, and the setup guide is explicit that it should never be exposed directly to the public internet. Your code and your agent sessions stay on machines you control.
Keeping a phone in sync with a live agent
Phones drop connections all the time, so the bridge keeps a log of recent events, each with an ID. When the app reconnects, it asks for whatever it missed and replays it, and it falls back to periodic syncing of the saved conversation history so the screen always catches up.
There is one honest limit, documented in the repository. If you start a turn from the Codex command line on your computer, outside the bridge, the app still shows the main messages once they are saved, but the fine-grained live detail, such as each tool call as it happens, is only guaranteed for runs that go through the bridge.
From first commit to two app stores
The whole history is public on GitHub (opens in a new tab), commit by commit:
- 20 February 2026: the first commit.
- 23 February: the bridge is published to npm, and version 1.1 adds a full Git diff view with staging and commits from the phone.
- 11 March: the iPhone app is released on the App Store. OpenCode support follows later that month.
- April: Clawdex gets its own site at getclawdex.com (opens in a new tab), version 5.1.2 adds a browser for opening web apps running on the bridge machine, and the Android app opens to testers.
- May: the Android app goes live on Google Play. Version 5.2.0 on 18 May adds Cursor, and 5.2.3 on 30 May adds push notifications.
Notifications without keeping the app open
Notifications took some care. When the app is in the background, its WebSocket closes, so the phone cannot be the one listening. Instead, the always-on bridge sends the notification when an agent finishes or needs approval, through Expo’s push service, which hands it to Apple or Google. Approval notifications have Approve and Deny buttons that resolve over the authenticated bridge connection without opening the conversation.
A completed-turn notification can include a short preview of the agent’s last reply, capped at 140 characters. That snippet passes through Expo, Apple, or Google on its way to your phone, which the Clawdex privacy policy (opens in a new tab) discloses, and notifications can be turned off or narrowed per event in Settings.
What you need
- A computer you control, with Node.js 20 or later, to run the bridge.
- Your own access to the agent you use: for example, a Codex subscription, or a Cursor account API key for Cursor.
- A private network path between the phone and that computer: the same local network, a VPN, or Tailscale.
Clawdex is open source under the MIT licence. Setup steps are in the bridge setup guide (opens in a new tab), and bugs and ideas are welcome as GitHub issues (opens in a new tab).