# \[Bug\]: Command approvals stay pending after a delegated task is cancelled · Issue \#21935 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/21935)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

State: backlog

Priority: 0

## Description

[Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/21935)

---

What happens: on 0.0.46-nightly.20261008.2819, two delegated Codex tasks were each blocked on a pending shell-command
approval. Each was cancelled by its parent agent's `task_cancel` call, and both runs are now `interrupted`. Their command
approval requests remained pending afterwards. A comparable delegated Claude task's pending file-read approval, cancelled
the same way, was cleared.

This one sample shows inconsistent cleanup between the two delegated tasks. It does not establish a Codex-only bug. The
provider-specific cause is not traced; the records were found by read-only state inspection.

Expected: when a run is interrupted or cancelled, its unresolved approval requests are withdrawn, because their provider
callbacks no longer exist. They should then no longer count as pending.

The effect on any UI view was not inspected.