Edit Your Theme with Cartly Command

What Cartly Command Can Do in Your Theme

Cartly Command can change your storefront theme for you. Describe the change in your own words, in any language, and Command makes it on an AI draft: a copy of your theme that shoppers do not see. Every change passes the automatic theme check before it is offered to you, you review it, and your store changes only when you publish the draft.

Before You Start

Theme changes use the AI credits included in your plan. See AI credits in your plan.
Only the store owner or an admin can run, accept and publish AI changes.
A theme connected to GitHub cannot be changed this way. Make the change in the repository.
The AI draft is a theme in your library, and a library holds up to 20 themes. If yours is full, delete a theme first.

1. Describe the Change

Go to Online Store → Themes and open the theme in the visual editor or the code editor.
Open Cartly Command with its button or ⌘J (Ctrl+J on Windows). Command knows the theme, the page template and the section or file you have open.
Type the change, or start from a suggestion such as Dark header or Footer copyright.

A question about the theme, such as “Where do I change the logo?”, is answered in the chat and nothing is changed. If you ask for a theme change somewhere else in the admin, Command offers Open theme editor, because a theme task runs from the editor.

2. Run the Task

For a change request, Command shows a task card with the goal, a short plan and an estimate of the most the task can cost, shown as a share of your monthly AI credits. Read the plan, then click Run. The task starts only when you click it.

Cartly creates a copy of the theme named <theme name> — AI draft, and the editor moves to it. If you have unsaved edits, the editor stays where it is and offers Open the AI draft. The card shows the progress: Studying the theme, Writing N files, Checking the theme, and Fixing N errors when the check found something. Click Stop to end the task early. You can also close the tab: the task keeps running, and the editor shows it again when you come back.

One task runs at a time in a store, and there is a daily limit on the number of tasks.

3. Review the Result

When the task finishes, the card shows a short summary of what changed, the files it created, changed or removed, any theme check warnings, and the credits used.

Show code opens the code editor with the AI changes panel. Click View diff on a file to compare it side by side: the file as it is now on the left, the file after Accept on the right. Untick the files you do not want and click Accept selected, or click Reject all. A file that changed since the AI read it starts unticked.
Accept on the card applies the whole change to the AI draft. Reject discards it.

After you accept, use Before and After in the visual editor toolbar to compare the draft with the theme it was made from (your live theme, if you started there) on any page, or open a preview. You can keep asking for changes: they go into the same draft. You can also edit the draft yourself in either editor.

4. Publish the Draft

While you are on the AI draft, a banner at the top of the editor says that shoppers see your store's theme until you publish. Click Publish draft and confirm.

The theme check runs first. If it finds an error, nothing is published and the problems are listed.
A restore point is saved, then the draft becomes your store's theme. The theme it was made from stays in your theme library, unchanged.
If the original theme has edits the draft does not have, the publish dialog tells you: those edits stay in the original.
Changes still waiting for your review are not included.

Undoing a Change

Before you accept: click Reject.
After you accept: open the draft's Version history (the link is in the banner) and restore the version saved before the AI changes were accepted.
After you publish: the publish dialog links to the Version history of the theme that was live before. Restore its version saved before the switch, and that theme is your store's theme again. You can also publish it from the Themes page.

See Restoring an earlier version of your theme.

Writing Good Requests

Say where the change goes and what it should look like: “On collection pages show 4 products per row on desktop and 2 on mobile.”
Put the exact text you want shown in quotes. Command keeps it as written; check it in the preview before you publish.
If you want to change something yourself later, say so: “… with a heading I can change in the editor.”
Ask for one change at a time. A large request may stop at the task's step limit; the result card then says so.

What It Will Not Do

Change anything outside the theme: payment methods, the checkout, apps, products or other store data. Command explains what you can do instead.
Add third-party tracking scripts, chat widgets or files loaded from other sites (web fonts from Google Fonts are allowed).
Write texts for you, such as FAQ answers, reviews or delivery promises. Use your own words in the request, or fill the new settings in the editor.

Credits

The estimate on the task card is set aside when the task starts. When the task ends, you are charged only for what it actually used and the rest returns to your balance. If you stop a task, or it cannot finish, only the steps already done are charged. A task that needs more credits than you have left does not start.