All guides

How to follow a Kiro session from your phone without SSH

A provider-specific guide for running Kiro on your computer and monitoring it from your phone, including kiro-cli login, conservative auth detection, and what “Unknown” really means.

Based on
CLI
0.1.0
Preview ref
f36aa45

Kiro is one of those providers that people tend to run on a “real” computer:

  • a laptop with the repo
  • a dev box
  • a server

And then the moment you stand up, you want the same thing everyone wants:

  • see whether it’s still running
  • see whether it needs input
  • send one follow-up

A lot of people default to SSH here.

This guide is the alternative: run Kiro where the repo is, then follow it from your phone.

TL;DR

  1. Install Kiro CLI (kiro-cli --version) on the computer that will run sessions.
  2. Log in with kiro-cli login.
  3. Don’t over-interpret auth status.
    • Kiro auth probing is conservative and may show Unknown even when login works.
    • Under the hood, Kiro is probed via kiro-cli whoami --format json when a safe status command is available.
  4. Use a phone-friendly session UI to follow the transcript and handle approvals.

The problem

Following a local CLI session from your phone is mostly about two things:

  • reliable connectivity to the computer running the session
  • reliable understanding of “is it logged in / is it ready?”

Kiro is particularly strict here because its auth probing is treated as manual-only.

So the workflow needs to be explicit.

What I tried first (and where I bounced off)

  • SSH: works, but it’s a terminal workflow on a phone.

  • waiting until I’m back at the keyboard: safe, but slow.

  • Happier: it gives me a phone UI to follow the session, handle approvals, and send one follow-up. Trade-off: it still depends on the computer running the session being online.

If you’re new to Happier (what it is, and where to get it)

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) for coding sessions.

Get set up:

Step 1: Install Kiro

From the provider docs, verify:

kiro-cli --version

Step 2: Log in (machine-local)

Kiro uses a machine-local login:

kiro-cli login

That means:

  • logging in on your laptop does not log in your server

A practical login checklist

On the computer that will run the session:

  1. Run kiro-cli --version.
  2. Run kiro-cli login.
  3. Verify the account explicitly:
kiro-cli whoami --format json

If that prints a user/account payload, you’re logged in on that computer.

Once it works once, you can stop thinking about auth unless something changes.

Step 3: Understand why auth status can be “Unknown”

In source, Kiro auth probing is defined as:

  • statusCommand: ['whoami', '--format', 'json']
  • parser: 'kiroWhoamiJson'
  • background checks: manual_only

That last point is why “Unknown” isn’t a bug.

It’s a safety posture: don’t probe aggressively in the background.

Step 4: The phone workflow

The phone loop is intentionally small.

If I had to describe it as one loop:

  1. open the session
  2. check whether it’s waiting on approval
  3. send one follow-up
  4. leave

What I do from my phone (and what I don’t)

I’m comfortable doing this from a phone:

  • approvals
  • short constraints (“stop after next step”, “summarize first”)
  • quick diff sanity checks

I avoid doing this from a phone:

  • big refactors
  • anything where I can’t verify the path/command

Three copy/paste follow-ups that work well for Kiro

  1. Checkpoint

Stop after your next step and summarize:

  • what you changed
  • what you didn’t change
  • what you want to do next
  1. Constraint

Don’t touch migrations/auth. If you think you need to, stop and ask.

  1. Verification

Before you keep going, paste the exact command you’re about to run and explain why.

If the session needs a real terminal intervention, I wait for a keyboard.

If you’re new to Happier

If you haven’t seen Happier before: it’s an open-source companion app that can run Kiro as a catalog-defined ACP provider and gives you a phone-friendly way to follow sessions.

Get set up:

Troubleshooting

Kiro shows logged out but I’m sure I logged in

  • run kiro-cli whoami --format json
  • if it prints account info, login worked

If it doesn’t, you’re not logged in on that computer (even if you are on another one).

The session isn’t updating

  • confirm the computer is online and the session runtime is still running
  • check whether it’s waiting on approval
  • reload/reopen the session

I’m seeing stderr noise from Kiro

Happier uses a Kiro-specific transport that suppresses a known optional notification “method not found” stderr pattern.

So if you see a one-off warning, it may be harmless.

FAQ

Why does auth look different across computers?

Because Kiro login is machine-local.

If you have multiple computers, each one needs its own kiro-cli login.

What does “manual-only” auth probing mean?

It means the app won’t aggressively probe Kiro auth state in the background. “Unknown” is a safe status, not necessarily a broken status.

kiromobileworkflows
Last updated: 2026-04-03