Version: 4.13.1
Magellan is a deterministic codebase indexing tool. It watches or scans source trees, extracts symbols, references, calls, AST nodes, code chunks, CFG data, and coverage metadata, then stores those facts in a local SQLite database for fast CLI and downstream-tool queries.
Magellan is intentionally fact-oriented: it records what is present in source code and leaves higher-level reasoning to tools such as llmgrep, Mirage, and Splice.
Compiler frontends
- Tree-sitter multi-language symbol extraction: Rust, Python, C, C++, Java, JavaScript, TypeScript, Go, CUDA
- C/C++ CFG via clang → LLVM IR (
llvm_ir_parser; clang detected at runtime, tree-sitter fallback) - Java CFG via javac →
.classbytecode (javac_invoker,class_parser)
Indexed facts
- Symbols with canonical / display FQNs, byte + line spans, stable IDs
- References and interprocedural call graph
- AST nodes and code chunks for source retrieval
- CFG blocks and CFG edges,
#[cfg]attribute inheritance - Coverage ingestion from LCOV into CFG side tables
Storage
- SQLite, schema v20: repository snapshots, temporal symbol/edge history, graph memory tables, project metadata, FTS5 full-text search over code chunks, and cfg-aware CFG blocks
- Auto-detect project layout from
Cargo.toml,pyproject.toml,go.mod,package.json,tsconfig.json,pom.xml,CMakeLists.txt
Keyword index: code intelligence · codebase indexing · compiler frontend · tree-sitter · LLVM IR · Java bytecode · call graph · interprocedural · control-flow graph · CFG · AST · FTS5 · SQLite · Rust
The supported user-facing database is SQLite:
code.db
Use .db files for normal operation.
Schema version: 20 (repository snapshots, temporal symbol/edge history, telemetry events, cfg-aware CFG blocks, project metadata, graph memory tables, symbol_fts, and code_chunks_fts)
- Multi-language symbol extraction with tree-sitter: Rust, Python, C, C++, Java, JavaScript, TypeScript, Go, and CUDA
- Stable symbol IDs, canonical FQNs, display FQNs, and byte/line spans
- File watching and one-shot indexing
- References and call graph queries
- AST node storage and AST queries
- Code chunks for source retrieval and editor context
- CFG blocks and CFG edges for control-flow analysis
#[cfg]attribute extraction: CFG blocks inherit cfg conditions from function attributes- Cargo.toml manifest parsing: features, dependencies, and test/bench/example targets
.magellan.tomlproject configuration with include/exclude filters- Auto-detect project layout from
Cargo.toml,pyproject.toml,go.mod,package.json,tsconfig.json,pom.xml,CMakeLists.txt - Coverage ingestion from LCOV into CFG coverage side tables
- Graph algorithms: reachability, dead code, cycles, condensation, paths, slice
- Temporal history: snapshot ingestion, as-of symbol lookup, barcode-style lifetime queries, and SCC persistence analysis
- HopGraph v2: embedding-based semantic symbol search with HNSW, name resolution, and
--hops Ngraph expansion via BFS on REFERENCES edges - Source inventory: index wiki pages, specs, and other non-code documents
- Candidate facts: structured knowledge triples linked to source documents
- JSON, pretty JSON, human output, and graph exports
- LSIF import/export and SCIP export
- Impact export: blast radius analysis for single symbols
- Repo-root export convention: automatic
.magellan/directory exports - Pre-commit hooks: git hooks for blast score validation
doctorchecks for schema and database health
From crates.io (recommended):
cargo install magellan --lockedOne-line install with service + pre-commit hook setup:
# bash / zsh
curl -sSf https://raw.githubusercontent.com/oldnordic/magellan/main/install/install.sh | bash
# fish
curl -sSf https://raw.githubusercontent.com/oldnordic/magellan/main/install/install.fish | fishBoth scripts install the binary, create ~/.magellan/, set up a systemd user service (Linux), and install a pre-commit blast-radius warning hook. Pass --no-service or --no-hook to skip either step.
Requires: Rust toolchain (rustup.rs), git, jq (for the hook).
# Orient on an existing project (see what is indexed)
magellan orient --db ~/.magellan/<project>/<project>.db --repo /path/to/project
# Initialize project configuration
magellan init --path /path/to/project
# Build an index
magellan watch --root /path/to/project/src --db ~/.magellan/<project>/<project>.db --scan-initial
# Check database contents
magellan status --db ~/.magellan/<project>/<project>.db
# Query symbols in a file
target/release/magellan query --db .magellan/code.db --file src/main.rs
# Find symbols
target/release/magellan find --db .magellan/code.db --name main
# Show incoming or outgoing references/calls
target/release/magellan refs --db .magellan/code.db --name main --direction out
# Index or delete one file
target/release/magellan index --db .magellan/code.db --file src/lib.rs
target/release/magellan delete --db .magellan/code.db --file src/lib.rs
# Refresh from git working tree changes
target/release/magellan refresh --db .magellan/code.db
# Recompute derived metrics
target/release/magellan backfill --db .magellan/code.db
# Build temporal history from git commits
target/release/magellan temporal-sweep --db .magellan/code.db --repo . --every 10
target/release/magellan temporal-status --db .magellan/code.db
target/release/magellan as-of --db .magellan/code.db --commit <oid> --symbol parse_args
target/release/magellan temporal-barcode --db .magellan/code.db --symbol <stable-id>
# Semantic symbol search (requires embed + configured embeddings)
target/release/magellan embed --db .magellan/code.db
target/release/magellan hopgraph "error handling" --db .magellan/code.db --k 5
target/release/magellan hopgraph "parse arguments" --db .magellan/code.db --k 5 --hops 1
# Re-embed after significant code changes so HopGraph stays current
# (magellan watch updates the graph, but not embeddings automatically)Magellan can ingest LCOV data and attach it to CFG blocks and edges:
magellan ingest-coverage --db .magellan/code.db --lcov coverage/lcov.info
magellan status --db .magellan/code.db --output prettyStatus JSON always includes a stable coverage object:
{
"coverage": {
"available": false,
"covered_blocks": 0,
"covered_edges": 0
}
}When coverage exists, source, revision, and ingested_at are included.
Magellan can run as a background daemon with per-project filesystem watchers and a JSON-RPC control socket for integration with downstream tools.
The daemon uses notify::RecommendedWatcher directly with custom debouncing
that filters out read-only filesystem events (ACCESS/OPEN/CLOSE_NOWRITE).
Only write-side mutations (CREATE/MODIFY/REMOVE) are tracked. This prevents
the feedback loop where reading a file for reconciliation would trigger
re-indexing.
When magellan watch detects an already-running daemon, it sends a filtered
file batch to the daemon using the registered project tag instead of queuing a
directory path. During reconcile, chunk-side FTS corruption in code_chunks_fts
is repaired automatically by rebuilding that index and retrying the chunk
write/delete, so the daemon no longer fails entire batches on recoverable FTS5
side-index damage.
magellan service start # start daemon
magellan service register --root /path --name myproject \
--include src/ --include tests/ --exclude target/
magellan service list # list enabled projects
magellan service status # detailed project info
magellan service stats # per-project DB statistics
magellan service events # daemon event log
magellan service stop # graceful shutdownThe daemon stores databases at ~/.magellan/<name>/<name>.db. The JSON-RPC
socket (at $XDG_RUNTIME_DIR/magellan.sock) supports project management,
cross-project queries, and an evolution loop for automated refactoring
candidates. See docs/API_INTEGRATION.md for the full method reference.
magellan --help
magellan --help-full
magellan --backends
magellan doctor --db code.db
magellan doctor --db code.db --fix
magellan files --db code.db --symbols
magellan chunks --db code.db --limit 20
magellan ast --db code.db --file src/main.rs
magellan find-ast --db code.db --kind function_item
magellan reachable --db code.db --symbol <SYMBOL_ID>
magellan dead-code --db code.db --entry <SYMBOL_ID>
magellan cycles --db code.db
magellan condense --db code.db --members
magellan paths --db code.db --start <SYMBOL_ID> --max-depth 8
magellan slice --db code.db --target <SYMBOL_ID> --direction backward
magellan export --db code.db --format json --output graph.json
magellan export --db code.db --format scip --output graph.scip
magellan export --db code.db --format impact --symbol "function_name" --output impact.json
magellan import-lsif --db code.db path/to/index.lsif
# Blast score single-symbol impact analysis
magellan blast-score --db code.db --symbol "handle_request" --file src/request.rs
magellan blast-score --db code.db --symbol "parse_args" --depth 5 --output json
# Install pre-commit hooks for blast score checking
magellan install-hook --db code.db --threshold 10.0
magellan install-hook --db code.db --threshold 10.0 --strict
magellan source-inventory --db code.db --scan ./wiki markdown
magellan source-inventory --db code.db --kind wiki
magellan candidate-fact submit --db code.db --from-source 1 --subject-type Task --subject-key "task-1" --predicate assigned_to
magellan candidate-fact list --db code.db --status pending
# Natural language query routing (callers, CFG, cycles, impact, semantic search, find)
magellan ask --db code.db "who calls index_file"
magellan ask --db code.db "cfg for parse_watch_args"
magellan ask --db code.db "blast zone of handle_request"
magellan ask --all "who calls index_file"
# Grounded investigation packet (term extraction → symbol find → callers/callees/impact/context)
magellan navigate --db code.db "parse_watch_args error handling"
magellan navigate --db code.db "handle_request" --concise
magellan navigate --db code.db "CodeGraph open sync" --depth 3 --with-llmgrep --with-mirageC/C++ and Java CFG extraction uses installed external tools detected at runtime. No special build flags are required.
C/C++ (clang required): When clang is on PATH, magellan compiles each
C/C++ file to LLVM IR and extracts accurate per-function CFGs and call edges.
Falls back to tree-sitter approximations when clang is absent.
Java (javac required): When javac is on PATH, magellan compiles .java
files and extracts CFG from bytecode.
compile_commands.json: For projects with non-trivial build flags (defines,
include paths, language standards), load a compile_commands.json via the
--compile-commands CLI flag or the CodeGraph::set_compile_commands API. Per-file
flags are forwarded to clang during CFG extraction.
Neither clang nor javac is required. When absent, CFG extraction degrades gracefully to tree-sitter-based approximations.
- MANUAL.md: command reference and workflows
- CHANGELOG.md: release notes
- docs/MAGELLAN_ARCHITECTURE.md: architecture
- docs/SCHEMA_SQLITE.md: SQLite schema
- docs/SCHEMA_REFERENCE.md: stable IDs and data model
- docs/API_INTEGRATION.md: Rust/API integration notes
- docs/JSON_EXPORT_FORMAT.md: JSON response shape
- docs/CONTEXT_API_CONTRACT.md: context API contract
- docs/TESTING.md: verification commands
The blast-radius impact scoring (magellan blast-score), the symbol-map and
impact JSON exports (magellan export), the pre-commit hook (magellan install-hook),
and the repo-root .magellan/ file convention were inspired by
codeindex by scheidydude.
GPL-3.0