Prompt versioning

Prompt versioning is the discipline of treating prompts as source-controlled artefacts — each prompt has a versioned ID, a deploy history, and a regression-tested change log.

By 2026 every credible production LLM team versions prompts the way they version code: prompts live in source control or a dedicated prompt registry (Braintrust, Vellum, PromptLayer, Langfuse), every prompt change ships through a review + eval pipeline, and a stable prompt ID lets you trace which version produced which generated output in tracing data. Versioning enables A/B testing prompts in production, rolling back a bad change, and analysing performance drift over time. Treating prompts as untracked strings is the most common source of silent quality regressions in production LLM apps.

When to use prompt versioning

• Any production LLM feature.
• Multi-prompt agent systems.
• Teams larger than one person.

Common mistakes

• Storing prompts as inline strings — un-tracked, un-versioned.
• Shipping prompt changes without running the eval suite.
• Missing version IDs in traces — you can't debug what you can't pin to a version.

FAQ

Related terms

• Prompt engineering — Prompt engineering is the practice of designing input text that reliably steers a large language model toward a specific output.
• Evals (LLM evaluations) — Evals are systematic tests that measure how well a language model or LLM-powered system performs on a defined task using a golden set of inputs and reference outputs.
• System prompt — A system prompt is the high-priority instruction block that defines a model's role, constraints, and default behaviors for an entire conversation.
• AI agent — An AI agent is a system where a language model autonomously plans and executes a sequence of tool calls to accomplish a goal.

Last updated: 2026-06-01. Raw markdown: https://promtable.com/glossary/prompt-versioning.md.