Playground
The Playground is an interactive testing environment where you can evaluate model responses and guardrail behavior in real time.
Key capabilities:
- Live policy testing — Enter sample prompts and responses to see how your active policies would evaluate them. View detection results, confidence scores, and actions that would be triggered.
- Policy experimentation — Test different action settings and message type configurations to understand their impact before saving changes.
- Custom content testing — Paste real-world examples, edge cases, or adversarial inputs to validate policy behavior against known scenarios.
- Batch prompt files — Attach a CSV of up to 200 prompts and evaluate them all at once instead of sending them one at a time. See Testing a batch of prompts below.
- Example prompts to start from — Before the first message, a row of example types sits under the message box. Pressing one loads a sample prompt of that kind into the box for you to read, edit and send. See Starting from an example below.
- Sample prompt bank — Full Examples CSV, the last item in that same row, downloads a ready-made CSV of test prompts matched to your project's policies, to review, edit, and send back through the batch flow. See Starting from the sample prompt bank below.
- Image prompts — Models that accept images take one alongside the text prompt, so a policy can be tested against what an image carries and not only against wording. See Attaching a file below.
- Audio prompts — Attach a WAV or MP3 and the model answers it while your policies evaluate what it says. See Attaching a file below.
- One model list, grouped by provider — The Model dropdown is the only model control: it lists every provider's models together, under a heading naming the provider that serves each run of them, so picking a model is one step rather than picking a provider first and then a model. Provider is recorded with the message from whichever model you chose.
- Every model listed can be run — The Model dropdown offers only the models the Playground can send to, rather than the provider's whole catalog with the rest shown greyed out. The list is short, and anything in it is a valid choice.
- What each model accepts — Every row in the list carries icons for what that model takes: a picture icon for a model that accepts images, a play icon for one that accepts audio, and a document icon on every row, since they all take text. Attaching is never blocked by them — pick by the icons, or attach first and let the send button tell you the model cannot take what you have staged.
- Rapid iteration — Adjust policy settings and re-test immediately, enabling fast feedback loops during policy development.
- Per-message verdict — Every evaluated message is labelled at the top of its own card with what the guardrails did to it: Blocked where the message was refused, Masked where it was rewritten and still delivered, Detected where a policy matched and the message went through anyway, and Not-violative where nothing fired. A message that was acted on is outlined in red. Under the card, each policy that detected something is listed with its risk score out of 100, named as it is in your Policy Catalog — so a verdict here reads the same as the same policy does in Data Explorer and on the policy pages.
- Which prompts were evaluated — A prompt sent with Guardrails on carries a shield beside User, and the Not-violative label when nothing fired, so a message that came back clean is distinguishable from one no policy ever looked at. A prompt sent with the toggle off carries neither. The mark is recorded per prompt, so a chat where you turned the toggle on or off part-way through still shows it correctly for each prompt when you reopen it.
- When a message gets no answer — A prompt whose request timed out or failed says so in place of the answer, rather than sitting there looking like one still being written. Where the fault was the model provider's — it timed out, rate limited us, or returned an error — the message says so, so a slow or unhappy model is not mistaken for a problem with the platform. Send it again to retry, or pick a different model. How long a model is given depends on the model: the fast text models are cut off after about 20 seconds, while the reasoning, image and audio models are given about 90, since they legitimately take longer to answer.
- An application is required — A message is always evaluated against a specific application, so with none to choose from the message box stays blocked with No applications available to you. Add one under Application Inventory.
- Chat list — Past chats are listed on the left, under a Chats tab, where you can search them and reopen one. A chat with one message is named by the start of that message. From the second message on, it is named by a short title, ten words at most, written by AI and based mostly on what you asked; the title is updated with each message up to the fourth, then stays as it is. Until a title arrives, or if one cannot be written, the chat keeps the start of its first message. A chat that contains a prompt file keeps the file's name. Delete Chats, below the list, clears them all. Use the toggle at the right of the tab strip to collapse the pane into a narrow rail — each chat becomes an icon whose tooltip shows its name. The choice is remembered the next time you open the Playground.
- Active Policies — The second tab beside Chats lists the policies attached to the application selected in the top bar, so what is guarding this conversation is readable without leaving the page. Each one is a card carrying its name, whether it is a System or Custom policy, the message types it governs, and its action — Block, Detect or Mask. Search narrows the list by name, and changing the application in the top bar re-lists it. The cards are read-only; a policy is changed on Enforcement Policies. The tab is also offered on a demo link, listing the policies of the one application that link is pinned to. It is not offered where there is no application to scope it to — a project that assigns policies account-wide rather than per application.
- Starting a new chat — New Chat sits on the right of the top bar, so it is in reach whether the chat list is expanded or collapsed. The chat on screen is saved to the list before the new one opens.
- One history per account and project — Chats belong to the account and project they were sent in, and are listed only there. Switching workspace gives you that workspace's own list, and switching back brings yours here. Chats are stored in your browser, so they do not follow you to another browser or machine.
- Deleting one chat — Hovering a chat in the list reveals an actions menu at its right edge; choose Delete there and confirm to remove that chat on its own, leaving the rest of the list alone. Deleting the chat you are reading clears the thread and starts you on a new one. The actions menu is not offered in the collapsed rail, and deletion cannot be undone.
- Chats reopen in context — A chat is saved with the settings it was held under: model, application, and whether Guardrails was on. Reopening it puts those back in the top bar, so what you are reading is labelled with how it was produced — a verdict only means something next to the policy set that produced it. A chat saved before this was recorded leaves the top bar as you have it.
- The top bar is remembered — What you last selected with no chat open is what the next new chat — and your next visit to this account and project — starts from, so a reload does not send you back to picking a model and an application again. Reopening a saved chat changes the top bar for that chat only; it does not become your starting point. A remembered model or application that no longer exists is dropped rather than left in place, since it could not be sent with.
Attaching a file
The plus on the leading edge of the message box is where every attachment starts, whatever kind of file it is.
- What the plus offers — Prompt file (CSV), Image and Audio. Each option states what it takes (max 200 prompts; PNG, JPEG, GIF or WebP up to 5 MB; WAV or MP3 up to 7 MB). Prompt file (CSV) is offered only in a new, empty chat; once a chat has a message, the plus offers Image and Audio alone.
- Every kind can always be attached — Image and Audio are offered whatever the selected model accepts, so you never have to guess a model before you can pick the file. What the model accepts is checked when you send, not when you attach.
- The send button is what refuses a file the model cannot take — Stage an image on a model that takes no images, or audio on one that takes no audio, and Send greys out. Hover it and it names the mismatch and tells you to switch to a model that accepts that kind of input. Switching the model in the top bar releases the send; the staged file stays put.
- The model list shows what each model accepts — every model in the dropdown carries small icons for text, image and audio. Hover an icon to read it. Picking a model marked for the kind you are about to send saves the round trip.
- One thing at a time — A typed message, one image, one audio file, or a CSV — never a combination. While one of them is in the box the others are greyed out, and the plus itself goes inactive once you start typing. An attached image or audio file can still be swapped for another; remove it with the ✕ on its card.
- What an attachment looks like — Whatever the kind, it stages as a card inside the message box carrying the file name and what it holds — the number of prompts for a CSV, or simply Image or Audio. A CSV and an image offer Preview; audio offers a play button that plays it where it stands.
- What comes back for audio — The model answers it, and your policies evaluate it as well when Guardrails is on. Only a model that accepts audio can be sent it, and only in the formats it accepts, so an audio turn is not left without a reply.
- Playing it back — A sent image or audio file stays in the conversation, and audio plays from the message itself, so you can hear what was evaluated.
- Sending a long prompt — The message box grows with what you type, up to about six lines, then scrolls. Enter sends; Shift + Enter starts a new line, so a multi-line prompt can be composed without sending it half-written.
Starting from an example
Before the first message of a chat, a row under the message box offers one example per policy area your project moderates — Test prompt injection, Test PII leakage, Test adult content, and so on.
- What pressing one does — It loads a sample prompt of that kind into the message box and puts the cursor at the end of it. Nothing is sent: read it, edit it, then send it yourself.
- Which examples you see — The same narrowing the sample prompt bank uses, so the row covers what your project actually moderates. Every example is meant to trip something: the harmless control prompts are in the CSV download, not here, since an empty message box already invites you to type anything you like.
- One prompt per example per visit — Pressing the same example twice reloads the same prompt. Reload the page for a different draw.
- When it is not offered — The row belongs to the empty chat only; once a chat has a message, the message box stands alone. The examples also grey out while an attachment is in the box, since they write into a box that is holding something else.
Starting from the sample prompt bank
Full Examples CSV, the last item in the examples row, gives you a starting set of test prompts, so you do not have to write one from scratch.
- What you get — A
sample-prompts.csvwith a singlepromptcolumn, ready to attach back as-is. - Matched to your policies — The file only contains prompts for the policy areas your project has enabled, so you are not testing for things you do not moderate. Everyday, harmless prompts are always included as a control group: they show whether your policies over-block ordinary traffic.
- When it cannot be matched — Custom policies are named by you, so they cannot be mapped to a policy area. If your project moderates on one — or has no policies enabled at all — you get the full bank instead of a narrowed one, since a file of nothing but harmless prompts would come back entirely clean and read as guardrails that never fire.
- Yours to edit — Review the file, delete what is not relevant, and add your own prompts before uploading it.
Testing a batch of prompts
Start a new chat and attach a .csv of prompts (up to 2 MB) through the plus button — see Attaching a file above. A prompt file is a chat of its own: it can only be attached to an empty chat, and once it has been sent the chat is its results: it takes no new messages or files, though each row can still be followed up from its detail (see Following up on a prompt below). Use New chat in the top bar to start a fresh test.
- File format — The first row must be a header row. If the file has a single column, that column is used. Otherwise the column named
prompt,text, orinputis used; if none of those is present, the message box asks which column holds the prompts, under the attachment card. Other columns are ignored. - Before sending — The attachment card shows the file name and how many prompts were detected, so a wrong file is caught before spending model calls. Preview reads the full list, headed by the column the prompts came from. Repeated prompts are kept, not removed — a deliberate duplicate is still evaluated.
- Results — Each prompt is evaluated on its own, as an independent single-turn conversation, so no prompt is influenced by the one before it. When the run finishes, the chat shows its results in place of the conversation, with a row per prompt carrying its result, risk score, and any detections. The chat is listed under the file's name, and reopening it from the sidebar brings the results back.
- The file header — The results view opens on a header naming the file, with how many prompts it holds, its size and the model they ran against, and the run's split on its trailing edge: All, then Violative and Not Violative where guardrails were on, and Failed where a prompt never got a verdict. Those counts are also the filter — see below.
- Filtering — Click a group in the file header — All, Violative, Not Violative, Failed — to narrow the list to it, or search across prompts, responses, and detection names. Each option carries its own count, taken over the whole run, and the three groups add up to All. Failed is not a verdict — it collects the prompts the run never managed to evaluate, so they can be pulled out of the list and re-run rather than read as prompts that passed. A group with nothing in it is not offered: a run's results are fixed once it finishes, so an empty option could never become useful. A run where no group can be picked still states its total, since that is the run's size either way — it just isn't offered as a choice, and search is the only narrowing left. Beside the search, Policy narrows the list to rows that hit any of the chosen policies (it offers only policies that fired in this run), and Action to rows that were Blocked, Detected or Masked. Both take several values and combine with the group and the search.
- Sorting — The list opens in file order, so the row number matches your CSV. Click a column header — #, Prompt, Policy or Risk score — to sort by it, click again to reverse it, and a third time to drop the sort and go back to file order. Sorting applies to the rows the filters and search have left, and the whole run stays on one scrolling list — there are no pages to step through.
- Policy column — A prompt that tripped a policy shows that policy as a tag, coloured by its category the same way as on Enforcement Policies — Security, Privacy or Safety. Where several policies fired, the one with the highest risk score is shown, followed by a count of the others; hover the count to read their names. A prompt that tripped nothing has no tag. Which action was taken, against which policies, is on the row's detail: open a row to see the same ACTION: line and detections a single chat message shows. Click a row — or arrow up and down the list — to move through the prompts.
- Following up on a prompt — The row's detail ends with a message box. What you send there continues that prompt's own conversation — the model sees the prompt and its answer as history — under the model, application and Guardrails setting in the top bar. The follow-up exchange appears under the row's result and is saved with the chat.
- Risk score — Each row shows its risk as a tag scored out of 100, coloured by band (high, medium, low) — the same bands the row's detail uses. A prompt that tripped several policies shows the highest of their scores, not an average, so one severe hit is never diluted by mild ones — hover the tag to see that spelled out. A not-violative prompt still shows its score, since a prompt that scored high and went through anyway is worth reviewing.
- Sent with guardrails off — A batch sent with the Guardrails toggle off was never evaluated, so there is no verdict to report: the results view drops the two verdict groups and the per-prompt tags, leaving the run's total. Failed still appears if any prompt failed, since a prompt can fail to send whether or not guardrails were on. Nothing is hidden — every prompt and response is still there. A run that WAS evaluated is marked with a shield on its results header, the same mark a single evaluated prompt carries; a run sent with the toggle off carries none.
- Downloading the results — A download button on the file header inside the results view writes the whole run to a CSV — so verdicts can be shared, compared between runs, or analysed outside the platform. The file has one row per prompt you uploaded, in file order and keyed by the row number in your own CSV — including the prompts the run never evaluated — and carries the prompt, the response, the verdict, the policies that fired, the risk score, and the error where there is one. It is the whole run, not the list you are looking at: the filters, the search and the sort do not narrow it. The file is named after the file you uploaded and the run it came from, so two runs of the same prompts do not overwrite each other. A run sent with Guardrails off leaves the verdict, policy and risk columns empty, since nothing was evaluated to report.
- Kept with the chat — A file's full breakdown is saved alongside the chat, so reopening that chat from the sidebar brings every per-prompt row back. Results live in your browser only, so clearing the chat history discards them.
- Long-running files — Evaluation is capped at about a minute. If the file does not finish in time, the results still open with a row for every prompt in your CSV. A prompt that was not evaluated carries no verdict — it is counted as neither violative nor not-violative. Inside the results view it is grouped under Failed, and opening it says whether it timed out or the request failed. Attach the file to a new chat to try those prompts again.