Technology Radar
With agent-maintained knowledge bases, a team keeps its shared knowledge in linked plain-text files, often in an Obsidian vault, and uses a coding agent to maintain them. Andrej Karpathy's LLM Wiki describes the pattern: raw sources the agent reads but never changes, a wiki it maintains and a schema that guides how it does it. OpenWiki applies a narrower version of the idea to a single code repository's documentation. The technique is practical today because general-purpose coding agents can already read and edit files effectively, while Git provides version control.
Many people start with a personal "second brain." We recommend taking the next step and sharing one across a team, although expanding it into an organization-wide knowledge base takes more than pointing a coding agent at a folder of files. Generated knowledge can drift from reality, and without regular human effort to keep it accurate, the knowledge base risks creating AI-driven documentation sprawl.
Several of our teams use variations of this approach, with product managers, designers, developers and their agents all querying the same knowledge base. These teams find their information more connected and accessible.
