Create a prompt in Studio

Use Studio›Prompts ↗ in Studio to save prompt templates. Keep a template private or share it with your workspace, then reuse it in Studio or from your applications.

• Reusable instructions: store system instructions, task templates, and output formats in one place.
• Versioning: update a prompt without losing earlier versions.

By the end, you have a saved prompt that you can test, reuse, and share.

Time to complete: ~5 minutes

• An active Studio account.
• A prompt you want to reuse. Good first candidates are support tone guidelines, extraction instructions, or a structured summary format.

1. Open Studio›Prompts ↗ in Studio.
2. Click New prompt.

Give the prompt a clear title and description so teammates know when to use it.

Add the prompt text. Keep the instructions specific enough that another teammate can reuse the prompt without extra context:

You are a customer support assistant. Acknowledge the issue, answer clearly, and propose the next action. Use a calm, concise tone for enterprise administrators.

1. Click Save or Create prompt.
2. Open the saved prompt and review its first version.
3. Test it in a supported Studio surface, such as the Playground, before using it in an application.

From the prompt details page, click Share to choose who can use the prompt:

• Keep it private to use it on your own.
• Share it with the entire workspace so that teammates can find and reuse it.

You can update this visibility later from the same Share button.

Create a new version when you want to change the prompt without overwriting the version that teammates or applications already use. Studio creates the new version after you save changes.

1. Open the prompt from the Prompts list.
2. Update the prompt text.
3. Add version notes that explain what changed, such as Shorter support replies or Adds escalation guidance.
4. Click Save.
5. Confirm the version history shows the new version.

Older versions stay available for review and rollback. Test the new version before you promote it.

To promote the tested version, point an alias such as production at it. For more information, see Versions and aliases.

Your prompt is ready if:

• It appears in the Prompts list with the right title and description.
• A test run produces the expected tone, structure, and constraints.
• Its visibility is correct: private to you or shared with the workspace.
• The version history shows your original version and the updated version.