AutoRAG Lite setup

Use this skill when the user wants AutoRAG's indexing lifecycle without a model: initialize a config, build and refresh indexes, watch roots, and inspect index health. Everything here is model-free. Use autorag-setup instead when a search model must be configured or repaired. Use autorag-lite-search for retrieval, reports, evidence, and feedback.

Safety

• Inspect only non-secret config metadata: searchPaths, workspacePath, memoryPath, minSync, jikji, datasources, datasourceAccess.
• Never print, copy, migrate, compare, or persist credential values. Store only environment-variable names such as tokenEnv or apiKeyEnv.
• Never move, rename, edit, or delete source documents. Lite commands write indexes only under the configured workspace .autorag/ directory and Jikji's per-source .jikji/ caches.
• Do not index system trees, app bundles, caches, credential stores, node_modules, .git, dist, build, target, .cache, .autorag, or .jikji.

Install the CLI if needed

The CLI is @autorag/librarian (autorag). Runtime is Node.js >= 24 or Bun.

command -v autorag >/dev/null || bun install -g @autorag/librarian
autorag lite --help

If Bun is unavailable, npm install -g @autorag/librarian is acceptable.

Initialize a model-free config

autorag lite init \
  --search-paths "/path/to/documents,/path/to/notes" \
  --workspace "/path/to/workspace" \
  --memory-path "/path/to/memory.json"

lite init writes the configured model-free lifecycle config. Use --force only when intentionally replacing an existing config. Explicit user paths win; otherwise propose one to three document-dense roots and get approval before indexing. Supported parsed formats are md, markdown, txt, text, pdf, docx, pptx, xlsx, xls, hwp, hwpx, and eml. Legacy .doc is not a supported parsed format.

Config resolution follows the usual order: --config, AUTORAG_CONFIG, $AUTORAG_HOME/config.json, or ~/.autorag/config.json. Environment overrides include AUTORAG_HOME, AUTORAG_CONFIG, AUTORAG_SEARCH_PATHS, AUTORAG_WORKSPACE, and AUTORAG_MEMORY_PATH.

Probe and configure datasources (setup wizard)

autorag lite ui is still in development — do not recommend it for datasource setup. Configure datasources directly in trusted config, wizard-style:

1. Probe every datasource for setup feasibility before asking the user anything: the backing CLI exists (lazykatok, discrawl, slacrawl, wacrawl, telecrawl, notcrawl, qmd, mailcrawl, rclone) and its local store or archive is present. CLI-backed datasources own their own archive, index, and authentication, so environment credentials (such as bot tokens) are never required or checked for them. Non-CLI connectors (such as github) require their credential environment variable (GITHUB_TOKEN).
2. Auto-configure every datasource that probes feasible — write its trusted datasources / datasourceAccess entries without asking. For example, when Slack (slacrawl) and Discord (discrawl) are installed with local stores present, set both up automatically. Discord uses discrawl's local desktop wiretap archive; no Discord bot token is configured or needed.
3. Skip every datasource that probes infeasible (for example Notion or Telegram when their CLIs are not installed) and always report the skipped list to the user, with what is missing for each.
4. Set up a skipped datasource only when the user explicitly asks for it: install or authenticate the backing CLI first, then configure it.
5. E-mail datasources (mail-export, mailcrawl) matter to most users — always probe them and report their status, even when they end up skipped.

Datasource skills belong in trusted config and remain default-deny.

Config keys may be builtin template names (kakao, whatsapp, telegram, slack, discord, clawgallery, notion, github, cloud-drive, mail-export, mailcrawl, obsidian, rss, spotlight) or connection aliases with "type": "<template>". Unknown names are skipped with an unknown-datasource-skill warning; they do not fail config resolution. datasourceAccess.allowedTags and allowedScopes narrow trusted access and can never grant it. Store only env-var names such as tokenEnv or apiKeyEnv, never credential values.

Build and refresh indexes

autorag lite refresh --json
autorag lite refresh --method parsed,minsync --json
autorag lite refresh --full --json
autorag lite refresh --force --json

