Odevio CLI
A CLI and agent skill that build, sign and publish Flutter iOS apps with no Mac and no Xcode
- 423 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Works with your Apple Developer account: the App Store Connect key, certificates and signing profiles
- Publishes builds to TestFlight and the App Store and can update the app's store listing
- Project code is built on the service's remote machines, and after the skill install the odevio commands are pre-approved in Claude Code
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/odevioDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Works with your Apple Developer account: the App Store Connect key, certificates and signing profiles
- Publishes builds to TestFlight and the App Store and can update the app's store listing
- Project code is built on the service's remote machines, and after the skill install the odevio commands are pre-approved in Claude Code
This is third-party code. Review the repository files before installing.
What it does
Odevio builds, signs and publishes iOS apps on remote Macs, so you need neither a Mac nor Xcode. The package installs with pip, the `odevio skill install` command connects a skill to your agent, and from there the agent runs the whole path from plain requests. In Claude Code this works with no extra setup, and for Codex, Cursor and Gemini you add the `--agent` flag. The skill handles iOS specifics: certificates, devices, provisioning profiles, app identifiers and Xcode settings. The agent builds a Flutter project on a remote machine, reads the log when a build fails and fixes the cause, then ships the build to TestFlight or the App Store. The same steps work by hand: `odevio build start --build-type ad-hoc` creates an IPA for test devices, and the `publication` type publishes the app to the App Store. The skill also maintains the App Store listing and makes marketing screenshots with a headline over a shot in a phone frame. They can be made before the first build and before an Apple account is connected. The agent appends `--agent <name>` to its commands so Odevio knows who ran them.
Who it is for. For Flutter developers on Windows or Linux who want to ship the iOS version of an app through Claude Code, Codex or Cursor.
Good fit when
- You write a Flutter app on Windows or Linux and want to see it on an iPhone without buying a Mac
- You need a TestFlight build: the agent prepares certificates and profiles, builds the app and uploads it
- A build failed, and the agent should read the log with `odevio build logs`, fix the cause and rebuild
- You need an IPA to install on test devices: an ad-hoc build type fits
- The App Store listing and screenshots must be prepared before the first build
Not a fit when
- The app is written in another framework or natively in Swift: the service and its skill are built for Flutter projects
- Source code must not go to third-party machines: builds run on the service's remote Macs
- You need Google Play publishing: Odevio works with iOS only
- Apple Developer keys must not be entrusted to an agent: the commands use your account and App Store Connect private key
Example request
Build my Flutter app for iPhone and upload it to TestFlight. If the build fails, read the log and fix the causeLimitations
- An Odevio account is required, and `odevio signup` creates it. Builds for publication need an Apple Developer account, connected with `odevio apple add` passing the Apple team ID, the key ID and the issuer ID from App Store Connect, and the path to the private key.
- Builds are made for Flutter projects and run on the service's remote Macs, so the project code lands on its machines.
- Only Claude Code gets pre-approved commands. In Codex, Cursor and Gemini those agents' own approval rules apply.
- If a command answers «no such option: --agent», the CLI is out of date and should be updated with `pip install -U odevio`.
- Odevio sets the service terms and price, and the CLI description does not list them.
How to disable. Remove the package with `pip uninstall odevio` (or `pipx uninstall odevio`). The skill folder stays in the agent's skills directory and must be removed by hand. In Claude Code, `odevio skill install` also leaves pre-approved odevio commands in the settings: remove those as well.
FAQ
How do I install Odevio for Claude Code?
Run `pip install odevio`, then `odevio skill install`. The second command connects the skill and, for Claude Code, pre-approves the odevio commands. After that, in a Flutter project, ask the agent to put the app on your iPhone.
How do I connect Odevio to Codex, Cursor or Gemini?
Add the `--agent` flag: `odevio skill install --agent codex`, `--agent cursor` or `--agent gemini`. The `--agent universal` option puts the skill in .agents/skills, and `--agent all` installs for every supported agent at once. For any agent that follows the Agent Skills standard, the directory can be set with `--to`.
Can I build an iOS app without a Mac?
Yes. Building and signing run on the service's remote Macs, so you only need your own Windows, Linux or macOS computer and an Odevio account. The service handles certificates, provisioning profiles and app identifiers itself.
What if an Odevio build fails?
Check the log with `odevio build logs`. When the skill is running, the agent reads it itself, fixes the cause and starts the build again.
How do I get an IPA for a device test or publish the app?
For test devices run `odevio build start --build-type ad-hoc`, then `odevio build ipa`. For the App Store use `odevio build start --build-type publication`. Before that, connect your Apple account with `odevio apple add` and create the app with `odevio app mk`.
Discussion
No questions or reviews yet.
Related
CLI toolsA skill with scripts for building iOS apps and driving the simulator through the accessibility tree, with compact output for agents
A set of skills, agents and commands for iOS, iPadOS, watchOS and tvOS development: Swift 6, SwiftUI, Liquid Glass and Apple Intelligence
Lets Claude Code and Codex drive a real iPhone: read the screen, tap, type and scroll in any app
A skill that builds in-app screen and element capture for a SwiftUI app and loops it across every locale for the App Store
The Flutter team's agent plugin: Flutter and Dart skills, the Dart MCP server and a hot reload rule for Claude Code, Cursor and Codex
A set of skills for iOS 26+, Swift 6.3 and SwiftUI that gives the agent knowledge of modern Apple frameworks
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Odevio (this entry) | yes | 423 | ||
| App Store Connect MCP | no | API key | 5 | works through App Store Connect: subscription prices, offers, review and sales reports, and does not build the app |
| ASO App Store Screenshots | no | 1,801 | makes screenshots for an app's App Store page, while Odevio adds building, signing and publishing to screenshots |
README in short
The page opens with the promise of building and shipping iOS apps through an agent with no Mac, then shows the install and skill connection. Below is the manual path: signup, an Apple account, builds of three types and the log. The end has documentation links, the mission statement and contributor rules.