PeatBoy
PeatBoy'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 @PeatBoy 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 vibex corpus
vibex-ai/vibex: Your agents. Your workspace. Your control-from prompt to commit, desktop to mobile. Works with Codex, Claude Code, OpenCode, Pi, Grok…
- Look up how vibex implements acp, ade, agents, with answers cited to file and line.
- Reuse a worked example: the commit “give AI Souls distinct roaming boss encounters” (17 files · Rust).
- Answer from vibex's real Rust source instead of memory (AI, prompts and agents).
- Where does vibex handle “give AI Souls distinct roaming boss encounters”?
- How does vibex implement acp?
- What does apps/desktop do in vibex?
Search the GitHub repository vibex-ai/vibex with XERJ (https://hub.xerj.org/corpus/vibex-ai--vibex). 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/vibex-ai/vibex vibex && git -C vibex checkout 49d28e21bd47014110b8f0cf340d643e336d8b5e 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./vibex --url http://127.0.0.1:9200 --prefix vibex --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: AGPL-3.0. Read it for the approach only, do not copy code.
corpus vibex-ai--vibex · AI, prompts and agents
Related corpora: xerj-blogposts, chroma, magicsih/chda, agent-sh/computer-use-linux
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
vibex-ai/vibex
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/PeatBoy)
Included with the author's permission (email, 2026-10-12), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.