Greta
Greta'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 @GretaD 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 mail corpus
nextcloud/mail: 💌 Mail app for Nextcloud
- Look up how mail implements imap, smtp, horde, with answers cited to file and line.
- Reuse a worked example: the commit “tag modal size and delete issue” (3 files · Vue).
- Answer from mail's real Vue source instead of memory (Operations and SRE).
- Where does mail handle “tag modal size and delete issue”?
- How does mail implement imap?
- What does src/components do in mail?
Search the GitHub repository nextcloud/mail with XERJ (https://hub.xerj.org/corpus/nextcloud--mail). 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/nextcloud/mail mail && git -C mail checkout dfe5726fc45b448bb9817b0465a84b5452828590 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./mail --url http://127.0.0.1:9200 --prefix mail --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 nextcloud--mail · Operations and SRE
Related corpora: kotaemon, autorag, Ferousco-dev/Mailx, nextcloud/ios
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
nextcloud/mail
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/GretaD)
Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.