@expo/agent-cli weekly downloads statistics

@expo/agent-cli

Agent-native CLI on top of the Expo CLI family. Coding agents (and humans) use it to run Expo workflows and get machine-readable answers. It runs expo, eas-cli, expo-doctor, and friends as subprocesses. It does not import their internals.

Design documents: llp/0001-agentic-cli-on-expo-cli.rfc.md and its child LLPs in this package.

Start here

Step	Command	Gets you
1. Check the project	npx @expo/agent-cli status	what this project is, and what to run next
2. Start the app	npx @expo/agent-cli dev --ios --detach	the dev server starts, the terminal comes back
	npx @expo/agent-cli navigate /	the app opens a route, on a device
3. Edit and reload	npx @expo/agent-cli runtime:reload	after your edit, the app runs the code on disk
	npx @expo/agent-cli runtime:errors	what it threw, over a time window
	npx @expo/agent-cli runtime:tree	what is on screen, and its testIDs
4. Verify before you're done	npx @expo/agent-cli smoke --ios	the app on the code on disk, and one exit code
	npx @expo/agent-cli typecheck	the type errors neither of those can see
5. Release	npx @expo/agent-cli deploy	the web app to EAS Hosting
One-time setup	npx @expo/agent-cli new my-app	create a project
	npx @expo/agent-cli install expo-sqlite	add a package at the version this SDK wants
	npx @expo/agent-cli agents:setup	confirm agent setup for a project or user home

npx @expo/agent-cli help workflow is this loop in one screen, plus exit codes, --json, and what to do when a command fails.

npx @expo/agent-cli -h lists every command. Each command's --help has the same shape: purpose, options, examples, what to run next, and the --json keys.

Commands

Command	What it does
new	Create a project without prompts
install / add	Run expo install, then sync that package's skills
status	What this project is, whether a rebuild is needed, what to run next
dev	Plan how to get the app on a device, then do it. --eas does it all on EAS
start	expo start and nothing else, then sync skills
dev:logs / dev:stop	Read or stop a detached dev server
navigate	Open a route on a simulator, a device, or EAS Simulator (--eas)
runtime:reload	Put the running app back on the code on disk
runtime:errors / runtime:eval	Read runtime errors, or evaluate JS in the running app
runtime:tree / runtime:tap / runtime:type	Drive the app by testID
runtime:stop	Stop the app on the device
smoke	Reload onto the code on disk, open a route, check for errors
typecheck	The project's own tsc --noEmit
doctor	expo-doctor, normalized
deploy	Ship the web app to EAS Hosting, or the native app with --native
inspect:build-log	Find the line in a native build log that says why it failed
inspect:config-plugins	What the config plugins produced. Experimental
agents:setup	Set up Expo agents in a project or user home
feedback	Send feedback to the Expo team, with agent and project context
skills:sync / skills:list / skills:show / skills:clean	Discover and link skills shipped by installed modules
docs:sync / docs:search	The Expo docs for the project's SDK as local Markdown files to grep

Grouped commands use group:action, the way eas-cli does. The space form is the same command: skills list is skills:list. Bare skills syncs, bare doctor checks, bare dev runs the plan.…