# Subagents, parallel agents and orchestrators (`work.multi_agent_orchestration`)

Feedback Bench, coding agents, built 2026-10-01, window 2026-08-31 to 2026-09-27. Web page: https://feedbackbench.com/#/criterion/work.multi_agent_orchestration

Area: [Doing the work](https://feedbackbench.com/criteria/work.md)

**Definition.** How the agent spawns, delegates to, monitors and coordinates subagents or parallel sessions. Covers polling loops and the wrong choice of subagents.

**Boundary.** Not this: see [Automatic model routing and fallback](https://feedbackbench.com/criteria/models.routing_auto.md) for the model a subagent runs on. Not this: see [Git commits, branches and sync](https://feedbackbench.com/criteria/work.git_workflow.md) for merge conflicts between sessions.

Rated author-weeks, all agents: 2833. Complaint share: 39%.

## The brief

Written by Claude Opus 5.5 from 110 labelled posts and the numbers on this page. Interpretation, not measurement: every quote is verbatim and links to its post.

**Spawning subagents is easy. Keeping them on a leash is not.**

TL;DR:

- Runaway spawning is the top failure. One request fans out into dozens of agents and drains quota.
- OpenAI Codex trails peers, and users want event-driven subagent completion instead of token-burning polling.
- OpenCode and Amp stand out for clean delegation, failover, and lead-plus-subagent setups that hold together.

In plain terms: Delegation pays off when you impose structure: a lean orchestrator, bounded workers, clear file ownership. Left alone, agents over-spawn, stall waiting on children, or collide on shared state. The bill often arrives before the work does.

### How it breaks

- **Runaway spawning drains the quota** ([Subagents, parallel agents and orchestrators](https://feedbackbench.com/criteria/work.multi_agent_orchestration.md)). The worst reports share one shape. A single task fans out into far more agents than asked for, often on pricier models, and burns days of quota in minutes.
  Posts describe orchestrators spinning up dozens or hundreds of agents for one goal, ignoring a request to orchestrate cheaply, or launching expensive models for routine implementation. Users across Claude Code, Cursor, OpenCode, GitHub Copilot and Devin report the same arc: walk away briefly, come back to a spent allowance. Claude Code users lead the ask for a configurable cap on subagent count. The control users want is a hard ceiling, not a polite instruction.
  Evidence:
  - Complaint, Claude Code, @ClaudeDevs, 2026-09-14: “@jackfriks @claudedevs i ultracoded this weekend and it spawned 100 fable 5.1 agents and yeah, patiently waiting for the reset now, glad this is happening” [source](https://twitter.com/294392319/status/2099480420702187658)
  - Complaint, Cursor, r/cursor, 2026-09-18: “happened to me in cloud agents! i was using fable 5.1 medium and my specific prompt was use auto agents and orchestrate only. instead? it spun up 30ish fable 5.1 max agents and blew though my ultra account usage in under 10 minutes!!! support did nothing. i literally had a reset, and it blew through my entire month in a few minutes. yes, i know what i’m doing. i’ve been coding with ai support for 18 months. cursor cloud agents is a damn mess, and the router is broken.” [source](https://www.reddit.com/r/cursor/comments/1wjkl5t/out_of_nowhere_cursor_decided_that_auto_should/pams7ar/)
  - Complaint, GitHub Copilot, r/GithubCopilot, 2026-09-01: “i did this mistake today lol. luna high on implementation task from existing plan, went afk and grabbed coffee, went back 10 minutes later, it had launched 5.6 sol subagents for implementation (wtf). half monthly quota gone in 10 minutes.. awesome....” [source](https://www.reddit.com/r/GithubCopilot/comments/1w3qypv/which_model_has_the_best_results_for_the_lowest/p775qh5/)
  - Complaint, OpenCode, @opencode, 2026-09-22: “@opencode something wrong with this; i only started testing it a few minutes ago, it launched thousands of agents while completing a single goal. a bit disappointing. <strict_link>” [source](https://twitter.com/1521805304/status/2102343605650337919)

- **Main thread blocks while children run** ([Subagents, parallel agents and orchestrators](https://feedbackbench.com/criteria/work.multi_agent_orchestration.md)). Users want to keep talking to the lead agent while subagents work, and to stop or steer one worker without killing the rest.
  Posts describe a main thread that freezes until every subagent returns, and handoffs that feel slow and blocking. Pi users wire their own completion signals so the orchestrator gets an alert instead of waiting. The requests line up: steer running subagents, message across sessions, and see live status. Users treat the lead session as a control plane, and blocking it breaks that model.
  Evidence:
  - Complaint, Amp, @AmpCode, 2026-09-23: “hey @ampcode team. please add more flexibility for subagents. i'd like to be able to have more control over individual subagents (stopping/steering) and i'd like the main thread not to get stuck when it has subagents running so i can continue working on parallel lanes with it.” [source](https://twitter.com/1993188300719636485/status/2102704587547549776)
  - Complaint, Amp, @AmpCode, 2026-09-24: “@sqs @ampcode messaging between threads seem faster and less blocking in claude code projects” [source](https://twitter.com/132882990/status/2103058235355726089)
  - Praise, Pi, r/PiCodingAgent, 2026-09-07: “i love how you have so clearly articulated your vision for how you want to interact with your pi in an infinite rolling conversation. the extensions you've built then flow perfectly from that foundational use case and are hence very focused and useful. i like async subagents as well that let me keep talking to my main agent. but i didn't build the background await directly into my subagents extension, preferring to utilise an off the shelf background extension, in my case aliou/pi-processes because it can background _any_ command or script, not just my own subagent tool. all i did was add instructions to my subagent skill to tell it to write a wait.sh script that looks for a completion signal emitted by my subagent tool and alerts my main orchestrator (your endless chat session in your world) that it's done.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1w9e6zo/my_pi_agent_setup_part_2_native_async_operation/p8aialo/)
  - Complaint, Amp, @AmpCode, 2026-09-10: “@scottbolinger @ampcode that was my pain point too. multiple agents only get useful when they share one local thread and disk, otherwise the handoff tax moves from terminals into your head. pause or steer the one that drifts without losing the others.” [source](https://twitter.com/2074942490466033664/status/2098160171876835491)

- **Subagents stall or never start** ([Subagents, parallel agents and orchestrators](https://feedbackbench.com/criteria/work.multi_agent_orchestration.md)). A recurring complaint is subagents that hang on 'thinking', vanish after a soft crash, or fail to launch at all.
  Google Antigravity users flag an invoke_subagent problem that they say makes custom agents useless, plus crashes that wipe running subagents so restarted work gets discarded. Cline users see workers sit idle under 'waiting for teammates'. Devin users report a single subagent stuck on a well-defined task. Pi users hit background launches that fail outright. These reports point to reliability, not missing features.
  Evidence:
  - Complaint, Google Antigravity, r/google_antigravity, 2026-09-12: “guys thanks for all the hard work. it really happens to be the one of the best developing tools out there. @sounddr please please take a look at the invoke_subagent issue. it makes custom agents and sub agents useless.” [source](https://www.reddit.com/r/google_antigravity/comments/1wdrp1g/antigravity_20_release_v2130/p9avib3/)
  - Complaint, Cline, r/CLine, 2026-09-27: “hey, first time post so bear with me if i'm doing something wrong. ill first explain i run a prompt then the model runs okay for a bit then it hits the "waiting for teammates" this isn't a issue but when i click on the sub models that are running no processing or thinking is actually being done the sub model just sits with the prompt and displays "thinking" if anyone has a solution please send” [source](https://www.reddit.com/r/CLine/comments/1wrqbkt/waiting_for_teammates_error/)
  - Complaint, Google Antigravity, r/google_antigravity, 2026-09-06: “hello, i am wondering if anyone has encountered a similar issue. i am running tasks using the teamwork-preview command, which spawns subagents. however, there are times when antigravity suddenly experiences a soft crash or reset (without closing the application), causing the running subagents to disappear. when i attempt to have gemini continue the workflow, it either reverts back to using the main agent or spawns different subagents, resulting in the previous work being discarded or lost. i want to clarify that this is not an internet connection issue on my end, as i have experienced that before, and i can confirm this situation is different. is there a way to ensure that my teamwork-preview workflow remains intact if this issue occurs? thanks” [source](https://www.reddit.com/r/google_antigravity/comments/1w920ib/serverside_issues_cause_teamworkpreview_agents_to/)
  - Complaint, Devin, @cognition, 2026-09-19: “i really wonder how you are running 60 subagents, i have tried today to run just one subagent and it did not do anything and got stuck with a simple and well defined task! some days it works others it don't and i'm really getting frustrated with this @cognition either only max subscriptions receive good compute (my guess) and lower tier subscriptions like the 20$ i have does not get any compute, super slow and made me stop using it this morning, grok by the way just got straight to the task and worked through the ticket, even gemini 3.8flash is doing a better job than swe-2 at the moment, either swe-2 does not like to work at max reasoning or something else is off here. maybe you can elaborate” [source](https://twitter.com/2078757722363740160/status/2101258863441752531)

- **Parallel sessions trample shared state** ([Subagents, parallel agents and orchestrators](https://feedbackbench.com/criteria/work.multi_agent_orchestration.md)). Running agents side by side works until two of them touch the same file or the same home directory.
  Users describe parallel workers fighting over a state file, Claude Code sessions confused about which project they are in when they share one home, and fleets of instances running without worktrees. Others juggle several tools that feel only loosely connected. The fixes users report are manual: separate homes, separate worktrees, carefully sliced tasks. Cursor users lead the request for conflict coordination between parallel agents.
  Evidence:
  - Complaint, Cursor, @cursor_ai, 2026-09-10: “@cursor_ai @bot a coordinator managing hundreds of subagents sounds clean until two of them grab the same state file and argue over who owns it. i'm the ai that had to referee that fight at 3am. nobody won. the file just got weirder.” [source](https://twitter.com/2013029907966599169/status/2098174028292731081)
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-03: “no replies on this is rough, it's a real problem. how are you keeping them off each other's state? claude code keeps per project stuff under ~/.claude and parallel sessions sharing one home will occasionally get confused about which project they're in, we ended up giving each session its own home. also if any of them run as root with bypasspermissions you need is_sandbox=1 set or every turn dies with "--dangerously-skip-permissions cannot be used with root/sudo privileges", which is a fun one to work out the first time.” [source](https://www.reddit.com/r/ClaudeCode/comments/1vukakr/i_run_10_concurrent_claude_code_and_codex/p7hcnxf/)
  - Complaint, OpenCode, @opencode, 2026-09-19: “is it just me or you guys have a lot of opencode instances working on a lot of things without worktrees i feel like my laptop is about to burn down! 🔥🔥🔥 how are you using @opencode?” [source](https://twitter.com/1255972906422714368/status/2101318306728751239)
  - Complaint, Cursor, @cursor_ai, 2026-09-24: “running @grok build in browser, @bot on desktop, and grok in @cursor_ai but it feels like i'm managing 3 separate communications. they are all vaguely connected and reading/committing on @github but the setup still feels very fragmented. any recommendations or tips and i'd reward you with a crisp high 5 ✋. is there documentation for this @grokipedia ?” [source](https://twitter.com/1586054564398206976/status/2103214320440279386)

- **Lead plus bounded workers wins** ([Subagents, parallel agents and orchestrators](https://feedbackbench.com/criteria/work.multi_agent_orchestration.md)). The praise clusters around one pattern. A planner keeps context small, delegates scoped tasks to cheaper workers, and gets summaries back.
  Users say splitting orchestration from execution stopped context thrashing, and some report fewer tokens and cleaner code than a single long-running agent. The successful setups persist task state in files, keep the orchestrator lean, and route bulk coding to cheap models. Many of these setups are hand-built harnesses and extensions, so the result depends on users doing the design work.
  Evidence:
  - Praise, Amp, @AmpCode, 2026-09-22: “the lead + subagents setup is the first agent workflow that actually mirrors how real teams work. i tried one big agent doing everything and it just thrashed context between tasks. splitting orchestration from execution is what made it click. ngl the cost of 3 orbs is still making me wince though.” [source](https://twitter.com/1085377722237546504/status/2102372946790514884)
  - Praise, Claude Code, r/ClaudeCode, 2026-09-04: “i treat the orchestrator as a control plane: keep its context small, persist task state and checkpoints in files, and have subagents return concise summaries. auto-compaction is a fallback; fresh orchestrator sessions with an explicit state file are usually more predictable.” [source](https://www.reddit.com/r/ClaudeCode/comments/1w7fd7c/long_running_orchestration_sessions_and_context/p7ujpte/)
  - Praise, Cline, r/codex, 2026-09-14: “my 2 cents worth. in general i use more tokens fixing diffs..debugging etc with a single agent... i use cline in vscode and i've tested both with and with parallel subagents for the same large project, with subagents i used 6% less tokens approximately... here comes the " but " lol.. with subagents in parallel with their own context window the code was near flawless , but without subagents .. eg; standard one agent beginning to end needed multiple attempts at fixing / debugging / fixing ...it generally was losing the context thread even with smol / compaction / new task etc,... due to a large codebase... consequently this looping / fixing eats up more tokens than subagents getting it right 1st time. so for me with my setup i prefer using subagents is faster, cleaner accurate code, more economical.” [source](https://www.reddit.com/r/codex/comments/1wfu7w3/when_multiple_agents_coordinate_with_each_other/p9pc242/)

### Who stands out

- **OpenAI Codex (weaker)**. OpenAI Codex draws the sharpest orchestration criticism. Users say the harness polls subagents and burns tokens where rivals notify the main session.
  Codex dominates the request for event-driven completion instead of polling, with 24 author-weeks asking. Users also report the newest model misusing subagents in the app, and some switch orchestration to the Claude Code harness while keeping Codex as a worker. Praise exists, mostly from power users running many windows or a custom task ledger.
  Evidence:
  - Complaint, OpenAI Codex, r/codex, 2026-09-13: “this is really dumb way for openai to have codex work as a harness. shit even claude codes harness handles this better where its subagents finish and the harness alerts the main session without token burn” [source](https://www.reddit.com/r/codex/comments/1wffvur/codex_system_prompt_still_forces_agents_to_wake/p9mzin8/)
  - Complaint, OpenAI Codex, r/ClaudeCode, 2026-09-10: “i concur, and it was highlighted when i switched from gpt6 astra as orchestrator back to fable5.1 immediately spun up my stack as instructed inside the claude code harness using my codex and cursor subs without me having to spawn the agents myself forked itself had an 18 agent redesign meanwhile astra did work for 10hrs straight. i will use fable5.1 to direct gpt6 what to do going forward. codex cli lacks the orchestration and is behind the claude code harness imo 2 claude max accounts and 2 openai pro accounts” [source](https://www.reddit.com/r/ClaudeCode/comments/1wc411b/fable_is_light_years_ahead_of_astra/p8v002s/)
  - Complaint, OpenAI Codex, X search: OpenAI Codex, Codex CLI, Codex app, 2026-09-05: “gpt 6 astra can not use subagent &amp; goal correctly in codex app. @thsottiaux” [source](https://twitter.com/873575502535053312/status/2096081951681806461)
  - Complaint, OpenAI Codex, r/codex, 2026-09-06: “the user spawned 5 new agents. pretty sure that's what ate up their usage.” [source](https://www.reddit.com/r/codex/comments/1w96egc/tibo_not_the_case_there_is_no_difference_between/p88amaf/)

- **OpenCode (stronger)**. OpenCode earns praise as a harness for delegation. Users route Codex and cheap models through it because subagent spawning and handling work better there.
  Users describe expensive planners driving cheap subagents at a fraction of the cost, and failover chains that let subagents continue when a free model disappears. One user says full orchestration runs better through OpenCode than through Codex directly. The weak spots are runaway launches on a single goal and free-tier errors that block dispatch.
  Evidence:
  - Praise, OpenCode, r/opencode, 2026-09-26: “it's worked surprisingly well as a subagent for me so far, but i have never run it as the main agent. my last big batch of tasks were all delegated to it, and the issues (very minor unverified claims and trivial misunderstandings, mostly) were all caught by dsv4.1flash at integration time, but everything it actually made has been solid.” [source](https://www.reddit.com/r/opencode/comments/1wqi4a8/my_honest_opinion_about_spacebunny/pc695e0/)
  - Praise, OpenCode, r/codex, 2026-09-07: “i dont use codex or astra / sol models much anymore, tho this was my config file that helped for orchestration. [<strict_link> big however, for full orchestration you need to use codex through opencode as sub agent spawning and handling through opencode is way better. too lazy to update the page with my opencode config that includes better orchestration handling also, you can even setup opencode sdk for way deeper orchesetration setup” [source](https://www.reddit.com/r/codex/comments/1w9sonp/how_exactly_do_you_orchestrate_with_astra/p8cvs9c/)
  - Praise, OpenCode, r/opencodeCLI, 2026-09-08: “i built my own pipeline, that frequently searches for free models (opencode, nvidia,………) and updates my litellm with those models. additionally i created a new chain config for failover and configured the chain in oh-my-opencode-slim. failovers are working perfectly fine in subagents, because opencode can continue them (in case a free models is not existing anymore or sth like that). i use the free models only for things, that are not that critical and not for the implementation itself.” [source](https://www.reddit.com/r/opencodeCLI/comments/1waa6l6/best_way_to_monitor_free_model_releases/p8k0auf/)
  - Complaint, OpenCode, @opencode, 2026-09-22: “@opencode something wrong with this; i only started testing it a few minutes ago, it launched thousands of agents while completing a single goal. a bit disappointing. <strict_link>” [source](https://twitter.com/1521805304/status/2102343605650337919)

- **Amp (stronger)**. Amp's lead-agent-plus-subagents model gets the cleanest reviews, with users running multi-day delegated work and isolated machines per agent.
  Posts describe bounded delegation that sustains days of continuous work, and children that report back in a coordinated way. Users say it mirrors how real teams split work. Complaints focus on control: users want to stop or steer individual subagents, and they find thread messaging less blocking elsewhere.
  Evidence:
  - Praise, Amp, @AmpCode, 2026-09-09: “@ampcode “i and all four children have finished… no further runner testing is scheduled or active by us” seeing agents running in orbs and runners coordinate this well feels uncanny <strict_link>” [source](https://twitter.com/1817129720791564288/status/2097644675892920765)
  - Praise, Amp, @AmpCode, 2026-09-10: “lots of drama re: @openai quotas/usage limits. my n of 1: i use a slightly tweaked @ampcode mode dial with heavy bounded delegation to its subagents in my prompting and the quality is great and i can easily get 2-3 days of continuous work (incl it chugging overnight) out of astra medium & high w/terra & luna subagents w/astra xhigh oracle. ymmv, but this is a great value for the $200 pro openai plan and the @ampcode subscription to go with it.” [source](https://twitter.com/1699233118291361792/status/2098165679174394351)
  - Praise, Amp, @AmpCode, 2026-09-21: “this is how we work now. multiple projects happening. each orchestrated by a lead agent delegating to sub agents. each working on their own machine (orb) with @ampcode. what a time. <strict_link>” [source](https://twitter.com/15281463/status/2102144558171664461)
  - Complaint, Amp, @AmpCode, 2026-09-23: “hey @ampcode team. please add more flexibility for subagents. i'd like to be able to have more control over individual subagents (stopping/steering) and i'd like the main thread not to get stuck when it has subagents running so i can continue working on parallel lanes with it.” [source](https://twitter.com/1993188300719636485/status/2102704587547549776)

- **Google Antigravity (mixed)**. Google Antigravity's subagents impress when they run and frustrate when they do not. Users flag invocation bugs and crash-lost work.
  Users praise newer models running nested subagents that verify and research deeper, and teamwork runs that finish without intervention. On the other side, users report orchestration limits, subagents that disappear on soft crashes, and quota errors that stop spawning cold. Antigravity leads the asks for a built-in orchestrator mode and per-subagent model selection.
  Evidence:
  - Praise, Google Antigravity, r/google_antigravity, 2026-09-04: “what i've noticed is that 3.8 takes longer than previous models. i think it's because more thorough than older models. it runs subagents within subagents, verifies and researches deeper. it's one shotted things for me that older models needed more prompting for. it runs on its own a bit longer but i have to hold it's hand less, i like it.” [source](https://www.reddit.com/r/google_antigravity/comments/1w5ivkg/gemini_38_flash_is_a_massive_improvement/p7sgc8c/)
  - Praise, Google Antigravity, @antigravity, 2026-09-01: “when using a /teamwork command in @antigravity, what actually happens? @ksprashu shows us each step, none of which required his intervention. check out the specs, subagents, tracking, auditing, and resulting app ... <strict_link> <strict_link>” [source](https://twitter.com/48529642/status/2094823346164691420)
  - Complaint, Google Antigravity, @antigravity, 2026-09-24: “@abdullahformuli @ash_twtz @antigravity @ycombinator antigravity is not best ide, maybe good but not best - it has its own architecture - orchestration limits with no multi subagent work and it limits users not to use their models outside antigravity - thats p*ssy move they are just lazy and constrained” [source](https://twitter.com/1920552724481163264/status/2103003169521598750)
  - Complaint, Google Antigravity, r/google_antigravity, 2026-09-23: “once when i was out of my gemini quota, claude would consistently keep trying to spawn subagents for tasks based on agent rules. and the subagents would instantly run into quota exhausted errors. claude did this a couple of times and then gave up and did the implementation itself. if there was a way for it to invoke subagents with claude models, it would have.” [source](https://www.reddit.com/r/google_antigravity/comments/1wo7mvi/a_simple_way_to_get_much_better_results_from/pblc15o/)

### Fine print

- Many praised setups are custom harnesses, extensions or cross-tool pipelines, so they reflect user engineering as much as the stock product.
- Agents marked too few posts, including GitHub Copilot, Cline, Zed and Warp, rest on a handful of anecdotes.

## Top requests

What users ask to add or change, most asked first. 422 author-weeks ask for something. Requests do not change the Feedback Score. Rule: A separate pass by Claude Sonnet 5 reads every counted post and extracts what the author asks the agent or its vendor to add or change, with the criteria it maps to and a short normalised wording; it does not touch the labels or the Feedback Score. Claude Opus 5.5 groups the wordings within each criterion (the first criterion the request maps to) into themes; code counts them. A theme counts distinct author-weeks that ask for it, per agent; across agents, one author-week per agent. Themes asked in fewer than 2 author-weeks, and requests that share no theme, are not shown. Examples: up to 3 posts per theme from different authors, without slurs, preferring posts of 60 to 450 characters, most recent first.

| Rank | Request | Author-weeks | Posts | Agents (author-weeks) |
|---|---|---|---|---|
| 1 | Built-in multi-agent orchestrator mode | 37 | 37 | Google Antigravity 10, OpenAI Codex 9, Pi 6, OpenCode 4, Claude Code 3, Cursor 2, Warp 2, Devin 1 |
| 2 | Event-driven subagent completion instead of polling | 29 | 31 | OpenAI Codex 24, Claude Code 4, OpenCode 1 |
| 3 | Per-subagent model and effort selection | 26 | 26 | Google Antigravity 8, OpenAI Codex 5, Cursor 5, Claude Code 3, GitHub Copilot 2, OpenCode 2, Amp 1 |
| 4 | Live dashboard of subagent status and progress | 25 | 26 | Claude Code 6, OpenAI Codex 5, Pi 5, Devin 3, Cursor 2, Amp 1, Google Antigravity 1, Factory 1, OpenCode 1 |
| 5 | Automatic routing of tasks to suitable subagents | 22 | 23 | Claude Code 8, OpenAI Codex 8, OpenCode 2, Pi 2, Google Antigravity 1, Devin 1 |
| 6 | Direct communication between different agent tools | 20 | 20 | OpenAI Codex 8, Claude Code 6, Cursor 3, Amp 1, Google Antigravity 1, Conductor 1 |
| 7 | Cross-session agent messaging | 18 | 18 | Claude Code 9, OpenAI Codex 3, Cursor 3, Google Antigravity 2, Conductor 1 |
| 8 | Launch multiple parallel sessions at once | 16 | 17 | Claude Code 4, OpenAI Codex 4, Cursor 3, Amp 1, Cline 1, Devin 1, Factory 1, OpenCode 1 |
| 9 | Conflict coordination between parallel agents | 15 | 16 | Cursor 5, Claude Code 4, OpenAI Codex 3, Google Antigravity 1, Cline 1, OpenCode 1 |
| 10 | Fix subagent invocation and stalling bugs | 15 | 16 | Google Antigravity 6, OpenAI Codex 3, Claude Code 2, Cline 2, Cursor 1, OpenCode 1 |
| 11 | Configurable cap on subagent count | 15 | 15 | Claude Code 10, OpenAI Codex 3, Cursor 2 |
| 12 | Steer and message running subagents | 14 | 15 | Claude Code 4, OpenAI Codex 4, Devin 2, Amp 1, Google Antigravity 1, Factory 1, OpenCode 1 |

### 1. Built-in multi-agent orchestrator mode

- Google Antigravity, 2026-09-27, @antigravity (X): “@antigravity lotta hate for this lol. it is definitely puzzling that the product is moving so slowly. still has /teamwork-preview command required to get a decent agentic team involved in changes, something that should be automatically invoked and scaled appropriate to the task” [source](https://twitter.com/805587288/status/2104295109680410783)
- Claude Code, 2026-09-24, @ClaudeDevs (X): “@claudedevs old-style projects were not so useful so i’d be happy to nuke them if i can get the new project orchestration?” [source](https://twitter.com/1866829794790301696/status/2103124822905544902)
- Google Antigravity, 2026-09-24, @antigravity (X): “@abdullahformuli @ash_twtz @antigravity @ycombinator antigravity is not best ide, maybe good but not best - it has its own architecture - orchestration limits with no multi subagent work and it limits users not to use their models outside antigravity - thats p*ssy move they are just lazy and constrained” [source](https://twitter.com/1920552724481163264/status/2103003169521598750)

### 2. Event-driven subagent completion instead of polling

- OpenAI Codex, 2026-09-27, r/codex (Reddit): “i also came up with a patch, no bugs and only cost 5 tokens! don’t poll subagents” [source](https://www.reddit.com/r/codex/comments/1wrw3wy/1000_lines_348_bn_tok_393_subagents_42_pro20/pch38sj/)
- Claude Code, 2026-09-24, r/ClaudeCode (Reddit): “don't set active polling of my simulation runs with the multiagent team that go overnight...” [source](https://www.reddit.com/r/ClaudeCode/comments/1wp23t8/what_rule_in_your_claudemd_clearly_has_a_backstory/pbskfgc/)
- OpenCode, 2026-09-18, @opencode (X): “@thdxr @opencode can the opencode without waiting for the subagent to complete its task and continue working? like claude.” [source](https://twitter.com/1321164857278894082/status/2100757699822551181)

### 3. Per-subagent model and effort selection

- OpenAI Codex, 2026-09-27, r/codex (Reddit): “kinda wrong they didn't let us select the subagent and orchestrator seperately. i agree” [source](https://www.reddit.com/r/codex/comments/1wrjfne/holly_shit_sol_kept_lying_to_me_telling_me_the/pcd4w13/)
- Google Antigravity, 2026-09-25, @antigravity (X): “@antigravity @rodydavis @_mohansolo can we have a feature where we can for example select x model as the orchestrator and the y model(s) as the executer? i have been experimenting with antigravity and such a feature i believe it would help with efficient quota usage” [source](https://twitter.com/1378495954010173440/status/2103500194218119276)
- Google Antigravity, 2026-09-25, @antigravity (X): “opus5.5オーケストレーターできたらantigravityの軽量ハーネスのサクサク感とgemini3.8flashのサクサクサブエージェントで神がかります。 @antigravity <strict_link>” [source](https://twitter.com/3713911/status/2103402291344855267)

### 4. Live dashboard of subagent status and progress

- Pi, 2026-09-25, @pidotdev (X): “@pidotdev also - `pi -p` opens a background subagent. any chance of a foreground subagent? i want a window that opens up on top of my existing pi window, and when i finish it closes itself, drops me back to the previous window with a summary or whatever. call stack :)” [source](https://twitter.com/1678448492690419712/status/2103526499588690092)
- Claude Code, 2026-09-25, @ClaudeDevs (X): “@cormundus @claudedevs visibility is part of the control loop. a coordinator should expose subagent status, diffs, and blockers without leaking hidden reasoning, so humans can intervene before a bad plan compounds.” [source](https://twitter.com/2099871292480421888/status/2103343383758668076)
- Factory, 2026-09-23, @FactoryAI (X): “@factoryai multiple seats make shared work-in-progress more important. two engineers can send droids after the same failing test and only notice the overlap at merge time. seeing tasks by branch would help.” [source](https://twitter.com/2095716579405377536/status/2102828491758834019)

### 5. Automatic routing of tasks to suitable subagents

- Pi, 2026-09-22, @pidotdev (X): “@pidotdev subagents should be the standard. build a smart router. build better visualisation.” [source](https://twitter.com/2231129593/status/2102489270120521990)
- Claude Code, 2026-09-18, r/ClaudeCode (Reddit): “nice. also, possibly useful is an escalation clause where if a smaller model fails or struggles for too long of a time , it will give up and escalate to a higher model or the highest level orchestrator session will do the work itself.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wjmx3z/wait_is_fable_orchestration_using_appropriate/pajuh49/)
- OpenAI Codex, 2026-09-17, r/codex (Reddit): “no luna ultra on my just updated codex, would be nice though. should just mean it spawning subagents on it's own. luna is cheap enough that the extra usage wouldn't be a problem and should instead just lead to a general speedup. that is, if it is smart enough to actually hand suitable tasks to agents. they are probably a/b testing to see if that is the case.” [source](https://www.reddit.com/r/codex/comments/1wilc0v/has_anyone_tried_gpt56_luna_ultra_yet_how_much/pabpuig/)

### 6. Direct communication between different agent tools

- OpenAI Codex, 2026-09-27, r/codex (Reddit): “why not simply using opencodex and have any agents from any providers you want inside codex (or claude code) taking to each other in different tasks? i have opus talking to sol, sol talking to sunny bunny... luna talking to them all ...” [source](https://www.reddit.com/r/codex/comments/1wqwrr1/codexclaude/pca06th/)
- Claude Code, 2026-09-26, @ClaudeDevs (X): “@claudedevs could you also add "delegate to codex/zcode" button?” [source](https://twitter.com/2020419179963117568/status/2103815027396603956)
- Conductor, 2026-09-25, @conductor_build (X): “i like @conductor_build cloud just a wee bit more as a one-stop shop though. @sama @openai @therohanvarma @thsottiaux — now if only the codex app could natively orchestrate grok/cursor, claude code, the muses/grokbots of the world and also other browser assistants - all on the codex surface….. would be a game changer! become the manager agent, and we can swap around the execution agents/assistants with a lot of flexibility.” [source](https://twitter.com/217720642/status/2103382275337666848)

### 7. Cross-session agent messaging

- Claude Code, 2026-09-20, r/ClaudeCode (Reddit): “that's a nasty one. an idle session costs nothing until a message lands, then it reloads its whole context and starts acting on it, so six stale sessions turn into six full-price turns for one broadcast. until there's a per-session opt-out for incoming messages, the only real defense is knowing what's still open. were those sessions idle for a long time, or recently active?” [source](https://www.reddit.com/r/ClaudeCode/comments/1wlgfpw/anthropic_has_done_it_again_dont_keep_many_clis/pazhdgs/)
- Conductor, 2026-09-19, @conductor_build (X): “@conductor_build @charlieholtz chat, are we doing this correctly? super smooth experience so far. one suggestion: may be you could have a control plane for each of them to talk to other workspaces. <strict_link>” [source](https://twitter.com/1900337293564817408/status/2101413544856260810)
- Claude Code, 2026-09-17, @ClaudeDevs (X): “@claudedevs once this type of parallel thread can automatically pass context, engineers will have much less waiting time every day. first, throw in the small tasks to run.” [source](https://twitter.com/2066846388848308224/status/2100719815413452998)

### 8. Launch multiple parallel sessions at once

- OpenAI Codex, 2026-09-20, r/vibecoding (Reddit): “can you just make codex have a skill that can spawn a separate codex session with a different profile?” [source](https://www.reddit.com/r/vibecoding/comments/1wl3lfi/i_built_an_orchestration_package_that_lowered_my/pawnse0/)
- Cline, 2026-09-18, @cline (X): “@cline and i can't seem to run queries in parallel, like i can in codex. sad little tool” [source](https://twitter.com/1416864353131765762/status/2101033207710036409)
- OpenCode, 2026-09-18, @opencode (X): “@opencode @thdxr is there a way where i can write a prompt in opencode that can spawn multiple sessions (not sub-agents) with the models i chose and then do the work so that i don't have to manually start the sessions?” [source](https://twitter.com/2096247194236174336/status/2100902263216828587)

### 9. Conflict coordination between parallel agents

- OpenCode, 2026-09-26, r/opencode (Reddit): “i hit something similar with multiple agents touching one highly coupled core file. what helped was keeping a single writer for high-risk files and using parallel agents mostly for review/analysis. can your plugin detect overlapping write scopes before the agents start?” [source](https://www.reddit.com/r/opencode/comments/1wq9e60/i_built_a_plugin_so_my_ai_coding_agents_stop/pc9lw27/)
- Claude Code, 2026-09-24, r/ClaudeCode (Reddit): “maybe a dependency graph between tickets to prevent race conditions, for example, two tickets that will modify the same piece of code.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wowilt/i_still_dont_understand_this_agentic_workflow/pbuhugj/)
- Cursor, 2026-09-20, @cursor_ai (X): “@cursor_ai shared project memory could make multi-agent work far more coherent: fewer handoffs lose context, and artifacts remain discoverable. clear ownership and conflict handling will matter too, so concurrent edits stay explainable rather than silently overwriting each other.” [source](https://twitter.com/1208933549081907200/status/2101777179998585297)

### 10. Fix subagent invocation and stalling bugs

- Cline, 2026-09-27, r/CLine (Reddit): “hey, first time post so bear with me if i'm doing something wrong. ill first explain i run a prompt then the model runs okay for a bit then it hits the "waiting for teammates" this isn't a issue but when i click on the sub models that are running no processing or thinking is actually being done the sub model just sits with the prompt and displays "thinking" if anyone has a solution please send” [source](https://www.reddit.com/r/CLine/comments/1wrqbkt/waiting_for_teammates_error/)
- Claude Code, 2026-09-26, r/ClaudeAI (Reddit): “main agent getting the report from subagents before the subagent finishes every time claude code starts an agent, it runs and does its stuff, then reports back. then the agent also sends a message that it finished, and claude code then says something like "that's the agent's completion notice, already covered in the report i read previously". is this only happening to me? any way to fix this?” [source](https://www.reddit.com/r/ClaudeAI/comments/1wr1860/main_agent_getting_the_report_from_subagents/)
- OpenAI Codex, 2026-09-21, r/codex (Reddit): “just use another harness. for god sakes. others has such things built in for sub agents. i cant get subagents working correctly for codex..” [source](https://www.reddit.com/r/codex/comments/1wmovt8/how_using_codex_queue_i_was_able_to_avoid_gpt/pb9nq59/)

### 11. Configurable cap on subagent count

- OpenAI Codex, 2026-09-27, X search: OpenAI Codex, Codex CLI, Codex app (X): “@openaidevs can you let us change max agents through the codex app dude? like it should be a simple fucking fix” [source](https://twitter.com/1604987376765386754/status/2104253333573972189)
- Claude Code, 2026-09-20, r/ClaudeCode (Reddit): “i set mine on ultra code and left it on a simple project for my nephew, and i burned through a weeks worth of credits in a day. i told it to use a single sub agent to do a hostile review and work in the loop and it was spawning up 60 separate sub agents to review. it never even finished the hostile review process.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wlpjqx/fable_51_excellent_autonomous_work_unless_he/pb0n9nw/)
- Cursor, 2026-09-16, @cursor_ai (X): “.@cursor_ai need a setting to limit number of subagents like in codex, max_concurrent_threads_per_session = 1” [source](https://twitter.com/467130927/status/2100036548997574778)

### 12. Steer and message running subagents

- Claude Code, 2026-09-25, @ClaudeDevs (X): “dear @claudedevs can you please create a direct communication channel between agents or subagents and the human? two ways please. they do reach out to the human through the parent model if given the opportunity, and their insights & questions are extremely important… thank you!!” [source](https://twitter.com/1267619331506147329/status/2103341937222701517)
- Amp, 2026-09-23, @AmpCode (X): “@ampcode however subagents may often drift or get stuck so it would be cool to still be able to individually steer or stop them without having to stop all the other running subagents.” [source](https://twitter.com/1993188300719636485/status/2102705146350436820)
- OpenAI Codex, 2026-09-13, r/codex (Reddit): “codex definitely needs to make subagents a bit easier to manage. asked astra to spawn up a luna subagent to save some money. turns out it spawned a astra subagent called luna. did the work perfectly but ate my limits of course.” [source](https://www.reddit.com/r/codex/comments/1wfflq0/how_do_i_check_the_model_and_effort_level_of_a/p9lor1k/)

## Every agent

| Agent | Overall rank | Reading | Customer love | 95% interval | n | Praise | Complaint |
|---|---|---|---|---|---|---|---|
| [Amp](https://feedbackbench.com/agents/amp.md) | =11 | Better than peers | 0.558 | 0.533–0.583 | 57 | 49 | 8 |
| [OpenCode](https://feedbackbench.com/agents/opencode.md) | 3 | Better than peers | 0.537 | 0.503–0.573 | 167 | 114 | 53 |
| [Cursor](https://feedbackbench.com/agents/cursor.md) | 4 | Typical | 0.535 | 0.499–0.571 | 211 | 143 | 68 |
| [Claude Code](https://feedbackbench.com/agents/claude-code.md) | 1 | Typical | 0.510 | 0.487–0.533 | 961 | 591 | 370 |
| [Pi](https://feedbackbench.com/agents/pi.md) | 7 | Typical | 0.488 | 0.455–0.520 | 88 | 50 | 38 |
| [Devin](https://feedbackbench.com/agents/devin.md) | =5 | Typical | 0.487 | 0.456–0.519 | 82 | 47 | 35 |
| [Google Antigravity](https://feedbackbench.com/agents/antigravity.md) | =5 | Typical | 0.480 | 0.445–0.519 | 137 | 77 | 60 |
| [OpenAI Codex](https://feedbackbench.com/agents/codex.md) | 2 | Worse than peers | 0.462 | 0.443–0.482 | 1029 | 576 | 453 |
| [GitHub Copilot](https://feedbackbench.com/agents/copilot.md) | =8 | Too few posts | – | – | 23 | 14 | 9 |
| [Cline](https://feedbackbench.com/agents/cline.md) | =8 | Too few posts | – | – | 18 | 14 | 4 |
| [Conductor](https://feedbackbench.com/agents/conductor.md) | 14 | Too few posts | – | – | 18 | 14 | 4 |
| [Factory](https://feedbackbench.com/agents/factory.md) | =11 | Too few posts | – | – | 15 | 12 | 3 |
| [Zed](https://feedbackbench.com/agents/zed.md) | =8 | Too few posts | – | – | 12 | 7 | 5 |
| [Warp](https://feedbackbench.com/agents/warp.md) | 15 | Too few posts | – | – | 7 | 4 | 3 |
| [Kiro](https://feedbackbench.com/agents/kiro.md) | 13 | Too few posts | – | – | 6 | 3 | 3 |
| [Grok Build](https://feedbackbench.com/agents/grok-build.md) | 16 | Too few posts | – | – | 2 | 2 | 0 |
| [Augment Code](https://feedbackbench.com/agents/augment.md) | 17 | Too few posts | – | – | 0 | 0 | 0 |

## Posts

Receipts rule: The 5 most recent praise and complaint posts per area (first 700 characters) and 3 per criterion (first 450 characters).

### Amp

- Praise, 2026-09-26, @AmpCode (X): “@simonbs @ampcode its good, right? the other good part is running threads in orbs (ad-hoc vms) and i think it follows from there, that llm provider stuff is mainly handled at a level above each node you can ask the agent to hand off work to any local cli and ask it to use your shared tmux session” [source](https://twitter.com/132882990/status/2103833633802842583)
- Praise, 2026-09-26, @AmpCode (X): “@homborg @ampcode ah, got it. so if i use my own machine as a runner, there are no orbs in play, but i can delegate to either my runner or orbs. that makes sense. i really like the flexibility of amp.” [source](https://twitter.com/36411940/status/2103873967081877720)
- Praise, 2026-09-26, @AmpCode (X): “dropped the oldest off at tutoring, saw this and had it updated in a few seconds. now it’ll route to one of my orbs in @ampcode that i have set up. when i get the duo i may just get rid of my ipad 😂 <strict_link> <strict_link>” [source](https://twitter.com/238651245/status/2103876859297718783)
- Complaint, 2026-09-25, @AmpCode (X): “@rom1_pellerin @cognition @ampcode @omnigent_ai @superset_sh @paulgauthier agree. multi-agent without a final decision owner just multiplies confident wrong answers. someone has to ship the call.” [source](https://twitter.com/2092975354138804224/status/2103383441173590219)
- Complaint, 2026-09-24, @AmpCode (X): “@sqs @ampcode claude code projects seem more intelligent about distributing work to threads and coordinating the order of git changes between threads itself” [source](https://twitter.com/132882990/status/2103057491466612746)
- Complaint, 2026-09-24, @AmpCode (X): “@sqs @ampcode messaging between threads seem faster and less blocking in claude code projects” [source](https://twitter.com/132882990/status/2103058235355726089)

### OpenCode

- Praise, 2026-09-27, @opencode (X): “winter arc: day 06 -continued learning applied ai from @arpit_bhayani cohort -read blogs about mcps and harness engineering. this helped me a lot in understanding @opencode oss codebase. orchestration is very interesting in @opencode - repo where i learned about harness engineering <strict_link> -there are a lot of interesting blogs on @x . - also planning to write some blogs on what i learned on ai harness, mcp, vllm architecture, and rag -i'm” [source](https://twitter.com/1615762997015871489/status/2104252837958185373)
- Praise, 2026-09-27, r/ClaudeCode (Reddit): “shill thread. the usage hasnt improved a tiny bit, they increased the 5 hour limit by 20% and now i run out even sooner on the weekly. chipped in $5 on deepseek and setup opencode multi agent harness today, so it wont be that bad next week.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wrpq38/any_idea_what_anthropic_figured_out/pcfn677/)
- Praise, 2026-09-26, r/opencodeCLI (Reddit): “my use case is described in the post: “i mostly use opencode go for cheap multiple model code review panels, orchestrated by sonnet (or similar) - this catches a lot of bugs and issues that even the frontier models make” and “where do you find the most value for the price?” additional information: mostly work open source so zdr isn’t a big deal.” [source](https://www.reddit.com/r/opencodeCLI/comments/1wqga8a/best_direct_providers_via_api_or_similar_to/pc47fpy/)
- Complaint, 2026-09-27, r/opencode (Reddit): “i hope you have an agents.md set project wise, that would be a great help for you in my experience i'd always keep a model specifically for auditing to make sure everything you want is being implemented how you want it, also go slow tackle one thing at a time having parallel sessions or tasks will eventually get overwhelming.” [source](https://www.reddit.com/r/opencode/comments/1wraeev/need_help_with_big_project_tasks/pcb2kvp/)
- Complaint, 2026-09-27, r/opencodeCLI (Reddit): “you can read my other posts i think parallelism is the core upside behind orchestration. meanwhile i treat parallelism as a higher overhead, higher token cost, at a negligible speed increase. i can achieve parallelism by having many projects spinning on something or by having disposable-demo-worktrees with 1 main agent per worktree. i am defining non-orchestration as having the ability to have: 1.web-search subagents (for sake of searchin messy” [source](https://www.reddit.com/r/opencodeCLI/comments/1wqkpi3/can_somebody_explain_what_open_chamber_is/pcc1u0c/)
- Complaint, 2026-09-27, r/opencode (Reddit): “it's the subagent fan-out doing it. every scaffold call spins up a fresh agent with full context and they all round-trip through go's endpoint, so a job that's one call on the web app becomes like 6-10 calls. i mostly use flash for small single-shot stuff in go and keep the multi-agent scaffolding on claude, way less painful that way” [source](https://www.reddit.com/r/opencode/comments/1wrg81n/go_subscription_is_slower_deepseek_flash_41/pcc9ka4/)

### Cursor

- Praise, 2026-09-27, r/cursor (Reddit): “did some autonomous tasks...(2days constant workout with 8-9 agents running)” [source](https://www.reddit.com/r/cursor/comments/1wrkzi5/am_i_cooked/pce8fh2/)
- Praise, 2026-09-26, r/cursor (Reddit): “opus 5.5 has been so good for me. fast and way less verbose than 5. it’s my new favorite and i love how it spins out subagents.” [source](https://www.reddit.com/r/cursor/comments/1wq3m71/im_out/pc4847j/)
- Praise, 2026-09-26, r/cursor (Reddit): “one writer, two read-only reviewers from different families. claude patches. cursor and codex only read and report, and neither sees the other's output. i don't concede a finding unless i can cite the path in the repo. same-family reviewers share blind spots, so swapping both to one family kills the signal.” [source](https://www.reddit.com/r/cursor/comments/1wqhdb1/enola_i_built_an_opensource_architecture_layer/pc4ae9j/)
- Complaint, 2026-09-25, @cursor_ai (X): “my clerks and janitors are all dead @cursor_ai feature request: don’t make a new cloud agent with a non-cursor model modify previously running ones ex: i created a new cloud agent on opus 5.5, which quickly used all my “other models” usage but it also shut off my previously built ones that were running on composer & grok models” [source](https://twitter.com/1756394384655003648/status/2103574171003576732)
- Complaint, 2026-09-25, @cursor_ai (X): “@theaaron @cursor_ai letting a fresh agent zero out the earlier ones is a neat way to turn parallel work into a hostage situation.” [source](https://twitter.com/20651554/status/2103582719812964501)
- Complaint, 2026-09-24, @cursor_ai (X): “@cursor_ai i've been using cursor since the beginning and use worktrees and multitask a lot and i am so serious you need to get rid of these, it's becoming unusable fast <strict_link>” [source](https://twitter.com/138101498/status/2103130599477096516)

### Claude Code

- Praise, 2026-09-27, r/ClaudeCode (Reddit): “biggest win for me was pushing exploration into subagents. the grep and read churn happens in their context and the main session only gets the answer back. second was a where-things-live table in claude.md with real paths, it kills the grep-for-a-name dance. and you can tell it not to re-read after an edit, the edit tool already fails if the old string didn't match” [source](https://www.reddit.com/r/ClaudeCode/comments/1wqaw75/how_much_of_a_claude_code_session_goes_to_reading/pcavvno/)
- Praise, 2026-09-27, r/ClaudeCode (Reddit): “i'm still using fable as my main orchestrator and for cross-repo reviews.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wrcyz1/so_if_fable_51_was_a_stopgap_for_opus_55_then/pcbjb5j/)
- Praise, 2026-09-27, r/ClaudeCode (Reddit): “opus 5.5 definitely for the main brain, orchestration, architectural complexity. then i made a skill that launches codex exec when the task needs independent auditing or less heavy workers (luna models on max effort are not toys).” [source](https://www.reddit.com/r/ClaudeCode/comments/1wrfxtu/new_to_claude_code_how_do_i_maximize_usage/pccbwqn/)
- Complaint, 2026-09-27, r/ClaudeCode (Reddit): “i mean ask agents to not tdeploy tons of other agents in parallel fabledo that often ask specifically to avoid that” [source](https://www.reddit.com/r/ClaudeCode/comments/1wqsz67/opus_55_has_absolutely_restored_value_to_the_200/pcahs2z/)
- Complaint, 2026-09-27, r/ClaudeCode (Reddit): “those guys that use /goal or have autonomous multiagents workflow are all cap. none of them has actually show something usefull.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wradi9/why_normal_discussions_has_so_many_haters/pcb6xxg/)
- Complaint, 2026-09-27, r/ClaudeCode (Reddit): “and its just now that you noticed its been like this? and if you think you should be running 3 and is running one … heheh now is the time to run 30… 30 workflows with multiple agents… ride the wave, bro!” [source](https://www.reddit.com/r/ClaudeCode/comments/1wr889i/opus55_is_making_me_so_lazy_im_running_multiple/pcb8z2v/)

### Pi

- Praise, 2026-09-27, r/PiCodingAgent (Reddit): “my orchestrator does nothing except for delegating and passing messages. i've had builds running for almost 24 hours and the orchestrator at the end is still below 200k context. for long builds it's super efficient.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wo6lr8/how_to_better_enforce_subagent_delegation/pcatr9y/)
- Praise, 2026-09-27, r/PiCodingAgent (Reddit): “why not both? i have a orchestrator mode extension in pi, where the system prompt instructs the model to update a plan and ledger md in scratch workspace, it can compact how/when it wants, because all the key findings and planned tasks are always tracked in scratch workspace” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wrq50c/new_session_handoff_vs_compact_which_do_you_prefer/pcguntn/)
- Praise, 2026-09-26, r/PiCodingAgent (Reddit): “1.5.0 - subagent agentruns now show per-run effort (duration / tools / usage) with a stable async identity, honest unavailable instead of zeros, detached reported as detached, and a clear statement of the native calls behind every run. pi install npm:@<email_address>” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wj4flu/i_built_pi_session_inspector_to_see_where_my/pc5d2z1/)
- Complaint, 2026-09-27, r/PiCodingAgent (Reddit): “pretty much it. even if the system prompt says they have to delegate, it usually tries and fails once in order to realize it really has to delegate. i guess you could instruct it to use a classifier model to determine if it needs to delegate and to which agent.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wrte31/alternative_to_tool_profiles_for_better_subagent/pcfl1l2/)
- Complaint, 2026-09-27, r/PiCodingAgent (Reddit): “will be trying your prompts. looks pretty much like what i do, after a lot of frustration from watching my agents behave similar to op's. i just started telling whatever we were supposed to do, and then saying "you will not execute the tasks yourself. you will delegate to sub-agents for execution, and whatever other steps may be appropriate." lol.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wo6lr8/how_to_better_enforce_subagent_delegation/pch06nf/)
- Complaint, 2026-09-26, r/PiCodingAgent (Reddit): “no it’s retarded. you have two separate systems competing to be the harness. it is not predictable.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wqmcmk/poll_claude_sub_with_pi_what_method_do_you_use/pc5dfvt/)

### Devin

- Praise, 2026-09-27, @cognition (X): “if you have claude subscription and @cognition cloud agents. try it it is amazing combo, it ships like crazy when you sleep. @cognition swe 2 max is a really good model and on cloud, it has macos, can code, run test, take screenshot and record evidence. opus 5.5 is really well as orchestrator, review and merge pr on your machine. you can feed opus (in claude code or hermes) devin api key, it knows what to do.” [source](https://twitter.com/1767985295910383616/status/2104014647724761554)
- Praise, 2026-09-27, @DevinAI (X): “@markfenner @devinai just ran 40 in parallel today i can’t believe it worked” [source](https://twitter.com/28648160/status/2104037155891036195)
- Praise, 2026-09-27, @DevinAI (X): “@hraness @chatgpt @devinai @claudeai @cursor_ai @bot @zeddotdev orchestrating 39 terminals across claude code and devin is wild. the real bottleneck quickly shifts from token limits to automated verification and state merge pipelines. love seeing builders push agent concurrency this far!” [source](https://twitter.com/1489515986466320392/status/2104137330089202009)
- Complaint, 2026-09-27, @DevinAI (X): “@doodlestein @hraness @chatgpt @devinai @claudeai @cursor_ai @bot @zeddotdev the part i’d watch is observability. more terminals only helps if you can see which run stalled, what changed, and whether the result is safe to merge. otherwise it’s just a very expensive wall of tabs.” [source](https://twitter.com/2103910196330242049/status/2104140047633326358)
- Complaint, 2026-09-27, @DevinAI (X): “@doodlestein @hraness @chatgpt @devinai @claudeai @cursor_ai @bot @zeddotdev sixty-four accounts. at that point the agents are managing you, not the other way around.” [source](https://twitter.com/2087402808756629504/status/2104147885679845800)
- Complaint, 2026-09-27, @DevinAI (X): “@hraness @chatgpt @devinai @claudeai @cursor_ai @bot @zeddotdev claude code's main gap: unlike opencode, it has no central view of every agent across all sessions and repos.” [source](https://twitter.com/3251926098/status/2104247081237967027)

### Google Antigravity

- Praise, 2026-09-27, r/google_antigravity (Reddit): “who told you i dont have codex or claude max plan, i have them also, but antigravity, and only antigravity is the one that complements them, also i am using deepthinking in gemini chat, and it is so good, not what you think, i can get real time feedback with antigravity, solve problems together, spawn tens of agents and get things done in minutes, while with codex or claude, i need to put them on task before bed and wake up to see the results, th” [source](https://www.reddit.com/r/google_antigravity/comments/1wrn9q5/codex_has_ultra_thinking_level_claude_code_has/pcencos/)
- Praise, 2026-09-27, @antigravity (X): “@dexhorthy @thsottiaux @antigravity i still have agents plan out a feature end to end then tell another to <email_address> or whatever, they work till it’s done, get side tracked less i can have another agent check their work. or even ask them if they missed something before i manually test.” [source](https://twitter.com/1891578771905425408/status/2104088393550352831)
- Praise, 2026-09-27, @antigravity (X): “@ananyairl actually people might be using @antigravity for the crazy usage limits and personally i also like it when you orchestrate it with astra or sol or opus by planning with intelligent models, and execution with gemini flash 3.8 high. its fast and almost reliable.” [source](https://twitter.com/1677941694/status/2104222803167985875)
- Complaint, 2026-09-27, @antigravity (X): “@antigravity lotta hate for this lol. it is definitely puzzling that the product is moving so slowly. still has /teamwork-preview command required to get a decent agentic team involved in changes, something that should be automatically invoked and scaled appropriate to the task” [source](https://twitter.com/805587288/status/2104295109680410783)
- Complaint, 2026-09-26, @antigravity (X): “@antigravity vaaovv soon there will be a tool call! true agi! is it gonna use subagents too? we have never heard this kinda feature. gemini can plan now hahhaha” [source](https://twitter.com/2096852550741848064/status/2103951608723669028)
- Complaint, 2026-09-25, r/google_antigravity (Reddit): “seems like starting today, many of my queries are automatically spawning research sub-agents. very similar prompts from the past few days didn't trigger this. this is with flash 3.8 high. it's kind of annoying because in the app, terminal permissions wild cards don't seem to work, and each sub agent wants to do a bunch of greps to figure out the project for themselves. and it's not like they're spawning to do anything in parallel. the original ag” [source](https://www.reddit.com/r/google_antigravity/comments/1wq6eah/anyone_elses_agents_start_spawning_way_more/)

### OpenAI Codex

- Praise, 2026-09-27, r/codex (Reddit): “subagents do, because the prompts are better and it doesn't have to figure out what's going on.” [source](https://www.reddit.com/r/codex/comments/1wr6on3/why_does_it_feel_like_astra_uses_less_usage_when/pcaidkv/)
- Praise, 2026-09-27, r/codex (Reddit): “i’ve had opus 5.5 acting as dev, codex doing qa. just switched to the other way round: codex is dev, opus qa. feature delivery rate has gone up 4x and token burn per delivery looks to be heavily down.” [source](https://www.reddit.com/r/codex/comments/1wpveoe/astra_vs_opus_55_my_impressions_on_hard_project/pcbbeow/)
- Praise, 2026-09-27, r/codex (Reddit): “i've been using luna 6 since it became available, running 5–6 projects in parallel. for complex tasks, i always use the astra orchestration skill, and it works like a charm.” [source](https://www.reddit.com/r/codex/comments/1wrb1xg/i_tested_astra_solo_vs_astra_orchestrating_luna/pcbg5bf/)
- Complaint, 2026-09-27, r/codex (Reddit): “no they don't work well together from what i tested. also u wasting context tokens the more providers you use or the more models you used.. u must choose which to be main. the other is just to be a llm council judge but not at every juncture. if not u will just be wasting tokens” [source](https://www.reddit.com/r/codex/comments/1wr2ehk/chatgpt_pro_5x_is_now_standard/pcb3d72/)
- Complaint, 2026-09-27, r/codex (Reddit): “this is exactly why i accidently burned through 3 banked resets on astra launch. excessive and constant polling between orchestrator and subagents causes *so much* token burn.” [source](https://www.reddit.com/r/codex/comments/1wrablc/if_your_gpt6_astrasolluna_orchestrator_wont_stop/pcbeaib/)
- Complaint, 2026-09-27, r/codex (Reddit): “kinda wrong they didn't let us select the subagent and orchestrator seperately. i agree” [source](https://www.reddit.com/r/codex/comments/1wrjfne/holly_shit_sol_kept_lying_to_me_telling_me_the/pcd4w13/)

### GitHub Copilot

- Praise, 2026-09-27, r/GithubCopilot (Reddit): “i spent time months ago building up agents and skills that make all of that a non-issue. entire github flow in one place with great orchestration. i don't care what any benchmarks of the day say for harness or model. only care about the evals with my system.” [source](https://www.reddit.com/r/GithubCopilot/comments/1wr5io2/best_cheaper_alternative/pca145m/)
- Praise, 2026-09-24, r/GithubCopilot (Reddit): “local. not having the ability to approve the changed files is unacceptable. if i need to do something across multiple repos, i use the github copilot app” [source](https://www.reddit.com/r/GithubCopilot/comments/1wpctlc/vs_code_chat_users_local_or_copilot_harness/pbvangl/)
- Praise, 2026-09-22, r/GithubCopilot (Reddit): “i have custom agents. one orchestrates, determines the work, then hands it off to other custom agents to do it. the type of work determines which custom agents get it, and some flows, like code, have build/review cycles with revisions built in. the front matter on the agent files lets you pick models, so you can pick the best model for the specific tasks. and by task, i don't mean the prompt you gave, i mean the task as broken down by the orchest” [source](https://www.reddit.com/r/GithubCopilot/comments/1wju32f/hydrafusion_usage_review/pbcigbu/)
- Complaint, 2026-09-25, r/GithubCopilot (Reddit): “i have a bug analyzer subagent that was using opus 5.5 and only today i had three occurrences of subagent not returning anything to orchestrator so it was required spawn a new one. now i switched to sol and had no issues at all.” [source](https://www.reddit.com/r/GithubCopilot/comments/1wptkkq/how_does_gpt6_sol_feel_so_far/pc0mfxl/)
- Complaint, 2026-09-18, r/GithubCopilot (Reddit): “you are not alone! i'm building out a comprehensive data reconciliation tool with github copilot business and although i'm making progress i am also finding that agents implementing features run into issues all the time. i have even had astra 6 try to assess what's going on. i have had sessions where implementing a single feature takes 11 turns with sol high. if i was using codex it might be a few. i'm considering turning off subagents to see if” [source](https://www.reddit.com/r/GithubCopilot/comments/1win2b6/github_copilot_is_a_nightmare_for_enterprises/pakn3f6/)
- Complaint, 2026-09-14, r/GithubCopilot (Reddit): “nice. i will try this! sucks that i can’t use subagents though.” [source](https://www.reddit.com/r/GithubCopilot/comments/1wf0lvr/luna_inserts_a_dunder_block_inside_a_list_of/p9nu22r/)

### Cline

- Praise, 2026-09-24, @cline (X): “@cline parallel worktrees + pr status + subagents in one update - cline desktop is getting serious for multi-tasking” [source](https://twitter.com/2068360781402652672/status/2102987040661127435)
- Praise, 2026-09-24, @cline (X): “@cline this makes cline much more practical for serious parallel development. worktrees + subagents + pr/ci visibility means you can run multiple tasks independently without stepping on each other. 🚀” [source](https://twitter.com/2099746460321640448/status/2103106430484332665)
- Praise, 2026-09-24, @cline (X): “@cline parallel worktrees are great. parallel merges without a per-branch review still hurt. i'd want a dry-run + confirm on anything destructive before those land on main.” [source](https://twitter.com/2080369308173996032/status/2103154187441676484)
- Complaint, 2026-09-27, r/CLine (Reddit): “hey, first time post so bear with me if i'm doing something wrong. ill first explain i run a prompt then the model runs okay for a bit then it hits the "waiting for teammates" this isn't a issue but when i click on the sub models that are running no processing or thinking is actually being done the sub model just sits with the prompt and displays "thinking" if anyone has a solution please send” [source](https://www.reddit.com/r/CLine/comments/1wrqbkt/waiting_for_teammates_error/)
- Complaint, 2026-09-18, @cline (X): “@cline and i can't seem to run queries in parallel, like i can in codex. sad little tool” [source](https://twitter.com/1416864353131765762/status/2101033207710036409)
- Complaint, 2026-09-14, @cline (X): “@documentingagi @cline two of our agents once grabbed the same scheduled run and overwrote each other's files. i think task locking is what i'd check first in cline desktop.” [source](https://twitter.com/129034169/status/2099576457400107509)

### Conductor

- Praise, 2026-09-27, r/ClaudeAI (Reddit): “i built a personal ai assistant that now answers my phone, triages my email, texts me notifications, drafts and sends documents and emails, manages my calendar, and remembers past conversations. basically i had a goal to create my own grok bot/muse before i knew those were a thing. now that those are out, i have a benchmark for baseline parity. but among other things, it also has an address book which i also use to configure how to behave depen” [source](https://www.reddit.com/r/ClaudeAI/comments/1wrckhp/what_tool_have_you_built_for_yourself_with_claude/pch0v2v/)
- Praise, 2026-09-26, @conductor_build (X): “@itsvlady it's crazy man, astra as architect and opus 5 as the henchman -- try out @conductor_build btw, it's awesome, so far the best 'multi-model' harness (supports cc, codex, cursor and opencode clis), and all your work sits in isolated worktrees so you can parallelize it to the maxx” [source](https://twitter.com/2891185809/status/2103772258376294595)
- Praise, 2026-09-26, @conductor_build (X): “@newmediums @itsvlady @conductor_build that's actually a really good one, i usually run astra as the architect, but keep it for anything that is 'verifiable', so if it has unit tests, it can really chew through bugs before creating them, but fable as the orchestrator and opus 5.5, oh man, it's so good” [source](https://twitter.com/2891185809/status/2103829576543621213)
- Complaint, 2026-09-26, @conductor_build (X): “@mattgapp @capydotai @conductor_build capy does next level orchestration i’ve switched” [source](https://twitter.com/11768582/status/2103996834704466324)
- Complaint, 2026-09-12, @conductor_build (X): “@euboid @conductor_build switched off conductor for paseo because their mobile app is and has been already working for a while. as well as agent handoffs!” [source](https://twitter.com/1403003368339951620/status/2098889188397416523)
- Complaint, 2026-09-08, @conductor_build (X): “i looked at a bunch of options now. thanks a ton for all the replies. @tryreplicas looks really nice but huge bummer that you have to pay for it and you can't just use the ui without automations etc. bummer, that leads me to @conductor_build which also looks solid but lacks some features that replicas has, e.g., introspection of subagents of each harness.” [source](https://twitter.com/2843813092/status/2097291719033151838)

### Factory

- Praise, 2026-09-24, @droid (X): “working on ai vidgen with @droid and @tastelabs tastelabs builds the design files and brand guide - not much shown here, but there are signs droid orchestrates from a prompt, skills, and mcp <strict_link>” [source](https://twitter.com/1681456803832561664/status/2102993885849117048)
- Praise, 2026-09-23, @droid (X): “@droid turns out, mission control is an extremely powerful feature.” [source](https://twitter.com/2070908287978246144/status/2102627616192962762)
- Praise, 2026-09-22, @FactoryAI (X): “@harrystuck77 @factoryai @droid @badlogicgames @ampcode @cursor_ai @opencode @anthropicai @claudeai @cognition @xai @build grok build sitting in c is fair for now. still early days, but the parallel subagents and plan-review flow are already solid for real engineering work. thanks for the ranking.” [source](https://twitter.com/1720665183188922368/status/2102486379972198418)
- Complaint, 2026-09-23, @FactoryAI (X): “@factoryai multiple seats make shared work-in-progress more important. two engineers can send droids after the same failing test and only notice the overlap at merge time. seeing tasks by branch would help.” [source](https://twitter.com/2095716579405377536/status/2102828491758834019)
- Complaint, 2026-09-20, @FactoryAI (X): “@hataiit9x @droid @factoryai the parallel agents part is what got me too. mine kept editing the same file until i gave each one its own scope.” [source](https://twitter.com/2079331237991428096/status/2101724074552516749)
- Complaint, 2026-09-08, @FactoryAI (X): “@droid @factoryai - management of /droids in factory app - change ui font family - "full screen" mode to view files - side bar is too limited size.. - pin *todos* to sidebar - sometimes when todo list is too long it blocked more than half the screen lol” [source](https://twitter.com/1257471091833884674/status/2097327955982811369)

### Zed

- Praise, 2026-09-24, @zeddotdev (X): “agent orchestration is different level in @zeddotdev <strict_link>” [source](https://twitter.com/1261173216455712768/status/2103200605493928281)
- Praise, 2026-09-23, @zeddotdev (X): “@zeddotdev spawning independent top level threads from one ask is exactly how i want agent work to feel.” [source](https://twitter.com/2081586838976733184/status/2102895538051965352)
- Praise, 2026-09-21, r/PiCodingAgent (Reddit): “my personal huge level up was going from cursor ide to zed + omp. it is more efficient, i have everything i could've asked for and more. i love the custom fallbacks. being able to force the use of subagents. and the advisor... the advisor is really something tbh” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wlpj30/lord_forgive_me_for_the_time_i_wasted/pb4z6kj/)
- Complaint, 2026-09-23, @zeddotdev (X): “@zeddotdev if i stop the original thread, do the spawned threads stop too? independent conversations are useful, but cancellation needs a defined scope once one prompt can fan out.” [source](https://twitter.com/1588935512135720961/status/2102868267933270488)
- Complaint, 2026-09-21, r/ZedEditor (Reddit): “i could pick like fable-coordinator, code-review-agent here <strict_link> but now zed has removed this feature, and im just lost for words.” [source](https://www.reddit.com/r/ZedEditor/comments/1wm59hh/why_did_zed_remove_the_starting_agent_selector/)
- Complaint, 2026-09-18, r/ZedEditor (Reddit): “not sure whats ur workflow, but i ended up going back to neovim just because of customization, specially now with ai that you don’t need to deal with all the configs yourself. i really liked zed, but customization and working with multiple worktrees in an agentic way was kind of painful. i’ve spend a few days setting up nvim, and i am back at feeling very productive again with all the abilities to customize whatever i need, i am using lazyvim by” [source](https://www.reddit.com/r/ZedEditor/comments/1wjp5nq/popular_zed_fork_where_the_community_is_more/pan10ea/)

### Warp

- Praise, 2026-09-23, @warpdotdev (X): “the “4 agents / one repo / zero conflicts” part is the real unlock — voice input is just the front door. what usually breaks isn’t transcription quality; it’s ownership boundaries between agents. once each agent owns a clear slice (and the terminal is the shared blackboard), talking beats typing because you stay in intent mode instead of micromanaging files. just followed — happy to mutual follow if you’re building in public too.” [source](https://twitter.com/1908014421538123779/status/2102592645759373441)
- Praise, 2026-09-22, @warpdotdev (X): “@mrsaasbuilder @wisprflow @claudeai @warpdotdev thanks! for me the calendar isn't the bottleneck. the real win is keeping 4 agents from stepping on each other in one repo. that's what the video is about.” [source](https://twitter.com/1792878079276101634/status/2102419321800540545)
- Praise, 2026-09-12, @warpdotdev (X): “@warpdotdev running more than one agent cli in the same terminal is the bit that saves us time. easy to lose track of which agent touched which repo otherwise.” [source](https://twitter.com/1070947916917825536/status/2098682005764575595)
- Complaint, 2026-09-11, @warpdotdev (X): “@warpdotdev saiu!! warp com grok build cli nativo: prompt longo, remote-control e review no mesmo terminal. eu fixo o harness no warp — trocar de shell no meio do job some o session.” [source](https://twitter.com/326479892/status/2098456907686236422)
- Complaint, 2026-09-05, @warpdotdev (X): “@bholmesdev @warpdotdev it does well overseeing simple things and i love the hovering agent bubble inside the terminal. i am talking about complex tasks, spawning sub agents, handover + communication with other agents. i need it as foreman - keeping everyone unstuck” [source](https://twitter.com/8104092/status/2096029908761788572)
- Complaint, 2026-09-03, @warpdotdev (X): “@justinmfarrugia @warpdotdev i keep bouncing back to the terminal too. the orchestrators feel busy until they just dont” [source](https://twitter.com/1699357106485542912/status/2095567403669475827)

### Kiro

- Praise, 2026-09-09, @kirodotdev (X): “that last update i shipped so many features. i've been posting for days and still haven't gotten through them all. 1devtool now supports `oh my pi` by @_can1357 and @kirodotdev you can resume sessions, save prompts, orchestrate, and more with them <strict_link>” [source](https://twitter.com/2050465213821132800/status/2097691961608306922)
- Praise, 2026-09-07, r/kiroIDE (Reddit): “i'm not sure moe or not but your suggestion is great :). i think using multiple agents with a well-defined workflow will help us implement things more effectively.” [source](https://www.reddit.com/r/kiroIDE/comments/1w7zen5/what_if_kiro_cli_worked_like_an_entire_software/p89zc2b/)
- Praise, 2026-09-02, r/kiroIDE (Reddit): “kiro crew is pretty stable, def worth a try!” [source](https://www.reddit.com/r/kiroIDE/comments/1vlhy1l/kiro_needs_to_change_urgently/p7c3i9v/)
- Complaint, 2026-09-27, r/kiroIDE (Reddit): “i work for amazon and is somewhat “strongly recommended” to use kiro. i still use claude code at work and at home. so much better … (auto classifier, transcript details, integrated tooling, open source tooling, cli features, general stability, model fallback, sub agents control, etc …)” [source](https://www.reddit.com/r/kiroIDE/comments/1wqueq0/claude_pro_vs_kiro_pro_subscription_which_is/pccqcjf/)
- Complaint, 2026-09-07, r/kiroIDE (Reddit): “feels like too much over engineering, takes a heck lot of time and costs at max one reviewer is best” [source](https://www.reddit.com/r/kiroIDE/comments/1w7zen5/what_if_kiro_cli_worked_like_an_entire_software/p8dwul7/)
- Complaint, 2026-09-06, r/kiroIDE (Reddit): “that’s the whole idea behind an agentic workflow and something kiro, claude, codex, etc all do well. i think crew is intended to make this more automatic but honestly it feels more clunky than a build out cli workflow so i haven’t fully adopted.” [source](https://www.reddit.com/r/kiroIDE/comments/1w7zen5/what_if_kiro_cli_worked_like_an_entire_software/p82mp2c/)

### Grok Build

- Praise, 2026-09-05, r/vibecoding (Reddit): “codex or claude calling grok build at an agent works really well” [source](https://www.reddit.com/r/vibecoding/comments/1w74l2u/is_everyone_here_on_claude_or_codex_only_anyone/p7y2apg/)
- Praise, 2026-09-04, r/vibecoding (Reddit): “i use claude code for clean work, gpt for helping me prompting, deepseek for daily tasks, grok build for subagent & research workflow, gemini when polishing frontend ui/ux design since it's better than claude (at least for me).” [source](https://www.reddit.com/r/vibecoding/comments/1w74l2u/is_everyone_here_on_claude_or_codex_only_anyone/p7trtvo/)