Drafts and publishing
Everything is a draft until published
Every change an assistant makes (pages, layers, styles, components, collections, fonts, assets, locales and translations) is saved as a draft. Your live storefront does not change until the drafts are published.
- Open the storefront builder at any time to review the drafts. Changes appear live in the builder while the assistant works.
- Drafts can be edited or undone in the builder like any other change.
Publishing
Two tools handle publishing:
| Tool | Access | What it does |
|---|---|---|
get_unpublished_changes | read | Lists what would change on the live site if you published now. |
publish | destructive | Publishes all drafts, including locales and translations, to your live storefront. |
The assistant is instructed to publish only when you ask, typically as the last step of a job you approved:
text
Show me what's unpublished, then publish it.Pages marked as not publishable are skipped when publishing.
Recommended approval settings
Most assistants let you choose, per tool, whether to run it automatically or ask first. We recommend:
| Tools | Setting |
|---|---|
read tools (for example get_shop_context, list_pages) | Always allow |
| write tools (draft edits) | Always allow |
destructive tools (publish, delete_*) | Ask every time |
Where to set this:
- Claude.ai / Claude Desktop: Settings → Connectors → Cashfin → tool permissions.
- Claude Code: approve when prompted, or set rules with
/permissions. - ChatGPT: each write action is confirmed in the chat by default.
- Cursor / VS Code / Windsurf: use the per-tool or auto-run settings in the MCP or agent configuration.
See the tools reference for each tool's access hint.