DeepWiki, AutoWiki and OpenWiki point to a new pattern for agent context
garrytan · x · 2026-07-23
A thread argues that the emerging “LLM wiki” pattern is becoming a standard way to feed agents better context: compile docs once, keep them updated, and have the agent read the generated pages instead of raw sources.
It cites several implementations:
- Cognition launched DeepWiki, a generated wiki for every public GitHub repo, with Devin reading that instead of raw code.
- Factory built AutoWiki, which treats docs as a build artifact and regenerates them in CI on every push.
- LangChain open-sourced OpenWiki, extending the idea from repos to a person’s working life across Gmail, Notion, and Git.
- Garry Tan open-sourced GBrain, a personal-scale version built from files in Git.
The common idea is to compile once at ingest, maintain the pages, and route agents to the curated wiki rather than the original noisy sources.
More from coding & agent
- Resin lets an agent build standalone LLM inference engines; vLLM and SGLang optimize DeepSeek kernels differently — AccBalanced · 2026-10-27
- Context layout is a cost decision: one memory edit can bust your entire agent prompt cache — dscape · 2026-10-27
- Alchemy adds effect/Workflow support across Durable Objects, Workflows and Lambda Durable Functions — samgoodwin89 · 2026-10-27
- Alchemy's Lambda Web Functions run plain Node web servers on Lambda, no OpenNext needed — samgoodwin89 · 2026-10-27
- Alchemy Domain brings domain-driven design and story testing to Effect backends — samgoodwin89 · 2026-10-27
- Alchemy makes all ~2,850 AWS bindings work from any cloud, not just S3/Lambda/DynamoDB — samgoodwin89 · 2026-10-27