Eric Tao

Corpus Hub contributor since 2026-10-22

Eric Tao'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.

1corpus

1selected commit

11files

577lines

★ 1GitHub stars on repo

Totals across every corpus @Hajime-No-Ippo 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 bridge corpus

Hajime-No-Ippo/bridge: ✏️ Telegram-bridged OS level automation agent: live opencode session, browser control (cua-driver/CDP), pending-question lifecycle…

Look up how bridge implements automation, macos, telegrambot, with answers cited to file and line.
Reuse a worked example: the commit “Changes on relevant renders” (11 files · TypeScript, JavaScript).
Answer from bridge's real TypeScript source instead of memory (Web and frontend platform).

Example questions

Where does bridge handle “Changes on relevant renders”?
How does bridge implement automation?
What does src do in bridge?

Paste it into your AI agent. It clones the repo at the pinned commit and indexes it on your machine.

Search the GitHub repository Hajime-No-Ippo/bridge with XERJ (https://hub.xerj.org/corpus/hajime-no-ippo--bridge).
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/Hajime-No-Ippo/bridge bridge && git -C bridge checkout 5f56386d4b127aaca6e1ab2d39805e97f6422d71
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./bridge --url http://127.0.0.1:9200 --prefix bridge --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 hajime-no-ippo--bridge · Web and frontend platform
Related corpora: gatling, caldera, Abaniumbay/conveyor, alexneverland/Astakos-AI-Agent
Case study: reference coding for agents

Selected work

GitHub ★ 1

Hajime-No-Ippo/bridge

5f56386d4b Changes on relevant renders

selected commit: 11 files · 577 lines · TypeScript, JavaScript · src, src/ubuntu24, src/tools

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus hajime-no-ippo--bridgeWEBApache-2.0automationmacostelegrambotubuntu-x11bun agreed 2026-10-22

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.

[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/Hajime-No-Ippo/badge.svg)](https://hub.xerj.org/contributors/Hajime-No-Ippo)

Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.