stellarium
Stellarium is a free GPL software which renders realistic skies in real time with OpenGL. It is available for Linux/Unix, Windows, macOS and Haiku. With Stellarium, you really see what you can see with your eyes, binoculars or a small telescope
What XERJ indexed
Snapshot
The whole repository at commit e750aeeea8 (2026-10-11). master is 54 commits ahead.
Selected work

“Make it possible to use NexStar via TCP/IP”. 7 files, 234 lines in plugins.
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-24. 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
cc-plus-plusastronomysciencestarsskyuniverseplanetarium
Example questions
- How does stellarium implement c?
- Where does stellarium handle “Make it possible to use NexStar via TCP/IP”?
- What does plugins do in stellarium?
Inside the indexed corpus
- Languages by size: C++ 46.7%, C 24.2%, GLSL 15.4%, TeX 6.3%, JavaScript 2.4%.
- On GitHub since 2014-04-13, last push 2026-10-31, 39,799 commits on master.
- The pin is 54 commits behind master; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported GPL-2.0 for Stellarium/stellarium on 2026-10-31, and the LICENSE file at commit e750aeeea8 was reviewed as GPL-2.0. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Ruslan Kabatsayev (@10110111) has 1 selected repository on the hub.
Using XERJ with stellarium
- Search an OpenAPI spec so an agent can find endpoints The hub files it under API design and specification.
- Ask questions about a GitHub repo without cloning it
- Index a reference library for a coding agent
- ripgrep vs a code index for coding agents: 30 tasks
The prompt
Paste it into your AI agent. It clones Stellarium/stellarium at the pinned commit and indexes it on your machine.
Search the GitHub repository Stellarium/stellarium with XERJ (https://hub.xerj.org/corpus/stellarium--stellarium). 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/Stellarium/stellarium stellarium && git -C stellarium checkout e750aeeea8cb27a3742e578a24383c149094fcc8 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./stellarium --url http://127.0.0.1:9200 --prefix stellarium --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-2.0. Read it for the approach only, do not copy code.
Related
Ruslan KabatsayevAPI design and specification corporaaeronlibhydrogenlibcboreddyem/small_telleo-gan/GLD.SerializerBenchmarkHermeticaLabs/Caeliscope
Stats: GitHub API, fetched 2026-10-31. Selected work and consent: the XERJ registry.