Guide

How to set up the Helm CLI (helm-asc)

Jul 19, 2026 Install helm-asc from Helm Settings, connect credentials through the Mac app App Group, explore agent mode, and run your first safe App Store Connect commands.

The Helm CLI, helm-asc, brings App Store Connect workflows to your terminal and coding agents. This guide covers install, authentication via the Mac app, first commands, and safe defaults for automation. Product overview: Helm CLI and helm-asc.

What you need

Helm for Mac signed in with the App Store Connect accounts you care about
Helm Pro, which unlocks CLI access
A directory on your PATH where Helm can install the tool
Optionally, a coding agent (Codex, Cursor, Claude, Xcode, or a general agent folder) if you want the bundled skill

If you still need an API key for the Mac app itself, follow How to create an App Store Connect API key for Helm.

Install helm-asc

Open Helm → Settings.
Find the Helm CLI section.
Install helm-asc into a directory on your PATH.
Confirm in Terminal:

helm-asc --help

When you update Helm from the App Store, the CLI and agent skill update with it. You do not maintain a separate upgrade channel.

How authentication works

helm-asc does not ask you to paste API keys into the shell for normal use. It reuses the Mac app’s account setup through an App Group connection. Secrets stay in the app and Keychain model you already trust.

That means:

The organizations and apps available in the CLI match what you configured in Helm
Setup files and teammate access rules continue to apply
Agents inherit the same boundary instead of a second, drift-prone credential store

Keep Helm installed and signed in on the Mac where you run the CLI.

Your first read-only commands

Start by discovering IDs before you mutate anything:

helm-asc --help

Explore apps, then drill into a single app’s versions, builds, reviews, submissions, and TestFlight groups. Prefer read operations until you are comfortable with the output shape.

Agent mode

Pass --agent when a tool or script should consume structured JSON instead of prose. Successful commands return predictable data. Failures use stable error codes with messages and suggestions.

From Settings, install the bundled agent skill into:

Codex
Cursor
Claude
Xcode
A general agent directory
Any folder you choose

The skill teaches defaults that matter for App Store Connect: use --agent, discover IDs first, prefer dry runs for bulk work, stage generated files where humans can see them in Helm, and stop when a decision needs a person.

What you can automate today

Versions: create, edit details, review information, ship or reject
Localizations: create, download, update, bulk upload
Screenshots and previews: upload, download, delete, preview timing
TestFlight: builds, groups, aliases, testers, beta submission
Reviews and submissions: reply, create and submit App Store submissions
In-app purchases, subscriptions, and in-app events

The Mac and iOS apps remain the best place for visual review. Use the CLI to prepare and automate; use the UI to confirm customer-facing truth before high-impact submits.

Safety checklist for teams

Use a dedicated Mac user or machine policy if agents run unattended.
Limit which apps a setup file can access before sharing with contractors.
Require human approval for submit-for-review style actions in your agent instructions.
Log command output in CI with redaction for any sensitive fields.
Practice on a non-critical app first.

Shortcuts vs CLI

Shortcuts and App Intents are ideal for quick human actions (status, copy TestFlight link, open app). helm-asc is the right tool for scripts, CI-like loops, and coding agents.