Kilo Code
Kilo, in the same inbox.
Follow sessions in Kilo Code’s local daemon, reply to them and answer their requests from your phone. Keep Kilo beside the other agents you run. You can stop arranging your day around whichever one asked last.
From your phone
- Reply to the existing session, steer a running turn or queue a follow-up.
- Answer native permission requests and questions. Edits without a full diff stay on the computer.
- Start a session in a project on a paired computer where the Kilo daemon is running.
- Read replies and tool output, and interrupt a turn.
Yes, Kilo already has a phone app.
Kilo’s own iOS and Android app supports remote CLI and extension sessions, plus Cloud Agents. If Kilo is all you run, start there.
Dashup puts Kilo with your other agents across your paired computers. Its connector talks to the local daemon; conversations and phone commands reach Dashup’s servers as ciphertext, with the keys on your paired devices.
Connect the local daemon
Run kilo daemon start on the paired computer and use that daemon’s sessions. Dashup discovers it locally; it doesn’t start a daemon just because you opened the app.
A standalone Kilo TUI, server or editor session outside that daemon isn’t attached by this integration. Phone permissions show the native rule being saved when “Always allow” is available. If an edit’s full change can’t be shown, review it at 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