Give your coding agent TestFlight

A coding agent can write a whole iOS app and then stall at the last mile, because shipping needs a Mac, a certificate and a form. Here is the loop that closes it: build, TestFlight, crash reports, back to the agent.

September 2, 2026 · 6 min read

Need a Mac for this? NoMac gives your agent full macOS with Xcode for $0.80 an hour, billed by the minute. Start now →

A coding agent can write a complete iOS app. It can plan the data model, argue with itself about navigation, and produce a Swift project that compiles. Then it stops, because the next step is not code: it is a certificate, a Mac, a provisioning profile and a web form.

The gap is not intelligence. It is hands. Everything past the source code requires acting on systems the agent has no account on. The usual workaround, telling the human to go do fourteen things in App Store Connect, is where most agent-built apps quietly die.

The loop that closes it

What an agent needs is not a dashboard. It needs verbs it can call and structured answers it can reason about:

• ·start_mac: a full macOS VM with Xcode, ready in about a minute, billed by the minute.
• ·exec_mac: xcodebuild and the Simulator on that Mac, run by the agent, with the output coming straight back.
• ·set_up_signing: profiles and build settings for the project, with your App Store Connect key kept on NoMac's server.
• ·send_to_testflight: the signed .ipa on your phone once Apple has processed it, usually 5 to 15 minutes.
• ·publish: metadata, screenshots, review checks, and the submission.

The important half is the return path. On its own Mac, the agent sees xcodebuild's errors as they happen (piped through xcbeautify, so they stay short), fixes the source and builds again in the same session. When the problem is not code, the tools say so: set_up_signing switches on the capabilities Apple's API can, and returns the steps only a person can take with a link. An agent that knows the blocker is an agreement in App Store Connect does not go guessing at your source code.

Wiring it up

Two steps, then the agent runs the rest. First, the login:

npx @nomac/cli login
# prints a URL and a short code: you approve it in the browser.
# No key is ever pasted into the agent's context.

Then give the agent the MCP server, either locally or hosted:

# stdio
command: npx
args: ["@nomac/cli", "mcp"]

# or hosted (OAuth sign-in, or a key)
https://mcp.nomac.app/mcp
Authorization: Bearer <nmk_key>

Or skip all of that and tell the agent to read nomac.app/install, which is written for exactly this: an agent-readable setup page that configures the rest itself.

Your part beyond that is small: add credit, and connect your App Store Connect team key once at nomac.app/apple when the agent first needs to sign.

What to keep the human for

An agent that can submit to the App Store unattended is a bad idea, and not because agents are careless. Submission is irreversible in the ways that matter: a rejection is on your developer account, a shipped bug is on your users, and Apple's patience with repeat low-quality submissions is finite.

• ·Builds and TestFlight: let it run. Cheap, reversible, and the fast loop is the entire value.
• ·App Store submission: ask first. The agent prepares everything and stops for a yes.
• ·Anything touching credentials: never. The device login exists so the key never enters a prompt, and request_secret gives you a link to enter any other secret yourself.

What comes back

Once a build is on TestFlight, the interesting direction is inbound. Crash reports and tester feedback flow back to the agent, which means the debugging loop closes without you copying stack traces between windows: it shipped it, it can see what happened, it can fix it and ship again.

That is the part that changes how it feels to build. Not “the AI wrote my app” (plenty of tools do that), but that the distance between noticing a bug on your phone and having a fixed build back on your phone is one sentence and Apple's processing time.

Before the first submission

Getting a build to TestFlight is mechanical and now largely solved. Getting through App Review is neither, and an agent will happily submit something with a generated icon, placeholder copy and a category Apple has closed. Read why App Review rejects AI-built apps before you spend a review cycle finding out, and what actually needs a Mac for the one-time Apple setup no tool can do for you.

The full command surface is in the CLI reference, and the HTTP equivalent in the API reference.