{"version":"2.1.286","anchor":"subagenttool-use-filtering-takes-a-parent-agent-id","canonical_anchor":"subagenttool-use-filtering-takes-a-parent-agent-id","heading":"Running-agent list can now be filtered by parent agent","tier":"internal","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/subagenttool-use-filtering-takes-a-parent-agent-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Running-agent list can now be filtered by parent agent\n\nThe filter that picks running agents now matches agents belonging to a given parent agent, not only agents with no parent\n\n**Unclear.** It is not clear what a user will see differently on screen as a result.\n\n**What**\n\nClaude Code can run helper agents, sometimes called subagents: separate workers it starts to handle part of a task. Some of these are started by other agents, so an agent can have a parent.\n\nThe filter that picks out running agents now takes a parent agent as input and returns the agents started by that parent. Before, it could only return top-level agents, the ones with no parent at all.\n\n**Why**\n\nThis affects how nested agents, meaning agents started by other agents, are grouped and shown on screen.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}