<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd" -->

---
title: Introducing @expo/agent-cli: the CLI designed for agents
description: Expo released @expo/agent-cli, an experimental CLI built specifically for coding agents working on Expo apps. The status command inspects a project and reports...
canonical: https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Introducing @expo/agent-cli: the CLI designed for agents | daily.dev
og:description: Expo released @expo/agent-cli, an experimental CLI built specifically for coding agents working on Expo apps. The status command inspects a project and reports...
og:url: https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd
og:image: https://api.daily.dev/og/posts/EoFYpc0Cd.png
og:image:alt: Introducing @expo/agent-cli: the CLI designed for agents
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introducing @expo/agent-cli: the CLI designed for agents

**[Expo Blog](https://daily.dev/sources/expo-blog)** · 9 min read · 1 upvotes · 0 comments

## Summary

Expo released @expo/agent-cli, an experimental CLI built specifically for coding agents working on Expo apps. The status command inspects a project and reports whether it works with Expo Go, needs a native rebuild, and what to run next, without launching the app. A single dev command (e.g. dev --ios) decides whether to use Expo Go or a development build and gets the app running, while smoke checks that it actually loads without runtime errors. With SDK 58, packages can ship co-located skills that sync via the CLI, and --eas lets agents opt into cloud builds via EAS without accidentally burning credits.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://expo.dev/blog/introducing-expo-agent-cli>

## Questions this post answers

### What does the @expo/agent-cli status command do?

It inspects an Expo project without launching the app and reports whether the project is compatible with Expo Go, whether a native rebuild is needed, and what command to run next. It's designed so a coding agent can check compatibility before making a decision rather than hitting a runtime error and debugging afterward. Run it with 'npx --yes @expo/agent-cli@latest status'.

_Developers wiring agents into Expo projects can follow CLI releases like this on daily.dev._

### How does @expo/agent-cli prevent AI coding agents from accidentally triggering paid EAS cloud builds?

By default the CLI stays local and will not switch to EAS on its own; you must explicitly opt in with the '--eas' flag or configure the project to use EAS. This matters because EAS builds and simulator sessions consume credits, and an agent could otherwise start a costly cloud build just because a local build failed.

_Teams budgeting cloud build credits can track tooling safeguards like this via daily.dev._

### What are co-located skills in the Expo SDK 58 agent tooling?

Co-located skills let individual npm packages, like expo-sqlite, ship their own agent skills alongside their code instead of bundling every skill into the central Expo agent plugin. Skills become available only when the package is installed, keeping agent guidance relevant to what a project actually uses. The approach builds on Anthony Fu's skills-npm convention and is synced via '@expo/agent-cli skills:sync'.

_Developers managing agent instructions across packages can keep up with conventions like this on daily.dev._

## Similar posts on daily.dev

- [Build an AI QA Agent for Expo Apps with EAS Workflows in minutes today](https://daily.dev/posts/build-an-ai-qa-agent-for-expo-apps-with-eas-workflows-in-minutes-today-920jfgips) · Expo Blog · 0 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#mobile](https://daily.dev/tags/mobile), [#cli](https://daily.dev/tags/cli), [#react-native](https://daily.dev/tags/react-native)

[View this post on daily.dev](https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Introducing @expo/agent-cli: the CLI designed for agents","url":"https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd"},"datePublished":"2026-10-27T16:49:21.038Z","dateModified":"2026-10-27T16:51:10.740Z","description":"Expo released @expo/agent-cli, an experimental CLI built specifically for coding agents working on Expo apps. The status command inspects a project and reports...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b96bea0eb105dfb2bde343433509a70f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b96bea0eb105dfb2bde343433509a70f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Expo Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Expo Blog","logo":"https://media.daily.dev/image/upload/s--E7LK6L3y--/f_auto,q_auto/v1774179051/logos/expo-blog?_a=BAMAMiWQ0","url":"https://daily.dev/sources/expo-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,mobile,cli,react-native","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Expo Blog","item":"https://daily.dev/sources/expo-blog"},{"@type":"ListItem","position":3,"name":"Introducing @expo/agent-cli: the CLI designed for agents"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-expo-agent-cli-the-cli-designed-for-agents-eofypc0cd#faq","mainEntity":[{"@type":"Question","name":"What does the @expo/agent-cli status command do?","acceptedAnswer":{"@type":"Answer","text":"It inspects an Expo project without launching the app and reports whether the project is compatible with Expo Go, whether a native rebuild is needed, and what command to run next. It's designed so a coding agent can check compatibility before making a decision rather than hitting a runtime error and debugging afterward. Run it with 'npx --yes @expo/agent-cli@latest status'. Developers wiring agents into Expo projects can follow CLI releases like this on daily.dev."}},{"@type":"Question","name":"How does @expo/agent-cli prevent AI coding agents from accidentally triggering paid EAS cloud builds?","acceptedAnswer":{"@type":"Answer","text":"By default the CLI stays local and will not switch to EAS on its own; you must explicitly opt in with the '--eas' flag or configure the project to use EAS. This matters because EAS builds and simulator sessions consume credits, and an agent could otherwise start a costly cloud build just because a local build failed. Teams budgeting cloud build credits can track tooling safeguards like this via daily.dev."}},{"@type":"Question","name":"What are co-located skills in the Expo SDK 58 agent tooling?","acceptedAnswer":{"@type":"Answer","text":"Co-located skills let individual npm packages, like expo-sqlite, ship their own agent skills alongside their code instead of bundling every skill into the central Expo agent plugin. Skills become available only when the package is installed, keeping agent guidance relevant to what a project actually uses. The approach builds on Anthony Fu's skills-npm convention and is synced via '@expo/agent-cli skills:sync'. Developers managing agent instructions across packages can keep up with conventions like this on daily.dev."}}]}
```

