Skip to main content

Cookbook

Complete, copyable, end-to-end recipes. Each solves a real use case with code you can paste and run.

Unlike guides (which are tasks), recipes are complete projects.

Available recipes​

RecipeUse case
Q&A bot over PDF corpusTurn a folder of PDFs into a Q&A bot with a web UI

Coming soon​

In development

The following recipes are queued:

  • Claude Code with per-project memory — set up persistent memory that travels with your repo.
  • Multi-tenant memory on S3 — one GRAIL project per client, centralised storage.
  • Auto-discovered entity types — use create-entities to adapt GRAIL to a new domain.
  • Mixed KB + memory project — official reference (PDFs) plus agent memory over conversations.

Typical recipe structure​

Each recipe follows the same format:

  1. Use case — what problem it solves.
  2. Stack — which pieces you use (mode, vector store, LLM, etc.).
  3. Step by step — complete code, commands, configuration.
  4. Try it — a command or sample to verify it worked.
  5. Extend — how you'd adapt it to a similar case.

Have a recipe you think is missing?​

Open an issue on the repo or a PR against docs-site/docs/cookbook/.