Working with sessions

Sessions are the center of Kiro Mobile. The sessions list is the first thing you see after you sign in, and each session opens into a live conversation with the agent. Every session runs in Kiro's cloud sandbox, so closing the app doesn't stop the agent.

The sessions list shows the sessions on your account, including sessions you started from Kiro Web, the IDE, or the CLI as cloud sessions. Each row shows:

• The session's title
• The repository it works in, if any, with a count such as +2 when it works in more than one
• How long ago the session was active, such as 13h ago
• The pull requests, merge requests, or code reviews it opened, with a status badge such as 1 open, 1 merged, or 1 closed

Spec and autonomous sessions also show a small mode icon before the time.

1. On the sessions list, tap the new session button in the bottom-right corner.
2. Tap Connect repositories and choose one or more repositories. Use Search repos to find a repository by name.
3. Optionally, turn on Build with spec or Autonomous. See Work modes.
4. Optionally, choose a model. Auto picks a model for the task. See Models.
5. Describe the task and send it.

To add repositories, connect GitHub or GitLab in Kiro Web first.

Kiro Mobile uses the same modes as Kiro Web:

• Default mode: you work with the agent interactively and iterate on a problem together. A new session starts in this mode.
• Spec mode: turn on Build with spec before you send your first message. The agent asks which kind of spec you want, such as a Feature Spec, a Bugfix Spec, or a Quick Spec. It then turns your request into the spec documents for you to review, and implements the approved tasks.
• Autonomous mode: turn on Autonomous in the chat input bar, either before your first message or later in the session. The agent builds a plan, does the work, and opens pull requests or merge requests.

Spec mode and autonomous mode can't be combined. A spec session stays a spec session, so Autonomous isn't available in it.

To delete a session, swipe left on its row in the sessions list, then confirm Delete. Deleting removes the session from Kiro Mobile and Kiro Web.

Open a session to see the full conversation. As the agent works, its activity streams in without a refresh:

• Replies render with headings, lists, tables, and code blocks.
• Tool activity shows each step the agent takes, such as reading files or running commands. Tap a step to see its inputs and outputs.
• Diff cards show each file the agent edits, with added and removed lines.
• Subagents appear as their own blocks when the agent delegates work. See Subagents.
• Context usage shows how much of the model's context window the session has used.

Older messages load when you scroll up, using Load earlier messages.

Your messages go to the same session running in the cloud, so you can steer the agent from your phone in these ways:

• Reply to add direction, correct course, or ask the agent to continue.
• Attach images, such as screenshots or mockups, with Attach image.
• Answer the agent's questions. When the agent pauses to ask you to choose, such as which kind of spec to create, the app shows the question with an option for each choice. Tap an option, or type other instructions instead.
• Stop a running turn with Stop.

In a spec session, the spec opens on its own when the agent finishes a turn that writes spec documents. To open it yourself, tap the spec button in the session header. On iPhone, you can also tap View Spec below the conversation.

The spec has a tab for each document: Requirements, Design, and Tasks. A tab is available once the agent has written that document. For a Bugfix Spec, the bug analysis in bugfix.md doesn't have a tab; read it in Kiro Web or ask the agent to summarize it. Use the button at the bottom of each tab to move to the next phase:

• Requirements: Generate design, or Generate design & tasks to create both at once
• Design: Generate tasks
• Tasks: Run all tasks to have the agent implement every task. On iPhone, you can also tap a single task to run only that one.

When you tap one of these buttons, the spec closes and the agent's work streams into the conversation.

In the default mode, ask the agent to open a pull request on GitHub or a merge request on GitLab when you're happy with the changes. In Autonomous mode and spec sessions, the agent opens one when it finishes the work. Its status shows on the session row, so you can tell at a glance what's open, merged, or waiting on you. You review and merge in your Git provider, the same as work you start from Kiro Web.

Sessions belong to your account, not the device. You can start a session on your phone and continue it in Kiro Web, or attach to it from the CLI or IDE. See Move between surfaces.