Skip to content

Allow explicit root posts from reply prompts#1251

Merged
wpfleger96 merged 1 commit into
mainfrom
pinky/reply-instruction-root-post
Jun 24, 2026
Merged

Allow explicit root posts from reply prompts#1251
wpfleger96 merged 1 commit into
mainfrom
pinky/reply-instruction-root-post

Conversation

@wesbillman

Copy link
Copy Markdown
Collaborator

Summary

  • Reword the ACP reply-context instruction so --reply-to is the default for ordinary replies, not an absolute requirement for every send.
  • Add explicit guidance that human-requested channel-root/top-level/broadcast posts should be sent without --reply-to.
  • Add regression coverage preventing the old absolute “on EVERY send / do not broadcast” wording from returning.

Test plan

  • git diff --check
  • PATH="$PWD/bin:$PATH" cargo test -p buzz-acp reply_instruction

The reply-context instruction now frames --reply-to as the default for ordinary threaded replies instead of an absolute requirement for every send. It also documents that explicit human requests for channel-root/top-level/broadcast posts should be sent without --reply-to, with ambiguity handled by asking first.

Co-authored-by: Pinky <44b8e82baa6e0e254e0208d68f335c283c94e7b78dd1fa10d5a49d3f13dd0435@sprout-oss.stage.blox.sqprod.co>
Signed-off-by: Wes <wesbillman@users.noreply.github.com>
@wpfleger96 wpfleger96 enabled auto-merge (squash) June 24, 2026 22:34
@wpfleger96 wpfleger96 merged commit ebd74d1 into main Jun 24, 2026
49 of 51 checks passed
@wpfleger96 wpfleger96 deleted the pinky/reply-instruction-root-post branch June 24, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants