Skip to main content
Your context repository is just a file system. You have complete freedom to organize it however works best for your team.

​
Customize your context

You can customize your context by:
  • Creating new folders — Organize by team, domain, project, or any structure that makes sense
  • Adding new types of context — There are no restrictions on what you can include
  • Using any file format — Markdown, YAML, SQL, JSON, CSV, and more

​
Examples of Custom Context

Here are some common types of context teams add to their repository:
  • Business Definitions — How your organization defines key metrics (e.g., active customer, churn, revenue)
  • Query Examples — Vetted SQL queries your team can reference
  • Dashboard References — Links to trusted dashboards and reports
  • Glossary & FAQs — Common questions, acronyms, and terminology
  • Data Quality Notes — Known data gaps, timezone info, caveats
Keep your custom context organized and modular. Ensure each metric has only one canonical definition, and organize context by domain to keep the agent focused and reduce token costs.

​
Request New Context Types

Want a new type of context to be automatically synced? We’d love to hear from you.

Open an Issue

Request new context types or suggest improvements on GitHub
 Next Steps

Context Engineering Playbook

Step-by-step guide to building effective context

Context Principles

Learn how to optimize your context structure

Start Chatting

Use your fully configured agent

Deploy

Deploy for your team