Expo Agent CLI streamlines agentic app development

Expo is treating mobile development ambiguity as a tooling problem agents can solve systematically. That could eliminate a major source of wasted agent cycles, though the experimental CLI still needs to prove reliability across complex native projects.

• –`status` identifies Expo Go compatibility, rebuild requirements, and next steps before failures occur
• –`dev` handles local or EAS workflows while avoiding unnecessary native rebuilds
• –`smoke` verifies that the app actually launches and runs, not merely that a build succeeds
• –Runtime commands let agents navigate, reload, inspect screens, and read errors
• –Co-located skills keep agent guidance synchronized with installed Expo packages