Skip to content
Lithora
Lithora Docs

Code Search & Architecture

Two repo-grounded agents. Code Search indexes a connected repo and lets you search it in plain language; Architect sketches a Mermaid diagram of how a repo fits together.

Code Search
semantic
where do we verify the webhook signature?
webhooks/verify.py
def verify_signature(payload, header):
routes/github_hooks.py
if not verify_signature(body, sig): ...

Ask by meaning, not exact keywords — matches deep-link to the file on GitHub.

Code Search

Search your code in plain language

Beta
  • Index a linked repo: Point it at a repo connected to your team and Lithora indexes its files in the background. The status shows how many files are indexed and whether an index is running.
  • Search by meaning: Ask for a concept — “where do we rate-limit logins” — and results are ranked by semantic similarity, each deep-linking to the file on GitHub.

What beta means here

Code Search is semantic(embeddings-based). It finds code by meaning, not by exact string — there is no keyword, symbol, or AST layer yet, so it complements rather than replaces GitHub's exact code search. It also depends on the embeddings model being available to your deployment; if that grant is missing, search returns no results rather than guessing.

Architect

Sketch a repo's architecture

AI sketch
  • From a repo or a description: Generate a Mermaid diagram from a connected repo's structure, or from a plain-text description of your system. Generated diagrams are saved to your team.
  • Editable output: The result is standard Mermaid, so you can drop it into a doc or refine it by hand.

It's an approximation

The diagram is AI-approximated from repository structure (folder and file names), not a real import or dependency graph. Treat it as a fast first sketch to react to — verify it before relying on it.

Repositories

Both agents only work on repos connected to your team — either linked directly to the team or to one of its projects. You can link, list, and unlink repos right on these pages, and the picker shows exactly the repos you can index, search, or diagram, so you're never stuck on a “no repo found” dead end.

Plan requirement

Architect runs on Lithora AI and requires an active Pro or Scaleplan — the check is enforced on the API and resolves from the team owner's plan. Both agents need a repository connected to your team first; connecting GitHub itself has no plan gate, so link the repo before you try either. See GitHub PR & CI sync.

Find it

Open Dashboard → Code Search and Dashboard → Architecture, or install Code Search and Architect from the Agents gallery.