All your agents
Several agents. One inbox.
Keep Claude Code, Codex, OpenCode, Kimi, Cline, Pi, Kilo Code and Junie in one phone inbox across your paired computers. See what needs you without touring every window. Controls depend on how each session connects.
From your phone
- Needs you, Working and Recent, across every agent on every computer.
- Alerts when an agent asks something, hits an error or finishes, opening the exact conversation.
- A page for each computer, with its sessions and the login and usage details its agents expose.
- Search every thread and project. Pins, archives and thread names stay on your phone.
- Subagents fold under the thread that started them.
- Zed and VS Code projects and conversations join the same list.
- Cline uses existing local hubs; Pi stays in its current TUI; Kilo uses its local daemon. Junie sessions started from your phone take replies and permissions; imported Junie history is read-only.
One vendor per remote
Claude’s Remote Control shows Claude Code sessions. Codex Remote shows Codex in the ChatGPT desktop app. Kilo has its own mobile app, and Junie has a browser remote for its CLI. Each follows its own agent.
Dashup keeps the agents you run in the same inbox. A computer can run more than one. Its owner can sit down for a minute.
Claude Remote ControlCodex RemoteKilo mobileJunie Remote mode
We’re still out of the loop
Every agent’s conversations reach Dashup’s servers end-to-end encrypted, with the keys on your paired devices. The servers hold ciphertext they can’t read.
Details of other products checked against their documentation in October 2026.
Set up once. Then leave.
Run this on each computer you want on your phone, scan its code with the Dashup app, and let Dashup keep running in the background. The computer has to stay on. Dashup can’t wake it.
npx @dashup/connector pair