OOliver ZehentleitnerOct 18 · 7 min readSeven Coding Agents. One Chat Window.After the planning was done, seven agents started working. Infrastructure, ingestion, retrieval, frontend, accounts, shared library, coordination. Separate sessions, working in parallel and talking to15DBblog.technopathy.club
OOliver ZehentleitnerOct 12 · 13 min readKeep the Why vs. past.dev vs. Agent Memory Repo vs. agentmemoryThis is the third dated comparison. The first looked at Claude Code auto memory, MemoryCustodian and AgentsRoom. The second compared OKF Agent Memory and RepoWise, the two that work closest to the repblog.technopathy.club
OOliver ZehentleitnerOct 5 · 16 min readKeep the Why vs. OKF Agent Memory vs. RepoWise: Three Approaches to Git-Native Project MemoryThree approaches to Git-native project memory for coding agents "Project memory for coding agents" is becoming a broad category. Three projects are especially interesting because all are repository-or2Ablog.technopathy.club
OOliver ZehentleitnerSep 29 · 9 min readThe reasoning behind a codebase, as a web you can walkOpen this before you read on: keepthewhy.com/dashboard/live/#graph Give it a few seconds to settle. Then come back. It looks like a knowledge graph. It isn't. There is no graph database behind it. Nob34JKblog.technopathy.club
