A coding agent finishes a branch while its owner is changing trains. The phone shows a permission request, a diff, and a merge button. Approving the wrong action takes one tap; understanding its blast radius takes much longer.
That is the friction Kilo Code mobile has to solve. The app makes agent work reachable away from a desk, but the small screen also compresses the context needed to judge a consequential change.
Neyrotex did not install Kilo Code, connect a repository, run an agent, or merge a pull request. We did not measure diff readability, notification latency, battery use, crash rate, command recovery, or the accuracy of generated code. This first look scores the documented product and current public evidence.
Kilo Code mobile first look: what has shipped?
Apple’s US listing showed version 1.0.15 on November 16, updated November 11, with iOS 16.4 or later required. Its eight ratings averaged 4.75, which is a storefront snapshot with too little volume to establish reliability.
The current mobile documentation covers iOS and Android. It lists Cloud Agent creation, control of remote CLI and editor sessions, queued follow-up messages, session search, file transfer, voice input, pull-request review, checks, comments, and merge actions.
Version 1.0.15 adds overnight briefs, Siri and Shortcuts actions, alert history, memory-proposal review, session deletion, and MCP App interfaces. Those are meaningful control-surface additions, but release notes do not prove that a long coding session survives a weak mobile connection.
What changes when the laptop is no longer the control point?
The full editor, terminal, file tree, and test output stay visible together. The operator can inspect several files before approving a command or merge.
The phone sends prompts and approvals to a CLI or editor session still running on a computer. That machine must remain online, and anyone who controls the Kilo account may be able to send it work while remote mode is enabled.
Kilo provisions remote compute, reads and changes an authorized repository, runs commands, and can optionally commit or push. The laptop can be absent, but repository scope, secrets, spend, and recovery become cloud controls.
A developer walking through a station concourse can glance at an unbranded phone while a backpack stays closed. The physical convenience is obvious: the coding environment no longer has to be in the developer’s hands.
The security trade changes with the destination. A remote session reaches the computer where the CLI is running; a Cloud Agent reaches a hosted environment and the repository selected through an integration.
Repository scope is the first real permission
Kilo’s GitHub integration can be installed for all repositories or only selected repositories. The same documentation points users back to GitHub to change the selected list or uninstall the app.
Choose selected repositories for a first trial. A sandbox repository with synthetic data limits the cost of a bad prompt, an unsafe dependency, or an incorrect commit without asking the permission UI to carry the entire defense.
GitLab needs a second cleanup step. Kilo says disconnecting the integration clears its tokens but does not itself revoke OAuth authorization on GitLab, so a full exit also requires revocation in GitLab’s authorized-applications settings.
Before the phone leaves the office, two teammates inspect one laptop and one face-down phone while they agree which repository and commands the agent may touch. The visible ritual should happen before the first mobile session, not after an unexpected branch appears.

A disposable-repository test
- Connect one repository that contains no production data, credentials, customer material, or deployment path.
- Use a branch that can be deleted. Set shell, edit, external-directory, MCP, and subagent permissions to ask or deny unless the task needs them.
- Ask for one bounded documentation change. Read the changed files, commands, checks, and cost before approving a commit.
- Interrupt the network, resume the session, reject one permission, and confirm that no hidden work continues.
- Revoke the repository integration and verify the revocation at the Git provider before adding a real project.
The permission model is granular, but defaults matter
Kilo documents allow, ask, and deny actions for tools and target patterns. Rules are evaluated in order, and the last matching rule wins. A broad rule placed last can therefore override the narrow exception a developer thought was protecting a command or path.
The settings documentation says most tools default to allow for a smoother start, while sensitive environment-file reads, external directories, and repeated-failure continuation prompt by default. A session-level auto-approve switch can also skip waiting permission cards for that session.
Cloud Agent documentation draws a harder boundary: autonomous mode is always on there, and the environment can modify code without per-action confirmation. That makes repository selection, branch policy, sandbox choice, secret handling, and push settings the practical guardrails.
Kilo’s sandboxing guide also warns that a denial for one file-reading tool is not a complete confidentiality boundary. Another allowed shell or search tool may reach the same file, so permissions need to cover every relevant path to the data.
Privacy and price both branch by configuration
Kilo’s mobile privacy notice says prompts and conversation content travel through OpenRouter to the AI provider selected for a request. Provider retention policies continue to apply after data has been shared.
Sentry receives anonymous crash and performance diagnostics without prompt content, according to that notice. AppsFlyer receives mobile attribution and app-event data without prompt content. The app presents a consent screen, and users can later revoke optional data sharing in Settings.
Apple’s privacy label is developer supplied and not verified by Apple. It declares identifiers used for tracking, user content and user IDs linked to identity, and coarse location, usage, and diagnostics not linked to identity. That label is a disclosure, not an independent audit.
The individual platform plan is free, Teams costs $15 per user each month, and Enterprise pricing is custom. AI inference is separate: users can choose free or local models, bring their own keys, pay provider rates through Kilo Gateway, or buy Kilo Pass from $19 a month.
Cloud compute is separate again. Kilo currently lists Docker and Small Cloud Agents at $0.60 per hour and Standard at $1.20 per hour, billed per second, with model inference charged separately.
Kilo Code mobile source-based score: 78/100
Cloud and remote sessions, queued prompts, files, voice, PR review, checks, comments, merge, shortcuts, and session search cover a broad mobile control job. Neyrotex has not verified long-session recovery or diff completeness.
The app consolidates active sessions and approval points. A phone still compresses branch context, command output, and multi-file review, while the safest setup requires work outside the app.
Free individual access and pay-as-you-go choices make a bounded trial practical. Platform, inference, payment fees, and compute are separate meters that need a budget.
Selected-repository access, granular permissions, telemetry consent, BYOK, and enterprise controls help. Write-capable agents, broad defaults, provider retention, remote-computer access, and third-party integrations keep the risk material.
Current docs describe explicit failure states, retry paths, and connection behavior. The low number of iOS ratings and absence of a Neyrotex device test leave real-world reliability unknown.
The app moved from its June iOS release to version 1.0.15 with new actions, briefs, alerts, MCP views, and reliability work. Anaconda’s July acquisition adds organizational backing without proving future support quality.
Sources checked
Product and store state: Kilo mobile documentation, Cloud Agent documentation, Apple App Store, and Anaconda’s acquisition announcement.
Access, data, and cost: integration controls, agent permissions, auto-approval defaults, sandboxing guidance, mobile privacy notice, and pricing.