---
title: "Sub-Agent Coordination + Rubrics: Anthropic's New Beta"
description: "Anthropic's expanded public beta adds sub-agent coordination and rubric-based evaluation. The actual mechanics and what it means for production AI systems."
canonical: https://callsphere.ai/blog/tw26w19-agent-sub-coordination-rubric-evaluation-anthropic
category: "Agentic AI & LLMs"
tags: ["sub-agents", "rubrics", "anthropic", "ai engineering", "callsphere"]
author: "CallSphere Team"
published: 2026-05-10T00:00:00.000Z
updated: 2026-05-10T00:00:00.000Z
---

# Sub-Agent Coordination + Rubrics: Anthropic's New Beta

> Anthropic's expanded public beta adds sub-agent coordination and rubric-based evaluation. The actual mechanics and what it means for production AI systems.

Alongside the May 2026 managed-agents research preview, Anthropic shipped an **expanded public beta** of two primitives that matter for anyone building production AI systems: **sub-agent coordination** and **rubric-based evaluation**. This post is the engineering view.

## Sub-agent coordination: what it is

In the new beta, an agent can:

1. **Spawn sub-agents** with their own scoped context, tool access, and stop conditions.
2. **Coordinate them** via a parent agent that dispatches work and synthesizes results.
3. **Cap budget per sub-agent** (token, time, tool-call counts).
4. **Resume or terminate** sub-agents based on intermediate signals.

This is the API surface for what advanced teams have been hacking together with custom orchestration code. Anthropic is making it a first-class platform feature.

### Concrete pattern

A primary agent receives "research and draft a competitive analysis." It spawns:

- A **search sub-agent** to gather public info.
- A **read sub-agent** to summarize each source.
- A **draft sub-agent** to write the deliverable.

The primary agent monitors progress, kills sub-agents that are off-track, and synthesizes the final output.

### What you get over rolling your own

- **State management** across sub-agent lifecycles.
- **Budget enforcement** without manual tracking.
- **Tracing** that connects parent and sub-agent calls in observability tools.
- **Graceful failure** when a sub-agent times out or hits a tool error.

If you have built multi-agent orchestration in LangGraph or custom code, you know the dragons. Anthropic's primitive is not magic — it has the same failure modes — but it is significantly less code to maintain.

## Rubric evaluation: what it is

The rubric eval primitive lets you:

1. **Define a rubric** as a structured set of criteria (e.g., for a legal brief: "cites valid precedent", "addresses opposing counsel's argument", "is under 25 pages").
2. **Run an eval agent** that scores any output against the rubric.
3. **Aggregate scores** across runs to detect drift, regression, or improvement.
4. **Feed scores back** into prompt/tool selection over time.

### Why this matters

The hardest part of running production AI is **knowing when it broke**. Rubric eval gives you a signal. It is not perfect — eval agents have their own biases and failure modes — but it scales in a way human review cannot.

### The honest caveat

Rubric eval is a **weak supervisor**. It catches gross failures (wrong format, missing required field) reliably. It catches subtle failures (slightly off tone, factually questionable claim) less reliably. Use it as one signal in a multi-signal eval pipeline, not as the only signal.

## How CallSphere uses both

CallSphere has been running rubric evals on voice calls since 2025. The expanded Anthropic beta gives us a more standard format to express rubrics and an eval-agent primitive that is competitive with what we built internally. We are evaluating adoption for:

- **Pre-call sub-agent fan-out.** Spawning a parallel context-gathering sub-agent while the conversation agent talks. We currently do this with custom code; the new primitive would simplify.
- **Per-call rubric scoring.** We score every call today; the new format may let us expose rubrics to customers more cleanly so they can customize per-vertical scoring.

We are NOT planning to use it for:

- **Real-time conversation routing.** Latency is too tight; sub-agent overhead doesn't pencil mid-call.
- **Autonomous prompt updates.** Still keeping a human in the loop for any regulated-vertical change.

## What to build with it

If you are building an agent system in 2026, the practical advice:

1. **Use rubric eval from day one.** Even a 3-criterion rubric is better than no eval. It is the cheapest insurance you can buy against silent regressions.
2. **Use sub-agents sparingly.** Every layer of coordination adds latency and failure modes. Default to a single agent; reach for sub-agents when the task truly decomposes.
3. **Cap budgets aggressively.** Sub-agents without budget caps are how you end up with $4,000 inference bills.
4. **Trace everything.** Hook the beta primitives into your observability stack before you ship.

## What this signals

Anthropic is converging on the "agent platform" shape — sub-agents, rubrics, managed runtimes — that the market has been asking for. Expect OpenAI and Google to match within a quarter.

For voice specifically, [CallSphere](https://callsphere.ai/demo) already runs rubric evals and sub-agent context gathering in production; the new Anthropic primitives are an accelerant, not a replacement.

## FAQ

**Q: Can sub-agents in the new beta call other sub-agents (nested)?**
A: Yes, with a depth cap. Anthropic recommends max 3 levels for production.

**Q: Does rubric eval work for voice transcripts?**
A: Yes — feed the transcript as text input to the eval agent. The primitive is modality-agnostic.

**Q: What is the pricing for the beta?**
A: Standard Claude pricing applies; no separate beta surcharge. Sub-agent calls bill as normal Claude calls.

---

Source: https://callsphere.ai/blog/tw26w19-agent-sub-coordination-rubric-evaluation-anthropic