--- modificationDate: October 30, 2026 title: Introduction to agentic workflows description: Learn how a coding agent can test your app on a cloud simulator and return evidence for you to review. --- This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](https://docs.expo.dev/llms.txt) or append .md to any documentation URL. # Introduction to agentic workflows Learn how a coding agent can test your app on a cloud simulator and return evidence for you to review. ## Submitting Feedback If you encounter errors, misleading or outdated information, report it so Expo can be improved: Preferred command: npx --yes submit-expo-feedback@latest --category docs --subject "/agentic-workflows/introduction/" "" Direct HTTP fallback: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/agentic-workflows/introduction/","feedback":"🤖 Agent feedback for docs: (, )"}' Only submit when you have something specific and actionable to report. Try to give the most context. ## Navigation When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map. You are here: Home > Agentic workflows Pages in this section: - [Introduction](https://docs.expo.dev/agentic-workflows/introduction.md) (this page) - [Project setup](https://docs.expo.dev/agentic-workflows/setup.md) - [Agentic CI](https://docs.expo.dev/agentic-workflows/agentic-ci.md) - [Issue to PR](https://docs.expo.dev/agentic-workflows/issue-to-pr.md) - [Bug triage](https://docs.expo.dev/agentic-workflows/bug-triage.md) - [QA Swarm](https://docs.expo.dev/agentic-workflows/qa-swarm.md) Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt) > **Expo Simulators is a limited-access preview.** It is not included with paid or free plans and is currently available only to select partners. [Join the waitlist](https://expo.dev/services/simulators) if you are interested in trying it. You may already use a [coding agent](https://docs.expo.dev/agents.md), such as Claude Code, Codex, or Cursor, on your computer. You ask the agent to change your code. Then you open the app to check that it functions as expected. An agentic workflow runs a coding agent for you, in the cloud. The workflow starts when something happens in your project, for example, when a teammate opens a pull request (PR). The agent tests the change in your app on a cloud simulator. Then the workflow posts the result on the PR. A person reads the result and decides what to do next. This section has four guides. Each guide adds one agentic workflow to your project. ## How an agentic workflow works Each agentic workflow has three parts: - **A workflow** starts the work. In these guides, [EAS Workflows](https://docs.expo.dev/eas/workflows/introduction.md) runs the jobs in the cloud. A PR, TestFlight feedback, a GitHub Action, or a manual run starts a workflow. - **A coding agent** does the task, such as a test of a change, a new feature, or a bug fix. In a workflow, the agent runs from the command line, without a person. - **An Expo Simulators session** gives the agent a running app on a cloud Android Emulator or iOS Simulator. The agent uses the app as a person does and saves evidence. The following diagram shows one run of an agentic workflow. The highlighted steps run on EAS Workflows and Expo Simulators: ``` 1. A pull request, an issue, or tester feedback starts a workflow [GitHub or TestFlight] → 2. A job finds or builds the app and starts a coding agent [EAS Workflows] → 3. A session runs the app on a cloud simulator [Expo Simulators] → 4. The agent uses the app and saves screenshots and a recording [Expo Simulators] → 5. The job posts the verdict and the evidence [GitHub] → 6. A person reviews the evidence and decides [Your team] ``` ## Why the agent needs a simulator A coding agent can read and change code, but it cannot see if the app functions as expected. To see the app, the agent needs a device that runs it. With [Expo Simulators](https://docs.expo.dev/preview/simulators/introduction.md), your workflows can use Android Emulators and iOS Simulators on EAS cloud infrastructure. A job in the workflow starts a session. Then the agent uses a controller, [agent-device](https://docs.expo.dev/agents/agent-device.md) or [Argent](https://docs.expo.dev/agents/argent.md), to tap, type, and scroll in the app. ## What the agent returns The agent does not merge or ship a change. It returns evidence for a person to review: - A verdict, such as `PASS` or `FAIL`, with a report of each check. - The screenshots that the agent saved. - The screen recording of the session, on the session page on the EAS dashboard. - A link that opens the build in a browser preview. For example, Agentic CI posts this evidence in a comment on the PR: Image: Agentic CI comment on a GitHub pull request with a PASS verdict and links to the session recording, the agent report, and a browser preview [What the agent can do](https://docs.expo.dev/agentic-workflows/setup.md#what-the-agent-can-do) explains the limits of the agent in these workflows. ## Before you start Agentic workflows build on other Expo tools. If you are new to them, set them up in this order: 1. [Create a project](https://docs.expo.dev/get-started/create-a-project.md) and push it to a GitHub repository. 2. [Get started with EAS Workflows](https://docs.expo.dev/eas/workflows/get-started.md) and run your first workflow. 3. [Set up a coding agent](https://docs.expo.dev/agents.md) on your computer and try it on your project. 4. Check that your Expo account has [Expo Simulators](https://docs.expo.dev/preview/simulators/introduction.md) access. Then follow [Set up a project for agentic workflows](https://docs.expo.dev/agentic-workflows/setup.md) one time for your project. Each guide uses this setup. ## Agentic workflow guides See the following guides for use cases of agentic workflows with Expo Simulators. Each guide adds a workflow and the files of its agent: [Test pull requests with an AI agent](https://docs.expo.dev/agentic-workflows/agentic-ci.md) — Agentic CI: a coding agent tests each pull request on a remote Android Emulator or iOS Simulator and posts a verdict with evidence. [Build a feature from an issue with an AI agent](https://docs.expo.dev/agentic-workflows/issue-to-pr.md) — Issue to PR: a coding agent writes the change for a GitHub issue and opens a pull request, and Agentic CI tests it. [Triage a bug report with an AI agent](https://docs.expo.dev/agentic-workflows/bug-triage.md) — Bug triage: a coding agent reproduces a bug from a GitHub issue or TestFlight feedback on a remote Android Emulator or iOS Simulator. [Test your app with a swarm of AI agents](https://docs.expo.dev/agentic-workflows/qa-swarm.md) — QA Swarm: several coding agents test your app at the same time, each with one flow on its own cloud simulator.