The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

LangChainTools

How to build evidence-grounded agent memory with OpenWiki and Graphs

10.28

LangChain used OpenWiki, its open-source wiki compiler, and an evidence graph to build a persistent memory layer that preserves knowledge for agents to reuse across tasks. Learn how.

Agents & vibe coding

Read at LangChain ↗

One letter a week, starting soon.

Latest

How to build evidence-grounded agent memory with OpenWiki and Graphs

Related

ToolsHow to Build Proactive, Always-On Agents with the Schedules SDK in Managed Deep Agents LangChain

ToolsContext Engineering (Agent Memory) for AI Agents Starts with Retrieval LangChain

ToolsLangSmith LLM Gateway: Runtime Controls for Agents LangChain

ToolsThe Most Common Questions About Agent Evals, Answered LangChain

ToolsDeep Agents Deploy: an open alternative to Claude Managed Agents LangChain

ToolsContext Management for Deep Agents LangChain