Configuration
Vault configuration lives in .context/config.yaml.
Full schema
name: "My Project"
namespace: "my-project"
layout: structured # structured or obsidian
federation: none # none, federated, or scoped
# Server registry for source nodes
servers:
jira:
url: "https://mycompany.atlassian.net"
transport: mcp
github:
url: "https://api.github.com"
transport: mcp
slack:
url: "https://slack.com/api"
transport: rest
# Telemetry (opt-in, metadata only, never vault content)
telemetry: falseFields
| Field | Type | Default | Description |
|---|---|---|---|
name | string | "My Context Nest" | Vault display name |
namespace | string | — | Unique namespace for federation |
layout | string | structured | structured or obsidian |
federation | string | none | none, federated, or scoped |
servers | object | — | Server registry for source nodes |
telemetry | boolean | false | Opt-in anonymous usage telemetry |
Environment variables
| Variable | Description |
|---|---|
CONTEXTNEST_VAULT_PATH | Override vault root directory |
PROMPTOWL_API_URL | Override cloud API URL (default: https://api.promptowl.com) |
CONTEXT.md
The CONTEXT.md file at the vault root is a free-form markdown file that serves as the vault-level system prompt. AI agents read it first before accessing individual documents.
Write it to describe:
- What the vault is for
- How the agent should interact with it
- Any conventions or rules specific to your team
Last updated on