Appearance
Set up with Codex or Claude
You can start from Set up with AI on the PushOTA homepage. Choose Copy for Codex or Copy for Claude, then paste the instruction into your agent with the React Native project open. Both buttons use the same managed integration. View setup instruction provides a manual-copy option if your browser blocks clipboard access or JavaScript is disabled.
The homepage instruction reads the public agent guide. Your agent inspects the project and asks for missing platform, app and organisation details. You still need a PushOTA account with access to the app; the prompt does not grant access or publish an update. If the service is unavailable, the agent must report that rather than bypass authentication or use another server.
For a command already filled in for your app, open your platform app in Setup guide → Connect → Set up with Codex or Claude. Copy AI integration instruction and paste it into your coding agent.
The instruction contains the exact project connection command and the platform saved for this dashboard app. For an older app without a platform, choose iOS or Android in Connect first; commands stay unavailable until you choose. Reloading or switching apps never substitutes another app's platform. After setup, the agent reads ota-setup/SKILL.md, inspects the project and finishes its integration. It uses your existing package manager: npm, pnpm or Yarn.
If you already ran setup, paste this into either agent:
text
Read ota-setup/SKILL.md and complete the OTA integration in this project.
Ask me about any project decisions you cannot infer. Run the relevant checks
and available native builds, and distinguish completed work from remaining
store and device testing. Do not publish or promote an update without my authorization.What it handles
- Inspect React Native/React versions, existing native targets and any previous updater.
- Use the pinned SDK and automatically merged Production native settings.
- Adapt the native loader for Swift, Objective-C, Kotlin or Java.
- Connect the generated silent/immediate update worker to the app's healthy startup point.
- Add the reusable testing entry at the location you choose.
- Run relevant checks, verify uninstall recognition with a dry run, and report what remains.
The agent should ask when it cannot infer a native target, testing-panel location, health milestone or intended store version/build. It should preserve unrelated work and the app's existing startup/navigation.
Keep newly added OTA-only imports and lifecycle wiring inside // BEGIN PUSHOTA and // END PUSHOTA comments. Never include existing app logic in those regions. Use the cleanup-aware startup example, including the case where startup finishes after teardown. The agent must run node ota.cjs uninstall --dry-run and resolve any unrecognized integration before reporting setup complete.
Login and ownership
Your existing Codex or Claude environment performs the work. PushOTA does not receive your AI account credentials and does not run an agent on your behalf. The normal CLI login still enforces project authorization. If the agent cannot handle interactive login, sign in from your terminal and let it continue. Never paste passwords, MFA secrets or private signing keys into the agent chat.
The guide is local and versioned with the setup helper. It is read explicitly by the pasted instruction; no global agent configuration, AGENTS.md, CLAUDE.md, API key or separate AI service is installed. Uninstall removes the generated guide along with the rest of the setup, including when public configuration has been deleted.
What still requires a native release
The agent can edit and build the integration; that does not mean an OTA has reached a device. Distribute the new native app through TestFlight or Google Play testing and install it before pairing and Staging update/rollback tests. A public rollout, store submission or OTA publication remains subject to the actions you actually authorize.