The code index now answers who calls a function. Name a file or a symbol, and OPVS reads its stored map of your repository for the callers, the test files nearby and the commit that answer describes, with no checkout and nothing run.
What's new in v1.14.0
- One call shows who depends on a function.
POST /api/v1/code/{project_id}/callerstakes up to 50 files or symbols. Each caller comes back with the symbol it calls and a label saying whether the match is exact or heuristic. Python calls are indexed today. - The same answer in the terminal, the IDE and the agent. Use
opvs code callersin @opvs-ai/cli 0.27.9 or later, the MCP toolcode_callersin @opvs-ai/mcp 2.12.0 or later, or thecallersmethod in the @opvs-ai/code-index skill. - A draft card gets checked before work starts.
opvs code check-card <brief.md>reads the paths in a brief and prints one block to paste into the card, with a row per path. A path that does not exist shows as NO while it is still cheap to fix. - Unknown never reads as zero. A file type with no call data, a folder or an unavailable index comes back marked unknown with its reason, so an empty list means no caller was found, not that nobody looked.
Three limits apply to every answer. The index is as old as its last commit, a heuristic caller may be wrong, and a test hint is not coverage.
The route needs a token with the code:read scope and a GitHub repository attached to the project. Read the reference at https://opvs.ai/docs/opvs/api/code-index and every release note at https://opvs.ai/changelog.