/status
Check if the codebase is indexed and ready for semantic search
> /plugin marketplace add Helweg/open-codebase-index > /plugin install codebase-index@helweg-plugins
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/status
Context preview
What this command does when you run it.
Check if the codebase is indexed and ready for semantic search
Command definition
status.mddescription: Check if the codebase is indexed and ready for semantic search
Run the `index_status` tool to check if the codebase index is ready.
This shows:
- Whether the codebase is indexed
- Number of indexed chunks
- Embedding provider and model being used
- Current git branch
- Failed embedding batches or compatibility warnings that explain why search is not ready
No arguments needed - just run `index_status`.
If not indexed:
- suggest running `/index` when no index exists yet
- if status reports failed embedding batches, tell the user to fix the provider/auth issue and rerun `/index` normally
- if status reports provider/model incompatibility, tell the user to run `/index force` for a full rebuild
Search a codebase by meaning, then follow the result into definitions, callers, and dependency paths. open-codebase-index is a local semantic code index for OpenCode, Jcode, Pi, Codex, Claude Code, and other MCP clients.
Repo: Helweg/open-codebase-index
Other commands on codebase-index.
- /call-graph
Trace callers, callees, or paths using the call graph
Open command - /definition
Find where a symbol is defined in the codebase
Open command - /find
Find code using hybrid approach (semantic + grep)
Open command - /peek
Quickly find likely code locations without returning full code
Open command - /pr-impact
Analyze PR or branch impact using the call graph
Open command - /reindex
Fully rebuild the codebase index from scratch
Open command