Outputs and revisions

The output is the working document for a chat. It appears in the conversation right after the reply that produced it, so you can refine the deliverable without losing the discussion around it. While the Agent writes, the reply and the document fill in as they are generated; the saved version replaces them when the turn finishes. The document is saved together with the reply, so a turn that stops early saves neither.

Review the first output

Check the target, intended audience and supporting sources. Each reply lists the sources CiteLadder read for it, grouped by kind and linked to the screen that shows them; a revised document keeps the sources of the version before it. Separate measured facts from recommendations. If the Agent reports omitted or unavailable evidence, decide whether you can proceed with those limits.

Ask for a focused revision when necessary: “Keep the structure, remove the unsupported claim, and explain which data supports the second recommendation.”

Ask for an outline when you want one

The Agent writes the whole deliverable straight away. If you would rather agree the structure first, ask for an outline; it answers in the chat, and you can then ask for the full draft. When you ask for a change to an existing document, the Agent edits just the parts that change and keeps the rest.

Edit without losing history

Edits, yours and the Agent’s, append a new revision. They do not overwrite the earlier one. The next Agent turn works from the latest revision, including your own changes.

Restoring a previous revision also creates a new revision. Use history to inspect earlier work and deliberately bring back the version you want.

If the output changed since you opened it, reload the latest revision before saving an edit. Edits and restores are unavailable while a turn is queued or running.

Copy or export

Use the output pane’s copy or Markdown export controls to move reviewed work into your team’s publishing or implementation workflow.

Review the destination after pasting, especially tables, links and formatting. Exporting content is separate from publishing it.

Tie the shipped work to the right version

After your team makes the actual change, use Mark implemented for the attached Action and confirm the revision you shipped. CiteLadder preserves that relationship for later measurement.

Do not declare a speculative draft or a different Action’s output as implemented.

Recover from an interrupted turn

Use Stop in the composer to end a turn that is running. A stopped, failed or budget-limited turn is not a completed new revision. The Agent replies with what happened and what to do next, and nothing from that turn is saved.

Choose Try again to send the same request as a new turn, or Edit last request to change it first. After a finished reply, Regenerate asks for a fresh answer the same way. If the reply says the request was too large, make it smaller, for example one section at a time. Earlier completed revisions stay part of the chat’s history.