Getting started with the Prompt Library
Your agent depends on prompts that change frequently. The Prompt Library lets you manage them outside your codebase, version each change automatically, and link the exact version that ran to its trace.

Adding the Prompt Library to your code
AI Integration
Manual integration
You can use the Opik skills to wire your existing agent up to the Prompt Library:
Choosing a version
Pass the version parameter to control which version is returned:
- Omit
version(default) — The most recently created version. Useful when you want the agent to pick up new prompt edits automatically. "v3"(or anyv<N>name) — A specific version. Useful when you want the prompt to stay fixed regardless of newer edits — for example, when reproducing a past run or comparing versions.
Chat prompts
For multi-turn agents with system, user, and assistant roles, use create_chat_prompt /
createChatPrompt and the matching get_chat_prompt / getChatPrompt. See
Text and chat prompts for a deeper comparison,
multimodal content, and template engines.
Recommended if you build with an AI coding assistant. One command — opik configure —
installs both the MCP server and the Opik skills, and your assistant can then
version prompts here as it edits them, and measure whether a change actually helped instead of
you judging by eye.
An example prompt:
“Rewrite this system prompt to cut hallucinations, save each attempt to the Opik prompt library, and evaluate every version against my dataset so we can see which one wins.”