# Lexa

> Fast local code intelligence for humans and AI agents.

## Docs

- [Benchmark](/docs/benchmark): Lexa includes a Criterion-based benchmark suite for indexing, search, and
snapshot performance.
- [Binary Releases](/docs/binary-releases): GitHub Actions builds Lexa artifacts for four targets on every release tag.
- [Changelog](/docs/changelog): No changes yet.
- [Configuration & Environment Variables](/docs/configuration): Lexa has no global config file. Configuration is split between environment
variables, CLI flags, and a few optional per-project files (notably the audit
config).
- [Development](/docs/development): Lexa is a Rust project. The full contribution guide lives in
[`CONTRIBUTING.md`](https://github.com/anvia-hq/lexa/blob/main/CONTRIBUTING.md).
- [Getting Started](/docs/getting-started): If you already have `lexa` installed, head to the [Quick Start](/docs/quick-start) for the 60-second tour.
- [Global Flags](/docs/global-flags): These flags apply to every Lexa subcommand unless noted.
- [Install](/docs/install): Lexa ships as a single native binary. Pick the path that matches your platform.
- [Language Support](/docs/language-support): Lexa has two parsing tiers: tree-sitter (full symbol + import extraction) and
lightweight (regex-based, symbol-level only). All 33 supported languages get
outline, search, and safe-edit coverage; tree-sitter languages additionally
get precise imports and dependency resolution.
- [Project Graph](/docs/project-graph): Every Lexa command operates on a single per-project graph file.
- [Quick Start](/docs/quick-start): Lexa works on any codebase — point it at a directory and it builds a local
graph in milliseconds.
- [Safe-Edit Semantics](/docs/safe-edit): Lexa reads, patches, and creates files with hash-aware concurrency control.
This page describes the model. For the per-flag reference see the
[Read & Edit CLI page](/docs/cli/read-edit).
- [Why Lexa](/docs/why-lexa): Lexa is a fast local code intelligence engine for humans and AI agents.
- [MCP Setup](/docs/mcp): Lexa ships an MCP server over stdio. It exposes every CLI command as a tool
under the same name, plus three recovery tools (`reindex`, `clear_index`,
`status`) that the CLI does not have direct equivalents for.
- [MCP Output Formats](/docs/mcp/output): Lexa's MCP server emits two response shapes: text only (default) and
text-plus-JSON when structured content is opted in.
- [MCP Tools Reference](/docs/mcp/tools): Lexa's MCP server exposes 22 tools. The table below summarizes every one. Use
the per-tool headings below for input schemas and notes.
- [Audit](/docs/cli/audit): The `lexa audit` command runs a read-only review of the project graph and
reports architecture findings: import cycles, large files, large symbols, and
dependency hotspots. Dead-code candidates are opt-in.
- [Code Structure](/docs/cli/code-structure): Commands for symbols, dependencies, and task context.
- [Discovery](/docs/cli/discovery): Find files and paths in the indexed project.
- [CLI Overview](/docs/cli): Lexa is a CLI plus an MCP server backed by a single indexed graph. Every
command reads from the same per-project graph, and every command is also
exposed as an MCP tool under the same name.
- [Indexing](/docs/cli/indexing): These commands build, rebuild, and inspect the per-project graph.
- [Maintenance](/docs/cli/maintenance): Commands for keeping Lexa and the project graph in shape.
- [Pipeline](/docs/cli/pipeline): The `lexa pipeline` command chains query operations into a single invocation.
Use it to express multi-step lookups without scripting bash.
- [Read & Edit](/docs/cli/read-edit): Read files, apply line-based patches, and create new files. For the conceptual
model — hash-aware flow, edit ops, path safety — see
[Safe-Edit Semantics](/docs/safe-edit).
- [Search](/docs/cli/search): Text and symbol search over the indexed graph.