Mobile Apps

Use Kilo Code from your phone to keep coding sessions moving while you are away from your desk. The mobile app connects to Cloud Agents, KiloClaw, and remote sessions from your local CLI or editor extensions.

ℹ️Android app available now

Install Kilo Code for Android from Google Play.

What you can do

The mobile app lets you:

  • View and manage Kilo Code sessions, including remote CLI and extension sessions running on your local machine.
  • Chat with KiloClaw from your phone.
  • Spawn Cloud Agents and code directly from the app.
  • Monitor and view all non-remote sessions in one place.
  • Create, onboard, and manage KiloClaw instances.
  • Send follow-up messages while a session is still running — they are queued and processed in order.
  • Run slash commands (like /compact) on connected remote CLI sessions, and start a new session in the same workspace with /new. Older CLI versions that do not support remote commands prompt you to upgrade.
  • Review GitHub pull requests end to end — diffs, checks, comments, and merging.
  • Start a new session on a connected kilo remote CLI instance with the Run on picker.

Kilo Pass and Billing

For Kilo Pass pricing, billing, and account management details, use the Kilo Pass pricing page.

Kilo Code mobile home screen showing KiloClaw and active agent sessions
Start coding tasks, open KiloClaw, and resume active sessions from the mobile home screen.
Kilo Code mobile new session screen with coding mode selector
Create a new Cloud Agent session and choose the right mode for the task.
Kilo Code mobile session chat with an active coding task
Review progress and continue coding conversations from the mobile app.
KiloClaw chat in the Kilo Code mobile app
Chat with KiloClaw on mobile.
Kilo Code mobile session filter panel for Cloud Extension CLI Slack and other platforms
Filter sessions by platform and project, including Cloud, Extension, CLI, Slack, and other sessions.

Choosing where a session runs

The new-session screen includes a Run on picker that chooses where your session runs:

  • Cloud Agent — the managed cloud environment (the default).
  • A connected CLI instance — a kilo remote CLI running on your own machine. The picker lists the instances currently connected to your account.

Remote sessions use the CLI's own defaults, so the composer skips model, mode, and repository selection; you type your first prompt in the chat after the session starts. Sessions started in an organization context always run on the Cloud Agent, so the picker does not appear there.

Queueing follow-up messages

The composer stays editable while the agent is working, so you don't have to wait for a session to finish before sending your next message. Type your follow-up and press Send to add it to the session's queue; queued messages are processed in order. While a session is streaming, Stop appears only when the composer is empty — with text entered, Send takes its place.

A queued message shows a subtle Queued badge on its bubble. The badge clears when the message starts processing or when the queue drains or is cancelled. Queueing works for Cloud Agent sessions and for remote sessions on a connected kilo remote CLI instance.

Reviewing GitHub pull requests

Open a pull request from a PR link to review it without leaving the app:

  • Overview — PR state and CI checks at a glance.
  • Files — syntax-highlighted diffs with line-level comments and a file navigator.
  • Discussion — review threads with replies, resolve/unresolve, and reactions.

Comments you leave are collected into a pending review on your device and submitted to GitHub as a single review. When the PR is ready, you can merge it (merge, squash, or rebase), enable or disable auto-merge, or update the branch — all from the app.

PR review uses your connected GitHub account; the app asks you to connect GitHub if you have not already.

Session cost and model details

The app shows what each session cost and which models did the work:

  • Session list — a finished session with a recorded cost shows it in the row's meta line (for example, $0.12 · 5m ago). Sessions that are still running or have no cost show no cost.
  • Cost breakdown — open a session's Context usage sheet to see a Token usage section (input, output, reasoning, cache read, and cache write tokens, plus the cache hit rate) and a collapsible Models section with each model's name, provider, step count, and cost. A Subagents row covers any remaining spend, so the per-model costs always add up to the session total.
  • Per-message model label — assistant messages show a dimmed model label on the first assistant reply and whenever the model changes during the session. Turns routed by Auto Model show the concrete model that handled the turn.

Cost is recorded when a session closes; sessions that closed before this feature shipped do not show a cost.

Android App

The Android app is available now on Google Play.

Install the Android app →

iOS App

The iOS app is in review with the App Store team and will be available soon. You can already sign up for the iOS waitlist to be notified when it launches.

Join the iOS app waitlist →