{"id":382,"date":"2026-02-13T08:18:17","date_gmt":"2026-02-13T06:18:17","guid":{"rendered":"https:\/\/vittrup-graversen.dk\/?p=382"},"modified":"2026-03-28T12:11:03","modified_gmt":"2026-03-28T10:11:03","slug":"fra-solo-agent-til-dev-team-claude-codes-nye-agent-teams-aendrer-spillereglerne","status":"publish","type":"post","link":"https:\/\/vittrup-graversen.dk\/index.php\/2026\/02\/13\/fra-solo-agent-til-dev-team-claude-codes-nye-agent-teams-aendrer-spillereglerne\/","title":{"rendered":"Fra Solo-Agent til Dev Team: Claude Codes nye Agent Teams \u00e6ndrer spillereglerne"},"content":{"rendered":"\n<p>Da Anthropic lancerede Opus 4.6 den 5. februar 2026, fulgte en feature med, som fundamentalt \u00e6ndrer den m\u00e5de udviklere arbejder med AI-assistenter p\u00e5: <strong>Agent Teams<\/strong>. Ikke l\u00e6ngere \u00e9n AI-agent, der k\u00e6mper sig igennem opgaver sekventielt \u2014 men et helt team af specialiserede agenter, der arbejder parallelt i dit codebase.<\/p>\n\n\n\n<p>Jeg har fulgt udviklingen t\u00e6t \u2014 og har nu selv gjort mig nogle erfaringer med multi-agent workflows via Claude Code. Her er hvad du skal vide.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hvad er Agent Teams?<\/h2>\n\n\n\n<p>Agent Teams er Claude Codes svar p\u00e5 det, udviklere har bygget selv i m\u00e5neder: multi-agent orkestrering. Konceptet er simpelt men kraftfuldt:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Team Lead<\/strong>: Din prim\u00e6re Claude Code-session. Analyserer opgaven, opretter teamet, fordeler arbejde og samler resultaterne.<\/li>\n\n\n\n<li><strong>Teammates:<\/strong> Selvst\u00e6ndige Claude Code-instanser med eget kontekstvindue. Hver agent loader projektets `CLAUDE.md`, MCP-servere og skills \u2014 og arbejder uafh\u00e6ngigt.<\/li>\n\n\n\n<li><strong>Shared Task List:<\/strong> En central opgaveliste med tre tilstande: *pending*, *in progress*, *completed*. Opgaver kan have afh\u00e6ngigheder, der automatisk blokerer\/frigiver.<\/li>\n<\/ul>\n\n\n\n<p>Den afg\u00f8rende forskel fra sub-agents: <strong>teammates taler med hinanden<\/strong>. En sub-agent rapporterer tilbage til sin caller. Agent team-medlemmer sender direkte beskeder, udfordrer hinandens konklusioner og koordinerer autonomt.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bag kulisserne: TeammateTool<\/h2>\n\n\n\n<p>Historien om Agent Teams startede faktisk f\u00f8r den officielle lancering. <a href=\"https:\/\/paddo.dev\/blog\/claude-code-hidden-swarm\/\" target=\"_blank\" rel=\"noreferrer noopener\">En udvikler<\/a> k\u00f8rte <code>strings<\/code> p\u00e5 Claude Codes bin\u00e6re fil og fandt <strong>TeammateTool<\/strong> \u2014 et fuldt implementeret multi-agent system med 13 operationer, mappestrukturer og environment variables. Feature-flagged off. Klar til brug.<\/p>\n\n\n\n<p>Systemet inkluderer:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>**Team lifecycle:** `spawnTeam`, `discoverTeams`, `cleanup`<\/li>\n\n\n\n<li>**Koordination:** `write` (direkte beskeder), `broadcast` (alle teammates)<\/li>\n\n\n\n<li>**Plan-godkendelse:** `approvePlan`, `rejectPlan`<\/li>\n\n\n\n<li>**Graceful shutdown:** `requestShutdown`, `approveShutdown`<\/li>\n<\/ul>\n\n\n\n<p>Det viste sig, at Anthropic havde produktificeret de community-byggede multi-agent l\u00f8sninger som <code>claude-flow<\/code>, <code>ccswarm<\/code> og <code>oh-my-claudecode<\/code> \u2014 og absorberet m\u00f8nstrene ind i platformen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u00e5dan kommer du i gang<\/h2>\n\n\n\n<p>Agent Teams er stadig eksperimentelle. Aktivering kr\u00e6ver \u00e9t environment variable i din Claude Code setting (setting.local.json eller setting.json) :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"env\": {\n     \"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS\": \"1\"\n   }\n}<\/code><\/pre>\n\n\n\n<p>Eller direkte i shell:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1<\/code><\/pre>\n\n\n\n<p>Derefter beder du Claude i naturligt sprog:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>*&#8221;Jeg vil refaktorere auth-modulet. Opret et agent team: \u00e9n teammate p\u00e5 backend JWT-logik, \u00e9n p\u00e5 frontend session-h\u00e5ndtering, og \u00e9n der skriver integrationstests.&#8221;*<\/p>\n<\/blockquote>\n\n\n\n<p>Claude spawner teamet, opretter en delt opgaveliste og begynder at koordinere. Ingen YAML-konfiguration. Ingen boilerplate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fire koordineringsm\u00f8nstre<\/h2>\n\n\n\n<p>Erfaringerne fra de f\u00f8rste uger viser fire m\u00f8nstre, der fungerer:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Hierarkisk<\/h3>\n\n\n\n<p>En Chief Orchestrator dirigerer Team Leads (Frontend, Backend, DevOps), som igen styrer specialistagenter (CSS, API, Testing).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Afh\u00e6ngighedsbaseret<\/h3>\n\n\n\n<p>Task B venter p\u00e5 Task A. Sekventielle workflows med logiske afh\u00e6ngigheder forhindrer for tidlig eksekvering.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Broadcast<\/h3>\n\n\n\n<p>Systemd\u00e6kkende opdateringer. Alle agenter modtager information samtidig for synkroniseret forst\u00e5else.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Peer-to-peer messaging<\/h3>\n\n\n\n<p>Direkte agent-til-agent kommunikation. Samarbejdende probleml\u00f8sning og krydsvalidering af tilgange.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Tre use cases der retf\u00e6rdigg\u00f8r token-forbruget<\/h2>\n\n\n\n<p>Agent Teams koster ca. <strong>5x mere i tokens<\/strong> end en enkelt agent. Disse scenarier g\u00f8r det v\u00e6rd:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Parallel Code Review (3 reviewere, 3 perspektiver)<\/h3>\n\n\n\n<p>Spawne tre reviewere med forskellige perspektiver: sikkerhed, performance og test-d\u00e6kning. \u2018Lederen\u2019 samler alle fund til \u00e9t samlet review. Tre agenter fanger, hvad \u00e9n overser.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Debugging med konkurrerende hypoteser<\/h3>\n\n\n\n<p>Den m\u00e5ske mest overbevisende use case. \u00c9n agent finder \u00e9n plausibel forklaring og stopper. Flere agenter, der <em>argumenterer mod hinanden<\/em>, finder den rigtige forklaring. Spawn 3-5 teammates, lad dem unders\u00f8ge forskellige hypoteser og debattere baseret p\u00e5 evidens.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Multi-modul feature-arbejde<\/h3>\n\n\n\n<p>Sp\u00e6nder over frontend, backend og tests. Hver teammate ejer et lag. Ingen filkonflikter. Backend-agent f\u00e6rdigg\u00f8r API \u2192 test-agent begynder automatisk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Agent Teams vs. Sub-agents: Hvorn\u00e5r bruger du hvad?<\/h2>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th><\/th><th>Sub-agents<\/th><th>Agent Teams<\/th><\/tr><\/thead><tbody><tr><td><strong>Kommunikation<\/strong><\/td><td>Rapporterer kun til caller<\/td><td>Teammates kommunikerer direkte<\/td><\/tr><tr><td><strong>Koordination<\/strong><\/td><td>Main agent styrer alt<\/td><td>Delt opgaveliste, selvkoordinering<\/td><\/tr><tr><td><strong>Token-forbrug<\/strong><\/td><td>Lavere<\/td><td>~5x per teammate<\/td><\/tr><tr><td><strong>Bedst til<\/strong><\/td><td>Fokuserede, isolerede opgaver<\/td><td>Komplekst arbejde der kr\u00e6ver diskussion<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Tommelfingerregel:<\/strong> Brug sub-agents n\u00e5r du bare har brug for resultatet. Brug Agent Teams n\u00e5r processen og dialogen mellem agenter giver v\u00e6rdi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Begr\u00e6nsninger og gotchas<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ingen session-genoptagelse: Lukker du terminalen, mister du teamet<\/li>\n\n\n\n<li>Ingen nestede teams: Et team kan ikke spawne et underteam<\/li>\n\n\n\n<li>Filkonflikter: To teammates, der redigerer samme fil = overskrivninger. Struktur\u00e9r arbejdet s\u00e5 hver teammate ejer forskellige filer<\/li>\n\n\n\n<li>Token-forbrug: Hold \u00f8je med omkostningerne. Start med code review (read-only) f\u00f8r du kaster dig ud i parallelle refaktoringer<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Det st\u00f8rre billede<\/h2>\n\n\n\n<p>Agent Teams er ikke bare en Claude Code-feature. Det er et signal om, hvor AI-assisteret udvikling er p\u00e5 vej hen. Vi bev\u00e6ger os fra &#8220;\u00e9n AI, der hj\u00e6lper \u00e9n udvikler&#8221; til &#8220;et team af AI-agenter, der selv-organiserer sig omkring en opgave.&#8221;<\/p>\n\n\n\n<p>GitHub Agent HQ, lanceret 11. februar, tager konceptet endnu videre: Claude Code, OpenAI Codex og GitHub Copilot k\u00f8rer parallelt og leverer draft-PRs i dit eksisterende review-flow.<\/p>\n\n\n\n<p>Vi er ikke l\u00e6ngere i &#8220;vibe coding&#8221;-\u00e6raen. Anthropic kalder det &#8220;vibe working&#8221; \u2014 AI, der h\u00e5ndterer professionelt arbejde, ikke bare kodning.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><strong>Kilder:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[Bytebot: Claude Sonnet 5 vs Opus 4.6 Developer Guide](https:\/\/bytebot.io\/articles\/claude-sonnet-5-developer-guide)<\/li>\n\n\n\n<li>[Marc0.dev: Claude Code Agent Teams Setup Guide](https:\/\/www.marc0.dev\/en\/blog\/claude-code-agent-teams-multiple-ai-agents-working-in-parallel-setup-guide-1770317684454)<\/li>\n\n\n\n<li>[Paddo.dev: Claude Code&#8217;s Hidden Multi-Agent System](https:\/\/paddo.dev\/blog\/claude-code-hidden-swarm\/)<\/li>\n\n\n\n<li>[Gaga.art: Claude Code 5 \u2014 AI Dev Team](https:\/\/gaga.art\/blog\/claude-code-5\/)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Fra solo-agent til dev team: Claude Codes nye Agent Teams \u00e6ndrer spillereglerne for multi-agent softwareudvikling.<\/p>\n","protected":false},"author":1,"featured_media":383,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[24],"tags":[23],"class_list":["post-382","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agentic-engineering","tag-claudecode"],"acf":[],"_links":{"self":[{"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/posts\/382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/comments?post=382"}],"version-history":[{"count":12,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/posts\/382\/revisions"}],"predecessor-version":[{"id":1058,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/posts\/382\/revisions\/1058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/media\/383"}],"wp:attachment":[{"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/media?parent=382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/categories?post=382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vittrup-graversen.dk\/index.php\/wp-json\/wp\/v2\/tags?post=382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}