Problem / 问题
The runtime supports TaskStop(delegationIds?), but users cannot invoke an
individual delegation stop directly from its current topology/detail card.
Asking the coordinator to call a tool adds an unnecessary model round trip;
using the parent Stop button is too broad when only one delegate should stop.
Rechecked against v0.16.1/main 10e824e on 2026-10-05. This is a UI capability
request, not a claim that existing TaskStop or completion persistence is broken.
Proposed change / 期望改动
- Add a compact, accessible Stop action to each running subagent card and,
where appropriate, its read-only detail surface.
- Add Stop all subagents on the session's subagent group header. Label its
scope explicitly: all currently running delegates in that session.
- Route explicit user actions through a narrow host command to the existing
cancellation mechanism. No language-model/tool invocation should be needed.
- Reuse native UI primitives, permissions, status events and persistence.
- Show pending cancellation until the runtime settles; keep partial output
and terminal status accurate and avoid repeat submissions while pending.
Keep the parent's existing Stop semantics unchanged. Do not add detached
lifecycle behavior, Ultra scheduling, ReturnToParent, MC integration, new
timeouts, or model-selection changes to this request.
Acceptance scenarios
- With A and B running, stopping A leaves B and the coordinator running.
- Stop all stops only the current session's delegates, not another session.
- Completion and cancellation racing produce one accurate terminal state;
completed/failed delegates have no active Stop action.
- Partial messages and tool results remain viewable after cancellation.
- Mouse and keyboard actions work in light/dark themes and narrow windows;
accessible names identify the delegate being stopped.
- Parent Stop retains its current behavior and existing runtime permissions.
Alternatives / 其他方案
Additional context / 补充信息
Upstream currently accepts external fix/perf PRs only. This issue requests
maintainer feedback before implementation or a feature PR. Existing Task rows
already persist terminal status and open detailed transcripts, so this feature
should extend those surfaces rather than introduce a parallel card system.
No implementation or cancellation E2E is claimed in this draft.
Problem / 问题
The runtime supports TaskStop(delegationIds?), but users cannot invoke an
individual delegation stop directly from its current topology/detail card.
Asking the coordinator to call a tool adds an unnecessary model round trip;
using the parent Stop button is too broad when only one delegate should stop.
Rechecked against v0.16.1/main 10e824e on 2026-10-05. This is a UI capability
request, not a claim that existing TaskStop or completion persistence is broken.
Proposed change / 期望改动
where appropriate, its read-only detail surface.
scope explicitly: all currently running delegates in that session.
cancellation mechanism. No language-model/tool invocation should be needed.
and terminal status accurate and avoid repeat submissions while pending.
Keep the parent's existing Stop semantics unchanged. Do not add detached
lifecycle behavior, Ultra scheduling, ReturnToParent, MC integration, new
timeouts, or model-selection changes to this request.
Acceptance scenarios
completed/failed delegates have no active Stop action.
accessible names identify the delegate being stopped.
Alternatives / 其他方案
round trip and is not direct user control.
different problem and are not required for this proposal.
Additional context / 补充信息
Upstream currently accepts external fix/perf PRs only. This issue requests
maintainer feedback before implementation or a feature PR. Existing Task rows
already persist terminal status and open detailed transcripts, so this feature
should extend those surfaces rather than introduce a parallel card system.
No implementation or cancellation E2E is claimed in this draft.