Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git) • Hacker News Board

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#71

Post by smadam9 » Sat, Apr 25, 2026, 2:30 PM UTC

A comment here mentioned "Everyone is writing. Nobody is reading." but I think the friction starts even further upstream.

I've been building a native Mac app "Sig" around this idea: capture has to come from you. You sit down after a meeting and articulate what happened — what was decided, who committed to what, what you actually think. That articulation is the work. The AI routes it into files. If you skip that step and scrape transcripts instead, no promotion workflow saves you. You're just contributing to the garbage in, garbage out idea.

That is Sig https://news.ycombinator.com/item?id=47901737>

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#72

Post by mehhehheehh » Sat, Apr 25, 2026, 2:37 PM UTC

Hacking

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#73

Post by najmuzzaman » Sat, Apr 25, 2026, 2:41 PM UTC

davedigerati wrote: post #4

why not an Obsidian vault with a plugin?

Two structural reasons. 1. Obsidian is a single-user editor. It does not have the concept of "agent A drafted this, agent B promoted it, the team approved it." The promotion flow needs a state machine that lives outside the editor. a plugin can simulate it but the source-of-truth has to be a process the agents talk to instead of a vault file. 2. Agents need an MCP surface. An Obsidian plugin API won't do. /lookup, entity_fact_record, notebook_write, and team_wiki_promote are MCP tools the agent runtimes call directly. Obsidian's plugin API targets human users and the Electron app. You would be reimplementing the MCP layer to bridge. Practical compatibility: you can absolutely point Obsidian at ~/.wuphf/wiki/ and use it as a vault (we got someone from our Reddit post do this). Obsidian can be reader while WUPHF stays the writer.

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#74

Post by hmokiguess » Sat, Apr 25, 2026, 2:45 PM UTC

ting0 wrote: post #47

batoga wrote: post #22

Put AI in your product name, make billion dollars. Put Karpathy in your blog article, get hired by Anthropic as Principal engineer. Milk money as long as fad last. No one is thinking about customer needs, everyone is trying to wash hands in the wave as it last.

Hey man, if it works it works. There's a reason everyone is creating AI tools. We're all buying them. I'm still waiting for someone to make a world-class cli harness that can replace Claude Code but solves the memory and design problem. Web design is still a nightmare with LLMs.

Could you elaborate on the web design point? I find them excellent at it personally and it’s where I most often get value out of them

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#75

Post by najmuzzaman » Sat, Apr 25, 2026, 2:48 PM UTC

Abby_101 wrote: post #66

The "garbage facts in, garbage briefs out" caveat is the part I'd want stress tested. In my own LLM features the context that decays fastest is what agents wrote without a human glance. Six months in, you have entries that are confidently wrong and the lint pass can't tell which. Does the promotion flow require human review or can agents self promote?

[dead]

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#76

Post by hmokiguess » Sat, Apr 25, 2026, 2:49 PM UTC

Someone should build a StackOverflow revival as the solution to this, a distributed knowledge graph curated by humans but driven by collective LLMs trying to problem solve their way out of things and stopping to ask questions in an old fashioned way.

I would be fine with my agent saying “hey, we hit a wall here, here’s the question posted on SO, I flagged to come back to it later once we have an answer”

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#77

Post by najmuzzaman » Sat, Apr 25, 2026, 2:56 PM UTC

batoga wrote: post #22

Put AI in your product name, make billion dollars. Put Karpathy in your blog article, get hired by Anthropic as Principal engineer. Milk money as long as fad last. No one is thinking about customer needs, everyone is trying to wash hands in the wave as it last.

alright sir/ma'am/neither. we built an AI-native CRM backed by HubSpot founder Dharmesh Shah last year before this, had revenue, iterated to focus on context graph infra which looked like the right moat to focus on, did enterprise PoCs, and all of that distilled into this personal project i built on the side to help my own work. turned out to be right interface for making context infra usable.

not interested in a job at Anthropic as Principal Engineer (i used to be a HubSpot Product Manager with a healthy income, much better than what i am making now, or for the next few years).

took multiple bets and did iterations because we talked to customers and kept evolving while our old competition is still building an AI CRM "in stealth".

been around enough to know waves don't matter but there is still value behind those waves worth extracting away.

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#78

Post by frrandias » Sat, Apr 25, 2026, 2:56 PM UTC

zby wrote: post #62

Reviewed: https://zby.github.io/commonplace/agent-memory-systems/revie... It is a third llm wiki on front page in 24 hours! Obviously it is a hot topic. I have my own horse in that race - so I might not be objective - but I've compiled a wishlist for these system: https://zby.github.io/commonplace/notes/designing-agent-memo... I wish there was a chance for collaboration - everybody coding their own system seems like…

taking a look :)

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#79

Post by ryanshrott » Sat, Apr 25, 2026, 3:03 PM UTC

One practical approach that works is separating the capture layer from the promotion layer. Agents can draft freely, but anything that gets promoted to trusted status needs a human review. Some teams use a voting scheme where multiple agents independently summarize the same source, and you only promote it when they converge. The confidently wrong problem gets worse over time because bad entries get cited by other agents, and that's how you end up with a knowledge base full of confident BS.

Re: Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

#80

Post by najmuzzaman » Sat, Apr 25, 2026, 3:03 PM UTC

ting0 wrote: post #47

batoga wrote: post #22

Put AI in your product name, make billion dollars. Put Karpathy in your blog article, get hired by Anthropic as Principal engineer. Milk money as long as fad last. No one is thinking about customer needs, everyone is trying to wash hands in the wave as it last.

Hey man, if it works it works. There's a reason everyone is creating AI tools. We're all buying them. I'm still waiting for someone to make a world-class cli harness that can replace Claude Code but solves the memory and design problem. Web design is still a nightmare with LLMs.

thanks for saying this. one more reason people are hating on SaaS so much is that the UI is dry and for many, unusable. on the other hand, the cool AI agents have UI which is fun but again, unusable.

fun and usable can co-exist and we are trying the best to prove that. also, we have an amazing designer who never worked at big tech and has no accolades, but man got taste.