Esta página aún no está traducida.

Roll back or withdraw a version

This page is for maintainers of an instruction, and shows how to undo a version that went wrong: make an earlier version live again, bring old text back into the draft, or withdraw a version for good.

All three start in History, the list of an instruction's versions and checkpoints. Each one solves a different problem:

You want to Use Agents switch
Send agents back to an earlier version now Promote to live… The next time they look
Start the draft again from older text Restore Only when you publish
Make sure no agent uses a version again Revoke… Agents pinned to it stop using it

Before you start

  • Your role: making a version live and restoring need the Maintainer role on the instruction. Revoking needs the Admin role. People and roles.
  • Signed in: promoting and revoking work on instructions kept in your workspace on instruction.md. Restoring also works without an account.
  • A published version: promoting needs at least two versions. You can't promote the version that is live already.

Make an earlier version live

Use this when the newest version is wrong and agents need the last good one now. Nothing new is published: the live version moves back to the version you pick.

  1. Open History

    Open the instruction, then open History in the side bar. The version that is live now is marked Live.

  2. Pick the version to go back to

    Click the earlier version you want, for example v3. Its buttons appear under it. Click Compare with now first if you want to check what it says.

  3. Promote it

    Click More options (the "…" button), then Promote to live….

    A question asks "Make v3 live?". It says "Agents that follow it get v3 instead of v5 the next time they look. You can move it back from History."

  4. Confirm

    Click Make v3 live.

    A message says "v3 is live — agents that follow it get it now". In History, v3 is marked Live.

History ▸ a version ▸ More options ▸ Promote to live…

When agents switch

Agents that follow the live version get v3 the next time they look. An agent that gets live updates is told at once. A coding agent takes it at your next prompt.

Some agents don't switch:

  • Agents that follow stable, or another name you made. Each name moves on its own, so promoting a version to live doesn't move stable. stable's Follows gate doesn't go back either: it only moves to newer versions. See Keep agents on a stable version.
  • Agents pinned to one version. They stay on it.

v4 and v5 are still there, in History. To make v5 live again, promote it the same way.

Restore old text into the draft instead

Use this when you want to keep working from an older text, not switch agents now. Restore puts a version's text, or a checkpoint's, back into your draft. Agents don't see it until you publish.

  1. Pick the version or checkpoint

    In History, click the version or checkpoint you want.

  2. Restore it

    Click Restore.

    The draft now holds that text. History keeps a checkpoint called Before restoring first, so you can go back to what you had.

  3. Publish it

    Check the draft, then publish it. It becomes a new version, for example v6, and agents switch to v6 as with any publish. See Publish a version.

Promote or restore?

  • Promote to live… is fast, and makes no new version. The live version is an older one again, and the newer versions wait in History.
  • Restore makes a new version from the old text when you publish. The newest version is the live one again. Use it when you want to change the old text a little before it goes out, or when you want the next version to start from it.

A restored checkpoint brings back its suggestions too, as suggestions.

Revoke a version

Revoking marks a version as one no agent should use again. Use it when a version must never be applied, for example if it had a mistake that could harm a customer.

Revoking can't be undone.

  1. Move every name off it

    A version that is live, or that stable or another name points at, can't be revoked. First make another version live, and move stable off it. History shows each name as a tag on the version it points at.

  2. Revoke it

    In History, click the version. Click More options, then Revoke….

    A question asks "Revoke v4?". It says "Agents pinned to it hold their last good version and are told it was revoked. It stays in History, marked revoked."

  3. Confirm

    Click Revoke v4.

    A message says "v4 is revoked". In History, v4 is marked Revoked.

What agents do after a revoke

An agent pinned to the revoked version keeps the last good version it had, and it is told the version was revoked. Pin it to another version, or let it follow the live version. Agents that follow live or stable aren't affected: those names pointed at other versions before you could revoke it.

Go back after an AI edit

When Claude or the editor's assistant edits your draft, History keeps a checkpoint first. It is called Before Claude's edit or Before the assistant's edit.

To undo the whole edit, click that checkpoint in History and click Restore. Nothing was published, so agents never saw the edit. To undo only part of it, click Compare with now and copy back what you need.

If History says "Claude is still writing: restore when it's done", wait until the edit has finished.

Check it worked

  • In History, the version you promoted is marked Live.
  • The Agents card shows the version each agent has. Once they have looked again, the agents that follow the live version show the one you promoted. See See the agents that follow an instruction.
  • A revoked version is marked Revoked.

Undo or stop

  • Promote to live… can be undone: promote the version that was live before.
  • Restore can be undone: restore the checkpoint Before restoring.
  • Revoke… can't be undone. Publish the same text again as a new version if you need it.

If it doesn't work

What you see What to do
No Promote to live… or Revoke… in More options The version is live already, or it is revoked, or your role is Reader or Contributor, or you aren't signed in. Ask a maintainer.
"move stable off v4 first" A name still points at the version. Move it to another version, then revoke.
"this needs manage on the instruction; you have publish" Maintainers see Revoke…, but only an Admin can revoke. Ask someone with the Admin role on the instruction.
"the ref latest takes versions whose checks passed; v3's failed" The live version has the gate Checks must pass, and this version failed. Restore its text, fix it, and publish it.
"Its text wasn't kept on this device, so it can't be compared or restored." The editor only has this version's text in the browser it was written in. Open it there, or sign in so it is kept in your workspace.
"This instruction is open read-only in this window" Use the window where it is open for editing.
"Making it live didn't work — check your connection and try again" Check your connection and try again. Still stuck: Troubleshooting.

Questions

What does 'live' mean, and how do I make an older version live again?

The live version is the one agents get when they follow the instruction without naming a version. History marks it Live. To go back, open History, click the older version, and choose More options ▸ Promote to live…. Make an earlier version live.

Does rolling back delete the newer versions?

No. Every version stays in History. Promoting only changes which version is live, so you can promote the newer one again later.

Does rolling back move stable too?

No. stable moves only when you move it, or when its own gate moves it to a newer version. Move it yourself if it points at the bad version. Keep agents on a stable version.

What is the difference between revoking and deleting?

Revoking withdraws one version and keeps the instruction and its other versions. Deleting moves the whole instruction to the trash. The Instructions page.

For developers: rolling back is moving a ref; see refs in the model.

Last checked against the product:

Was this page helpful? Report a problem