fix(messages): simplify sending and message lookup - #11
Merged
Merged
Conversation
Bjornftw
approved these changes
Sep 27, 2026
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
2 participants
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.
Sending a message currently requires an idempotency key, and the printed delivery command fails when no project is saved. Make the key optional and let messages get, events, and content use the message ID within the selected profile. Only an explicit --project restricts these lookups.
Omit the idempotency header when no key is supplied. Keep duplicate protection for explicit keys and reject empty or oversized values. Include the resolved profile in the delivery command. Update retry guidance, help, and documentation.
Validation: go test -race -p 1 ./..., go vet ./..., and terminal and pipe checks passed on this branch. Tests cover absent and invalid keys, a copied delivery command, project filters, events pagination, and retry guidance. The local terminal-check build used -buildvcs=false because Go could not read VCS status in this worktree.
Requires deployment of https://github.com/lettermint/lettermint/pull/2524 before a CLI release. Without a key, each send command creates a new message. No key is generated and no automatic retry is added.