Delegated completion callback rejected despite an explicit parent assignment

Observed behavior

In Codex Desktop, a user asked a Chief task to launch a main worker and own review of the result. The Chief created the worker using the native task-creation tool. The assignment explicitly specified the Chief task as the completion-message destination and authorized a report containing outcome, artifact links, verification and caveats.

The worker completed its work and attempted that native cross-task message. Automatic approval review rejected it, stating that trusted authorization for the destination and detailed payload was not established.

The user then requested recovery. Chief gave the same worker an exact destination and a minimal, non-sensitive completion-test sentence. The worker sent it once. The native tool returned success and the Chief actually received the sentence.

The successful attempt's approval result still classified user authorization as unknown. Its stated reason for allowing the action was the minimal, non-sensitive and bounded payload.

What this establishes

The native transport can deliver a worker message to the Chief. The successful test did not demonstrate that delegated authorization was recognized. Payload sensitivity and a new follow-up both changed, so this is not a controlled demonstration of why the original attempt failed.

The observed failure is approval recognition at the parent-to-worker authorization boundary. The available evidence does not establish whether this is intentional policy, missing authorization provenance supplied to the reviewer, or incorrect reviewer classification. This report does not claim a confirmed software root cause.

Expected clarification or repair

Please clarify the supported way for a user-authorized parent task to authorize a completion report back from its worker. If native delegation is intended to carry that authority, investigate why the approval check did not recognize it. If it is intentionally insufficient, document the supported authorization step so task coordination works without repeated user intervention.

Preserve meaningful privacy checks. A short-message workaround should not be mistaken for a fix to delegated authorization.

Reproduction outline

1. User asks a parent task to create a worker and review the result.
2. Parent creates the worker with an explicit native completion destination and report scope.
3. Worker attempts the specified completion report using native task messaging.
4. Inspect approval outcome and delivered-message state.
5. Separately test an exact non-sensitive receipt, preserving both the reported authorization classification and actual delivery result.

Observed once per payload type; not asserted to reproduce on every task.

Start with the native task-creation and cross-task messaging approval paths, then reproduce the two outlined payload cases while comparing authorization classification with actual delivery. Done means either the parent’s supported authorization is recognized without weakening privacy checks, or the supported authorization step is clearly documented.