DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to let your coding agent search a repo by meaning with Xerj

Index a project once so an agent pulls exact passages with file:line instead of reading files one by one.

Authorization notice. Xerj is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The --insecure start turns off TLS and API-key auth, so keep the node on 127.0.0.1 and do not index into a shared host this way.

Who it is forA developer using Claude Code or Cursor on a large project who is tired of the agent re-reading files and burning tokens.

The problemGrep returns whole files or many matches, and the agent still has to read them, which costs tokens and time.

The outcomeThe agent answers questions from ranked passages with file and line references, and you can look up a definition directly.

What you need first

  • A Linux, macOS or Windows machine on x86-64 or arm64
  • A local folder of code, docs, logs or PDFs to index
  • Claude Code or Cursor if you want the MCP and skill setup from xerj init
  • A terminal with curl and a shell

Steps

  1. curl -fsSL https://xerj.org/get | sh
  2. xerj --insecure --data-dir ~/xerj-data &
  3. xerj init
  4. xerj autoindex ~/my-project
  5. xerj search "how do we rotate the WAL segment"

Prompt for your agent

Use the XERJ repo (xerj-org/xerj) to index <project path> with xerj autoindex, then answer the question <question> using xerj search and cite the file:line results. Verify that each cited line exists in the file before you answer.

Caveat. The README says the data directory must sit outside any folder you autoindex, because data/ is not in the built-in ignore list.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page