Skip to main content

Your coding agent, in your pocket

Development work doesn’t have to wait. Start something new, pick up work already running, and step in when your input is needed, all from your phone. Sessions keep running while you’re on the move.

Requires a paid tier. Team and enterprise admins need to enable cloud sessions.

Loading image...
Kiro for Android new session screen with a white ghost icon and the heading Let's build, subtitled Plan, search or build anything. Below are a Connect repositories (optional) row with a badge showing 2 connected repositories and a Build with spec toggle switched off. The prompt field at the bottom reads: Move the request ID validation and generation logic into /myapp/common, then update the gateway to use the shared implementation.

Start from your phone

A new feature, bug, investigation, or follow-up. Fire up a new session, pick the repo, and get Kiro working right away.

Loading image...
Kiro for Android home screen listing cloud sessions with their repository and pull request status: fix metadata loss in structured logs (example/myapp-common, 1h ago, 1 merged), retry notification delivery after transient failures (example/notifications, 1h ago, 1 merged), request ID mismatch across service boundaries (example/myapp-common, 1h ago, 1 merged), jobs dropped during worker shutdown (example/worker, 2h ago, 1 merged), and order API latency regression (example/orders, 2h ago).

Check in from anywhere

Cloud sessions you start in Kiro IDE, CLI, or Web show up on your phone with the same context. See what’s running, what’s done, and where Kiro’s waiting on input. Open what needs attention and leave the rest running.

Loading image...
Kiro session titled Add RequestID Middleware to Notification Logs, across 2 repositories. Kiro recommends Option 2: request tracing shouldn't break traffic, but silent replacement hides client bugs, so it needs a small backward-compatible change in myapp-common, such as an onInvalid callback option. Whichever option is chosen, the rest of the work is the same: mount requestId before the routes in notifications/src/app.ts, and add requestId to the existing logger.info call. Kiro asks: Which option do you want? The reply reads: 2, but leave gateway as is for now.

Step in, keep it moving

Answer a question, add context, or redirect the work right from your phone. Handle the decision and let Kiro keep going.

Loading image...
File Diff view for src/auth/utils.ts. Two removed lines, struck through in red: a getPostLoginRedirect() function that always returned '/dashboard'. Eleven added lines in green: the function now takes a Request, reads returnUrl from req.query.returnUrl or req.session?.returnUrl, returns it when isAllowedRedirect(returnUrl) passes, and otherwise returns '/dashboard'.

Review the work, ship it

Review changes in mobile-friendly diffs. Ask Kiro for another pass, or open a pull request when the work is ready, all from your phone.

Common questions

Start from your phone. Come back to a PR.

Requires a paid tier. Team and enterprise admins need to enable cloud sessions.