xerj-org/xerj

XERJ is the new way for AI to search data. Its autoindex capability activates agents to know your data without the token waste of grep (1974 tool). One...

View on GitHub ↗Jump to charts ↓Open shareable report →

xerj-org/xerj has 8k+ stars and 400+ forks on GitHub, is written in Rust, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 54 minutes ago
Added to GitGenius on October 7th, 2026
Created on June 30th, 2026
Open Issues & Pull Requests: 71 (+1)
GitHub issues: Enabled
Number of forks: 443
Total Stargazers: 8,295 (+26)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.5 hours
Mean response time: 2.2 days
90th percentile: 5.3 days
Tracked items: 440

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 98% of issues opened in the past year have since been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 31
Closed in 7 days: 47
Avg open age: 2 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 31
Closed in 7 days: 27
Comments in 7 days: 4
Events in 7 days: 78

Top labels

  • bug (59)
  • triage (28)
  • enhancement (23)
  • engine (10)
  • security (10)
  • performance (7)
  • systemone (5)
  • agents (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

XERJ is a local AI search engine that indexes folders automatically to enable agents and developers to retrieve exact code passages without token waste from sequential file reading.

The problem XERJ solves is the inefficiency of agents reading files one by one through grep or similar tools, which consumes excessive tokens and slows down coding tasks. Its approach uses automatic indexing to create a searchable index of code, documentation, logs, and PDFs in a single command, then serves results through an Elasticsearch-compatible API. This allows agents to query for relevant passages directly rather than loading entire files into context. The tool is built in Rust and designed to run locally on a developer's machine.

Reference coding is the primary use case: pointing an agent at a coding task, having it download relevant open-source repositories, index them, and reuse existing solutions before writing new code. Developers should choose this tool if they work with coding agents and want to reduce token consumption and API costs while improving solution quality. The project is suitable for individual developers and smaller teams running agents locally. The Elasticsearch compatibility means existing search clients can work without modification.

The project maintains a community-driven development model centered on field reports: anyone running XERJ is asked to contribute one short report describing what they indexed, what they used it for, and their honest assessment. Field-report pull requests are exempt from contributor license agreements and merge without signatures. The tool includes a built-in feedback command that drafts reports with version and system information pre-filled. The security model is deliberately simple and documented: the tool binds to localhost by default and refuses cleartext binds on other interfaces unless explicitly enabled, treating the insecure flag as a trust boundary rather than a casual option.