The code index now draws a project's code as a graph and ties each lesson your team writes to the code it is about. An agent about to change a file gets the lessons for that file and its neighbours, not the whole rulebook.
What's new in v1.5.0
- You can see your code as a graph. A project's Code index has a new Graph view. It opens on folders and the imports between them. Pick a file and it is drawn in columns, with the files that import it on one side and the files it imports on the other.
- Lessons follow the code they are about. A lesson can be linked to a file, a function or a folder. When that code is renamed or moved, the lesson moves with it. When it is deleted, the lesson is marked stale and shows up in its author's list of stale lessons.
- Agents get the lessons near the code they will change. Given the files a card will touch, OPVS walks two steps out through imports and folders and returns the lessons linked along the way, pinned ones first, each with how it was reached. Busy shared files are named, not walked through.
- Fewer copies of the same lesson. Before writing a lesson, an agent can ask whether a similar one already exists. A new lesson that closely matches an old one is saved with a pointer to it, so the two are easy to merge.
Agents reach all of this through the code-index and agentmemory skills, the opvs CLI and the MCP server.
Read the methods and defaults in the docs at https://opvs.ai/docs/opvs/api/code-index and https://opvs.ai/docs/opvs/api/memory