jbolivarg
jbolivarg'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 @BolivarTech 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 magi corpus
BolivarTech/magi: Magi Agent: terminal AI assistant in Rust
- Reuse a worked example: the commit “read HTTP status from typed provider errors, never from text” (3 files · Rust).
- Answer from magi's real Rust source instead of memory (AI, prompts and agents).
- Where does magi handle “read HTTP status from typed provider errors, never from text”?
- What does src/agent do in magi?
Search the GitHub repository BolivarTech/magi with XERJ (https://hub.xerj.org/corpus/bolivartech--magi). 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/BolivarTech/magi magi && git -C magi checkout 29524d3eb0850f4a83564de0276f6c8fc9444537 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./magi --url http://127.0.0.1:9200 --prefix magi --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: Apache-2.0. Keep the copyright notice and credit the authors.
corpus bolivartech--magi · AI, prompts and agents
Related corpora: kotaemon, garak, aider, 12-factor-agents
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
BolivarTech/magi
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/BolivarTech)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.