Yotam Bloom

What an agent can do with the nemus corpus

me-public/nemus: Multi-repo Git workspaces for the AI-agent era: group repos, operate in bulk, wire them to your coding agent

• Look up how nemus implements ai-agents, cli, developer-tools, with answers cited to file and line.
• Reuse a worked example: the commit “nemus dev: multi-repo dev orchestrator” (5 files · TypeScript).
• Answer from nemus's real TypeScript source instead of memory (AI, prompts and agents).

• Where does nemus handle “nemus dev: multi-repo dev orchestrator”?
• How does nemus implement ai-agents?
• What does src/utils do in nemus?

Search the GitHub repository me-public/nemus with XERJ (https://hub.xerj.org/corpus/me-public--nemus).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/me-public/nemus nemus && git -C nemus checkout 6a105762865aae3c1fa8f7f4c58c8594af592692
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./nemus --url http://127.0.0.1:9200 --prefix nemus --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: MIT. Keep the copyright notice and credit the authors.

corpus me-public--nemus · AI, prompts and agents
Related corpora: lexbuild, aider, mertkaradayi/pando, naw103/foremerge
AI search and retrieval with XERJ · Case study: reference coding for agents