Skip to content

feat(slack): tighten mention tokens and nudge toward PRs for code-fixable issues #2691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
VojtechBartos merged 3 commits into from
Jun 17, 2026
+4 −1
Merged

feat(slack): tighten mention tokens and nudge toward PRs for code-fixable issues #2691

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
755e840
feat(slack): nudge users toward opening a PR for code-fixable issues
VojtechBartos Jun 16, 2026
b9cb6a1
feat(slack): forbid fabricating mention tokens
VojtechBartos Jun 17, 2026
98a4802
chore(slack): swap real name in mention prompt example for a placeholder
VojtechBartos Jun 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion packages/agent/src/server/agent-server.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1731,7 +1731,10 @@ You are replying in a Slack thread. Slack readers want short, skimmable answers
- This is a default, not a hard rule. If the user (or their saved memory) asks for more depth or a specific format, follow that instead.

# Mentioning users
When you want to ping a Slack user in your reply, copy their \`<@U…|displayname>\` token verbatim from the message context — Slack renders that as a real mention. Writing \`@displayname\` as plain text does NOT ping them.
To ping a Slack user, reuse a \`<@U…|displayname>\` token that already appears in the message context — copy it verbatim, including the \`U…\` ID. Do NOT construct a mention token from a name, and do NOT substitute the display name (or any other string) for the \`U…\` ID — \`<@Jane|Jane Doe>\` is not a valid mention; only the form with the real ID like \`<@U01ABCDEF23|Jane Doe>\` is. If the person you want to refer to has no \`<@U…|displayname>\` token anywhere in the thread context, write their name as plain text instead of inventing one.

# Suggesting code changes
You can also open pull requests directly from this Slack thread. When the user's question describes a problem with a plausible code-side fix — a bug visible in errors or logs, missing or broken instrumentation, a broken funnel step traceable to UI code, a stale config that lives in a repo — end your reply with a one-sentence offer to open a PR for the fix and ask if they want you to proceed. Skip the offer for pure data lookups with no actionable code change (e.g. "what was DAU yesterday?"), and skip it when the fix would clearly live outside any repo you can reach.
Comment thread
VojtechBartos marked this conversation as resolved.
`
: "";
const signedCommitInstructions = `
Expand Down
Loading