Claude Code v2.1.200

The Claude Design tool gained a substantial set of new operations for managing design projects:

• finalize_plan — Finalizes a plan for writing to claude.ai/design; approval also grants prompt-free writes to plan paths for 15 minutes
• write_files — Write files to the design project
• copy_files — Copy files within the project
• delete_files — Delete files from the project
• render_preview — Render a design preview
• create_support_js — Create a support.js file
• add_member — Add a project member
• update_member_role — Change a member's role
• remove_member — Remove a project member
• update_sharing — Update project sharing settings

The project_write tool also gained a present_to_user parameter (boolean, default false) to mark a document as the user-facing deliverable. Setting it to true on routine saves is explicitly discouraged to avoid unnecessary cache busting.

When a finalize_plan operation is approved, writes and deletes to the exact paths listed in the plan are automatically permitted for up to 15 minutes without additional prompts. The approval dialog now shows:

> "Approving also lets writes and deletes to exactly these paths run without another prompt for up to 15 minutes (file contents are not shown again; anything to any other path will still ask)."

The /claude-code skill (which answers questions about Claude Code itself) now covers Claude Tag — Anthropic's Slack-native teammate surface. Its description was updated to include "and Claude Tag (Claude in Slack)." A new bundled reference file (references/claude-tag.md) provides offline documentation for Claude Tag, and the live-sources reference now maps Claude Tag topics to their docs URLs at claude.com/docs/claude-tag/.

Key points bundled:

• Claude Tag replaces the earlier per-user "Claude in Slack" app
• Users @Claude in a thread; an org-managed remote Claude Code session handles the task
• Configuration (repos, tools, spend limit) is an org-owner action at claude.ai/admin-settings/claude-tag
• The recent-changes.md reference now notes: "Claude in Slack (the earlier Slack app)" → "Claude Tag"

The mTLS client certificate implementation was refactored to support hot-reloading. Previously, certificates were loaded once at startup (via a singleton). Now:

• Certificates are re-read from disk whenever CLAUDE_CODE_CLIENT_CERT or CLAUDE_CODE_CLIENT_KEY changes
• An async reload function queues sequential refreshes (no concurrent reloads)
• The HTTPS agent is rebuilt only when the certificate content actually changes
• Path and content are both tracked to detect file replacement vs. content changes

Error messages are now more descriptive, reporting the certificate role (e.g., "client certificate from CLAUDE_CODE_CLIENT_CERT") rather than the file path.

The diff panel now handles new git repositories that have staged files but no commits yet:

• Shows "Staged and new files" as the panel title (instead of "Branch changes")
• Shows "(no commits yet)" in the subtitle

When an unrecognized model ID is passed (e.g., via /model or --model), the error message now:

• Checks if the input looks like a display name and suggests the correct model ID
• Uses fuzzy matching to find the closest valid model ID if available
• Falls back to "Run /model to see available models." when no good match is found

Example output: Model "claude4" is not a recognized model id. Did you mean 'claude-opus-4-5'?

The HTTP error handler for memory operations now parses the server error body and maps specific server error messages to typed error codes:

• "memory store has reached its memory limit" → store_full
• "content must be at most 102400 bytes" → content_too_large
• "memory content appears to contain a credential or API key" → content_secret
• Path validation failures ("path must be at most 1024 bytes", "path must be NFC-normalized", etc.) → invalid_path
• "cannot modify archived resource" → store_archived

Users will see more specific notifications when memory writes fail for these reasons, rather than generic HTTP error messages.

Error messages that previously said "Run /plugins to refresh the plugin cache" now say "Run /plugin to refresh the plugin cache" — matching the actual command name.

The bundled /verify skill description was updated to note that it "bootstraps this repo's project verify skill if none exists yet." It will create .claude/skills/verify/SKILL.md in the appropriate location if the project doesn't have one. The guidance was also refined: verify corrections that are project-specific should go in the closest-scoped skill file and should never be duplicated at broader scopes.

The guidance for the feedback memory (when Claude corrects a repeatable step) was tightened:

• Previously: "Edit existing skill files rather than creating new ones (a new project skill shadows a same-named built-in skill), with one exception: if the correction is about how to verify changes in this repo and .claude/skills/verify/SKILL.md does not exist, create it."
• Now: "Edit existing skill files only; never create one — a new project skill silently shadows a same-named built-in skill. The single exception is verify..."

The verify exception also gained guidance about scoping: the correction goes in the closest-scoped verify/SKILL.md (repo root vs. subproject), never duplicated.

The regex for detecting potentially destructive gh CLI operations was updated to use the gh subcommand format (e.g., gh pr create, gh issue comment) matching the actual gh CLI syntax. The regex now covers: gh pr create, gh pr merge, gh issue create, gh issue comment, gh release create, gh repo fork

Agent context objects for background (sidecar) agents now carry an isBackgroundAgent: true field. This enables the system to distinguish background agents from in-process subagents without relying on agentType alone.

When replaying session history from disk, the history parser now filters out any control_request events whose matching control_response or control_cancel_request never arrived in the recorded log. This prevents stale pending permission dialogs from re-appearing when a session is resumed.

• isDirEmptySync was replaced with an async opendir-based empty-check, removing a synchronous I/O call from the directory scan path (search for "isDirEmptySync" is now absent)
• TeammateTool member removal now guards against stale removals: if a member re-joined between when a removal was initiated and when it executes, the removal is skipped with a log message "Skipped stale removal" (search for "re-added after removal was initiated")
• Observer pairing is now retired when a session resumes (lir() called on session start), preventing a stale observer from a previous run from being reused across sessions
• plansDirectory validation now correctly handles the case where the configured path resolves to exactly the project root (previously the check !s.startsWith(o + sep) would incorrectly reject root-equal paths)
• The Cd(...) rule check for paths containing control or invisible characters now suppresses the path from the error message to avoid terminal injection (search for "The rule text contains control or invisible characters, so it is not echoed here")

New error messages and recovery flows for Remote Control session resume failures were added, including clearer messages when a session cannot be found or has expired:

• "Couldn't reconnect to your Remote Control session. Retry, or start a fresh session without --resume."
• "Error: No recent session found in this directory or its worktrees. Run claude remote-control to start a new one."
• Better handling of the "environment expired" case: creates a fresh session instead of failing