Prompts
Store the prompts of your agents, save versions, and move them to production with a record of each change.
Manage prompts in the dashboard. An API key can only pull a prompt.
What runs today: you write, version, compare and promote prompts on the Prompts page of the dashboard. Your code pulls a prompt with get_prompt (npm: getPrompt).
What is not available: an API key cannot create a prompt, save a version, move a label or read the label history. The only prompt route that a key can reach is GET /v1/prompts/resolve. See the REST API reference.
A prompt in Risicare is a named object that holds versions. A version holds the messages, the model, the parameters, the tools and the output schema of one LLM call. A version never changes after you save it. A label, for example production, points to one version.
Your code pulls a prompt by name and label. A new version reaches production only by a promotion, and Risicare records each promotion. When you move a label, your code sees the new version after the cache time of the SDK (60 seconds by default): the first call after that time starts a refresh, and the calls after the refresh get the new version. You change no code.
The parts
| Part | What it is |
|---|---|
| Prompt | A name, an optional description and tags. The name never changes, because your code and your traces use it. |
| Version | The saved content, with a number (v1, v2), a note, an author and a content hash. |
| Label | A pointer from a name to one version. The prompt page always shows production and staging. |
| Gate and approval | A check that runs before a label moves, and an optional second person who approves the move. |
| Rollback | A move of a label back to the version that it held before. A rule can propose it. |
The list of prompts
The Prompts item in the side navigation opens the list. It has one row for each prompt.
| Column | What it shows |
|---|---|
| Name | The name, the first line of the description and the tags. An archived prompt has the badge Archived. |
| Production | The version that production holds, and since when. Not set when no version is on production. |
| Newest version | The number, the note, the author and the time of the newest version. |
| Waiting | On production when the newest version is on production. Otherwise a verdict chip against production, for example No change vs v3, or No run when no comparison exists. The marks Waits for your approval and Rollback proposed also show here. |
| Calls, 7 days | The production calls of the last 7 days that carry the prompt name, and how many had errors. |
| Model | The model of the newest version, or Not set. |
The list has no sort control. The api returns the prompts with the newest version first. Press J or K to move between rows, and Enter to open one.
- Search: type in Search name, description or tag and click Search. The search covers all prompts of the project and reads up to 100 characters. Clear the search removes it.
- Tags: click a tag on a row to show the prompts with that tag. Each active tag shows as a chip with a button that removes it.
- Show: a menu with All prompts, A newer version waits, Regressed versions wait, Waits for my approval and Rollback proposed. It filters the rows that the page shows.
- Show archived prompts switches to the archived prompts. Show live prompts switches back.
- Show more prompts adds the next page of rows.
- Seen on traces, not stored lists prompt names that appear on traces from
prompt_contextbut have no stored prompt. Store a version opens New prompt with the name filled in. The section shows only on the list of live prompts, when no search or tag filter is on and the list fits on one page.
A project holds up to 500 prompts.
Create a prompt
Open the editor
Click New prompt. A viewer does not see this button.
Name the prompt
Enter a Name. It starts with a letter or a digit, uses letters, digits, ., _ and -, and has at most 100 characters. Archived prompts keep their names, so you cannot reuse one. Description (optional) has at most 1,000 characters.
Write the content
Fill in the messages, the model, the parameters, the tools and the output schema. See The editor.
Save
Click Save. The dialog shows the change, and asks for a Note for this version (required) of 1 to 500 characters. Click Save v1. The save does not move a label.
The editor
Do not put keys or personal data in a prompt. Your code and your team can read it. A version can hold at most 128 KB.
- Messages: each message has a role (System, User or Assistant). Add a user message and Add an assistant message add one. Add a system message shows only when the prompt has none. Move up, Move down and Remove change the list. Alt + Up and Alt + Down move the focused message. A prompt holds up to 50 messages.
- Variables: write
{{name}}in a message to mark a value that your code fills in. A name uses lower-case letters, digits and_, and starts with a letter or_. The Variables line lists the names. A text such as{{Name}}stays plain text, and a note says so. - Model: Provider is OpenAI, Anthropic or Not set. Model is the model name.
- Tools: Add a tool adds a Name, a Description and Parameters (JSON Schema). A prompt holds up to 64 tools.
- Structured output: Off, or A JSON Schema with a Schema name and a JSON Schema.
Model parameters
| Field | Range |
|---|---|
| Temperature | 0 to 2 |
| Top p | 0 to 1 |
| Max output tokens | 1 to 200,000, a whole number |
| Seed | A whole number |
| Stop sequences | Up to 4, each 1 to 64 characters. Add a stop sequence adds one. |
A number has at most 3 decimal places. An empty field stores nothing, and the provider default applies (Not set). For the provider Anthropic, Temperature and Top p show Not sent to Anthropic: the version stores the value, and the SDK does not send it.
Press Ctrl or Cmd with S to open the save dialog. Press ? to list the keys. Discard asks "Leave without saving?" when the draft changed. On an existing prompt, Try in the playground opens the draft beside the version that you started from. It saves nothing.
Edit, duplicate and archive
- Edit (key E) on the prompt page opens the editor with the content of the open version. The save makes the next version. If another person saved first, Risicare saves yours as the next number and tells you. If the content equals a stored version, the save is refused: "This content is the same as v2. Nothing to save."
- Edit tags in the menu of a row opens a dialog. A prompt holds up to 10 tags. A tag starts with a lower-case letter or a digit, uses lower-case letters, digits,
.,_and-, and has at most 30 characters. Tags and the description are not part of the hash, and they change no version. - Duplicate in the same menu opens New prompt with the content of the newest version. The name starts as
name-copy, and the note starts as "Copied from name v4". - Archive the prompt is in the More actions menu of the prompt page. Risicare blocks it while a label holds a version: "Remove the labels first." Code that pulls an archived prompt keeps its last pulled version or uses its fallback. The name stays taken. Restore the prompt in the same menu brings it back.
Who can do what
| Action | Viewer | Member | Admin | Owner |
|---|---|---|---|---|
| Read prompts, versions and the label history | Yes | Yes | Yes | Yes |
| Create, edit, duplicate, tag, archive and restore a prompt | No | Yes | Yes | Yes |
| Move a label past a passing gate, ask for a promotion, roll back | No | Yes | Yes | Yes |
| Override a blocked gate, save the gate settings | No | No | Yes | Yes |
| Change a label rule in Settings → Prompt labels | No | No | Yes | Yes |
| Turn off approval in a label rule | No | No | No | Yes |
Who can approve a request depends on the rule of the label. See Gate and approvals. A member or a viewer sees the name of an author as "A team member". Owners and admins see the names.