Lifestyle

Claude Code 2.1.321 Update: Fable 5.2 Becomes the Default Model, With Changes to mods Permissions and Enterprise Management Rules

Anthropic's official Claude Code changelog says version 2.1.321 adds Claude Fable 5.2 and makes it the default Fable model. This release also changes mods permissions, Remote Control, managed marketplaces and gateway behavior. Both general users and enterprise administrators may be affected.

About 5 min read

Claude Code 2.1.321 Update: Fable 5.2 Becomes the Default Model, With Changes to mods Permissions and Enterprise Management Rules
Image: Mokaair (Original editorial artwork)

New Model: Claude Fable 5.2

According to the official Claude Code changelog, version 2.1.321 adds Claude Fable 5.2 (claude-fable-5-2) and makes it the default version of the Fable model. The changelog says it offers a 1M context window and is priced at $8/$40 per million tokens, with cache reads at $0.20 per million tokens. Context is the amount of content a model can consider at once. A token is the unit a model uses to measure text. A cache read means reusing content that has already been processed.

Impact on existing users: according to the changelog, a saved Fable 5.1 model selection is changed to fable. This takes effect immediately on Pro and Max plans, and on Team and Enterprise plans once the organization allows it. To go back to the older version, the changelog says you can switch with /model claude-fable-5-1.

Permissions and Security: mods Behavior Has Changed

mods are components that Claude can write and load itself. The changelog says that in auto and bypass modes, mods written by Claude are enabled without asking. These two modes reduce or skip per-action confirmation. This is the case even when managed settings specify allowUnsandboxedCommands: false or allowManagedDomainsOnly. In dontAsk mode, these mods are not loaded.

In addition, according to the changelog, mods' own tool calls ($.tool.call, $.mcp.call) no longer trigger permission prompts. This holds even under user-defined ask rules, dontAsk, or -p runs. Deny rules and organization policy still apply. For general users, this means confirmation prompts may become less frequent. Teams with control requirements should check the changelog to confirm these changes comply with their rules.

Changes Enterprises and Administrators Should Note

  • According to the changelog, managed extraKnownMarketplaces (the list of plugin sources designated by an organization) has three changes: a declared name cannot be added from another source, entries with the same name from elsewhere are hidden, and plugins listed by a declared marketplace are reinstalled from it.
  • According to the changelog, the Bedrock, Vertex and Foundry upstreams of the Claude apps gateway ignore ANTHROPIC_*_BASE_URL variables in the gateway environment. To use a different endpoint, set base_url on the upstream instead.
  • According to the changelog, under policy_mode: layered, the managed MCP servers from every matching policy now add up. An MCP server is a service that provides tools to Claude. Gateways already using this mode may offer more servers after upgrading.
  • According to the changelog, Remote Control sessions stay in the folder they were started in, and connected clients can no longer move a session to another folder.

Other Changes at a Glance

Other changes in 2.1.321 (compiled from the official Claude Code changelog)
ItemChange described in the changelogWho is affected
claude remote-controlAdds a --settings file parameter applied to every session it starts; after the file changes, a restart is needed before new sessions startRemote Control users
VS CodeWhen both an auth token and an API key are set, a warning is shown above the prompt boxVS Code users
Plan namesRelated messages and settings descriptions now list Ultra in addition to Pro and MaxPaid plan users
Headless (no interactive interface) sessionsmods reload when their files change; set CLAUDE_CODE_PLUGIN_DIR_WATCH=0 to turn this offAutomation or headless users
Background command notificationsCommands over 1,000 characters show only the beginning and end, to save contextAll users
WindowsWhen locating programs, skips relative and UNC PATH entries and links pointing to network shares, and reads PATH changes in settingsWindows users
Desktop Code tabNumber of messages that can be sent to other sessions raised from 10 to 20Claude Desktop users

FAQ

What is the main change in 2.1.321?

According to the changelog, this release adds Claude Fable 5.2 (claude-fable-5-2) and makes it the default Fable model, with a 1M context window.

How much does Fable 5.2 cost?

The changelog lists a price of $8/$40 per million tokens, with cache reads at $0.20 per million tokens.

What happens to people who had selected Fable 5.1?

According to the changelog, the saved selection is changed to fable. This takes effect immediately on Pro and Max plans, and on Team and Enterprise plans once the organization allows it. You can switch back with /model claude-fable-5-1.

Do mods now show fewer permission prompts?

The changelog says mods' own tool calls no longer trigger permission prompts, but deny rules and organization policy still apply. Mods written by Claude are not loaded in dontAsk mode.

What should enterprise administrators watch for before upgrading?

According to the changelog, the source rules for managed extraKnownMarketplaces are stricter. The gateway's Bedrock, Vertex and Foundry upstreams must set endpoints through base_url. Under policy_mode: layered, managed MCP servers from every matching policy add up, so gateways already using that mode may offer more servers.

Browse the latest news in this topic

Sources

Lifestyle