• A plain refresh is incremental: it syncs parsed mirrors, MinSync, Jikji, and configured datasources against what changed.
• --full and --force both request a full resync. Use them only when incremental refresh is not enough, such as after config changes to roots or index settings.
• --method <csv> deliberately narrows the refresh. Valid values are parsed, minsync, datasources, jikji, and all. Omit the flag to run all methods. Unknown values are rejected.
• MinSync and Jikji auto-install on first use by default. If they are missing or broken, run a full refresh or return to setup rather than silently degrading to lexical-only search.
• MinSync's default embedder is in-process native Qwen3 embeddings (native:Qwen/Qwen3-Embedding-0.6B, 1024 dimensions, MinSync 0.4.5+): no embedder flags, no API key, and no external daemon (such as Ollama) are needed, and no corpus text leaves the machine. For gateway-profiled embeddings, prefetch with autorag models prefetch --profile qwen3-embedding-0.6b. The legacy Ollama/TEI adapter path (EmbeddingGemma, 768 dimensions) is for manual QA only. Override the embedder only when intentionally using a different provider.
• Exact duplicate exclusion during refresh is enabled by default via the external dupey CLI. Install dupey during setup when it is missing (command -v dupey || cargo install dupey) and tell the user the feature is available; when installation is impossible, refresh continues without it and the user is told duplicate exclusion is off. Set "excludeExactDuplicates": false to index every copy.

Retrieval requires a completed refresh. autorag lite retrieve before any refresh exits with code 2 and an index-not-ready diagnostic; a successful refresh is recorded even when the corpus is empty or only a non-parsed method was selected. Always refresh first, and refresh again when roots change. Once a refresh has completed, staleness is reported rather than enforced: a source that changed afterwards gives "stale": true with stale-index diagnostics (and autorag lite status reports stale: true) while retrieval still answers from the index. Sources the refresh deliberately skipped — exact duplicates, oversized or unparseable files, and AutoRAG/Jikji product artifacts such as .jikji_agent_map.md — do not count as stale. Use autorag lite retrieve --refresh to rebuild incrementally before one query, or --strict when a stale index must fail instead of answering. Jikji is a discovery/indexing preparer, not a lite retrieval method.

Watch and scheduled freshness

autorag lite watch --once --json
autorag lite watch

Prefer non-daemon autorag lite watch --once from cron, launchd, a systemd user timer, or Task Scheduler, hourly by default (every 1 hour; shorten only when the user asks for fresher indexes). Use the same config as retrieval, avoid overlapping runs, and keep logs outside source trees. --immediate triggers a first refresh on start and --debounce-ms N tunes change coalescing. Once the schedule is installed, tell the user right away that hourly freshness is set up.

Status and index maintenance

autorag lite status --json
autorag lite health --json
autorag lite index rebuild --yes --json
autorag lite index reset --method parsed --yes --json
autorag lite duplicates --json

• status shows path-opaque corpus freshness and index health. health is an alias of status; neither resolves a model.
• index reset and index rebuild remove or rebuild only workspace .autorag indexes selected by --method. They never target source documents.
• duplicates scans duplicate document families read-only and never deletes or moves files.

Unavailable components and failure handling

Missing optional components degrade gracefully: refresh and retrieval continue with diagnostics such as minsync-unavailable or retrieval-method-failed instead of failing the whole run. Each one quotes the underlying error verbatim, and lite retrieve --json also names the skipped surface under unsearched. Exit codes are 0 on success, 2 for config or usage errors, and 1 for runtime errors. When a component stays unavailable after a full refresh, return to setup rather than accepting silently degraded search.

Completion condition

Setup is complete only when the CLI is installed, roots are approved, a non-secret model-free config is written, every datasource has been probed and the auto-configured and skipped lists reported to the user, dupey is installed or its absence reported, refresh has built the requested indexes, status reports healthy indexes, and any requested watch schedule is installed or verified with the user told it is active.