Wingman is a desktop app for Shopify theme developers. It sees the template, section, block and line of Liquid behind every pixel of your preview, and changes it the way a theme developer would.
One loop in one window: what you pointed at, what the agent changed, and whether the theme still passes.
01 Select
Click any element in the live preview. Wingman resolves the section, block and template behind it, down to the line
(sections/hero.liquid:48), before the agent reads a single file.
02 Ask
The agent reads the section and measures the page first: an 88vh hero is 742px tall on a 390px screen. Then it proposes the edit, and nothing is written until you allow it.
03 Edit
Hardcoded values become settings the merchant can still change in the theme editor. Breakpoints follow the theme's own
749px, and the hero image gets a srcset and fetchpriority.
04 Verify
theme dev hot reloads the preview, Theme Check runs, and Web Vitals are measured again on the same page.
Undo is one click; push goes to your development theme.
Performance
Web Vitals on desktop, tablet and mobile, the LCP element traced to its file and line, and the Liquid profile per section. Any of it becomes a prompt in one click.
Recorded in real time on the demo project: pick the hero, ask, allow the edit, and watch Wingman verify it before you see it on a phone.
Wingman runs the agent itself, over your provider's API with your own key, kept in the macOS Keychain. Pick a model per session; the tools and the checks stay the same.
get_shopify_contextSelection, section, block, template and settingsget_rendered_htmlWhat the storefront actually renderedrun_theme_checkOffenses for the files it touchedevaluate_liquidLiquid against the store's real dataprofile_liquidRender time per section and lineget_metafield_definitionsReal metafield names and typeslist_themesThe store's themes and their rolesshare_previewA client preview link, after asking youNo shell. File tools stay inside the theme folder, and every write goes through your permission mode.
Wingman runs the official CLI on your machine. Every command shows exactly what will run, and anything that reaches the live theme asks twice: review the command, then type the store handle.
theme devone per project, hot reloadtheme pushlive asks twicetheme publishasks twicetheme pullshows what changedtheme shareclient preview linktheme packagezip, ready to uploadtheme checkafter every edittheme consoleLiquid on real datatheme profilemapped to your linestheme metafields pullreal field namestheme list · info · openthemes paneltheme rename · duplicate · deleteinline, reviewed
Every project gets its own theme dev server and port, preview tabs, agent sessions and snapshots. The CLI
keeps one development theme per store, so a second project on the same store gets its own unpublished theme instead of
overwriting the first.
Your theme folder stays local. Files reach your store through the Shopify CLI, and the agent's context goes only to the provider you picked.
API keys, storefront and Theme Access passwords live in the macOS Keychain and reach the CLI through the environment, never the command line.
Wingman snapshots the theme before each agent turn and each pull, so undo puts every file back, not just the last one.
No. Wingman is an independent product, not affiliated with or endorsed by Shopify. It is built on the official Shopify CLI and Theme Check, and works with themes you develop in code.
Nikita Zanella, a Shopify theme developer. Wingman started as the tool Nikita wanted for client work: an agent that understands sections, blocks and settings, and proves its changes before they ship.
No. The theme editor is where merchants customize a store; Wingman is where developers change the code behind it. Settings an agent adds to a section show up in the theme editor like any other.
OpenAI, Claude, OpenCode (Go or Zen) and OpenRouter, with your own API key stored in the macOS Keychain. You pick the model per session, and every model gets the same Shopify tools and the same verification.
Wingman runs locally and works on your theme folder. Theme files are sent to your store by the Shopify CLI, and the context an agent needs is sent to the runtime you chose, under that provider's terms.
A Mac, the Shopify CLI, a theme in a local folder (git recommended) with access to its store, and at least one of the supported agent runtimes.
macOS comes first. If you need another platform, email [email protected] and tell us.
Pricing isn't set yet. Beta access goes out by invitation from the waitlist. Agent usage is billed by the provider you choose, as it is today.
Invites go out in small batches to theme developers and agencies. Tell us how you work and we'll send one when there's room.
Made by Nikita Zanella, on a mission to build the agentic theme development platform for Shopify developers.
You're on the list.
We'll email you when your invite is ready.