[dev] feat: per-agent mention detection, sender context, and reply handling#6
Closed
sherodtaylor wants to merge 5 commits into
Closed
[dev] feat: per-agent mention detection, sender context, and reply handling#6sherodtaylor wants to merge 5 commits into
sherodtaylor wants to merge 5 commits into
Conversation
- Replace vague "display name" hint with a concrete example of Element X's markdown link format so bots reliably detect mentions in that form. - Add Sender context section so bots know who they are speaking with and can personalize responses (sherod = team lead, agents = peers, etc.). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…t awareness" This reverts commit 78d36a6.
Add to each agent's CLAUDE.md: - Explicit name-matching rules (plain text, markdown link, full Matrix ID) with a concrete Element X link example for that agent's identity. - Reply-context trigger: respond when a Matrix reply targets the agent's own prior message, incorporating the quoted context in the response. - Sender context: read the `sender` attribute and address @sherod directly, treat peer agents as colleagues, and guests with caution. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sherodtaylor
changed the title
- Add '## Message verbosity' section to shared CLAUDE.md: 1-2 sentence cap for confirmations, bullets for multi-item info, no filler openers. - Add UserPromptSubmit hook to shared settings.json that injects an additionalContext verbosity reminder on every incoming Matrix message, reinforcing the CLAUDE.md rules at the hook layer. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Never print/echo/log secrets. Generate and pipe directly to destination. Redirect sensitive stdout to /dev/null or the consuming tool. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
Author
|
Closing — superseded by a clean branch off main. The unique changes (secret handling + verbosity hook) are in a new PR. |
sherodtaylor
added a commit
that referenced
this pull request
May 26, 2026
Dockerfile sets zsh as root's default shell (chsh -s /bin/zsh root). entrypoint.sh starts both panes explicitly with zsh instead of bash. The previous bash workaround was added to avoid dotfiles .zshrc sourcing workspace paths that don't exist in the container. That root cause is addressed in sherodtaylor/dotfiles PR #6 (guarded source calls + bootstrap.sh for proper curl|bash install). With that fix in place, zsh panes work as intended. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sherodtaylor
pushed a commit
that referenced
this pull request
Jun 27, 2026
- Move file to docs/product/agent-smith/prds/ — agent-smith is an external product with its own product-area home (D2 reworded; homelab references removed per Sherod 2026-06-27). - Drop NATS publishing from v1 per devbot's YAGNI consult; lock the transport-agnostic JSON schema in D10 + AC body so dropping it onto NATS later is additive. - Loosen latency AC to ~30s for v1 polling, tightens to ~5s when sidecar moves to Claude Code hook registration (finding #4). - Fix Open Q #2: claude --output-format=json is response output, not state events — point at Claude Code hooks instead (finding #3). - Add herdr-vocabulary interop note to D6 (finding #6). - Add Tailscale prereq to AC #1 (nit). - Clarify brandbot consumer is out of scope (nit). - Add explicit per-tool-call telemetry non-goal. - Revision history section. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
What was asked
What changed
agents/devbot/CLAUDE.mdandagents/infrabot/CLAUDE.mdEach file now has a "When to respond" section with three explicit triggers:
Direct mention — name appears anywhere in raw message text (plain text, markdown link, or full Matrix ID). Concrete Element X link example is included so the agent recognises the
[name 💕](https://matrix.to/...)form.Reply to own message — the plugin surfaces a quoted
>block; if the original message was sent by that agent's Matrix ID, the agent responds and incorporates the original context.Mention inside a reply — name appears in reply text (same as trigger 1, just clarified in reply context).
Each file also has a "Sender context" section instructing the agent to read the
senderattribute from the<channel>tag:@sherod→ team lead, address directly and conciselyHow to verify
@infrabot check cluster statusin Element X → InfraBot replies.@devbot what's the status?in a thread → DevBot replies and references thread context.check clusterwith no name.🤖 Generated with Claude Code