Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / agent-zero

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-agent-zero-direct-subagents-gain-visible-working-state-and-an-independent-stop

Direct subagents gain visible working state and an independent Stop. Direct delegation now runs through the child’s own context task, so child chats show Working/Paused and can be stopped independently. Caller cancellation kills the child task; stopping only the child produces a recoverable error for the parent. This extends v2.13’s deeper worker rendering with a usable intervention point.

Channel: tagged-release. Half: capability. Date: 2026-10-13 (first stable; implementation 2026-09-30T13:55:03Z).

Operator consequence: Use the child Stop when one delegated worker needs intervention instead of cancelling the whole parent run. Check cancellation semantics in a bounded task before relying on them for costly work. The attention gain is targeted intervention; the record contains no measured end-to-end throughput improvement.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-agent-zero-direct-subagents-gain-visible-working-state-and-an-independent-stop

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Agent Zero
    commit2026-10-13-agent-zero-direct-subagents-gain-visible-working-state-and-an-independent-stopgithub.com/agent0ai/agent-zero/commit/f4700b4256a9bd88d2a29d817961f8abaa919554tagged commit file2026-10-13-agent-zero-direct-subagents-gain-visible-working-state-and-an-independent-stopagent0ai/agent-zero / tools/call_subordinate.py

Versioned source: run artifact