Cline
Cline has a question. You have a sofa.
Read and reply to Cline’s existing SDK and CLI hub sessions from your phone. Keep the same conversation, answer its permission requests, and leave your computer to do the actual work. Older editor extensions without a hub aren’t covered.
From your phone
- Reply to the existing session, queue a follow-up or steer its current turn.
- Review a native tool request and allow it once or reject it. Requests without a complete preview stay on the computer.
- Read streamed replies and tool activity, and interrupt a turn when needed.
- Keep Cline beside your other agents, across the computers you’ve paired.
One session. Fewer trips to the desk.
Cline’s local hub lets several clients share a session. Dashup joins that existing hub and follows the original conversation. Opening it on your phone doesn’t start another Cline agent.
Cline also offers its own hub dashboard and connectors. Dashup’s reason to be here is the shared phone inbox: Cline beside Claude Code, Codex, Pi and the rest, with conversations encrypted between your paired devices.
Which Cline sessions?
Start Cline normally with a version that exposes its local hub. Dashup discovers that hub on the paired computer; you don’t have to start sessions through Dashup.
An older Cline editor extension without a hub won’t acquire phone controls. Dashup doesn’t launch or restore Cline sessions, change their settings, or take over requests that need their original interface.
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