Junie
Junie, with a shorter commute.
Start a Junie session from your phone and let it work on your paired computer. Reply, read its output and answer its permission requests from wherever you ended up. Existing IDEA and terminal sessions aren’t attached. Saved Junie CLI histories are read-only.
From your phone
- Start Junie in a project on a paired computer where Junie is installed and signed in.
- Reply to the Junie session your phone started, and interrupt its current turn.
- Answer the permission choices Junie actually offers, with a complete preview where available.
- Read saved Junie CLI user messages and final answers beside your other agents.
Junie has its own remote, too.
Junie’s Remote mode continues an existing CLI session in a browser. It requires a Junie subscription through a JetBrains Account or Junie API token; BYOK alone isn’t enough, and JetBrains AI Enterprise sign-in isn’t supported.
Dashup runs a phone-started Junie session through its local ACP interface and keeps it beside your other agents. That’s a different starting point: it doesn’t take over the terminal or IDEA session you already have open.
Saved doesn’t mean available to take over
Junie’s saved history can’t reliably tell Dashup whether another process still owns the conversation. Those imported sessions stay read-only, including after a connector restart. Start a new Junie session from the phone for replies and approvals.
Junie keeps its own credentials, provider configuration and permission rules. Dashup doesn’t add model or settings controls, and a request without a complete preview is reviewed on the computer.
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