--- title: A 2-person team ships multi-agent delegation, quietly description: A two-person team quietly shipped multi-agent v2 for their coding agent tooling, letting a model delegate subtasks to any supported agent rather than only... canonical: https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: A 2-person team ships multi-agent delegation, quietly | daily.dev og:description: A two-person team quietly shipped multi-agent v2 for their coding agent tooling, letting a model delegate subtasks to any supported agent rather than only... og:url: https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg og:image: https://api.daily.dev/og/posts/CkgUslFRg.png og:image:alt: A 2-person team ships multi-agent delegation, quietly og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # A 2-person team ships multi-agent delegation, quietly **[Trends](https://daily.dev/sources/trends)** · 3 min read · 1 upvotes · 0 comments ## Summary A two-person team quietly shipped multi-agent v2 for their coding agent tooling, letting a model delegate subtasks to any supported agent rather than only siblings from the same provider. The feature itself is unremarkable since cross-agent delegation is now common across frameworks, but notable developer-tool builders like Charlie Marsh and Jason Liu retweeted it, and Theo called it the best remote control for coding agents he's used, framing it as a small team outperforming big labs. The piece is skeptical of the flattering narrative, noting real headaches with cross-provider delegation like inconsistent tool-calling formats, auth handling, and debugging failures across multiple models' reasoning. ## Content There's a quiet feature drop this week that's generating outsized buzz relative to its size: multi-agent delegation to any supported model, shipped by a small team, and apparently nobody noticed until developers started retweeting it into everyone's timeline. The core claim, repeated by @pvncher and amplified by a chain of retweets from Hamel Husain, Charlie Marsh, and Jeremy Howard (jxnlco), is simple: "we just shipped the ability for models with multi agents v2 to delegate to any supported" model. Translation: agents can now hand off subtasks to whichever model fits the job, not just whatever model started the conversation. It's the kind of infrastructure change that doesn't make for flashy screenshots but changes how people actually build agent workflows day to day. What's interesting is who's noticing. Marsh (creator of Ruff and uv) and Husain (a well-known voice in the ML tooling space) don't retweet just anything, so their attention here is doing some of the work of validating that this matters, even without a flashy demo attached. Meanwhile, a separate but related thread is playing out around NanoClaw, which @rohanpaul_ai is calling out for landing directly in Slack. His framing: "from a single message I can let one agent create and coordinate multiple" other agents, all without leaving a chat window. That's the workflow a lot of teams have wanted for a while, agent orchestration that doesn't require jumping into a separate dashboard or CLI. Then there's the sharper, more pointed reaction from @theo, retweeting @makeavish11's take on what's apparently become their go-to remote control for coding agents: "2 person team is outperforming big labs." That's a real claim, and a loaded one. Whether it's hyperbole or an honest assessment of a scrappy tool beating out resourced competitors, it's the kind of line that gets people arguing in replies, and it's clearly resonating with the crowd that's tired of watching billion-dollar labs ship incremental agent updates. The throughline across all of this: small teams and lesser-known projects are quietly outpacing the marketing machines of the major AI labs on actual agent usability. Nobody's claiming these tools beat frontier models on raw capability. The claim is narrower and more interesting, that the people building the *interfaces* and *orchestration layers* for agents are moving faster and shipping more useful stuff than the labs building the underlying models. Given how much of the current agent hype cycle lives in that orchestration layer, that's worth paying attention to. ## Questions this post answers ### What does multi-agent v2 delegation mean for AI coding agent tools? It means a model can delegate subtasks to any supported agent rather than only to agents from the same provider. This cross-provider delegation was shipped as a quiet update by a small two-person team, without a launch thread or demo video, yet it drew attention from developer tooling figures like Charlie Marsh and Jason Liu. _Developers evaluating multi-agent orchestration options can follow updates like this on daily.dev._ ### What are the risks of delegating tasks across different AI agent providers? Cross-provider agent delegation introduces inconsistent tool-calling formats between vendors, complicated auth handling across different providers, and difficulty debugging a failure when it must be traced through three different models' reasoning chains. These issues are not visible in social media announcements praising the feature. _Teams weighing multi-vendor agent setups can track these trade-offs through daily.dev._ ## Similar posts on daily.dev - [NanoCo bets the future of enterprise AI is one sandboxed agent per employee](https://daily.dev/posts/nanoco-bets-the-future-of-enterprise-ai-is-one-sandboxed-agent-per-employee-g5lb20bx3) · The New Stack · 1 upvotes · 0 comments - [Slack makes it easier to install agents built with third-party tools](https://daily.dev/posts/slack-makes-it-easier-to-install-agents-built-with-third-party-tools-crjnwol5a) · The New Stack · 1 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents) [View this post on daily.dev](https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"A 2-person team ships multi-agent delegation, quietly","url":"https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg"},"datePublished":"2026-08-15T18:14:48.960Z","dateModified":"2026-08-21T12:56:28.287Z","description":"A two-person team quietly shipped multi-agent v2 for their coding agent tooling, letting a model delegate subtasks to any supported agent rather than only...","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"A 2-person team ships multi-agent delegation, quietly"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-2-person-team-ships-multi-agent-delegation-quietly-ckguslfrg#faq","mainEntity":[{"@type":"Question","name":"What does multi-agent v2 delegation mean for AI coding agent tools?","acceptedAnswer":{"@type":"Answer","text":"It means a model can delegate subtasks to any supported agent rather than only to agents from the same provider. This cross-provider delegation was shipped as a quiet update by a small two-person team, without a launch thread or demo video, yet it drew attention from developer tooling figures like Charlie Marsh and Jason Liu. Developers evaluating multi-agent orchestration options can follow updates like this on daily.dev."}},{"@type":"Question","name":"What are the risks of delegating tasks across different AI agent providers?","acceptedAnswer":{"@type":"Answer","text":"Cross-provider agent delegation introduces inconsistent tool-calling formats between vendors, complicated auth handling across different providers, and difficulty debugging a failure when it must be traced through three different models' reasoning chains. These issues are not visible in social media announcements praising the feature. Teams weighing multi-vendor agent setups can track these trade-offs through daily.dev."}}]} ```