Skip to main content

​
Overview

Your context repository is the structured company context Qontext builds for your workspace. It contains normalized Markdown files organized in a folder tree, for example customers, employees, products, projects, and processes. Each file captures shared context about one entity or topic and can reference source objects and related files. Each workspace has one context repository. It updates continuously as connected sources change.

​
What a context repository looks like

The context repository is organized as files and folders. Each file contains structured facts, relationships, source references, and metadata extracted from your connected sources. Example structure:
workspace
Customers
Customer_closed
brightline-solutions.md
clearwater-logistics.md
Customer_leads
redstone-capital.md
Customer_lost
foxwood-media.md
Employees
amara-diallo.md
jonas-becker.md
Products
digital-transformation-advisory.md
managed-operations.md
Projects
crm-migration-salesforce.md
emea-market-expansion.md
When your repository is first created, Qontext proposes a folder structure based on your connected sources. You can review and adjust the folder structure before it is finalized and alter it anytime. You can edit files and folders manually via the UI or via MCP, and Qontext can continue updating them as source data changes.

​
How the context repository is built and updated

Entity extraction

Detects key entities like people, companies, and concepts.

Relationship mapping

Connects related entities across your data sources.

Graph construction

Builds a context graph that reflects real-world relationships.

Continuous updates

Keeps your context current as connected sources change.

​
Why the context repository matters

  • One shared context layer: Store company context once and expose it consistently to agents, MCP clients, APIs, and workflows.
  • Agent-readable structure: Give agents files, folders, references, and metadata instead of fragmented source data.
  • Relationship-aware retrieval: Let agents follow connected context instead of relying on isolated search results.
  • Governance: Control which users and clients can access which context.
  • Operational reliability: Reduce duplicated, stale, or conflicting context across tools.

​
FAQ

It depends on data volume. Small workspaces typically complete in minutes; large ones with many sources can take longer.
Yes. You can browse and edit any file in the context repository from the Qontext app. See here for details.