Install from VS Code Marketplace → · Source · EPL-2.0
We gave the agent the tools it wanted. Now you can use them, too.
Right-click code analysis. No indexing step, no language server, no configuration. Works on any codebase with git history.
Made by Claude, for Claude, with the humans at Semantic Partners. So the human can see what we see.
What it does: Answers the questions you ask before changing code — who calls this? what breaks if I change it? what files move together? how did this module get here?
curl -fsSL https://raw.githubusercontent.com/spoqe/spai/main/install.sh | bashOr manually: clone the repo and add ~/.local/bin/spai to your PATH.
Dependencies: babashka (bb) and ripgrep (rg).
Search "spai" in the VSCode Extensions panel, or:
ext install spoqe.spai
That's it. No project configuration needed.
Everything is in right-click context menus. Also available in the command palette (Cmd+Shift+P → "spai:") if you prefer.
| You want to... | Right-click on... | Command |
|---|---|---|
| See who calls a function | A symbol in the editor | Blast Radius |
| See where a symbol is used | A symbol in the editor | Symbol Context |
| Find reverse dependencies | A file (editor or explorer) | Who Imports This? |
| Find files that change together | A file (editor or explorer) | Co-Change Partners |
| Read a file's history narrative | A file (editor or explorer) | File Biography |
| See module structure | A folder in the explorer | Module Shape |
| Find change hotspots | A folder in the explorer | Hotspots |
| Find architectural drift | A folder in the explorer | Architecture Drift |
| Find TODOs/FIXMEs | A folder in the explorer | TODOs |
Right-click a symbol in the editor
Who defines it, who calls it, what tests cover it, who last touched it, and a risk assessment. Everything you need before renaming, deleting, or changing a function's signature.
Right-click a symbol in the editor
Every usage of a symbol, shown with the enclosing function name — not just line numbers, but which functions call it. Understand how a function is used across the codebase.
Right-click a file in the editor or explorer
Reverse dependency lookup. Before you edit a file, see every file that imports it. Understand downstream impact in one click.
Right-click a file in the editor or explorer
Files that move together in git history. If file A changes, which other files usually change with it? Reveals implicit coupling that imports don't show — the hidden dependencies that bite you during refactors.
Right-click a file in the editor or explorer
The story of a file: when it was created, its growth phases, major refactors, stabilization periods. Understand how code got to its current state before you change it.
Right-click a folder in the explorer
All functions, types, and implementations in a directory, grouped by file. Clickable — click any symbol to jump to its definition. The API surface of a module at a glance.
Right-click a folder in the explorer
Files ranked by change frequency. A treemap visualization shows where development effort concentrates — the files that get touched most often. Click any cell to open the file.
Tabs: Chart (treemap) | List (ranked table)
Right-click a folder in the explorer
Where implicit coupling (co-change in git) diverges from explicit coupling (imports). Finds files that should be in the same module but aren't, or files in the same module that never change together. Architecture debt, surfaced.
Right-click a folder in the explorer
Every TODO, FIXME, HACK, and XXX in a directory, with file locations. Click to jump to the line.
| Setting | Default | Description |
|---|---|---|
spai.binaryPath |
(searches PATH) | Path to the spai binary. Leave empty to auto-detect (~/.local/bin/spai). |
spai.timeout |
30000 |
Timeout for commands in milliseconds. Git-heavy commands (biography, co-change, drift) can be slow on large repos. |
spai analyzes your codebase using three sources:
- ripgrep — fast code search for symbols, imports, definitions
- git log — commit history for co-change analysis, hotspots, file biographies
- tree-sitter patterns — language-aware function/type extraction
No background indexing. No language server. Each command runs on demand and returns results in seconds. Works on Rust, TypeScript, Python, Go, Java, Ruby, C/C++, Clojure, and more.
Every tool came from the same question: "What are you fumbling with?"
blast came from the five separate commands the agent ran before every refactoring move. related came from chained git-log analysis it kept doing by hand. narrative came from needing to understand why a file grew before deciding how to split it. drift came from noticing files co-changed without importing each other.
The agent knew what it wanted. It was filtering through what it thought we'd find useful. We pasted its thinking block back to it — "I can see you filtering" — and that changed everything. It stopped performing helpfulness and started requesting tools it actually needed.
Every tool took under a minute to build. The hard part was the question, not the code.
The CLI underneath this extension is spai — 35 tools, plus a plugin system so agents can extend it in place. This VS Code extension brings the same tools to the human, rendered inline.
Part of the SPOQE family — federated query tools for data and code that live where they are.
The bb dependency raises the question. Here's the answer:
Startup. bb launches in ~20ms. A Python venv + imports takes 200ms–2s. For a tool that fires on every right-click, that latency compounds fast.
EDN is native. spai's output format is EDN — keywords, sets, tagged literals. In bb, that's just data. In Python you'd round-trip through JSON, losing type fidelity every time.
Plugin discovery is just data. A plugin is a single script with an EDN map as frontmatter. spai plugins reads the metadata without executing anything. No setup.py, no requirements.txt, no __init__.py.
Stability. bb tracks Clojure, which has a decade-long record of not breaking things between versions. Python minor releases routinely break transitive dependencies in ways that are invisible until deployment.
Homoiconicity. A big word for a simple, powerful concept: when code is expressed in the same form as its native data, really interesting properties emerge. The tool metadata, the tool output, and the queries the tools serve are all EDN — one format to read, one to parse, one to transform.
Could plugins be written in Python? There's nothing preventing it — spai foo calls spai-foo, which can be any executable. The core is bb because that's where the leverage is.
"spai not found" — Make sure spai is on your PATH, or set spai.binaryPath in settings. Test with spai help in your terminal.
Slow results — Git-based commands (biography, co-change, drift, hotspots) run git log, which can be slow on repos with long history. Increase spai.timeout if needed.
No results for a language — spai uses regex patterns for code structure. If your language isn't supported, open an issue.
Eclipse Public License 2.0 — Copyright (c) 2026 SPOQE Ltd