xerj-org
It turns mixed local files into typed search indexes without schemas or pipelines, letting coding agents retrieve relevant passages rather than load whole files. Point it at a folder, then search by text, structure, vector similarity, or hybrid queries. It also accepts Elasticsearch API clients and provides MCP tools for assistants.
For Coding agents and their operators working with unfamiliar private code, and developers using Elasticsearch clients
XERJ keeps its engine independent from Elasticsearch while exposing the Elasticsearch 8.x HTTP protocol as a compatibility bridge. Folder ingestion is a separate HTTP client feature, so autoindex can create typed indices against an endpoint without linking the engine.
docs/ARCHITECTURE.md (Bird's-eye view, Crate responsibilities); engine/crates/xerj-autoindex/src/lib.rs (module documentation)
Search engine
Combines storage, full-text search, vectors, and aggregations into indexes.
engine/crates/xerj-engine/src/
Autoindex
Infers datasets and bulk-indexes folders through Elasticsearch-compatible HTTP.
engine/crates/xerj-autoindex/src/
API layer
Serves Elasticsearch-compatible and native HTTP endpoints through Axum.
engine/crates/xerj-api/
Index storage
Records mutations in WAL, writes segments, and atomically swaps read snapshots.
engine/crates/xerj-storage/src/index_store.rs
Generated