Live data from Hacker News

Viewing profile — wenhan_zhou

wenhan_zhou

HN member
Joined
Fri, Mar 13, 2026, 8:24 PM UTC
HN karma
13
Public activity
18 items

About wenhan_zhou

No profile information was provided.

Recent public activity

  1. comment
    Comment #48630942

    Yep. Or even better, compact after a random number of turns. The model must then learn to preserve useful context at arbitrary context lengths.

  2. comment
    Comment #48628992

    If understanding emerges from pre-training, then perhaps memory is what emerges from post-training.

  3. story
  4. comment
    Comment #47789857

    Currently working on a benchmark!

  5. comment
    Comment #47789849

    Ah, so you are effectively offloading the file exploration mechanism to the INDEX.md in the sub-directories rather than writing a complex prompt?

  6. comment
    Comment #47784662

    How does the agent intelligently synthesize information across different files?

  7. comment
    Comment #47767289

    In theory, yes. Although the privacy setting says otherwise. But in the end, it doesn't really matter; it is public on GitHub, so anyone can use it.

  8. comment
    Comment #47764009

    I just read LLM Wiki in more detail. I have heard about it second-hand before this project. The "no-code" idea was inspired by Karpathy. As I have understood it, in LLM Wiki, the h…

  9. comment
    Comment #47763800

    Although I have been working on memory before, ReadMe is very fresh. The moment I saw it running, I published it. So, no continuous running nor LLM ablation studies. Treat it as an…

  10. comment
    Comment #47762813

    I think what's missing is a benchmark that measures how well the memories contribute to future interactions.

  11. comment
    Comment #47762572

    I don't remember such details, but as you suggest, it is a healthy kind of compression. I address it through merging the lower-level memories into more abstracted ones through a te…

  12. comment
    Comment #47761978

    I see your point. A removal mechanism is not (yet) implemented. But in principle, we could adjust the instructions in Update.md so that it does a minor "refactor" of the filesystem…

  13. comment
    Comment #47761645

    Minimalism is my design philosophy :-) Good question. Since it is just an LLM reading files, it depends entirely on how fast it can call tools, so it depends on the token/s of the …

  14. comment
    Comment #47761597

    Yep. Markdown is the future :-)

  15. comment
    Comment #47761578

    Fair concern. ReadMe does support loading memories mid-reasoning! It is simply an agent reading files. Although GPT-5.4 currently likes to explore a lot upfront, and only then resp…

  16. comment
    Comment #47761528

    Context bloat is real, but the architecture has the potential to solve it. You need clever naming for the filesystem and exploration policy in AGENTS.md. (not trivial!) The benchma…

  17. comment
    Comment #47761473

    The editability is surely an underrated advantage, both for the program itself and the memories it generated. I think in terms of noise, it is less problematic here because not eve…

  18. story
    Show HN: Continual Learning with .md

    I have a proposal that addresses long-term memory problems for LLMs when new data arrives continuously (cheaply!). The program involves no code, but two Markdown files. For retriev…