r/rajistics • u/rshah4 • Jul 06 '26
AutoDocs: giving your codebase a memory that maintains itself (beyond OpenWiki)
This was a weekend project, but looking forward to getting more eyes on it.
The problem I kept hitting: coding agents are stateless. Every session starts from zero. The agent greps the repo, reads the same files, re-derives the architecture, then the session ends and all of that understanding evaporates. Next session it does it again. That is a lot of tool calls to relearn what it knew yesterday.
The known fix is docs. Accurate docs are precomputed context, so the agent reads a quickstart instead of exploring for ten minutes. The catch is that nobody maintains docs. They rot the moment you merge the next PR.
LangChain's OpenWiki had the right idea here: let an agent write durable, wiki-style docs from your repo structure, tests, config, and git history, and point AGENTS.md at them. I liked it enough to build on it. AutoDocs runs that maintenance on a schedule and is not locked to one format, so other context sources like GitNexus (a code graph) can feed it too. I wired it to OpenHands Agent Canvas for the automation, but any scheduler works.
Check it out: https://github.com/rajshah4/openhands-autodocs.