OTA updates from Cursor

Cursor OTA updates: one prompt installs the HotCodePush skills and ships the first release, and the MCP server answers in the editor. Free for 1,000 MAU.

Get started Install with AI

One prompt

From one prompt to the first update in Cursor

The prompt, the skills it installs and the commands they run, from the first sign-in to the first update.

Cursor — my-app

▸ hotcodepush MCP server added in the project settings, sign-in approved in the browser

▸ you, to the agent

Set up HotCodePush OTA updates in this project, following https://hotcodepush.com/docs/quickstart.md.

If you can run commands, install the agent skills with `npx skills add hotcodepush-team/skills`,

then run hotcodepush-init and hotcodepush-release.

If you cannot run commands, read that page and give me the steps to do it myself.

▸ the agent reads the quickstart and installs the skills

$ npx skills add hotcodepush-team/skills

✓ added hotcodepush-init, hotcodepush-release, hotcodepush-debug-no-update, hotcodepush-migrate

▸ hotcodepush-init

$ npx hotcodepush init

✓ sign-in — logged in as Anna

✓ app — created app My App

✓ configuration — wrote hotcodepush.json

✓ hook — wired the build step

✓ signing-key — generated, the private key stays on your machine

$ npx hotcodepush doctor --json

{ "status": "clean" }

▸ hotcodepush-release

$ npx hotcodepush release create --yes --json

✓ created release #1 on production — devices update on next launch

▸ done. Review hotcodepush.json and the native changes, then commit. Nothing was committed, no token was printed.

Three jobs

What Cursor does for you

One skill per job. The agent picks the one whose description matches your prompt and runs the CLI for you.

Set up the project
Installs the SDK, writes the configuration, wires the build step, generates the signing key and repeats the doctor until every check is clean. The repair run too.
How the skills work
Ship the release
Builds where the framework needs it, previews how many devices the release reaches, publishes it and reports audience and warnings. In CI it labels the bundle from the commit.
Staged rollouts
Find why a device skipped
Probes the device, reads its last check and walks the causes as a decision procedure, each with its reason, the field that shows it and the fix to apply.
Troubleshooting

How it fits

How Cursor works with HotCodePush

The skills carry the work in the project. The server answers from the chat. Both read the same docs.

Cursor's agent runs shell commands in your project, so the skills do the work: one command installs them, and the agent picks the matching skill for a prompt, runs the CLI and stops where a person must approve. The MCP server is the second half. Added once in the project settings, it lets you ask about channels, releases and adoption in the chat, pause a rollout or roll back, with the access you approved in the browser.

Set up the MCP server

FAQ

Cursor questions

In the project settings, for one project or for every project. Cursor then offers to sign in, the browser opens the consent page once, and the tools appear in the agent chat. Set up Cursor

Either or both. The skills ship from the project through the CLI and need no server. The server answers questions and acts from the chat. AI tools in the docs

It previews the audience first and stops where a person must approve, such as the sign-in or a signing key. The release itself runs once you asked for it, and nothing is committed to git for you. What each skill runs

Yes. In a pipeline a token stands in for the browser sign-in, and the release skill labels the bundle from the commit. The same commands run with or without an agent. Shipping from CI

The agent acts as you and gets no right you lack. You approve the sign-in once, every action lands in the audit log, and revoking the access in the console cuts Cursor off at once. Sign-in and tokens

Your first over-the-air (OTA) update, from Cursor.

Free for 1,000 MAU. No credit card.

Get started Book a demo

Questions? Join our Discord or contact us.