This article covers the day-to-day mechanics of working with Aimée once you're familiar with what she is (see Meet Aimée): how to hold a conversation that spans a template, a channel, and your catalog, how versions and undo relate to each other, and what happens when you and Aimée touch the same thing at once.
Editing a template, then a channel, in one conversation#
You don't need to start a new chat when you move from designing a creative to configuring how it exports. A single conversation can span both:
- Open the drawer while on a template in Studio and ask Aimée to make a layout or placeholder change.
- Ask her to take you to the channel that uses this template (or navigate there yourself) — she keeps the conversation going.
- Continue in the same chat, now asking her to adjust that channel's fields or automations.
Aimée's replies spell out in prose what she's currently looking at, so scrolling back up later still makes sense even after the context has changed.
Pointing Aimée at something specific#
The fastest way to direct Aimée at one particular thing is to select it first:
- In Studio: select one or more elements on the canvas.
- On a channel: tick fields in the Fields tab, or open an automation for editing.
Your selection shows up as focus chips by the chat input, and it's sent along with your message — so "make this bigger," "rewrite this," or "why is this field empty?" target exactly what's selected, no description needed. Remove a chip before sending if you don't want something included, and your sent message keeps a snapshot of the chips so you can see later what a request referred to.
Versions vs. Ctrl+Z — which to use when#
Both exist, and they solve different problems:
- Ctrl+Z (undo/redo) is for immediate, fine-grained correction — right after an edit (yours or Aimée's) that you want to back out of a step at a time. It works exactly like undo anywhere else in Studio.
- The version timeline is for checkpoints — a committed snapshot taken at the end of each of Aimée's turns. Use it when you want to go back to "how this looked before that whole request," not just the last keystroke, or when you want to see the recent version history of a template/channel across multiple chats. Restoring a version never deletes anything — it creates a new current version on top of history, so you can always come back.
Rule of thumb: reach for Ctrl+Z while you're still in the moment; reach for the version timeline once you've moved on and want to compare or roll back to an earlier checkpoint.
Interrupting Aimée mid-response#
If Aimée is in the middle of streaming a response or making a change, you can stop her at any point instead of waiting for the turn to finish. Interrupting stops further tool calls from that turn; anything already applied up to that point stays as it is — use undo or the version timeline afterward if you want to back it out.
Editing manually while she's working#
You can still work with your mouse and keyboard while Aimée is active — for example, tweak an element she just added, or make an unrelated change elsewhere in the template. Both human and AI edits go through the same undo history and versioning, so most edits coexist without conflict. If you and Aimée edit the exact same element at the same moment, though, the later write wins — so avoid touching the same element she's actively working on.
The channel safety net: draft first, publish when ready#
Channels get an extra layer of protection because they drive your live, ad-network-facing feed. Whether you or Aimée make the edit, changes to a channel's fields, automations, or settings land on a draft — the feed your ad network is actually reading keeps serving the last published version until you explicitly publish.
This means you can ask Aimée to make several channel changes, review them, and only publish once you're satisfied — she can never push a change straight to your live feed. See Publishing a channel for the full draft/publish/discard workflow.
Working with your catalog and feed in the same conversation#
Your catalog — and the product feed it imports — is a full surface Aimée can work in, just like a template or a channel, and you can move into it mid-conversation. Ask her to take you to a catalog, or open its page yourself, and keep the same chat going.
Once you're there, she can shape the feed the same way you would by hand:
- Set up a feed from your store's web address — give her your store's address and she finds the product feed, connects it, and lines the data up for what ad networks expect. See Let Aimée set up your feed.
- Fix or correct the feed URL — she checks the address actually serves a product feed before saving it.
- Clean and reshape the incoming data — add rules (conditions plus actions) to fix values, exclude products, or split variants; map your feed's columns to the fields channels expect; and pull in a second feed with a lookup or a mapping table. See Transforming your feed.
Catalog edits get the same draft safety net as channels: nothing reprocesses and no channel sees them until you publish — and publishing a catalog also kicks off a fresh import. As on every surface, she shows you an approve-or-cancel card before anything goes live.
Asking Aimée to wait for an import#
A feed import takes a little while to run. Rather than watching the catalog page yourself, you can ask Aimée to wait for the import to finish — she reports back the real product counts and any warnings once it completes, so you know the run worked without checking on it. A feed import is the one kind of job she'll wait on for you.
Can Aimée generate AI images or video in Studio?#
Yes, both. While you're editing a template, you can ask Aimée to generate an AI image or video directly in the conversation — she creates it and drops it into the template as a new element, for example a full-canvas backdrop video behind your product.
Video generation has a few things worth knowing:
- The template needs to already be in video mode (a duration set above zero) — see Video templates. Aimée can turn video mode on for you if you ask.
- She can generate video two ways: animating an existing image into motion (cheaper), or a freestyle video generated from a text description alone (more expensive, since it's building the whole scene from scratch).
- Generation takes a few minutes and consumes credits — she'll tell you before starting.
- She can't generate a music track. Background music has to be a file you upload yourself. A spoken voice-over is the exception — it doesn't need uploading either, because Studio can generate one from a templated Voice script at render time (see Video templates).
This is billed as part of your Studio AI credit usage, the same as other rendering work. See AI image and video generation for how to choose a generation model and how the result reaches your templates and channels.