Pair once
Start kimi rc on your machine and scan the code. No public IP, no port forwarding.
Run kimi rc on your computer, scan the code. After that the session is on your phone too.
Set it up once. After that it behaves like any other app.
Start kimi rc on your machine and scan the code. No public IP, no port forwarding.
Type the task on your phone and the output comes back as it runs. The actual work happens on your computer.
When a command needs a yes, you get a notification. One tap and the session keeps going.
The parts of the desktop session you actually reach for.
Paired computers show up with a name, a platform and whether they are online. Pick one and you are in.
Messages, tool calls and terminal output stream back as they happen. Nothing to refresh.
Open a file on the remote machine or pull up a shell when a task needs a closer look.
A command that needs a yes arrives as a notification. Tap once in the shade and the session keeps running.
Pairing, the session, approvals. The rest lives in settings.
01 — Pairing
02 — The session
npm installApprovals land as a notification. One tap and the run continues.
03 — Approvals
The things people ask before installing.
No. The phone and the computer connect through Kimi's relay service, so both can sit behind an ordinary router.
Yes, the same account you use for Kimi Code on the desktop. Sign-in happens on Kimi's account page; the password never passes through this app.
On your computer. The app receives what the session prints; we do not keep a copy.
The connection drops and the device shows as offline in the list. Reconnect once the computer is awake.
Android 8.0 and later.
No. There is no analytics SDK, no advertising and no third-party crash reporter in the app.
Sign-in credentials are stored locally with AndroidX Security (AES256). No analytics, no ads, and no third-party crash-reporting SDK.