bx-tacho
Open DIY Beyblade X launcher RPM meter: ESP32-C3 with IR sensors and an OLED, Bluetooth (Battle Pass protocol), and a browser app for shot data and firmware updates. KiCad hardware, ESP-IDF firmware, 3D-printed case
What XERJ indexed
Snapshot
The whole repository at commit bf8c09c377 (2026-10-25). master is 6 commits ahead.
Selected work
“Calibrate black and white launchers separately, bump to 2.0.0”. 13 files, 475 lines in firmware.
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The author agreed by email on 2026-10-27. Agents read it for how it works, not to copy it. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: approach only
3d-printingbeybladebeyblade-xesp-idfesp32esp32-c3kicadopen-hardware
Example questions
- How does bx-tacho implement 3d-printing?
- Where does bx-tacho handle “Calibrate black and white launchers separately, bump to 2.0.0”?
- What does firmware do in bx-tacho?
Inside the indexed corpus
- Languages by size: C 59.3%, JavaScript 29.2%, CSS 4%, HTML 3.8%, Python 2.8%.
- On GitHub since 2026-10-01, last push 2026-10-28, 46 commits on master.
- The pin is 6 commits behind master; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported GPL-3.0 for dazchi/bx-tacho on 2026-10-29, and the LICENSE file at commit bf8c09c377 was reviewed as GPL-3.0. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Darren Chi (@dazchi) has 1 selected repository on the hub.
Using XERJ with bx-tacho
- ripgrep vs a code index for coding agents: 30 tasks
- Best MCP servers for local code search in 2026, compared
- Best grep alternative for AI coding agents (2026)
- Ask questions about a GitHub repo without cloning it
The prompt
Paste it into your AI agent. It clones dazchi/bx-tacho at the pinned commit and indexes it on your machine.
Search the GitHub repository dazchi/bx-tacho with XERJ (https://hub.xerj.org/corpus/dazchi--bx-tacho). 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/dazchi/bx-tacho bx-tacho && git -C bx-tacho checkout bf8c09c377b99e3546137e4c7707c9c654ea889d 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./bx-tacho --url http://127.0.0.1:9200 --prefix bx-tacho --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.
Related
Darren ChiWeb and frontend platform corporabahguta/bahguta-Homelabcitycafe578/FixedPIDkirmisaki/FrameFilm
Stats: GitHub API, fetched 2026-10-29. Selected work and consent: the XERJ registry.