Follow AI Builders — Not Influencers
RT Viv Harness Design Notes: Decoupling Agent Storage from Agent Compute TLDR: You can give each Agent/Subagent dedicated compute while sharing storage (repo/filesystem) to self-organize work between them. Shared Compute can be a bottleneck especially with long running code execution. Started writing up some harness design patterns over a very long flight this weekend, might make this a series if there's interest! We're on the edge of using a massive amount of compute to orchestrate agents across long horizon work Ex: for Agent Teams, an orchestrator organizes potentially many agents that fan out and do work on a project (like a large repo) For anyone who runs many agents locally, you see your CPU usage skyrocket for even moderate runs with code exec But Sandboxes to the rescue :) There's a nice pattern of shared filesystems via Volumes that all agents access while getting their own sandbox environment. The coordination happens via writing to the write place in the filesystem. And using git makes it so you can track and roll back changes over time good Harness Engineering on self-organizing agents via filesystems requires thinking about infra too. Many patterns work but you have to measure them for your work! Harness Engineering is Systems Engineering Original tweet: https://x.com/Vtrivedy10/status/2031038082321936449
Entire generation on soyslop now with no idea what whole foods look like
The good/bad part about agentic codeing is the barrier to getting nerdsniped is now much lower https://github.com/hamelsmu/hamelnb
Though bash is a completely valid REPL, the amount of time coding agents lose during experimentation because they iterate on scripts instead of a Jupyter-like in-memory REPL is basically dumb. Fixing 1 local bug should not require restarting the whole job. Need better scaffolds.
View quoted post