V2.2.4

V2.2.4

Agent Teams fixes and fewer limits. Subagent results now always reach the parent, agent limits are lifted, and a model asking for a thinking level it cannot use no longer loses the whole batch. Context also shows tokens per second, and multi-question prompts can go back. Everything from 2.2.3 is included.

Subagent results always arrive

• A settled agent's final answer stays readable after it is released. inspect_agent returns it for any owned descendant, and wait_agent returns the latest answer of every child that changed, up to 16,000 characters each. Before, inspect_agent on a released child only said it was released and wait_agent listed paths.
• In agent_workflow, the graph-level notifyParent now carries the result text of every node that has no notifyParent of its own, up to 6,000 characters per node and 24,000 in total. Before, it only said the graph had settled, so a workflow set to immediate with default nodes silently dropped all eight answers. A node with its own notifyParent still delivers separately, so nothing arrives twice.
• The notifyParent, wait_agent and inspect_agent descriptions and the agent catalog now say where results come from.

Thinking levels no longer abort a batch

A thinkingLevel the selected model does not support is clamped to the nearest level it does support, and a non-reasoning model uses off. Before, admission rejected the launch with zero work done, even when the catalog listed the level. A level inherited from the caller is clamped the same way.

Fewer agent limits

• Agents nest up to depth 16 instead of 2.
• agent_workflow runs every ready node in parallel by default. maxConcurrency defaults to 256 instead of 4 and still works as an upper bound.
• Teams saved with the old limits (16 nodes, 3 active turns, depth 2) pick up the new ones on restore.
• The agent catalog no longer tells models about a 3-turn or 16-node ceiling that was already gone. That stale text made models plan around limits that did not exist.

Still in place: one writer at a time per shared checkout (agents in separate worktrees write in parallel), 32 KiB per team message, 256 nodes per workflow graph and 5 minutes per wait_agent call.

Context shows tokens per second

System → Context has a fourth field next to Session tokens, Cache coverage and Session cost: Latest t/s, the output tokens per second of the latest response. The time runs from the start of the response to when it was saved, so it includes time to first token and reads a little lower than pure decode speed. It shows "—" until a response completes or when no usable timing exists.

Questions can go back

In a multi-question prompt, Previous and Next buttons let you return to an earlier question and change your answer. The earlier answer is shown selected, and a typed answer is kept in the field.