Don’t know if Karpathy even wrote this version. Where are the citations?
i used this idea to create a version that works for a team of ai agents
121–130 of 140 posts
Don’t know if Karpathy even wrote this version. Where are the citations?
i used this idea to create a version that works for a team of ai agents
Don’t know if Karpathy even wrote this version. Where are the citations?
A lot of these tools (paperclip) don't, but for our small, agent-supported team, that would be the feature we're looking for. I.e. the agents of different marketing roles talking to each other, with clearly defined 'human in the loop' decision making.
I love that so many people are building with markdown ! But also would like to understand how markdown helps in durability - if I understand correctly markdown has a edge over other formats for LLMs. Also I too am building something similar on markdown which versions with git but for a completely different use case : https://voiden.md/
I'm interested. At a glance this sounds a lot like Hurl[0]. What's the difference? [0] https://hurl.dev/
Just to stir thought, I note the TiddlyWiki[1] community (wiki as a self-modifying single html file; 20+ years old) has of course been exploring AI tooling... though not necessarily as an agentic environment. There's a markdown plugin, and others to make the file executable, or into a self-serving web app. Git is more problematic. So hypothetically, one could have a single-file agentic wiki wandering around and self-…
For the single-file configuration you describe, there are already several LLM connectors — e.g. [1]. The appeal is exactly what you note: no dependencies, no installation, trivially archivable. A single-file agentic wiki wandering around and self-editing isfeasible today.
For something closer to Karpathy's LLM Wiki pattern, I've been working on twillm[2], which uses TiddlyWiki's Node.js configuration. That setup saves tiddlers as individual files, so you can point it at an existing Markdown vault and work alongside tools like Claude Code.
Some benefits of TiddlyWiki for this:
* Open source, so you can be confident it'll remain usable indefinitely.
* Web-based, so accessible anywhere.
* Computed views replace materialised index files. Karpathy's setup relies on an index.md that the LLM has to keep in sync as it adds notes — something LLMs are bad at, with staleness creeping in across sessions. TiddlyWiki views are live filter expressions: "tiddlers tagged concept, sorted by rating" computes its contents at render time.
* Frontmatter becomes queryable structure. Obsidian renders YAML frontmatter as boxed metadata at the top of a note. TiddlyWiki promotes frontmatter fields into first-class tiddler fields you can filter, sort, and aggregate over.
* LLM-authored applets, not just content. Beyond Markdown notes, the LLM can drop in wikitext tiddlers (.tid) that act as small interactive live views: dashboards, browse-by-tag tools, journal indexes, glossary pages.
[1] https://github.com/rimir-cc/tw-llm-connect [2] https://github.com/Jermolene/twillm
Couldn't you instruct your LLM to make the starting dir configurable?
yes, and we should expose it. today the wiki location is hardcoded to ~/.wuphf/wiki/. making it a config field is a quick change. just filed an issue: https://github.com/nex-crm/wuphf/issues/310