AI Assistant

Odevio can be driven by an AI coding assistant such as Claude Code. You describe what you want in plain words, and the assistant handles the rest.

Depending on what you ask for, it can:

  • show you your app running on one of our Macs, in the iOS simulator — this needs no Apple account at all

  • check that your app builds for iOS, without publishing anything

  • fix build errors on its own, then start again, until it works

  • install it on your iPhone, or share it through TestFlight

  • send it to the App Store, ready for you to submit

This is for you if you would rather not learn what a provisioning profile is.

Note

Only the first item works without a paid Apple Developer account. To reach a real iPhone you need one — 99 € per year, no way around it. Everything else is handled for you.

What you need first

1. Python and pip. PIP is Python’s package manager. If you do not have Python, install it first.

2. Odevio. In a terminal:

pip install odevio

3. An Odevio account. If you do not have one yet, create it on the website — odevio.com/user/registration — or from the terminal:

odevio signup

Already have one? Sign in:

odevio signin

You only do this once. The assistant cannot sign in for you, because the command asks for your password — so if it ever tells you to run odevio signin, that is why.

4. An AI assistant. These instructions are written for Claude Code, which runs in your terminal and in VS Code, and which odevio skill install configures for you.

Note

The skill follows the open Agent Skills standard, so it is not tied to one tool. For now the installer only sets up Claude Code; with another assistant that supports the standard, copy the same files by hand from odevio skill install --project into wherever it expects them.

Install the Odevio skill

A skill is a set of instructions that teaches your assistant how to use Odevio properly. Install it once for your whole machine — this sets up Claude Code:

odevio skill install

That is it. It is now available in every project on your computer.

Prefer to keep it inside one project, for instance to commit it with your repository?

odevio skill install --project

And if you would like the skill to update itself whenever you upgrade Odevio:

odevio skill install --link

Use it

Open your assistant in your Flutter project’s folder and ask for what you want, in your own words:

Get my app onto my iPhone

Or type /odevio to start it explicitly.

The assistant works out what needs doing. If your Apple account and your app are already set up, it asks nothing and gets straight to work.

What it will ask you, and why

It only stops when the answer is something no one else can give:

What it asks

Why

What you want to do with your app

Trying it on your own phone, sharing it with testers and publishing on the App Store are three different jobs

To sign in to Odevio

The command asks for a password, which it cannot type for you

Whether you have a paid Apple Developer account

Without one, nothing can reach a phone

Your Apple API key

Only you can create it, in your Apple account. It walks you through where to click

Your app’s name, and confirming its identifier

The name is your choice; it proposes the identifier so you do not have to understand the format

To create the app once in App Store Connect

Apple does not allow this to be automated. About two minutes, once per app

Everything else — versions, certificates, signing, build numbers — it works out by itself.

While it is working

Your project is compiled on a real Mac, so expect around fifteen minutes for a build — longer for a large app, and longer again if all our machines are busy and yours waits for the next free one.

There is nothing for you to do in the meantime. The assistant tells you when it starts, keeps you posted as it goes, and you can ask it where things are at any time — or tell it to stop.

If your app fails to build, it reads the error, fixes your code, and starts again — up to three attempts, then it stops and explains what it found rather than making things worse.

What you get at the end

Depending on what you asked for:

  • Running on a Mac we provide — you get connection details for a remote desktop, with your project and the iOS simulator already there, so you can watch your own app run. No Apple account needed. You will need a VNC client on your computer, and the machine stays available for an hour

  • On your phone straight away — you get a link and a QR code. Scan it with your iPhone camera and the app installs like any other. Your device needs to be registered on your Apple account once, which is easiest from a Mac — if you are on Windows or Linux, TestFlight below is the shorter path

  • Through TestFlight — Apple processes the build on its side first, usually five to thirty minutes, then it appears in the TestFlight app. Handy for sharing with a few people

  • On the App Store — the build is uploaded, and you then fill in the description, screenshots and privacy answers in App Store Connect and submit it

Warning

A successful build does not mean a published app. Apple reviews every App Store submission, which takes from a few hours to a few days, and it can be refused — most often for a missing privacy policy, or for an app judged too limited. That part is between you and Apple.

If it goes wrong

“You need to sign in first” — run odevio signin in your terminal, then tell the assistant it is done.

“The Odevio command is not installed” — run pip install odevio. If it still cannot find it, your terminal and your Python installation may not agree; pip --version and odevio --version tell you what is available.

Your app never shows up in TestFlight — usually Apple’s encryption question left unanswered. The assistant normally handles this for you; ask it to check.

Your build seems stuck waiting — our Macs may all be busy, or one may need attention. The assistant tells you rather than waiting for ever.

Never paste your password or the contents of your Apple key file into the conversation. The assistant is built to refuse them, and asks for a file path instead.

Using it without an assistant

Everything the skill does, you can do yourself with the CLI: see Tutorial and the Reference Guide. And for automated pipelines, see CI/CD.