Check the installed version#
Confirm that you are using the published CueSpec package rather than an old copy. Older versions and old update sources may need manual migration. Confirm the actual Codex version as well, because host changes can affect integration.
The reviewed repair received a real send-and-reply check, but that evidence belongs to the tested versions. It does not guarantee compatibility with every future host release.
Recover without duplicates#
Retain the original draft. If the attempt was definitely rejected before submission, update and recheck the route. If the outcome is uncertain, inspect Codex for the message before sending again.
Do not move work to a cloud environment solely because an old error text suggests it. The current documented product is a Mac Codex companion. If the message persists on the published version, report the exact error and version details using a non-sensitive test. Connection health and actual message delivery should be verified separately.