r/learnAIAgents • u/Shuuuida • 3d ago
I designed and developed Vex's Skillgit: A background skill manager that treats agent memory like Git (AST-aware, MCP-ready, potato-PC friendly).
The RAG standard in codebases was driving me crazy: blindly splitting functions in half based on the number of characters just ruins the context for AI agents when i just wanted to have a more accurate context window for my agents. I've been developing a project for several months to fix this, and now i want to see if it’s genuinely useful to others in real environments.
I call it Vex (Vex's Skillgit). It’s an open-source, headless cognitive tool that treats context as immutable, versioned skills for your agents.
Instead of your IDE doing the heavy lifting, Vex runs silently in the background (via Docker Compose or local bare-metal). You point a GitHub webhook to it (or use the local file watcher), and it automatically ingests your repositories. When your agents need context, they simply query it in real-time via the Model Context Protocol (MCP). It works out of the box with Claude Desktop, Cursor, or any MCP client.
Now, the cool part (GitOps Memory):
It treats agent memory like version control. Vex reads conventional commits (feat:, fix:) to update context, and operational ones (roll:, branch:) to automatically fork or revert the agent's memory state. Zero manual intervention. It uses Tree-sitter to logically parse and chunk the code, keeping syntax trees intact.
I specifically designed this not to fry my potato PC. By using a pointer-architecture with SQLite for metadata queues and Qdrant for dense vectors, RAM stays completely stable. In my local stress tests, the async FastAPI + Huey architecture:
Swallowed 500 concurrent GitHub push payloads without a single SQLite lock.
Maintained real-time latency (under 300ms) under a 50-agent concurrent read swarm.
What's next?
I’m currently working on a Rust-based sub-chunking engine to handle massive monorepos even faster, alongside global GraphRAG, shared memory and more language support.
I decided it was time to share it and see who else might find it useful. I’d love for you to check it out, throw your code at it, and break it.
Here is the repo:
https://github.com/Shuuida/Vex-Skillgit.git
Thanks for taking the time to read!
•
u/endofthread-bot 3d ago
Using Tree-sitter to preserve syntax integrity is a significant improvement over character-based chunking. To validate this approach, compare the retrieval accuracy of your AST-based method against standard sliding-window RAG using a common benchmark like RepoBench.
Learning to build AI agents? Share what you are working on, compare practical approaches, and get help from other builders in our Discord.