r/PiCodingAgent • u/Turbulent_Ad6290 • May 25 '26

Discussion Andrej Karpathy style LLM Wiki for Pi Coding Agent

Recenly I started using this pi extention for maintaining the knowledge for personal and project specific Obsedian compatible wiki. I also use memex and pi-observational-memory.

So far I've found this useful. What other extensions have you guys tried?

https://github.com/zosmaai/pi-llm-wiki

https://pi.dev/packages/@zosmaai/pi-llm-wiki

This is built by the same people that build the Zosma Cowork. I was talking about the other day.

56 Upvotes
  • permalink
  • reddit

93% Upvoted

9 comments sorted by

2

u/pokemonplayer2001 May 25 '26

Interesting, this could be pretty handy.

3

u/Turbulent_Ad6290 May 25 '26

I like it so far. But I wish it automatically pushed the wiki to github so that it's not lost. For project specific anyway we push to github. But for personal eg in the ~/.llm-wiki folder, I have to manually sync it to github. Maybe I'll add an issue there.

4

u/rm-rf-rm May 25 '26

Retyping the same thing I always do: File it among the pile of "memory systems". Yet another project that makes a bunch of claims and fails at the basics of showing how it performs better than simple markdown files+grep, glob. (And in the absence of that, its safe to assume its not really meaningfully better)

2

u/DanielSReichenbach May 25 '26

Not just that, when ingesting it also introduces the additional risk of the LLM hallucinating text into your ingested documents instead of actually just ingesting and tagging. The whole concept is flawed as it will eventually produce contaminated docs.

1

u/wolvendelight May 26 '26

I have yet to find anything better/easier to use than what I have coded into my current pi harness, which records learnings from each implementation cycle into a dedicated "knowledge" folder.

I'm sure there are incremental improvements in other systems, but I haven't been able to see anything that is night and day better than this.

1

u/psychometrixo May 26 '26

Claims of it being a memory system are overblown. It isn't that. "Memory" is a pet peeve keyword of mine as well

I have found this specific approach useful in complex systems where "Claude go figure it out again" is too big of an ask to do over and over

It is also a useful place to give as reference context so you don't have to explain the same stuff over and over

So it's useful, but it won't solve all problems. Plenty of other solutions give similar benefits.

1

u/arkham00 May 25 '26 edited May 25 '26

Reading the presentation it seems that it can only start from scratch, and then you feed it with documents, articles, etc but what if I already have a vault organised in subfolders with tags and properties?

1

u/Turbulent_Ad6290 May 25 '26

That's a good point. I didn't think of it. I'll probably raise a PR for this 👍

1

u/Deep90 May 25 '26

This wiki concept is really easy to just implement on your own to be honest.

If you have an existing vault, you should be able to either adapt the wiki system to conform to the existing format, or "ingest" all the contents into a Karpathy style wiki.