Skip to main content
Two complementary primitives for giving agents context without ballooning the system prompt.

Playbooks

A playbook is a prompt fragment + a list of tool names. Think of it as a self-contained capability: “I know how to book appointments, and to do that I need these three tools available.”
When an agent has a playbook attached, the playbook’s prompt body gets merged into the agent’s system prompt at runtime, and the agent becomes aware of the listed tools.

Why bundle tools and prompt?

Because the prompt and the tool list have to agree. A “book an appointment” prompt is useless if the book_appointment tool isn’t available. Wrapping them together as a playbook prevents the “prompt mentions a tool that doesn’t exist” bug and makes capabilities composable.

Built-in vs custom

Same model as tools: is_default = true for shipped playbooks, custom ones can be created, updated, and deleted.

FAQs

A FAQ is one question + answer + category. Surfaced to the agent as quick-lookup knowledge for common questions.
FAQs are simpler than playbooks — no tool dependencies, no prompt fragment. Just attached knowledge.

Operations

When to use which