What is BetterContext?
API Guide
Quickstart
Comparison
Agents, skills & MCP
How it works?
Experience Engine
Focus Mode
Memory Graph
Files & Folders
Token Usage
Overview
API keys
Invite team member
Tools connection
Usage & Analytics
Ingestion
General
Benchmarking
Billing and Invoice
Security & Compliance
Use cases
From other providers
Upgrade BetterContext
Using BetterContext Copy
Ingestion Pipelines
Stream codebases, documentation, wikis, and event logs into your memory graph with automated AST extraction and causal dependency linking.
BetterContext provides multiple ingestion pathways tailored for initial repository bootstrapping, continuous git branch synchronization, and automated enterprise webhooks.
Ingestion Pathways
Point the CLI at any local or remote git folder for instant parallelized AST indexing.
Configure GitHub or Linear webhooks to incrementally parse merged commits and closed tickets.
Programmatically upsert facts, customer schemas, and runbooks via SDK or cURL.
CLI Ingestion
The fastest way to index a project:
# Ingest the entire current directory on the 'main' branch
bettercontext ingest . \
--branch main \
--include "*.py,*.ts,*.md" \
--exclude "tests/*,dist/*" \
--threads 8
Programmatic Ingestion via Python SDK
Ingest custom documents with role-based ACLs and metadata:
from bettercontext import BetterContextClient
client = BetterContextClient()
# Upsert a sensitive architectural decision record
doc = client.memory.upsert(
title="ADR-042: Database Encryption at Rest",
content="All customer PII and authentication tokens must be stored in Postgres columns encrypted with pgcrypto.",
format="markdown",
tags=["security", "compliance", "database"],
acls={
"read": ["engineer", "security-lead", "admin"],
"write": ["security-lead"]
}
)
print(f"Created Node ID: {doc.node_id}")
print(f"Entities Extracted: {doc.extracted_entities}")
Handling Deletions & Tombstoning
When code or documentation is deleted in git, BetterContext uses Dual-Clock Tombstoning. Rather than instantly obliterating the node and breaking downstream historical queries, the node is marked as deprecated for current queries while remaining queryable during historical git-bisect and retrospective sessions.
Next Steps
Powered By BetterContext