> ## Documentation Index > Fetch the complete documentation index at: https://kiro.dev/llms.txt > Use this file to discover all available pages before exploring further. # Setup & First Run > Install Kiro Mobile on Android or iPhone, sign in, and start your first session. Get started with Kiro Mobile by installing the app, signing in with the account you use on other Kiro surfaces, and starting a session. ## Requirements - **Android:** Android 10 or later - **iPhone:** iOS 26 or later - A Kiro Pro, Pro+, Pro Max, or Power subscription - A GitHub or GitLab repository provider connected in [Kiro Web](https://kiro.dev/docs/web/setup.md), if you want the agent to work in your repositories ## Install the app Android iPhone ### Get the app Open [Kiro on Google Play](https://play.google.com/store/apps/details?id=dev.kiro.mobile), or search for **Kiro** in the Google Play app. ### Install and open Kiro Install the app, then open it to [sign in](#sign-in). Kiro for iPhone is in early access through Apple TestFlight. ### Request early access [Request early access](https://kiro.dev/mobile/). Invites go out to a limited number of people as the rollout expands. ### Install TestFlight When you receive your invite, install Apple's **TestFlight** app on your iPhone. ### Install Kiro Open the invite link and install Kiro from TestFlight, then open it to [sign in](#sign-in). ## Sign in Kiro Mobile supports the same sign-in options as Kiro Web. When you finish signing in, your sessions, connected repositories, model choices, and settings are already there. ### Your organization Use this option if your Kiro account is managed by an admin, through AWS IAM Identity Center or an external identity provider such as Okta or Microsoft Entra ID. **⚠️ Warning:** Kiro Mobile uses the same access as Kiro Web. Your administrator must turn on **Cloud Sessions** in **Settings > Kiro Settings**, in the AWS account that owns the Kiro profile, before you can start or continue sessions. Kiro Mobile is available in **US East (N. Virginia) (`us-east-1`)** only, and it requires a Kiro profile. It doesn't work with Q Developer profiles. 1. Open the app and tap **Enterprise sign-in**. 2. Under **Work email or start URL**, enter one of these: - Your work email, or the Kiro start URL your admin gave you, if your organization uses an external identity provider. - Your organization's start URL, if your organization uses AWS IAM Identity Center. 3. If your admin gave you an AWS Region, tap **Select AWS region - optional** and enter it. 4. Tap **Continue**, then finish signing in with your organization's credentials in the browser window that opens. You return to the app when you're done. 5. If you have more than one Kiro profile, choose the profile to use. See [AWS Identity Center](https://kiro.dev/docs/web/identity-center.md) for the settings shared between Kiro Web and Kiro Mobile, and [Authentication](https://kiro.dev/docs/getting-started/authentication.md) for how each sign-in method works. ### Social login and AWS Builder ID 1. Open the app and tap **Other sign-in options**. 2. Choose **Sign in with Google**, **Sign in with GitHub**, or **Builder ID**. 3. Finish signing in the browser window that opens. You return to the app when you're done. ## Connect your repositories Kiro Mobile works with the GitHub and GitLab repositories you've already connected to your account. The app shows your connection status under **Settings > Git Providers**, but you connect or change providers in Kiro Web. See [Connect GitHub](https://kiro.dev/docs/web/setup.md#connect-github) and [Connect GitLab](https://kiro.dev/docs/web/setup.md#connect-gitlab). ## Your first session 1. On the sessions list, tap the new session button in the bottom-right corner. 2. Tap **Connect repositories** and choose the repositories the agent can work in. 3. Describe your task and send it. The session starts in the default mode, where you iterate with the agent. To plan with a spec or hand off the whole task, turn on **Build with spec** or **Autonomous** first. See [Work modes](https://kiro.dev/docs/mobile/sessions.md#work-modes). After you send, the chat opens with your message, and **Working...** shows while the agent starts. The first reply takes longer than later ones, because Kiro first sets up the session's cloud sandbox and clones your repositories. Those steps appear in the chat as status rows, such as **Cloning repo**. If the session doesn't start: - **Unable to create new session**: Send your message again. If it keeps failing, check that you signed in with the right Kiro profile. - **No internet connection. Your message wasn't sent.** (Android): Reconnect, then tap **Retry**. The app keeps your message. - If you sign in through your organization, check with your administrator that **Cloud Sessions** is turned on. See [Your organization](#your-organization). The agent works in its cloud sandbox, so you can close the app and come back later. In the default mode, ask the agent to open a pull request or merge request when the changes are ready. In **Autonomous** mode, it opens one for you. See [Working with sessions](https://kiro.dev/docs/mobile/sessions.md) for everything you can do while a session runs. ## Next steps - [Working with sessions](https://kiro.dev/docs/mobile/sessions.md) - [Settings](https://kiro.dev/docs/mobile/settings.md) - [Cloud sessions](https://kiro.dev/docs/cloud-sessions.md)