Quasar applies edits through tools — each change appears as a card you can apply or revert. MDX edits often apply immediately with undo. Destructive or publish actions need your confirmation.
Change cards
When Quasar uses a tool, the message shows a Changes section listing each operation:
State
Meaning
Pending
Waiting for you to apply
Applying
In progress
Applied
Change is live in your draft site
Reverted
Undone — draft restored to prior state
Failed
Something blocked the tool — read the error and retry
Use Revert on a single change or Revert all on the message to roll back a whole turn.
What tools can change
Common tool actions include:
Create, rename, move, or delete pages and collections
Publish or unpublish pages (when you ask explicitly)
Generate images for use in content
The UI shows human-readable labels ("Created page", "Updating metadata…") while tools run.
MDX content changes
Text and component edits merge into your draft page content. The visual editor and preview update after apply.If a proposal looks wrong:
Revert the change card, or
Use Undo (⌘Z) in Visual/Source mode for manual edits afterward
Side effects on the file tree
Structural tools refresh the file tree automatically. If you had a page open that was renamed or moved, the editor tries to follow the new path.
Pages
After layout or style tools, the preview iframe refetches so you see updated chrome and tokens.
Publish tools
Quasar can call publish/unpublish tools when you clearly request it ("publish the homepage").
Publishing is intentional
Do not ask to 'set the publish date' expecting a go-live — that usually means page metadata (Published at). Say 'publish the page' or 'make it live' when you want visitors to see content.
Publishing affects the public site, not just your draft. Review the publish menu in Settings if unsure what will go live.
Difference view
Some changes offer a Difference or expand panel showing before/after text — especially for MDX proposals. Use Copy to grab proposed content without applying.
When nothing applied
If Quasar explains a change but no tool ran, click Run it when offered, or rephrase as a direct instruction: "Use the create_page tool to add /pricing.mdx."
Best practices
Review before publish — apply content changes, preview, then publish from Settings.
Revert early — easier than fixing a bad multi-page restructure by hand.
One structural task per turn — large site migrations are easier in steps.
Tool runs in the transcript
While Quasar works, tool calls appear inline in the reply — where they happened in the stream — as collapsed accordion rows. A single tool shows its label (for example "Created page"); multiple tools collapse to Used N tools. Expand a row to see arguments and results.
Older messages without inline offsets still list tools after the reply text. Change cards (apply/revert) are separate — they appear when Quasar proposes MDX or structural edits you review before keeping.
