| Hi HN, I’m the creator of agentfab, a distributed agentic platform that features task decomposition, multi-agent orchestration, model heterogeneity with custom agentic fabrics, bounded review loops, and a bespoke self-curating memory system that enable shared context. My background is in engineering at hyperscalers where I worked extensively with foundational distributed systems. I started agentfab because I wanted an agentic coding tool that could effectively decompose and parallelize work across different model providers and agent profiles. agentfab will run locally on your machine, on your VM fleet, on your K8s cluster, or any distributed compute environment. The clear benefit over existing agentic coding tools is that agentfab is able to fan out work across many different agents from various model providers (OpenAI, OAI-compatible, Google, Anthropic) with shared context - it’s able to break down large scope tasks into subtasks and assign the appropriate agent for each; it handles bounded review loops, artifact streaming between agents, and uses OS-level sandboxing and secure communication between agents. You are in full control of your agent "fabric" - simply define YAML agents and specify which tools, capabilities, and special knowledge they have and the platform will know how to make use of them during task decomposition. There are 4 default agents that cover most software development tasks. agentfab has an interactive CLI with taskgraphs and progress tracking - you can prompt agentfab to execute on end-to-end projects or chat with any of the agents in the fabric to query against their knowledge. If you want to read more about agentfab, check out this blog: https://razvanmaftei.me/article?slug=agentfab-stateful-multi... Check out the GitHub repo if you want to try it out. Looking forward to hearing your thoughts. Thanks! |
One question I had: in the demo, the agent builds a browser game. But that kind of task seems achievable even with vanilla Opus (plus Claude Skills / tool use), so I struggled a bit to see the core differentiation here.
Also, the project mentions "distributed" — is that mainly coordination between local processes, or does it already support cross-machine / networked execution? If it’s the former, tighter integration with remote execution (e.g. Tailscale-based peer agents or similar) could be a more meaningful differentiator. Not sure how practical that is in real deployments, but it feels like a clearer step beyond existing agent runtimes.
On the Graph-RAG part, I also couldn't fully understand how it's actually constructed internally (how the graph is built/updated and how retrieval is integrated into execution). A bit more detail on the internal mechanics there would help clarify the design.