Contexts
Capture your architecture, business rules, and technical decisions as living documents.
Contexts are where you document the "why" and "how" behind your project — architecture, business rules, technical decisions, and general project knowledge that both humans and AI tools need to stay aligned.
What a Context is for
Think of Contexts as your project's shared understanding — the things a new engineer (or a new AI session) needs to read before touching the codebase: how the system is put together, why a particular technical decision was made, what a business rule actually means in practice. If it's background knowledge someone should understand rather than a rule they must obey, it belongs here.
Typical Contexts: "System Architecture," "Multi-tenant Data Model," "Why We Chose Postgres Over Mongo," "Billing & Subscription Rules."
Creating a Context
- Open a project and go to its Contexts tab.
- Click Create.
- Give it a title and an optional short description (shown on its card in the list).
- Write the body in the built-in Markdown editor — headings, lists, code blocks, links, and bold/italic text are all supported through the toolbar.
- Save. The Context is created as v1, in draft status.
Finding a Context again
The Contexts tab is a searchable, filterable list: search by title, filter by draft/published status, and sort by most recently updated. Each card shows its status and current version number at a glance.
Draft vs. published
A new Context starts as a draft. Drafts are visible to everyone with project access but are never served to connected AI tools. An org admin (owner/moderator) flips it to published — from the card's action menu or the detail page — once it's ready to be the source of truth. Publishing doesn't change the content, just its visibility to MCP/API consumers.
Editing
Title/description and content are edited in two different places, on purpose, so quick metadata tweaks don't get mixed up with an in-progress rewrite of the actual document:
- Title & description — from the card's action menu on the list page, or the pencil icon next to the title on the detail page. Saves immediately.
- Content — open the Context and click Edit. This takes you to a dedicated content editor.
Every content save creates a new version snapshot — it does not automatically become what's live. You explicitly promote a version to Main when you're ready (see Versioning & Publishing for the full mechanics). Until you do, the Context keeps serving whatever version is currently Main.
Version history
From the detail page, open Version history to see every past version in a dropdown, preview any of them, set one as Main, or delete old versions you no longer need (you can't delete the current Main version, and a Context always keeps at least one version).
Deleting
Deleting a Context is permanent and immediate — there's no archive step for individual resources the way there is for Projects. Make sure you actually mean to remove it, not just unpublish it.
Who can write
Creating, editing, publishing, and deleting a Context requires org-admin-level project access (owner/moderator). Everyone with project access can read every Context, draft or published.
Reusing a Context in an Agent Profile
Once published, a Context can be bundled into one or more Agent Profiles alongside Instructions, Skills, Prompt Templates, and Checklists — the same Context can belong to as many profiles as make sense.