Hi everyone! Been working on this for a couple of months. First, let me tell you the problem: I found myself asking opencode to look at transcripts again and again to orient it with myself whenver I started a new session. It's like the thing has amnesia.

Trie creates an index of meaning and intent for your code to supplement the agent's understanding + adds historical context about changes at a per-symbol level. It's all stored permanently alongside your code as markdown files.

Using this index, I have been able to make the code navigation faster than the usual grepping - also allowing some graph based questions about blast radius to be answered. It also functions as a markdown wiki. All of it is kept in sync using fingerprinting and the index updates incrementally as the agent makes changes - updating only when it needs to

Trie installs pre-commit hooks that block the change until intent behind every changed symbol is explicitly recorded. Currently supports python, TS, Golang and more.

My eventual goal is making a fully reactive code editing system for agents and I think this is a good first step. Looking for alpha-testers and really just anyone who can take a look at this and give honest feedback.

Oh and it's not a service. It's easily self-hosted and available to any coding tools that can call a cli or use MCP. BYOK.

I created a self-hosted index of intent and meaning for your codebase that works with any coding agent. 3x better code navigation and maintains symbol level reasons for every change.