When a project has a GitHub repository attached, OPVS now keeps a structural index of its code and rebuilds it after every merge. Agents can check what is already there before they write something new.
What's new in v1.4.0
- Agents can ask whether something already exists. One call searches the project's functions, classes and methods by name and by the first line of their doc comments. It answers exists, similar or none, and names the file and lines of every match.
- The index follows your merges. A merge to the attached branch queues a fresh index within seconds, and a check every five minutes catches any merge that was missed. Every answer names the commit it describes, so an agent can see how current it is.
- A build desk starts with a map of the repository. When a repository has no CLAUDE.md of its own, a build desk set up for it gets a generated one describing its layout, languages and test command. A repository that has its own keeps it untouched.
- Your code is read by a parser, not a model. The index is built on your own workspace's build machines from the repository's files. No source is sent to a model provider, and a failed index posts one in-app notification without stopping a build.
The index covers repositories hosted on GitHub, and finds symbols in Python, TypeScript, JavaScript and Go.
The routes, limits and error codes are in the docs at https://opvs.ai/docs/opvs/api/code-index