In this video, I’ll be telling you about Google’s new Code Wiki, how it auto-generates living documentation for your repositories, and how the upcoming Gemini CLI extension could bring all of this into your private codebases.
—
Key Takeaways:
🧠 Google Code Wiki creates a continuously updated, structured wiki for your repos, tied directly to the actual code.
📚 Documentation is automatically regenerated after each change, fixing the problem of stale READMEs and outdated architecture notes.
💬 A built-in Gemini-powered chat uses the wiki as its brain, so answers are context-aware and specific to your repository.
📊 Code Wiki auto-generates architecture, class, and sequence diagrams that always reflect the current state of the code.
🔐 A Gemini CLI extension is coming so you can run Code Wiki locally on internal and private repos, keeping everything secure.
⚠️ Right now the web experience is focused on public repos, with open questions around pricing, large monorepos, and complex codegen.
🎥 For some projects, it can even generate a full explainer video via NotebookLM based on your code and documentation.
🚀 Overall, it’s a promising step toward “living documentation” that helps teams ship faster instead of getting stuck deciphering legacy code.
source
