sqry

sqry is a semantic code search tool. It parses source code into an AST and builds a graph of symbols and relationships, so you can search by what code means rather than just what it says.

Website: https://sqry.dev

Example

# Index a codebase (creates .sqry/graph/snapshot.sqry)
sqry index

# Find all public async functions
sqry query "kind:function AND async:true AND visibility:public"

# Who calls this function?
sqry query "callers:authenticate"

# Trace a path between two symbols
sqry graph trace-path main handle_request

# Find circular dependencies
sqry cycles

# Ask in plain English (translates to sqry syntax, then searches)
sqry ask "find all error handling functions"

Why sqry?

If you just need text search, use ripgrep - it's faster and simpler for that job.

sqry is useful when you need to search by code structure: finding all callers of a function, tracing execution paths, detecting cycles, or querying by symbol kind, visibility, or return type. These are things text search can't do reliably.

What sqry is good at

• Relation queries: callers:X, callees:X, imports:X, returns:Result - exact answers from the call graph
• Graph analysis: trace paths between symbols, find cycles, detect unused code
• Structured queries: combine predicates with boolean logic (kind:function AND lang:rust AND async:true)
• Cross-language detection: FFI linking (Rust<>C/C++), HTTP route matching (JS/TS<>Python/Java/Go)
• AI assistant integration: MCP server with 36 tools, LSP server for editors

When NOT to use sqry

• Simple text search: Use ripgrep. It's faster for grep-style patterns.
• Pattern matching on syntax: Use ast-grep. It's better for "find this syntax pattern and replace it."
• Linting or rule enforcement: Use language-specific linters (clippy, eslint, semgrep).
• Full IDE features: Use your editor's built-in language server.
• Hosted code search: Use Sourcegraph if you need a web UI and team features.

sqry is focused on one thing: local semantic code search via AST analysis.

What's New In 13.0.3

• Accurate unused-code analysis across binding boundaries: sqry unused, LSP analysis, and MCP find_unused now gather a full candidate superset before CLI/MCP/LSP filters run, then apply the binding-plane post-filter at the boundary. This prevents visibility, kind, and scope filters from hiding symbols that should still be considered during reachability.
• Binding-plane resolution is first-class: V9 snapshots derive scope, alias, shadow, import, and export tables from the graph, and sqry graph resolve <symbol> --explain --json exposes witness-bearing resolution for debugging name lookup.
• Derived Analysis DB is the shared query path: cycle, unused, reachability, entry-point, trace, dependency, subgraph, export, semantic-diff, CLI, and MCP analysis paths now share sqry-db query implementations with sharded derived-result caches.
• Incremental graph persistence moved to V10: snapshots now persist the file-segment table used for append-only node allocation and safe per-file reindexing. After upgrading from a pre-V10 release, run sqry index --force once so the graph is rebuilt with V10 metadata.
• Daemon-backed workflows are production surfaces: sqryd keeps graphs hot across CLI, MCP, and LSP sessions; sqry daemon load, sqry daemon rebuild, sqry daemon status, and sqry daemon logs are available, and sqry-mcp --daemon / sqry lsp --daemon can auto-start the d

... View full README on GitHub