{"version":"2.1.309","anchor":"new-bash-tool-guidance-on-bare-at-mentions-in-github-text","canonical_anchor":"new-bash-tool-guidance-on-bare-at-mentions-in-github-text","heading":"Claude now avoids accidental @mentions in pull requests and issues","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/new-bash-tool-guidance-on-bare-at-mentions-in-github-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude now avoids accidental @mentions in pull requests and issues\n\nClaude is now told to write a bare @name in GitHub text only for a real person it means to notify, and to put other @ words in backticks\n\n**What**\n\nGitHub sends a notification to the owner of any `@name` written in a pull request, issue or comment. The instructions Claude gets for its Bash tool (the tool it uses to run commands such as `gh`) now include a rule about this:\n\n- Write a bare `@name` only for a real GitHub login that is meant to be notified.\n\n- Put roles, placeholders and code, such as `@human`, `@reviewer` or `@types\/node`, in backticks, or leave out the `@`.\n\nThe same rule also appears in the instructions for agents and in the instructions used when a long conversation is summarised to save space. The Bash tool's description changed in this release to carry it.\n\n**Why**\n\nPull requests and issues that Claude writes should no longer ping strangers who happen to own a GitHub account called something like `reviewer`, or a package name.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}