Skip to main content

​
Overview

The Playground in Bifrost is an interactive workspace for building, testing, and managing prompts. It allows you to experiment with messages, switch models, adjust parameters, and iterate until the output looks right. Once you’re satisfied, you can publish a version and use it directly in your codebase. Over time, the prompt repository becomes a centralized CMS for all your prompts, making it easier to manage versions, collaborate with teammates, and maintain production-ready prompts. Prompt Repository Overview

​
How it Works

The playground is built around three core concepts: prompts, sessions, and versions.

​
Folders

Folders help organize prompts into logical groups. Teams often structure them by product area, feature, or use case.
  • Each folder has a name and optional description
  • Prompts can live inside folders or at the root level
  • Deleting a folder removes all prompts, sessions, and versions inside it

​
Prompts

A Prompt is the main unit in the repository. Think of it as a container that holds the full lifecycle of a prompt, from early experiments to production-ready versions. Each prompt can have:
  • Multiple sessions for experimentation
  • Multiple versions for stable releases

​
Sessions (Working Copies)

Sessions are editable working copies where you experiment with a prompt. You can freely:
  • Modify messages
  • Switch providers or models
  • Adjust parameters
  • Run the prompt repeatedly
Sessions don’t affect committed versions, so you can iterate safely. If your session has unsaved changes, a red asterisk appears next to the prompt name in the top bar.
You can save your progress using:
  • Save Session button
  • Cmd + S / Ctrl + S
Saved sessions can be renamed and restored from the dropdown next to the Save button.

​
Versions (Immutable Snapshots)

When you’re happy with a prompt, you can commit it as a version. Versions are immutable snapshots; once created, they cannot be edited. When the config differs from the last saved version, the Unpublished Changes badge appears, and it can be committed to create a new version. Each version stores:
  • The selected message history (system, user, assistant)
  • Provider and model configuration
  • Model parameters (temperature, max tokens, etc.)
  • A commit message describing the change
Versions are automatically numbered: 
v1 → v2 → v3 → ...
You can also restore a previous version from the dropdown next to the Commit Version button.

​
Workspace Layout

The playground uses a simple three-panel layout:
PanelPurpose
Sidebar (left)Browse prompts, manage folders, and organize items
Playground (center)Build and test your prompt messages
Settings (right)Configure provider, model, API key, variables, and parameters
Workspace Layout

​
Getting Started

1

Create a folder (optional)

Click the ”+” button in the sidebar and select New Folder.Folders help organize prompts by team, feature, or use case.Create Folder
2

Create a prompt

Click ”+” again and choose New Prompt.
Give it a name and optionally assign it to a folder.Create Prompt
3

Build your prompt

Add messages to your prompt in the Playground:
  • System messages for instructions
  • User messages for input
  • Assistant messages for examples or few-shot responses
Configure the provider, model, and parameters from the settings panel on the right.Playground
4

Run the prompt

Click Run or press Cmd + enter / Ctrl + enter.Optionally, if you do not want to execute the prompt and only want to add a message to history, use the + Add button.
5

Save and publish a version

Once you’re satisfied with the results:
  1. Save Session to preserve your work
  2. Commit Version to create an immutable snapshot Commit Version

​
Key Capabilities

​
Version Control

Each committed version creates a permanent record of your prompt. This allows teams to track changes and safely iterate without breaking production prompts. Key characteristics:
  • Sequential versioning — v1, v2, v3, …
  • Commit messages explaining what changed
  • Immutable history

​
Multi-Provider Testing

You can switch between providers and models directly in the Playground. Supported providers may include:
  • OpenAI
  • Anthropic
  • AWS Bedrock
  • Others configured in your Bifrost instance
You can also choose which API key to use:
  • Auto: Uses the first available key.
  • Specific key: Select a particular key.
  • Virtual key: Uses governance-managed keys.
This makes it easy to compare how different models respond to the same prompt.

​
Message Types

The Playground supports several message roles:
  • System: Defines behavior or instructions.
  • User: Input to the model.
  • Assistant: The model’s response to the user’s input.
  • Tool Calls: Function calls made by the model.
  • Tool Results: Mock or real responses from called tools.
These allow you to simulate complex conversations and agent workflows.

​
Attachments

For models that support multimodal input, you can attach files directly to user messages. Supported attachments may include:
  • Images
  • PDFs
  • Other supported file types
Attachments are only enabled when the selected model supports them.

​
Drag-and-Drop Organization

Prompts can be reorganized easily using drag and drop in the sidebar. You can move prompts:
  • Between folders
  • Back to the root level

​
Session Management

Sessions store the state of your prompt experiments. Each prompt maintains its own session history, allowing you to explore different approaches without losing previous work. With sessions you can:
  • Save specific conversation states
  • Rename sessions for clarity
  • Switch between past experiments
Sessions