Publishing and Versioning

Save prompt versions, review version history, roll back changes, and create prompt deployments for runtime use

Use versioning to save stable checkpoints of a prompt and create a prompt deployment when you want to call that prompt outside the editor.

Overview

The prompt editor separates authoring from runtime use. You can test changes with Run, save them with Save Version, review older versions in Version History, and use Create Endpoint or Update Endpoint when you're ready to make the prompt available outside the editor as a prompt deployment.

In docs prose, refer to this public runtime surface as a prompt deployment. Keep UI labels such as Create Endpoint and Update Endpoint exactly as they appear in the product.

How do I save a prompt version?

Open the prompt in the editor.

Click Save Version in the header.

Enter a short description of what changed.

Click Save Version to create a named checkpoint for the current state of the prompt.

Use version descriptions that explain the change clearly. This makes it easier to review and roll back later.

How do I review version history?

Open the prompt in the editor.

Click Version History in the header.

Select a version from the list to inspect its saved snapshot and description.

Use this view when you need to compare recent changes, confirm who saved a version, or decide which version you want to restore.

How do I roll back to an earlier version?

Open Version History.

Select the version you want to restore.

Click Rollback.

Confirm the rollback in the confirmation dialog.

After the rollback completes, Fetch Hive restores the selected version in the prompt editor so you can review it and continue working from that point.

How do I create or update a prompt deployment?

Open the prompt in the editor.

Open the prompt menu in the header, then click Create Endpoint if you do not have one yet.

Enter the name, then save it. Fetch Hive takes you to the deployment view for the new prompt deployment and its initial variant.

If the prompt already has a prompt deployment, open the same menu and click Update Endpoint. From there, you can create a new variant or update an existing variant.

Use the deployment name and variant when you want to invoke the prompt through the public API.

Deployment and versioning notes

Prompt versions and deployment variants are related, but they are not the same thing. A prompt version is your editor checkpoint. A deployment variant is part of the runtime surface you use when you invoke the prompt outside the editor.

Keep using Run while you are iterating inside the editor. Create or update a prompt deployment when you need a callable runtime entrypoint for your app or integration.

See also: Creating and Editing and Run with API