alt.hn

7/1/2026 at 8:51:52 PM

OpenWiki: CLI that writes and maintains agent documentation for your codebase

 https://github.com/langchain-ai/openwiki

by handfuloflight

7/2/2026 at 12:29:14 AM

maintaining an LLM wiki has been a lot more effort than I thought, at least if we are trying to maintain a high quality in structure and writing comprehension (for easier lookups both for the agent and human). Are people just shotgunning their agent wikis or how

by rrvsh

7/2/2026 at 5:15:37 AM

> maintaining an LLM wiki has been a lot more effort than I thought

Same here. Wikis start out good, but either devolve in a journal-y mess after a while and many updates, or require constant expensive rewrites. (I didn't use the software of the OP.)

by bad_username

7/2/2026 at 11:59:29 AM

Wikis start out good, but get stale too quick and become useless or worse confusing.

I’ve experienced this over and over again to strongly believe it.

I genuinely wonder if throwing LLMs at this problem would solve it at least to some extent. Make a LLM agent whose sole purpose is to act as a librarian. It periodically reviews _all_ of the wiki and validates them against codebases, newer docs, anything. Whatever it finds, it should be allowed to intelligently quiz the team/dev whether something is right/stale/wrong and updated it accordingly.

If one tolerates that toil - answering questions of a library bot, would it result in a usable wiki base?

by reacharavindh

7/2/2026 at 6:42:11 AM

generating docs is the easy part. keeping stale docs from becoming “truth” is the real problem.

by felixlu2026

7/2/2026 at 5:10:54 PM

Bot.

by AlexeyBelov

7/2/2026 at 4:10:37 AM

This is mostly a thin clintypescript wrapper around the prompts.

This could have been a SKILL

by TeeWEE

7/1/2026 at 11:25:47 PM

What does this do better than just asking your agent to "write docs" or a more robustly defined prompt/skill?

by dcreater

7/2/2026 at 2:42:09 AM

Have a look at the prompts in the GitHub [0]. It defines a System Prompt and specifies the documentation structure. This would allow you to switch coding agents, instead of relying on how your coding agent interprets the command "write docs".

[0]: https://github.com/langchain-ai/openwiki/blob/main/src/agent...

by capplexham

7/2/2026 at 1:48:21 AM

I swear most of these tools are made for the sake of it…

While good old prompting is often better than plan mode or superpower skills.

by b212

7/2/2026 at 12:10:19 PM

I've had a number of people send me tools like this at work, and easily 50% of them can't answer basic questions like "what's the reason someone would adopt this tool" or "how do you know that it will achieve its stated goals". Agents are good at reading code, I can't imagine what the point of autogenerating agent context could be if it's not showing demonstrable cost benefits.

by SpicyLemonZest

7/2/2026 at 12:30:41 AM

This is what we do. The same agent writing the code can also write the docs.

by _pdp_

7/2/2026 at 4:53:28 AM

We need to make an effort to distinguish “this is a thing for humans” vs “this is a thing for bots” in our naming IMHO. In that respect, “open wiki” is not such a great name. “Agent Wiki” or similar would be better.

Without such a qualifier, “wiki” carries a strong connotation of (usually collaborative) human involvement. That’s literally what it’s famous for.

Thats just my $0.02 on the naming. I definitely think it’s a worthwhile idea. All the best.

by mthoms

7/2/2026 at 7:53:57 PM

[flagged]

by shakargy

7/2/2026 at 2:16:58 PM

[dead]

by supermdguy

7/1/2026 at 10:12:26 PM

[flagged]

by wrencastellan

7/2/2026 at 3:44:28 AM

[dead]

by lodar