Claude Code v2.1.321 Adds Fable 5.2, Remote Control Settings, and Network Edit Fixes
What changed
Anthropic has released Claude Code v2.1.321, introducing support for new models, configuration options, security patches, and file-system bug fixes across local and remote environments.
Key updates in this release include:
- Claude Fable 5.2 Integration: Added
claude-fable-5-2as the default Fable model. It features a 1-million-token context window, priced at 40 per million output tokens, and $0.20 per million tokens for prompt cache reads. - Remote Control Settings Configuration: The
claude remote-controlcommand now accepts a--settings <file>flag to apply a unified settings configuration across all spawned sessions. If the specified file is modified on disk, new sessions are blocked untilclaude remote-controlis restarted. - Sandbox and Security Patches: Resolved an issue where Model Context Protocol (MCP) OAuth flows leaked secrets, such as refresh tokens, to unverified hosts following a server redirect. Fixed sandbox bypasses where read-only Bash commands executed without user prompts, corrected folder context evaluation during Bash file write checks, and enforced deny rules and protected-file prompts when
cpormvcommands target directories. These follow previous security hardening efforts in v2.1.309. - Network Directory and File Editing Fixes: Addressed destructive editing bugs occurring over UNC shares, WSL folders, and
/netmounts. FixedNotebookEditcalls deleting or overwriting the initial notebook cell when no cell index was specified. ResolvedEditfailures that replaced entire files on emptyold_stringinputs or treated notebooks as plain text on network mounts. - Hook and Environment Stability: Building on the hook controls in v2.1.295, this release fixes Windows
FileChangedhooks stalling on lowercase drive letters when monitoringwatchPaths. Resolved conflicts betweenPreToolUsehooks (askanddeferreasons) and corrected large hook output files overwriting unrelated outputs from the same tool call. Cloud sessions no longer match parent processes duringpkill,pgrep, orpidwaitoperations.
Why it matters
Developers running Claude Code across network drives, containers, or remote environments frequently face platform-specific edge cases. The fixes to NotebookEdit and path resolution prevent accidental data destruction on WSL and SMB/UNC mounts.
For enterprise operators, the new --settings flag in claude remote-control enables stricter policy enforcement across remote sessions, while the OAuth redirect fix eliminates a high-risk credential exposure vector when connecting to external MCP servers.
What to do next
- Update to the latest release using your package manager or CLI updater.
- If using remote management, supply
--settings <file>when initializingclaude remote-controlto enforce global session parameters. - Verify custom MCP server integrations that rely on OAuth flows to ensure redirects operate cleanly without dropping tokens.
Limitations
When using --settings <file> under claude remote-control, hot-reloading is intentionally disabled: editing the configuration file halts new session creation until the underlying background daemon process is completely restarted.
Sources
Share Article
If this article helped you, please share it with others!