Claude Code 2.1.248

• [new] Added a --restricted CLI flag (and matching CLAUDE_CODE_RESTRICTED control) for running Claude Code in a restricted configuration.
• [improved] Directory/file sync for cloud and remote sessions is more explicit about failure and recovery: upload give-ups, quiet/offline machines, empty checkouts, long waits, one-way sync, and mid-session stoppages now surface plain status to the model so it can tell you what landed, what did not, and when to redo work on your machine.
• [changed] Artifact publishing no longer requires a favicon on every redeploy — set it on first publish; omit it on later publishes (same path or existing url) to keep the current icon, and pass a new one only when you want it changed. Artifact listings can also include favicons.
• [improved] Updating an existing artifact is stricter about reading the live version first (action: "read" with that url) before publishing, so updates build on what is actually deployed instead of creating a separate artifact.
• [improved] Clearer handling when a remote or MCP tool is unavailable: org policy/settings blocks, re-authorization required, or a disconnected server — continue without the tool and say so when the task depends on it.
• [improved] Stronger guidance for attached-machine workflows: route Bash/Read/Edit/Write to the named machine with absolute paths, keep this environment for scratch only, and say plainly when the machine is unreachable.
• [improved] MCP connector discovery is richer — list/search/resolve flows distinguish org-level install vs enabled-in-this-chat, surface custom org connectors, and avoid claiming a connector is usable when it is only authenticated but toggled off.
• [changed] Subagent defaults emphasize background work unless the next step truly depends on the result; spawning remains opt-in when the user asks, with clearer “never fabricate pending results” behavior.
• [new] Default keybinding support for ctrl+enter.
• [changed] Release binaries are substantially smaller across platforms.

Models & prompts

• Refined prompts for directory sync edge cases (gave up sending changes, session-only inbound sync, turn-boundary-only sync, cancelled agents, and “files arrive on the user’s next message”).
• Ultracode / workflow authoring text tightened: standing ultracode opt-in still means exhaustive workflows by default; workflow scripts must declare a pure-literal meta block and are plain JavaScript passed inline.
• Focus mode, brief/autonomous execution, SendUserMessage-style user-visible replies, and correction/memory timing (“write memory in the same turn you engage the correction”) are spelled out more clearly for the model.
• PR flow still optionally offers Slack posting when CLAUDE.md mentions it; Chrome tools that are deferred should be batch-loaded via ToolSearch in one call.
• GitHub CLI sessions missing the workflow scope get a direct gh auth refresh -s workflow hint before /web-setup again.

Under the hood

• New environment knobs for experimental agent teams, coordinator worker model inheritance, background worker check-in interval, directory sync streaming, and remote tools policy.
• Additional internal telemetry and feature gates around directory sync (including git worker upload/pull points), daemon upgrade deferral when busy, bridge/partial message handling, remote tool preview, and workflow skill autoload.
• New metrics API route for Claude Code.
• CDN hosts used for web/artifact-related assets (cdn.jsdelivr.net, cdn.tailwindcss.com, cdnjs.cloud).
• Removed the CLAUDE_CODE_ASSUME_FIRST_PARTY_BASE_URL assumption path; SDK compat wrapper list drops an older tested version.
• Artifacts SDK typings updated for optional favicon on list results and the first-publish-only favicon rule.

Upgrade notes

• If you rely on artifact icons, you can omit favicon on redeploys; existing icons are preserved unless you pass a new value.
• Organizations rolling out locked-down installs can start adopting --restricted / CLAUDE_CODE_RESTRICTED.
• Remote and cloud sessions may report file-sync status more often when the local machine is asleep, offline, or stops uploading — that is expected and means the session is continuing on whatever tree it already has until the next successful sync.