Playground

Documentation Index

Fetch the complete documentation index at: https://docs.agentmark.co/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

The Playground lets you run the same prompt across multiple models and parameter configurations side-by-side. Compare outputs, tweak prompt text per variant, and apply the winning configuration back to your editor — all without leaving the Dashboard.

​

Entering comparison mode

Open any prompt in the editor and click the Compare button in the top-right corner of the tab bar. The Compare button sits at the right edge of the editor tab bar, next to the Editor and Commit History tabs. Its outlined style indicates comparison mode is off; clicking it switches the button to a filled style and collapses the file tree. When you enter comparison mode:

• The file tree collapses to give variants maximum horizontal space
• The navigation sidebar minimizes to icons
• Two variant panels appear side-by-side, ready for configuration

Click Compare again to exit and return to the standard editor. Your variant configurations are preserved — re-entering comparison mode restores them.

​

Configuring variants

Each variant panel has its own independent configuration: Two variant panels fill the editor area side-by-side. Each panel header shows a Variant 1 / Variant 2 label, an Apply button, duplicate and remove icons, a Model dropdown, a Temperature slider with a settings-gear button, and a Run button.

​

Model selection

Select a different model for each variant from the Model dropdown. All models configured in your model schema are available.

​

Temperature

The Temperature slider is inline for quick adjustments. Click the gear icon to open the Parameters popover for max tokens, top-p, and other settings.

​

Prompt override

Click the Prompt accordion on any variant to expand the prompt editor. Each variant starts with the base prompt text and can be edited independently. The Prompt accordion is expanded on the left variant, revealing the code editor populated with the base prompt text. Edits here only affect this variant. When a variant’s prompt differs from the base, a Modified badge appears. This makes it easy to see which variants have custom prompt text at a glance.

​

Running variants

​

Run all

Click Run All in the toolbar to execute all variants simultaneously. Each variant streams its output independently — if one errors, the others continue.

​

Run single

Each variant has its own Run button for re-running just that variant without affecting others.

​

Output and metadata

After execution, each variant displays its output alongside metadata chips showing:

• Model name — which model generated the response
• Latency — end-to-end response time
• Token usage — prompt / completion / total tokens
• Finish reason — why the model stopped (e.g., stop, length)

After Run all completes, each variant shows its streamed output as monospaced text, followed by a bottom metadata bar of chips: model name, latency (e.g. 3.45s), a combined prompt / completion / total tokens chip, and the finish reason.

​

Managing variants

​

Add and remove

Click Add Variant to add panels (up to 6 maximum). Remove a variant with the X button in its header (minimum 2 required).

​

Duplicate

Click the copy icon on any variant to duplicate its model, parameters, and prompt override into a new panel.

​

Grid layout

Variants are arranged in a 3-column grid:

• 2-3 variants: single row
• 4-6 variants: wraps to two rows (3 per row)

Six variants fill a 3×2 grid — three variants per row. The Run all button in the toolbar header executes every variant in parallel.

​

Applying a variant

Once you’ve found the best configuration, click the Apply button on that variant’s header. This writes the variant’s model, parameters, and prompt text back to the main editor — then exits comparison mode so you can review and publish.

​

Limitations

• Maximum 6 variants at a time
• Variables are shared across all variants (per-variant variables are not yet supported)
• No dataset integration — for systematic evaluation across many inputs, use Experiments
• Ephemeral state — variant configurations are not persisted across page reloads

​

What’s next

• Create a Prompt — set up your base prompt before comparing
• Version Control — publish the winning variant as a new version
• Experiments — run prompts against datasets for systematic evaluation