Compatibility

Context Nest is designed to work with existing tools and workflows.

Git

Context Nest vaults are git-friendly by design. All files are plain text (Markdown, YAML).

Recommended .gitignore:

.context/welcome.html

Version history (.versions/) should be committed — it’s part of the vault’s integrity chain.

Obsidian

Context Nest supports an Obsidian-compatible layout mode:

ctx init --layout obsidian

In Obsidian mode:

• Documents live at the vault root (no nodes/ directory)
• The source frontmatter block appears in Obsidian’s Properties panel
• Source node bodies are readable as regular markdown runbooks
• Context links use contextnest:// URIs which Obsidian will display as plain links

AI agents

Context Nest is agent-agnostic. It works with any tool that can read Markdown files or connect via MCP:

File format

The Context Nest format is intentionally simple:

• Plain Markdown with YAML frontmatter (GFM compatible)
• YAML configuration files
• No binary formats, no databases, no proprietary encoding
• Any tool that reads Markdown can read a Context Nest vault