On the reading list: I gave Pi one tool
Queued up for a proper read: I gave Pi one tool by Tom (monotykamary).
The premise alone earns it a spot on the list. Instead of handing the Pi coding agent a box of verbs — read, search, run, edit — Tom collapsed everything into a single fabric_exec tool that accepts TypeScript. The model writes a small program against Pi’s capabilities, it runs in a QuickJS sandbox, and only the returned evidence reaches the conversation. A loop becomes an actual loop; parallel work becomes Promise.all; twenty megabytes of tool output becomes ten useful lines.
Then it gets recursive: most of pi-fabric was built by models working through pi-fabric — 337 commits and 11,155 fabric programs in twelve days, with Tom steering, stealing good ideas, and rejecting bad ones.
This lands right in the middle of my Pi obsession — same orbit as the shape-your-own-tools prompt I captured earlier. Skimming it, the parts I want to sit down with: tool schemas as an entropy source (models drift while reproducing unfamiliar schemas, so give them a compiler instead), deliberate erasure — compaction, forgetting, and state transitions as runtime features — and the honest cost accounting: reading, not writing, is the bill.
Note to self: before going deeper I need to learn more about how Pi itself is built — the extension API and its lifecycle events, sessions as JSONL trees, compaction, the SDK and RPC modes — so I can adjust pi-brain to get the most out of the harness, and honestly validate whether the idea makes sense at all next to runtimes like pi-fabric.