Atlas Documentation
Atlas is a local-first file lineage engine. It watches directories you choose, hashes file contents with BLAKE3, and builds a graph of how your files relate — tracking every version, copy, reference, and origin across your filesystem. Atlas answers two questions no other tool can: where did this file come from? and what did this file become?
Getting Started
New to Atlas? Start here.
- Getting Started — Install, first run, watch your first directory
Core
Learn how Atlas works and how to use its features.
- Core Concepts — Content-based identity, entities, forks, lifecycle
- Watching Files — Watch paths, namespaces, daemon control, boot persistence
- Querying — Find files, search history, compare directories, explore activity
- Edges & Lineage — Inputs, outputs, impact analysis, lineage tracing
- Ignore Patterns — Default and custom patterns for skipping files
- Managing Data — Forget, rebuild, verify, scan, export, backups
- Configuration — Config file, settings, shell completions
- Privacy & Security — Local-first design, consent, data safety
- JSON Output — Machine-readable output for scripting and automation
Connect
Expose Atlas to AI agents and external tools.
- Overview — What Atlas Connect is, design philosophy, capabilities
- Setup & Reference — MCP server, agent setup, tools, aggregate queries, audit logging
Extractors
Atlas discovers structural references between files using extractor packs.
- Extractors Overview — How extractors work, edge types, packs
- Core Pack — HTML, CSS, Markdown, SVG, JSON/YAML
Atlas Audio
Extractors for audio production workflows.
- Reaper — DAW project files (.rpp), plugins, audio sources, render outputs
- Kontakt — Instrument files (.nki), libraries, samples
- Plugin Formats — VST, VST3, AU, AAX, CLAP plugin metadata
- WAV Metadata — Render provenance from BWF/BEXT metadata (.wav)