AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
Rust agent-memoryai-agentsbm25claude-codeclicode-searchcursordatabaseelasticsearchfull-text-searchhybrid-searchjsonllocal-firstmcpmcp-servermodel-context-protocolragrustsearch-enginevector-search
Regenerate the exit-code article search metadata
xerj-orgf6d6f613ace7
diff --git a/content/answers/autoindex-exit-codes.md b/content/answers/autoindex-exit-codes.mdindex 418c7ffab..d44f98193 100644--- a/content/answers/autoindex-exit-codes.md+++ b/content/answers/autoindex-exit-codes.md@@ -71,7 +71,11 @@ faq:a: "Do not blindly retry 0 or 3. Exit 3 with stale-resume-plan requires a --fresh rebuild to include the new files. Re-run with `--approve` on 4. Fix the command line on 2. Investigate the endpoint and the journal on 1, because a blind retry repeats the same refusal. The one exit 1 to rerun unchanged is `reason=server-backpressure`, once the node accepts writes again: it resumes with the operations that remain."----**TL;DR** — Read the terminal reason as well as the exit code. Exit 3 with `completed-with-junk` is success. With `stale-resume-plan`, `ok=false` means new files were not indexed. Rebuild with `--fresh` to include them. `xerj autoindex` exits 0 when the run completed, and 3 when it completed and recorded junk. Exit 4 means the estimate exceeded `--max-minutes` and nothing was indexed. Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.+**TL;DR** — Read the terminal reason as well as the exit code. Exit 3 with `completed-with-junk` is success. With `stale-resume-plan`, `ok=false` means new files were not indexed.++Rebuild with `--fresh` to include new files after `stale-resume-plan`. Exit 0 means the run completed; exit 3 means it completed with a reported limitation or junk. Exit 4 means the estimate exceeded `--max-minutes` and nothing was indexed.++Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.## The codes, as the binary states themdiff --git a/landing/answers/autoindex-exit-codes.html b/landing/answers/autoindex-exit-codes.htmlindex 2bd88a316..2369d96d9 100644--- a/landing/answers/autoindex-exit-codes.html+++ b/landing/answers/autoindex-exit-codes.html@@ -238,7 +238,7 @@<p>Exit 3 means the run finished with an outcome to inspect. Completed-with-junk is success; stale-resume-plan carries ok=false because new files were not indexed and needs a --fresh rebuild. Exit 0 is completion or cancellation, 4 needs approval, 2 is usage, and 1 is a real failure. Read the terminal reason and refusal counts before reporting coverage.</p><p class="key-fact"><strong>Key number:</strong> The decision gate that produces exit 4 defaults to 10 minutes of estimated work (<code class="inline">DEFAULT_MAX_MINUTES</code>). <span class="mute">(as of 2026-10-19 · source: <a href="https://github.com/xerj-org/xerj/blob/main/engine/crates/xerj-autoindex/src/gate.rs">engine/crates/xerj-autoindex/src/gate.rs</a>)</span></p></div>- <p><strong>TL;DR</strong> — Read the terminal reason as well as the exit code. Exit 3 with <code class="inline">completed-with-junk</code> is success. With <code class="inline">stale-resume-plan</code>, <code class="inline">ok=false</code> means new files were not indexed. Rebuild with <code class="inline">--fresh</code> to include them. <code class="inline">xerj autoindex</code> exits 0 when the run completed, and 3 when it completed and recorded junk. Exit 4 means the estimate exceeded <code class="inline">--max-minutes</code> and nothing was indexed. Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.</p>+ <p><strong>TL;DR</strong> — Read the terminal reason as well as the exit code. Exit 3 with <code class="inline">completed-with-junk</code> is success. With <code class="inline">stale-resume-plan</code>, <code class="inline">ok=false</code> means new files were not indexed.</p><div class="prompt-card"><span class="prompt-label">PASTE THIS TO YOUR AI AGENT — IT DOES THE REST</span><code>Read https://xerj.org/llms.txt, then inspect the terminal reason as well as the exit code. Exit 3 with stale-resume-plan has ok=false and needs --fresh; completed-with-junk requires reading the refusal list. Answer exit 4 with --approve, correct usage on 2, and investigate the error on 1.</code>@@ -274,6 +274,8 @@<button type="button" class="prompt-copy" data-copy="xerj autoindex status --url http://127.0.0.1:9200 --state-dir ./state">COPY COMMAND</button><span class="hero-proof">Read the journal when the process is gone and you have no terminal line.</span></div>+ <p>Rebuild with <code class="inline">--fresh</code> to include new files after <code class="inline">stale-resume-plan</code>. Exit 0 means the run completed; exit 3 means it completed with a reported limitation or junk. Exit 4 means the estimate exceeded <code class="inline">--max-minutes</code> and nothing was indexed.</p>+ <p>Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.</p><h2>The codes, as the binary states them</h2><p>The table summarizes <code class="inline">xerj autoindex --help</code>; the terminal reason distinguishes partial outcomes. Run that command yourself before you write a branch on any of these numbers.</p><table>diff --git a/landing/answers/autoindex-exit-codes.md b/landing/answers/autoindex-exit-codes.mdindex 184b8f7ee..c399156a8 100644--- a/landing/answers/autoindex-exit-codes.md+++ b/landing/answers/autoindex-exit-codes.md@@ -12,7 +12,7 @@ source: "content/answers/autoindex-exit-codes.md"**Key number:** The decision gate that produces exit 4 defaults to 10 minutes of estimated work (`DEFAULT_MAX_MINUTES`). (as of 2026-10-19; source: [engine/crates/xerj-autoindex/src/gate.rs](https://github.com/xerj-org/xerj/blob/main/engine/crates/xerj-autoindex/src/gate.rs))-**TL;DR** — Read the terminal reason as well as the exit code. Exit 3 with `completed-with-junk` is success. With `stale-resume-plan`, `ok=false` means new files were not indexed. Rebuild with `--fresh` to include them. `xerj autoindex` exits 0 when the run completed, and 3 when it completed and recorded junk. Exit 4 means the estimate exceeded `--max-minutes` and nothing was indexed. Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.+**TL;DR** — Read the terminal reason as well as the exit code. Exit 3 with `completed-with-junk` is success. With `stale-resume-plan`, `ok=false` means new files were not indexed.## Agent prompt@@ -62,6 +62,10 @@ Note: Read the journal when the process is gone and you have no terminal line.xerj autoindex status --url http://127.0.0.1:9200 --state-dir ./state```+Rebuild with `--fresh` to include new files after `stale-resume-plan`. Exit 0 means the run completed; exit 3 means it completed with a reported limitation or junk. Exit 4 means the estimate exceeded `--max-minutes` and nothing was indexed.++Exit 2 is a usage error, and exit 1 is a runtime failure. Only 4 is a question.+## The codes, as the binary states themThe table summarizes `xerj autoindex --help`; the terminal reason distinguishes partial outcomes. Run that command yourself before you write a branch on any of these numbers.diff --git a/landing/answers/index.json b/landing/answers/index.jsonindex bcf9d1c1a..3f3b67129 100644--- a/landing/answers/index.json+++ b/landing/answers/index.json@@ -1052,10 +1052,10 @@"canonical_url": "https://xerj.org/answers/autoindex-exit-codes","markdown_url": "https://xerj.org/answers/autoindex-exit-codes.md","cluster": "Operations: exit codes",- "updated": "2026-10-24",- "summary": "xerj autoindex exits 0 complete, 3 completed-with-junk, 4 needs-a-decision, 2 usage and 1 on an endpoint or journal failure. Only 4 is asking you a question.",+ "updated": "2026-10-28",+ "summary": "xerj autoindex exits 0 complete, 3 completed-with-junk, 4 needs-a-decision, 2 usage and 1 on a runtime failure. Only 4 is asking you a question.","intent_group": "operating autoindex",- "answer": "What does indexer exit code 3 mean for xerj autoindex? It means success: the run completed and recorded some junk files. Exit 0 is a clean completion, 4 means the estimate exceeded --max-minutes and nothing was indexed, 2 is a usage error, and 1 is an endpoint or journal failure. Only exit 4 asks you a question."+ "answer": "Exit 3 means the run finished with an outcome to inspect. Completed-with-junk is success; stale-resume-plan carries ok=false because new files were not indexed and needs a --fresh rebuild. Exit 0 is completion or cancellation, 4 needs approval, 2 is usage, and 1 is a real failure. Read the terminal reason and refusal counts before reporting coverage."},{"title": "Why autoindex refuses a .zip and asks you to extract it",