Moose
Moose's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @moooossee appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the moose corpus
moooossee/moose: Chat with local and cloud AI
- Look up how moose implements ai, chatgpt-alternative, desktop-app, with answers cited to file and line.
- Reuse a worked example: the commit “feat add secure cloud provider support” (29 files · Rust, SQL).
- Answer from moose's real Rust source instead of memory (AI, prompts and agents).
- Where does moose handle “feat add secure cloud provider support”?
- How does moose implement ai?
- What does src/providers do in moose?
Search the GitHub repository moooossee/moose with XERJ (https://hub.xerj.org/corpus/moooossee--moose). 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/moooossee/moose moose && git -C moose checkout 10ae11e3f38f9dea740bbcbb525c4368dd412db2 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./moose --url http://127.0.0.1:9200 --prefix moose --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: GPL-3.0. Read it for the approach only, do not copy code.
corpus moooossee--moose · AI, prompts and agents
Related corpora: haystack, atomic-agents, pavlenkosa/wayvoice, c9dev/penguin-mail
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
moooossee/moose
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/moooossee)
Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.