Milo CLI

Change your app from the terminal. Or ask your coding agent to.

Pull your app’s screens as JSON, change them on a draft, publish on a yes.

Comes with the Enterprise plan. Compare plans

In your app’s repo
MILO_PROFILE=external pnpm exec milo setup --targets claude-code,codex --yes

meadow-goods % milo theme create "Black Friday"

{
  "id": "theme_bf24kq",
  "name": "Black Friday",
  "baseThemeId": "theme_9xlive"
}

meadow-goods % milo theme use theme_bf24kq

{
  "activeTheme": "theme_bf24kq",
  "sessionRefreshed": false
}

meadow-goods % milo config pull | jq '.pulled | length'

16

meadow-goods % code .milo/sync/theme_bf24kq/draft/screens/home.json

meadow-goods % milo config commit screens home

{
  "theme": "theme_bf24kq",
  "committed": {
    "kind": "screens",
    "entityId": "home",
    "version": "32",
    "created": false
  },
  "warnings": []
}

meadow-goods % milo theme preview | jq -r .previewUrl

https://preview.appbrew.tech/bf24kq

meadow-goods % milo theme prepublish | jq '{themeName, message}'

{
  "themeName": "Black Friday",
  "message": "Updates the home screen with a new Black Friday banner."
}

meadow-goods %

Try
  1. 1/5milo theme createA draft, cloned from your live theme. Shoppers see none of it.
  2. 2/5milo config pullEvery screen arrives as JSON your agent can read and edit.
  3. 3/5milo config commitYour change saves to the draft, one screen at a time.
  4. 4/5milo theme previewOne link opens the draft on your phone.
  5. 5/5milo theme prepublishA plain summary for whoever says yes. You publish after it.

For coding agents

Your agent reads the manual first.

One command adds a Milo skill to Claude Code, Cursor, Codex or pi.

  1. 01
    Run setup in your app’s repo
    MILO_PROFILE=external pnpm exec milo setup --targets claude-code,codex --yespnpm exec milo skills status

    --targets takes claude-code, codex, cursor and pi.

  2. 02
    The skill lands in Claude Code

    At .claude/skills/milo/SKILL.md. Your agent reads it before it runs anything, and the next command after an update rewrites it.

  3. 03
    Sign in to your store
    pnpm exec milo login your-store.myshopify.com

    Each sign-in covers one store.

Output
One JSON value per command
Access
Only what your sign-in can run
Updates
Rewrites itself after an update
---name: milodescription: Drive an Appbrew app workspace from the terminal with the milo CLI — authenticate, manage themes, and pull → edit → commit → push app config, plus integrations, shopify, files, push notifications, onelinks, and analytics. Use whenever the user wants to inspect or change an app's config / theme / screens / navigation, trace why a block isn't rendering, debug styling / deep links / integrations, analyze growth (metrics, discounts, push campaigns), sign in to a store ("milo login"), land changes on the live theme, or run any `milo <group>` command. Every command prints JSON to stdout. To create an app for a store that has none, or to seed a theme from a curated brand-inspired blueprint, use the `create-app` skill instead. To build instant code block that no existing block can express, use the `instant-code` skill instead.--- # milo milo is the agent-facing CLI for an Appbrew app workspace. It is how youinspect and change an app: themes, config, integrations, shopify, files, push,and analytics.… 76 more lines

How it works

Every change takes the same road.

Pull it, change it on a draft, see it on your phone, publish on a yes.

Pull.

Screens, theme, navigation and settings arrive as JSON files your agent can read and edit.

milo config pull
Read the guide

For agencies

One terminal, every client’s store.

Sign in to each store once and switch between them. Send your client the preview. Publish after their yes.

Your agency

  1. Signs in to each client’s storeOne store per sign-in.
  2. Builds on a draftIn the client’s app repo.
  3. Sends the previewA link that opens on a phone.

Your client

  1. Opens it on their phoneBefore any shopper sees it.
  2. Says yesYou publish after it.
  3. Shoppers see itAnd it can roll back.

Signed inmeadow-goodsharbor-and-pine

% milo login meadow-goods.myshopify.com% milo login harbor-and-pine.myshopify.com% milo switch meadow-goods.myshopify.com# Switch this directory to an already signed-in store (no re-login)% milo theme prepublish | jq -r .messageUpdates the home screen with a new Black Friday banner.# send the summary and the preview to your client
Two client stores, one terminal. The summary goes to the client before anything ships.

