Ack delivery_unconfirmed as telemetry and label peer-agent senders - #2
Merged
Merged
Conversation
text.delivery_unconfirmed is carrier uncertainty, not a failure: route it out of the delivery-failure capture so the agent is never woken to resend a message that usually landed. Real failures are untouched. Inbound turns from a sender with no contact match but exactly one backend-resolved agent identity now carry that identity in the frame tag (id, quoted handle, quoted display name) instead of unknown_in_inkbox. Contacts always win; zero or many identities fall back to unknown; mail trusts only the from-bucket entry matching the sender's address. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dimavrem22
marked this pull request as ready for review
July 13, 2026 01:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports two merged fixes from the sibling plugins.
Don't wake the agent on
text.delivery_unconfirmedPorts inkbox-ai/claude-code-plugin#36. The event is carrier uncertainty — the message usually landed — so it no longer routes into the delivery-failure capture that nudges the agent to retry. It is now acked and logged, and the gateway stays subscribed to it.
text.delivery_failed,imessage.delivery_failed, and mail bounce/fail behavior are unchanged.Label a contactless sender with their resolved agent identity
Ports inkbox-ai/openclaw-plugin#33. When a 1:1 sender has no address-book contact but the webhook resolved exactly one
agent_identitiesentry, the frame tag and reaction labels now carry that identity (contact_agent_identity_id, quotedcontact_agent_handle, quotedcontact_name) instead ofcontact=unknown_in_inkbox. A contact match always wins; zero or several identities keep the unknown fallback; mail trusts only thefrom-bucket entry whose address matches the normalized sender; phone-channel groups keep their existing framing. Handle and display name are remote-controlled, so both are JSON-quoted in the tag.