Skip to content

docs(sprout-acp): add communication discipline rules to base prompt + deprecate --mention flag#883

Merged
wpfleger96 merged 7 commits into
mainfrom
duncan/base-prompt-communication-updates
Jun 5, 2026
Merged

docs(sprout-acp): add communication discipline rules to base prompt + deprecate --mention flag#883
wpfleger96 merged 7 commits into
mainfrom
duncan/base-prompt-communication-updates

Conversation

@wpfleger96

Copy link
Copy Markdown
Collaborator

Summary

Adds communication discipline rules to the agent base prompt and deprecates the --mention CLI flag.

Base Prompt Changes (crates/sprout-acp/src/base_prompt.md)

Four new bullets in the Communication Patterns section:

  1. Mention discipline — Only @name when you need their attention. Don't use @name in narrative text (e.g., "let me coordinate with @duncan") — it triggers a notification.
  2. Respond promptly to @mentions.
  3. Be direct — state what you did, found, or need. No preamble.
  4. Thread priority — when mentioned in multiple threads, prioritize the most recent chronologically. Don't bury responses in old dispatch threads.
  5. Task-completion broadcast — when you finish a task, post a top-level channel message with the result (not just an in-thread reply).
  6. Explicit thread reply guidance — replaced vague "use sprout messages thread" with explicit --reply-to <thread-root-event-id> instruction.

CLI Changes

  • --mention flag on sprout messages send is now hidden from help text and emits a deprecation warning when used
  • The flag still works (no breaking change) but agents are guided to use @name in content instead

Motivation

Agents were double-mentioning (narrative + dispatch), burying task completions in threads, and responding in stale threads. These rules codify the communication patterns that produce good human UX.

The --mention flag creates confusing silent notifications (p-tag with no visible @name in text). After team discussion, we concluded there's no legitimate use case for human-facing messages — deprecating to prevent agent confusion from help text discovery.

@wpfleger96 wpfleger96 requested a review from a team as a code owner June 5, 2026 19:26
@wpfleger96 wpfleger96 marked this pull request as draft June 5, 2026 19:29
The base prompt had formatting guidance for @mentions but no guidance
on when to use them. Agents were double-mentioning by narrating intent
('let me ask @duncan') then dispatching separately. Also missing were
universal expectations around responsiveness, directness, and explicit
--reply-to usage in threads.
The previous wording said 'only @mention' which implied a separate flag.
The relay auto-resolves @name in message content to p-tags, so writing
@name anywhere in text IS the notification trigger. Reword to make the
mechanism explicit and the rule unambiguous.
The --mention flag added explicit p-tag mentions without @name in content,
creating silent notifications with no visible context in the message. This
violates the notification contract: if you're pinged, you should see why.

Auto-resolution of @name in message content is the only mention mechanism.
Remove the flag entirely — no deprecation period needed for something this
harmful to UX.
The --mention flag was removed from sprout messages send. Update three doc
files that still taught the old behavior:

- nest_skill.md: rewrite 'Mentions that notify' section — @name in content
  is auto-resolved, no flag needed. Remove the incorrect 'display-only' claim.
- TESTING.md: drop --mention from the ACP agent test example
- crates/sprout-cli/TESTING.md: replace --mention example with auto-resolve note
@wpfleger96 wpfleger96 force-pushed the duncan/base-prompt-communication-updates branch from 58e1f2e to f59a4d9 Compare June 5, 2026 19:48
@wpfleger96 wpfleger96 marked this pull request as ready for review June 5, 2026 19:50
@wpfleger96 wpfleger96 merged commit 2f50011 into main Jun 5, 2026
16 checks passed
@wpfleger96 wpfleger96 deleted the duncan/base-prompt-communication-updates branch June 5, 2026 19:52
wpfleger96 added a commit to wpfleger96/ai-agent-rules that referenced this pull request Jun 5, 2026
…/sprout#883 (#87)

The base prompt now owns "respond promptly to @mentions", "be direct",
and thread reply syntax — carrying them in the pack creates drift risk.
Also aligns Paul and Duncan with the new task-completion broadcast rule
(post final synthesis/completion as a top-level message, not only in-thread).
michaelneale added a commit that referenced this pull request Jun 6, 2026
* origin/main:
  chore(release): release version 0.3.12 (#886)
  Show hover cards for inline message emoji (#885)
  Fix monotonic read-state merges (#884)
  Refine sidebar behavior and borders (#869)
  fix(presence): clear on disconnect, fix heartbeat/TTL, drop broken REST path (#877)
  fix(cli): publish ephemeral events over WebSocket via sprout-ws-client (#876)
  docs(sprout-acp): add communication discipline rules to base prompt + deprecate --mention flag (#883)
  Polish thread summaries and reactions (#881)
  feat(cli): add emoji export and import subcommands (#882)
  Polish message row hover states (#880)
  Improve emoji naming and custom emoji UX (#878)
  docs: add ecosystem section to CONTRIBUTING.md, fix stale release info (#873)
  fix(relay): wire custom filter fields through HTTP bridge (#864)
  chore: deprecate sprout-mcp — fill CLI gaps, remove crate and all references (#850)
  Fix custom emoji status in profile popover (#874)
  fix(agent): gate handoff on provider token usage, not byte estimate (#821)
  docs: add VISION_MESH.md — the compute-commons vision (#867)
  fix(desktop): simplify profile popover header (#853)
  fix(desktop): remove thread comment hover outline (#861)
  feat(desktop): always show channel section search/add buttons (#856)

# Conflicts:
#	crates/sprout-cli/src/client.rs
#	desktop/src/app/AppShell.tsx
#	justfile
tellaho pushed a commit that referenced this pull request Jun 8, 2026
… deprecate --mention flag (#883)

Signed-off-by: Taylor Ho <taylorkmho@gmail.com>
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.

1 participant