The Prompts page is your prompt version control system. Every prompt change creates a new immutable version — previous versions are never overwritten. You assign labels likeDocumentation Index
Fetch the complete documentation index at: https://docs.lumiqtrace.com/llms.txt
Use this file to discover all available pages before exploring further.
production and staging to versions, and your running application fetches prompts by label at runtime using the SDK. This means you can update a production prompt without touching your code.
The prompt library
The main Prompts page shows all prompts in your project as a list. Each row shows the prompt name, the number of versions, which labels are active, and when it was last updated. Click any prompt to open its version history view.Creating a prompt
Choose a name
Enter a slug-style name for the prompt, e.g.
support-reply or product-description-generator. This name is used by the SDK to fetch the prompt at runtime.Choose a type
- Text — a single string with
{{variable}}placeholders for dynamic content - Chat — an array of message objects (
role,content) with placeholder support
Write the prompt
Enter your prompt in the editor. Use
{{variable_name}} syntax for any values you want to substitute at runtime.Add model config (optional)
Optionally fill in suggested model, temperature, and max_tokens. These are stored with the prompt for reference but are not enforced by the SDK — you decide whether to use them.
Add a commit message
Write a short description of what this version contains. Commit messages appear in the version history.
Version history
Each prompt’s detail view shows a table of all versions:| Column | Description |
|---|---|
| Version | Sequential version number, starting at 1 |
| Labels | Active labels on this version (e.g., production, staging) |
| Commit message | Description of what changed |
| Created | Timestamp and author |
| Actions | View, promote, roll back |
production label to this version in one click.
Labels
Labels are mutable pointers to specific prompt versions. The recommended workflow is:- Create a new version and assign it the
staginglabel - Test the new version in your staging environment
- When ready, promote it to
productionby clicking Promote or by callingupdateLabels()in the SDK
Labels are not exclusive by default. You can have
production on multiple versions simultaneously. If you want a single canonical production version, remove the label from the old version before promoting the new one.Protected labels
Some labels — such asproduction — can be locked so that only users with Admin or Owner roles can move them. Configure protected labels in Settings → Prompts. This prevents accidental promotion from a Member-level account.
Rollback
To roll back to a previous version:- Open the prompt’s version history
- Find the version you want to restore
- Click Roll back — this moves the
productionlabel to that version instantly