---
title: "Delivery receipt versus task completion"
description: "A delivery receipt confirms a message’s arrival in the intended conversation."
slug: "receipt-vs-completion"
category: "agent-management"
language: en
editorial_status: published
capability_status: available
reviewed_at: 2026-10-13
keywords: ["AI message receipt","Codex task completion","CueSpec confirmed send"]
---

# Delivery receipt versus task completion

A delivery receipt confirms a message’s arrival in the intended conversation. Task completion concerns the work that happens afterward. Neither alone establishes that the result meets your requirements.

## Three checks
First, confirm identity: the message reached the correct task. Second, follow execution: the task is running, waiting, blocked or finished. Third, assess the output: the answer, changes or external result satisfy the request.

These checks prevent two common mistakes. Resending after a valid receipt can duplicate work. Treating a finished task as an approved result can skip review of incorrect assumptions or incomplete validation.

## An example
You send “Compare the two options without changing files.” A confirmed receipt means Codex received that request. A later answer may compare the options, ask for missing information or report a problem. Review the answer for the original no-change constraint.

CueSpec’s uncertain-send behavior preserves the draft and checks receipt rather than blindly repeating the message. If the companion and original conversation disagree, inspect Codex and keep the evidence. The current task monitor does not turn a receipt into a promise of execution or commercial outcome.

## Related reading

- [Use completion reminders as a review queue](/completion-reminders/)
- [A send result is waiting for confirmation](/send-pending-confirmation/)
- [The original conversation is unavailable for sending](/conversation-owner-unavailable/)
- [CueSpec product facts at a glance](/product-facts/)