@cobberhq/cli

Local theme development for Cobber. Pull a draft theme to disk, edit in your editor of choice, sync changes live as you save.

Install

npm install -g @cobberhq/cli

Authenticate

cobber login <subdomain>

A browser window opens. Approve the device code and the CLI receives a long-lived token (stored at ~/.cobber/config.json).

Pull, edit, sync

cobber pull                         # prompts to pick a theme (or `--all`)
cobber pull standard                # pulls just the "Standard" theme
cobber pull --all                   # pulls every theme
cobber pull --org for-families      # pull from a specific org, not the default

cd <subdomain>-themes/<slug>
cobber dev                          # watches for changes, opens preview URL

pull uses your default org — the one you most recently logged into. dev and push always use the org recorded in the theme folder's manifest, so they're unaffected by the default. Every command prints the org it's acting on.

Edits propagate to the draft theme via the API; the dashboard preview reflects them immediately. Production is untouched until somebody clicks Publish in /dashboard/admin/themes/:id/draft.

cobber push                         # bulk sync, useful if you edited offline

Manage orgs

cobber orgs                         # list logged-in orgs; * marks the default

Log out

cobber logout                       # removes credentials for the default org
cobber logout <subdomain>           # removes credentials for a specific org

Layout

<subdomain>-themes/
  <slug>/
    .cobber/manifest.json     # checksums + draft id (don't edit)
    page_layouts/*.liquid
    site_layouts/*.liquid
    snippets/*.liquid
    widget_partials/*.liquid