#multi-agent
Every post tagged "multi-agent".
28 posts · showing 1–10
-
The Tax Agent's Workers Counted March Twice and Skipped Late June. Make Every Delegation Return the Range It Actually Covered.
Splitting a year of transactions across four workers looks like clean delegation until the merged total is off and every worker reports success. The fix is a coverage contract the supervisor checks before it adds anything up.
-
Your Assistant Agent Reads Your Inbox and Pays Your Bills. Split It Where the Permissions Change, Not Where the Topics Do.
An email agent, a calendar agent and a finance agent look like clean architecture. They leave every agent exactly as manipulable as before and add three handoffs. There is a better place to draw the line.
-
Your Critic Agent Approves Everything Because It Read the Worker's Reasoning. Starve It of the Argument, Give It Its Own Evidence.
Forward the worker's transcript to your reviewer agent and it will approve nearly everything — anchored by a conclusion it treats as evidence. Here is the information diet, the mutation test, and the disagreement policy that turn a rubber stamp back into a check.
-
Parallel Subagents or One Agent in Sequence? Check Whether the Subtasks Share a Write
Fanning a task out to five workers looks five times faster, until two of them update the same record and the last write quietly wins. One question about shared writes settles most parallel-vs-sequential calls.
-
A Second Pass That Asks the Same Question Finds the Same Bugs. Change the Unit, Not the Temperature.
Raising the temperature on a review pass re-rolls the dice inside a frame that has already decided what is findable. Three properties determine what a pass can see, and a real second pass has to change at least two of them.
-
Forty Tools in One Prompt: What It Actually Costs, and the Three Signals That Say Split the Agent
Forty registered tools do not fail loudly — the agent just gets vague, picking near-synonyms and asking questions it had the answer to. Here are the three costs you're paying, and the signals in your traces that tell you to merge, gate, or finally split.
-
"Done" Is Not a Handback: What a Worker Agent Should Actually Return to Its Supervisor
A worker agent reporting "completed" tells its supervisor nothing it can verify. Here is the handback shape that makes a fabricated result catchable by code instead of by a second model's opinion.
-
Your Two Reviewer Agents Disagree. Who Breaks the Tie?
Running the same document past two agents is easy. Deciding what happens when they return opposite verdicts is the part most multi-agent designs quietly leave undefined — and the default resolution is usually the worst one available.
-
Blackboard or Mailbox: How Should Three Agents Share What They Learn?
Two agents discover the same fact; a third contradicts both and nobody notices. The shape of your shared state — a common board or point-to-point messages — decides which of those happens.
-
The Worker Agent Reported Success. Where Should the Check Live?
A worker agent's "done" is a sentence, not evidence — and in effectful work the gap between the two is where silent failures live. Three places to put the verification, and the one most teams pick that buys nothing.