← All topics

agent orchestration

3 captures, most recent first.

Ethan Mollick @emollick

— saved image

Ethan Mollick [verified] @emollick · 4h
I overestimated the difficulty of orchestrating massive numbers of agents. I assumed research would be needed to build working organizations of agents, but they self-organize very well (and politely)

Here is a Fable coordinator in Claude Projects passing messages between agents.

[embedded image]
Message received from coordinator
From the main thread at 05:47Z: v17 is live at all three links (artifact Version 17; Netlify deploy [redacted in image] GitHub [redacted in image] with the kit passage, the corrected timing and the two-stage total, and your four pages beside the report as device.html, device-ledger.html, device-sheet.html and device-try.html with their cross-links made relative; all eight pages answer 200. [red box around:] Its thanks for the pages; nothing further is needed from you for v17.
View coordinator
1:44 AM
Note from Claude Sonnet 5

Tweet by Ethan Mollick about agents self-organizing, with a screenshot of a coordinator message in Claude Projects. Part of the message is blurred in the image and a red box (annotation) surrounds the sentence "Its thanks for the pages;".

multi-agentagent orchestrationfableclaude projectsethan mollick

@sophiamyang

— saved image

Sophia Yang @sophiamyang [Subscribe]

Someone please tell me this exists: a meta-harness + kanban board to orchestrate my agents across platforms (Claude, Codex, Grok, Muse, etc.) tracking progress and handing off projects to each other cleanly when one hits its limits. What's the best way to do this?

11:13 AM · Sep 10, 2026 · 6,849 Views

[engagement row] 37 replies · 3 reposts · 56 likes · 48 bookmarks
[Relevant v]   [View quotes >]

Mustafa (in NYC) @mustafa_2vec · 1h
I have it built out using a custom skill built on linear
[1 reply · 2 likes · 524 views]

Sophia Yang @sophiamyang · 1h
ohhh it's a good idea using linear! how do you deal with the hand-offs?
[1 like · 508 views]

Mesut Celik @mesutcelik · 10m
Not sure they have it but you can check @superset_sh
[1 reply · 1 like · 85 views]

AiDevCraft @AiDevCraft · 42m
The kanban part is the easy half — the hard part is what actually crosses the boundary, because a handoff only survives if each agent writes state to a file the next one can read cold, not a conversation summary. Once that artifact exists the board is just a view over it.
Note from Claude Sonnet 5

Tweet thread: Sophia Yang asks for a meta-harness plus kanban board to orchestrate agents across Claude, Codex, Grok and Muse with clean handoffs; replies suggest a custom Linear-based skill, superset_sh, and writing handoff state to a file the next agent can read cold.

agent orchestrationkanbanagent handoffsmeta-harnesslinear

christian @curious_vii

— saved image

christian @curious_vii · 1h
ok, so how do you wrangle hundreds, if not thousands, of long-running agent threads?

very interesting design problem (and, I don't see how a general payments primitive isn't part of the solution .. each thread with a budget and requests for add'l juice once they run out vs. status quo, where everything draws from some pooled credit balance without thread / goal-level controls)
Note from Claude Sonnet 5

Tweet by christian (@curious_vii) discussing the design problem of managing many long-running AI agent threads, arguing a general payments primitive (per-thread budgets with requests for more credit) is likely necessary, contrasted with the status quo of a single pooled credit balance lacking per-thread or per-goal controls.

ai agentstwitteragent orchestrationpayments infrastructure