Concepts Copy

Files & Folders

Organizing codebases, documentation hierarchies, branch-level workspaces, and real-time filesystem watchers.

BetterContext maintains a mirror of your project's directory hierarchy, mapping physical files and folders into corresponding virtual nodes within your memory graph.

Supported Formats & Parsers

BetterContext natively extracts syntax trees, AST symbols, and semantic sections across a wide variety of formats:

Category	Extensions	Parser Capabilities
Programming Languages	`.py`, `.ts`, `.tsx`, `.js`, `.go`, `.rs`, `.java`, `.c`, `.cpp`	Tree-sitter AST, symbol references, imports, classes, functions, and docstrings.
Documentation	`.md`, `.mdx`, `.txt`, `.rst`, `.pdf`	Heading hierarchy, code block isolation, table extraction, and cross-document links.
Configurations & Schemas	`.json`, `.yaml`, `.yml`, `.toml`, `.graphql`, `.proto`	Object schemas, field definitions, environment variables, and proto RPCs.

Branch-Level Context Isolation

In collaborative software development, feature branches diverge quickly. BetterContext treats git branches as isolated virtual namespaces:

Base Graph: The main or production branch serves as the canonical base graph for your organization.
Branch Overlay: When an agent works on a feature branch (e.g. feature/stripe-billing), only the modified files and new symbols are overlaid on top of the base graph.
Zero Bleed: Work-in-progress code on one branch never contaminates agent prompts executing on another branch.

Real-Time Live Watchers

During active development, use the BetterContext CLI watcher to automatically synchronize file changes as you write code:

# Start continuous background file synchronization
bettercontext watch --debounce 300ms

The watcher debounces save events, calculates incremental AST diffs, and updates the memory graph in under 50ms without full repository re-indexing.

Next Steps

Was this page helpful?

ON THIS PAGE

Overview
Supported Formats
Branch Isolation
Real-Time Watchers
Next Steps