Menu

1 / 6

Orchestrating Agents: The Graph Is Yours, the Judgment Isn't

DEV Community: aws·Pin Xiong·2 days ago
#UOTnVR1a
#devtoaws#devto#dev#node#graph
Reading 0:00
15s threshold

Verified on 2026-11-13 against strands-agents 1.63.0, Python 3.11 and Bedrock in us-east-1 . Every number below came out of a run. The scripts and raw output live in https://github.com/pinxiong/strands-in-action/tree/master/usecases/07-graph . The model is amazon.nova-pro-v1:0 .

The last post in this series ended with a swarm that had no scheduler. Three agents passed a task around by calling one tool, and the runtime read the absence of that call as completion. The task is small: given a topic, produce research notes, add up the per-node token counts and write a short brief. This post runs the same task on a graph instead, using the same fixed input file and the same three roles, so the traces stay comparable. I assume you have read the UC06 trace, so I will not restate it.

Here is the judgment that changes. In a swarm the model decides who runs next, because routing is a tool call it can choose to make.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.