Code Access story · Salty

“With Code Access, there is no ceiling limit as such… the sky is the limit.”

Software engineer, owns the Salty app

Shopify brands running their app on Appbrew

  • SwimOutlet
  • Kut from the Kloth
  • SUGAR
  • Mixology
  • Anatomie
  • Pixi
  • Sukoshi
  • perfectwhitetee
  • littlebox
  • Beastlife
  • Minimalist

100+ commands

A command for every part of your app.

Grouped the way your app is built. Pick a group, or search.

milo theme --help

  • listList all themes (live / scheduled / draft)
  • createCreate a new draft theme (clones live by default, or starts from a blueprint)
  • renameRename a theme (defaults to active theme)
  • archiveArchive a theme (defaults to active theme)
  • previewPrint the preview link for the active theme
  • prepublishSum up what publishing would change for shoppers
  • publishPublish the active theme
  • scheduleSchedule the active theme to go live at a future time
  • unscheduleCancel the active theme's pending schedule
  • useSwitch active theme (`use reset` to clear)

Underlined commands write. 77 of 100+ shown, in the CLI’s own words, shortened.CLI reference

Guardrails

Your agent works on a draft. Publishing waits for a yes.

Where each command lands, and what it tells us.

  • Draft first

    theme createconfig commit

    Writing to the live theme prints a warning.

  • Waits for a yes

    theme publishbundle release

    After prepublish sums up what shoppers will see.

  • Rolls back

    config restore-releasebundle release --tag

    To an earlier release or build.

  • Read-only

    shopify query

    Admin GraphQL mutations are blocked.

  • Masked, backed up

    integration getintegration remove

    Keys stay masked unless you pass --reveal.

  • Goes straight through

    push createintegration updatefiles upload

    No yes step. Integration changes are backed up first.

One event per command
{
  "command": "theme preview",
  "status": "success",
  "exit_code": 0,
  "command_duration_ms": 1840,
  "cli_version": "0.5.20",
  "os": "darwin",
  "source": "local",
  "profile": "external",
  "app_id": "app_mG7d2Kq",
  "theme_id": "theme_bf24kq",
  "shop": "meadow-goods.myshopify.com",
  "$email": "dev@meadowgoods.com"
}

Arguments and option values are never sent.

Security

Secure. Always.

Appbrew is SOC 2 and ISO 27001:2022 compliant. Milo works inside the same controls.

SOC 2Compliant
ISO 27001:2022Compliant

In the trust center

User access reviewsTransmission confidentialityApproval of changesMalicious code protection Visit the trust center

FAQ

Questions about Milo CLI

What is Milo CLI?

Milo CLI is the command line for your Appbrew app, the AI app builder for Shopify brands. Your developers or your agency, or their coding agent in Claude Code, Cursor or Codex, use it to change themes, screens, Instant code, integrations and push notifications, and to read analytics. Every command prints JSON. It’s built on the same CLI Milo runs inside Studio.

Who can use it?

Milo CLI comes with the Enterprise plan, and Appbrew sets it up for you with Code access. It ships as a dev dependency in your app’s repo. Run MILO_PROFILE=external pnpm exec milo setup --targets claude-code,codex --yes to set up your coding agent, then pnpm exec milo login your-store.myshopify.com to sign in. Each sign-in covers one store. milo switch points the current folder at another store you’re signed in to, with no new sign-in.

Is it the same as Milo?

Milo is the agent inside Studio. Milo CLI is the command line it works with, opened up to your developers and their coding agents.

How is it different from the Appbrew MCP?

The Appbrew MCP comes with every plan and brings 30 tools into chat apps like Claude and ChatGPT, with nothing to install. Milo CLI lives in your app’s repo, with over 100 commands, including Instant code builds and integration setup.

Can it change my live app?

Theme and screen changes go to a draft theme you create, and writing to the live theme prints a warning first. Going live is its own step: publishing needs a summary of what shoppers will see, and a yes. Pushes scheduled with push create, integration updates and file uploads don’t wait for a yes. Integration updates and removals are backed up first.

What does it send back to Appbrew?

One event per command: its name, status, exit code, run time, Milo CLI version, operating system and profile, whether it ran on your machine or in CI, the app, theme and store, and the email you signed in with (or your git email). Arguments and option values are never sent.

Run it on your own app.

Milo CLI comes with Enterprise and is already in your app’s repo. Not on Enterprise yet? Book 30 minutes and we’ll look at your store before the call.