Example session
From a sentence to a safe release
The agent does the work. The approval block is always the same, so you can read it at a glance.
you Fix the checkout button label and ship it to production.
agent Built the app. Checking native compatibility against what's live...
compatible (12 packages unchanged)
Uploaded bundle 1.5.0. Prepared the release:
Publish com.acme.shop
lane production · runtime 2026.04
from 1.4.0 -> 1.5.0
native compatible (12 packages unchanged)
immediate no auto-revert on · 10% · min 100
Approve? This goes live for every device on that lane.
you Approve.
agent Published. Devices pick it up on their next launch.How it works
Check, prepare, approve
Ask in plain language, or use the built-in prompts.
Check
Reads your Capacitor project and compares native dependencies with what is live, so it knows whether this change can ship over the air.
/check
Prepare
Builds, uploads the web bundle and prepares the exact release lane. Nothing is published yet.
/release
Approve and watch
You approve the publish. Afterwards the agent reads rollout health and can prepare a revert for you to approve.
/rollout
Built for safety
Your agent can ship. It cannot surprise you.
Approval before publish
The OtaKit Skill tells your agent to stop for your approval before publishing, and publish and revert are flagged as destructive actions, so agent clients ask before running them.
No stale overwrites
A publish carries the release state the agent reviewed. If a teammate released in between, it is rejected instead of overwriting their release.
Native compatibility check
If the change needs a new store build, the agent stops and says so instead of shipping a broken update.
Automatic rollback
Devices that fail to start a new bundle roll back on their own, and auto-revert can pull a failing release for everyone.
Audit log
Every upload, publish and revert is attributed to the person or agent that made it.
Read-only when you want it
Remote connections ask for scopes. Grant read access only, and the agent can report but never release.
Set it up
One command from your project
It detects your agent, signs you in, and shows exactly what it will write before writing anything.
Any supported agent
npx -y @otakit/cli@latest connect
Claude Code
npx -y @otakit/cli@latest login claude plugin marketplace add OtaKit/otakit claude plugin install otakit@otakit
Codex
npx skills add https://github.com/OtaKit/otakit --skill otakit npx -y @otakit/cli@latest login codex mcp add otakit -- npx -y @otakit/cli@latest mcp
VS Code and GitHub Copilot
Create .vscode/mcp.json, then run MCP: List Servers.
{
"servers": {
"otakit": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@otakit/cli@latest", "mcp", "--project-root", "${workspaceFolder}"]
}
}
}npx -y @otakit/cli@latest mcp) or connect to https://console.otakit.app/mcp with OAuth. Full setup guide.What you can ask
Plain language works
- “Check whether this change needs a new store build.”
- “Upload this build to staging but don’t publish it.”
- “Prepare this for production with auto-revert on, then wait for me.”
- “How is the current production release doing?”
- “Roll production back to the previous release.”
FAQ