Hacker News Reader

Wait, isn't that how everyone is building their harnesses? I actually struggle to imagine an alternative. Just keeping a a single row in the DB for chat history and always overwriting that?

Maybe I'm biased because we are primarily building a chat interface ala ChatGPT, which isn't anything different than a "remote harness". I'm not sure why one would design a local harness differently.

I think a lot of people are building their harnesses this way more recently, but last year, Claude, Codex (and other harnesses) were storing everything on a big json file on disk.

Codex has (to my knowledge) always stored sessions in append-only .jsonl files. Whether you store an append-only log in a file or a database makes no difference.

It really feels like I'm being gaslight here into believing "durable agents" are novel. All I'm seeing is the API that is behind any Chat Web UI. Persistence, resumability, recovery from errors and branching and forking have been table stakes there since the release of the first ChatGPT.

Useless and misleading talk!!

thanks swyx! the log is the agent is a core insight behind this

you beat pi-durable to it!

haha yes! this was the reasoning for making durability native in our harness