Claude Code Update: Fable 5.2 Defaults and Permission Fixes

Claude Code Update: Fable 5.2 Defaults and Permission Fixes

  • Claude Fable 5.2 is now the default Fable model.
  • Remote Control applies a settings file to each new session.
  • The update fixes OAuth and Bash permission issues.

Claude Code update v2.1.321: what changed

Fable now defaults to Claude Fable 5.2

Claude Code Update: Fable 5.2 Defaults and Permission Fixes

Claude Code's default Fable model is now Claude Fable 5.2. Its model identifier is claude-fable-5-2, and its context window is 1M.

The listed price is $8/$40 per Mtok, with cache reads at $0.20/Mtok. The release notes do not say which request types the two rates apply to.

Itemv2.1.321 changeCondition or label
Fable default modelClaude Fable 5.21M context
Enterprise usage noticeUpdated notice for plans that include FableAfter switching, it displays “Draws from usage credits”

Remote Control reads a settings file for each session

Remote Control starts a Claude Code session remotely. This Claude Code update adds the --settings <file> option, which applies the specified settings file to every session started with it.

Editing the settings file does not make an already running Remote Control process load the changes for new sessions. After changing the file, restart claude remote-control to start sessions with the updated settings.

  1. Specify a settings file with --settings <file> when you run claude remote-control.
  2. If you edit the settings file, restart claude remote-control.

OAuth and Bash permission checks are fixed

Claude Code Update: Fable 5.2 Defaults and Permission Fixes

A problem that sent secrets such as refresh tokens when an MCP server redirected an OAuth request to another host has been fixed. MCP is the server protocol Claude Code uses to connect to external tools.

The update also fixes cases where read-only Bash commands ran outside the sandbox without a permission check. Bash could misidentify where a command would write a file and skip asking for permission. The fixes also cover deny rules and protected-file checks that were not applied to files copied or moved into a directory with cp or mv.

Fast mode falls back to standard speed on the same model

Claude Code Update: Fable 5.2 Defaults and Permission Fixes

When fast mode hit a rate limit or the server was overloaded or in an error state, Claude Code could lose a response, switch models, or retry for a long time. It now tries standard speed on the same model first.

Developers using fast responses may see fewer model switches or long retries after a temporary fast-serving problem. The release notes describe the fallback only as trying standard speed on the same model.

Project tools return when a work folder comes back

A fix addresses a problem where skills, commands, and agents stayed missing after a project folder disappeared and then returned. The release notes give workflows involving git stash or entering a worktree as examples.

The issue could occur when the folder returned during a session, and after entering a worktree. If you use either workflow, check whether the project tools reappear in the menu after restoring the folder.

If you use git stash to clear a project folder and then restore it, check the session menu to see whether skills and commands are visible again.

FAQ

Does 1M context apply to every Claude Code model?

The release notes list 1M context for Claude Fable 5.2. They do not say whether the same value applies to other models.

Are $8/$40 per Mtok the input and output rates?

The release notes list $8/$40 per Mtok and cache reads at $0.20/Mtok. They do not specify which request type each of the $8 and $40 rates applies to.

Did anything change on Windows?

Yes. On Windows, a bug caused FileChanged hooks set with watchPaths to stop after the first shell command when the drive letter in the working path was lowercase. The issue is fixed.

댓글