|
|
|
|
|
|
by razvan_maftei
68 days ago
|
|
|
Hi there. agentfab is distributed in the sense that it can run across different compute instances and has a control plane service managing nodes and agent instances. There's a blog post I wrote delving deeper into those capabilities with a more apt demo here: https://razvanmaftei.me/article?slug=agentfab-the-distribute... As to your other question - agentfab uses a Conductor agent (baked into every fabric) that creates the taskgraph, which supports bounded review loops. The platform also supports pausing running tasks for user queries or change requests, which fires the decomposition step again. The end-to-end process can get a bit wordy to explain, my blog posts and the docs in the repo do a better job at that. I'm 100% looking for collaborators on this, so if you're interested I'd love to discuss more. |
|
|
From what I understand, it's closer to a Kubernetes-style scheduler/worker model — so more about parallelizing computation for fully controlled systems/applications, rather than "distributed" in the sense of independent agents across boundaries.
One thought I had (just a random thought): it could be interesting to push this toward a broader notion of distribution — not quite full P2P, but something like an "agent hub", where agents owned by different organizations coordinate via MCP/A2A or similar protocols. If there were a way to manage collaborative task execution across those boundaries, that would feel pretty cutting-edge and a genuinely different class of system.