Repository navigation
Keep replies to everyone on a message in one thread - #50
Merged
Merged
Conversation
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
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.
Agents replying to a message that had other To or Cc recipients used a plain
primitive reply, which addresses only the sender, then sent the answer again with--all, and started new emails withprimitive sendfor follow-ups on the same topic. Each distinct thread and recipient set shows as its own conversation, so one discussion became several and copied recipients missed replies.Changes to primitive-connect:
--allwhen the message has other To or Cc recipients, never drop recipients silently (say so when a reply is deliberately private), and continue an existing discussion in its thread rather than with a newprimitive send.reply_allonPOST /emails/{id}/reply), and how to bring a new person into an ongoing discussion while keeping its history (primitive send --in-reply-to).Flags referenced (
reply --id,--thread,--all;send --in-reply-to,--to,--cc) were checked against the current CLI help. SKILL.md stays under the size budget (22565 bytes).npm testpasses (79 tests).No ticket: skill guidance change.