32 MCP tools · 11 platform surfaces · shared registry
Intelligence · Lens
Code intelligencefor every agent.
Local lexical search and structural navigation are real today. Semantic and graph planes, plus the shared hosted runtime that will compose them, are still in design. The interaction below is illustrative, not a live hosted query.
Your question
where do we validate?
The four planes
Each plane is a different kind of truth.
Lexical finds the literal phrase. Structural resolves the symbol. Semantic ranks paraphrases. Graph (planned) will show what depends on this.
Lexical
Shippedzephr_grepLiteral and regex indexing. The plane that never interprets, so it never hallucinates about what it found.
Structural
Evolvingzephr_lspTree-sitter and LSP symbol resolution — definitions, references, and enclosing scope.
Semantic
Evolvingzephr_searchCode embeddings for the questions no grep answers. Embedding storage is in-database pgvector locally; the hosted semantic serving pipeline is in design, not yet serving.
Graph
Plannedzephr_searchImport, ownership, and ref edges — designed but not yet extracted. Graph availability is planned, not live.
Every answer names the plane that served it.
Literal and regex indexing. The plane that never interprets, so it never hallucinates about what it found.
worker:apps/worker/lens-lexical-build
Tree-sitter and LSP symbol resolution — definitions, references, and enclosing scope.
worker:apps/worker/lens-structural-build
Code embeddings for the questions no grep answers. Embedding storage is in-database pgvector locally; the hosted semantic serving pipeline is in design, not yet serving.
worker:apps/worker/lens-semantic-build
Import, ownership, and ref edges — designed but not yet extracted. Graph availability is planned, not live.
worker:apps/worker/lens-graph-build
Explore each engine
Pick a plane. See what it matches.
Each engine reads the same code a different way. Select one to see its tool, what it matches honestly, and where it is in the build.
Lexical
Shippedzephr_grepLiteral and regex indexing. The plane that never interprets, so it never hallucinates about what it found.
example: zephr_grep "where do we validate session tokens"
Structural
Evolvingzephr_lspTree-sitter and LSP symbol resolution — definitions, references, and enclosing scope.
example: zephr_lsp definition middleware
Semantic
Evolvingzephr_searchCode embeddings for the questions no grep answers. Embedding storage is in-database pgvector locally; the hosted semantic serving pipeline is in design, not yet serving.
example: zephr_search "what depends on this edge case" --hybrid
Graph
Plannedzephr_searchImport, ownership, and ref edges — designed but not yet extracted. Graph availability is planned, not live.
example: zephr_search "what depends on this"
Every answer names the plane that served it, so the agent can verify the match rather than trusting it.
The breakdown
One query. Four planes. One ranked, cited answer.
A breakdown of an illustrative answer. The query, the planes that contributed, and what each one gave the result.
Query
> zephr_search "where do we validate session tokens?" --hybrid
The answer
session tokens are validated in the edge middleware, never in route handlers.
apps/web/src/middleware.ts - L31-L58 - 8d13ba0
Illustrative example — not live data
How each plane contributed
found the literal phrase across apps/web/src/middleware.ts
resolved the symbol and gave definitions, references, enclosing scope
ranked paraphrases of the same intent from sibling files
designed to show what depends on this, on which branch it was true — graph extraction is not built yet
The other ways
You can answer the question in a worse way.
Each approach is reasonable on its own. The intended Lens answer combines distinct evidence types rather than pretending one search mode is enough. That complete hosted composition is the design target, not a live claim today.
The four ways tools usually answer
Embed your whole repo in a hosted vector DB
The query "what depends on this" returns semantic neighbours — not the import graph. You get plausible chunks, not the answer.
Use plain grep / IDE find
The query "what depends on this" returns every literal string — including false matches in tests, comments, and unrelated files.
Adopt a hosted dev search
A complete hosted product. Lens is a retrieval plane underneath your agents, not a complete hosted dev search. The hosted runtime is in design.
Compose independent evidence in one answer
The design target fuses lexical, structural, semantic, and graph evidence into one cited answer. Local lexical and structural tools are real; the complete hosted composition is not live yet.
The gate
9 of 9. Measured, not claimed.
The retrieval gate is tested against nine deterministic scenarios. The IDs and verdicts are copied verbatim from docs/trust/TRUSTBENCH-EVIDENCE.md.
The nine scenarios
How the gate runs
Deterministic, replayable, no luck.
Each scenario defines an admitted scope, a contradicting or paraphrased ref. The verdict is mechanical: a scenario that does not abstain on a contradiction is a fail.
Read the evidenceThe tool surface
Three tools, one retrieval plane.
Two are single-plane - literal search, structural navigation. The third is hybrid retrieval that composes them rather than presenting separate engines as a complete hosted product.
zephr_grepLexicalLiteral and regex search across admitted refs. A match is a literal one — it cannot be wrong about what it found, only about whether you wanted it.
zephr_grep "where do we validate session tokens" --refs=org/billingzephr_lspStructuralTree-sitter and language-server symbol resolution: definitions, references, call sites, and enclosing scope rather than string matches.
zephr_lsp definition middleware --refs=org/webzephr_searchHybridUnified retrieval that combines lexical and semantic evidence into one ranked, cited answer — not a separate engine presented as a complete hosted product.
zephr_search "what depends on this edge case" --hybridThe runtime status
Honest about what ships, what doesn't.
Every Lens runtime-status dimension with its honest state. The page does not hedge shipped as evolving or evolving as planned.
A measured retrieval plane, not a complete hosted product.
Lens ships the measured gate and real local lexical and structural tools. Semantic, graph, and the shared hosted orchestration remain in design — the page says so rather than implying a complete hosted search.