Compatibility
Full support starts with Autotomy projects. Other Expo repositories receive compatibility findings without automatic restructuring. Modified Lite files produce conflicts rather than silent overwrites.
Expo Foundation
Use Node.js 22.20 or newer and the package-manager version recorded in the release. Installation and premium commands need a network connection. Native builds also need the matching iOS or Android toolchain.
Full support starts with Autotomy projects. Other Expo repositories receive compatibility findings without automatic restructuring. Modified Lite files produce conflicts rather than silent overwrites.
Plan an Expo upgrade
Expo upgrades are agent-guided. The CLI identifies an eligible version-specific plan; your AI makes the changes and you review the result. SDK 57→58 guidance is published only after rehearsal against the supported stack. Unsupported combinations stop with an explanation.
Help upgrade this Autotomy project to Expo SDK 58. Start with Git status and npx autotomy upgrade expo --to 58 --json. Read the returned compatibility evidence and blockers. If the target is unsupported or the recipe is blocked, stop and explain; do not invent a migration. Otherwise present the plan and affected files before changing dependencies or source. Preserve customer edits and native configuration, follow official release guidance, and run the prescribed verification including npx autotomy check. Report failures and recovery steps without weakening checks.Codex · Claude Code · Cursor
Codex, Claude Code, and Cursor receive their supported integrations. Your coding tool may require you to trust hooks. Hooks provide feedback; they do not automatically repair source.
Your app source stays on your machine. Autotomy accounts and subscriptions belong to the developer toolkit; they do not add login or payments to your app.