Rytora Code — Codebase Indexing

Semantic search across your repo. Tree-sitter symbol extraction + embedding-based retrieval.

Part of the Rytora Code suite — install Rytora Code to get the full toolkit (Composer, Tab autocomplete, Cmd+K, Codebase Indexing, Publish, and more).

What it does

Builds a semantic index of your codebase so other Rytora Code features (Composer, Tab autocomplete, Subagents) can pull in relevant context instead of dumping entire files into the prompt.

How it works

1. Parse — Files are parsed with Tree-sitter (~100 languages supported) to extract symbols, function bodies, classes, and exports.
2. Chunk — Symbols are grouped into semantic chunks. Files without a Tree-sitter parser fall back to text-based chunking.
3. Embed — Chunks are embedded into a vector store. Defaults to local embeddings; switch to managed embeddings via the Rytora BuildLabs API for higher quality.
4. Retrieve — When Composer or another feature needs context, it queries the index with the user's prompt and pulls the top-K most relevant chunks.

Why it matters

• Better suggestions — Tab autocomplete and Composer see your conventions, not generic patterns.
• Smaller prompts — Sends 5 KB of focused context instead of 50 KB of full files. Faster, cheaper, more accurate.
• Local-first — Local embedding mode means code never leaves your machine for indexing.

Commands

Configuration

• rytora-code.indexing.enabled — Master switch
• rytora-code.indexing.maxFiles — Cap on files indexed (default: 10,000)
• rytora-code.indexing.embeddingProvider — local (default) or managed

What gets indexed

• Source files matching common code extensions (.ts, .tsx, .js, .py, .go, .rs, .java, .cs, .rb, .php, .swift, .kt, .cpp, .c, .h, .css, .html, .vue, .svelte, and ~80 more)
• Respects .gitignore automatically
• Skips node_modules, dist, build, .next, .cache, and similar generated dirs

Getting started

1. Install Rytora Code (recommended) or this standalone extension.
2. Sign in with your Rytora BuildLabs account.
3. Open any workspace — indexing starts automatically in the background.
4. Check status: Command Palette → Rytora: Show Indexing Status.

Privacy

In local embedding mode, code never leaves your machine for indexing — only the resulting vectors do, and only when other features query them. Set embeddingProvider: managed to use Rytora BuildLabs' hosted embeddings for higher quality (sends chunks to the API).

Links

• Homepage: buildlabs.rytora.ai/code
• Documentation: buildlabs.rytora.ai/docs/code
• Support: buildlabs.rytora.ai/support

License

MIT