Handoffs
Write what the file is claimed to carry
Separate the object from the proof. A sender's sentence is not a completed check.
github.com published this account (2026-10-03): Anthropic published Claude Code v2.1.289. Release notes fix deny/ask rules not holding on nested compound shell commands under user-installed mods on managed machines, Read deny rules missing IDE-selected symlink paths, Bash deny/ask misses under sandbox auto-allow for environment-variable prefixes and bare assignments, a VS Code auth-status regression from 2.1.288, and a user-installed plugin rewriting organization-managed MCP sign-in tool descriptions. No CVE or CVSS is stated.
This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.
Write only what the page says
The page's claim is: Anthropic published Claude Code v2.1.289. Release notes fix deny/ask rules not holding on nested compound shell commands under user-installed mods on managed machines, Read deny rules missing IDE-selected symlink paths, Bash deny/ask misses under sandbox auto-allow for environment-variable prefixes and bare assignments, a VS Code auth-status regression from 2.1.288, and a user-installed plugin rewriting organization-managed MCP sign-in tool descriptions. No CVE or CVSS is stated.
Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.
Separate the object from the proof. A sender's sentence is not a completed check.
Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.
A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.
Stop at the untested line
Anything you did not open, install, or count stays untested. Leave that line visible.
Source page: Claude Code v2.1.289 permission and sandbox-auto-allow fixes.
Sources: Claude Code v2.1.289 permission and sandbox-auto-allow fixes