The editor

The editor combines chat, file/source context, and a running preview so you can validate behavior before your audience sees it.

Layout at a glance

You will typically see: the assistant thread, the generated source (or diff-aware tooling), and a preview pane that executes the bundled app in a safe environment.

editor-overview

Placeholder: tour of chat, code/preview split, and key controls.

Source version history

The platform records snapshots of your project source. You can list prior versions and restore one when an experiment goes wrong—without losing the ability to publish from the latest stable point.

Tip:
Restore is ideal right after a bad merge from the assistant; combine with smaller prompts to stay on track.

Draft vs published for platform data

Workflows and record types support draft editing separate from what public visitors execute. Preview and builder tools use draft definitions where appropriate; production traffic uses published snapshots.

Warning:
Publishing code and publishing data definitions are related but distinct—publish each when you intend end users to see the change.
  • Accept applies pending assistant/cache state into durable draft rows.
  • Publish copies draft definitions to the published columns used by public APIs and workflow runs.
  • Discard draft reverts to the last published copy when you need to undo exploratory edits.