Welcome to SourceIndex!
SourceIndex plugs into your coding agent as a CLI in Claude Code and OpenCode, and as MCP tools in Codex, so that the agent searches a prebuilt index of your repository and jumps straight to the right files and functions. Want to see it first? Watch the demo.
Make sure you have:
sk-si-) — apply for access herepip install sourceindex
sourceindex --version
cd /path/to/your/repository
sourceindex init claude # Claude Code only
sourceindex init codex # Codex only
sourceindex init opencode # OpenCode only
sourceindex init # all
If the repo has no CLAUDE.md or AGENTS.md yet, run
/init in your agent first.
Heads-up before you run it: SourceIndex sends your source files to our backend for processing — your code isn't stored. Exactly how that works: Security & Data Handling.
claude, codex or opencode to enter the agent and work with SourceIndex.
sourceindex search on its own — init told it to — and gets
back a roadmap of the exact files and functions for the task. While that runs, the status line
shows sourceindex is running.
search_index tool first, then reads the exact files and functions the roadmap points to.
sourceindex search with your request as the query
and gets back a roadmap of the exact files and functions for the task.After each turn, SourceIndex tells you what it saved in this session and over the past week — an estimate built from your agent's own token counts. Each agent shows it in its own way.
Run sourceindex savings in your terminal for the full picture: the past 7 days in total and
day by day, plus your best day and what SourceIndex has handled in the last 30 days.
Here are the most important commands for daily use. Shell commands run from your terminal.
Shell commands
| Command | What it does |
|---|---|
sourceindex deinit --force |
Remove SourceIndex from a repository |
sourceindex api-key set [KEY] |
Replaces the stored API key. |
sourceindex savings |
Prints the savings from the local ledger. |
sourceindex doctor |
Checks the install end to end. |
We're early, and every bit helps — even “I can't tell if it's working” is useful. Write to [email protected].
For more questions, see the FAQ.