Paste into Claude Code / CLAUDE.md task

# DevAgentRadar → Claude Code

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

## Context
Assistant: Claude Code
Proposal: Enable Focus view and sandbox mode:"mask" credentials in Claude Code
Summary: Turn on VS Code Focus view (Ctrl+Alt+F) to collapse tool noise, switch Linux/WSL sandbox credential files to mode:"mask", and run prompt-audit plus claude plugin validate so prompts and marketplace names stay compatible with v2.1.221.
Primary source: https://github.com/anthropics/claude-code/releases/tag/v2.1.221

## Why it matters
v2.1.221 adds Focus view in VS Code: a chat-menu toggle that hides tool activity behind an expandable per-turn summary with a live running-tool indicator (Ctrl+Alt+F or "Claude Code: Toggle Focus view"). It also adds mode:"mask" for sandbox credential files on Linux and WSL—sandboxed commands read a sentinel copy (whole file or extract-regex spans) while the sandbox proxy substitutes real values on egress; macOS still falls back to deny. The release further adds claude plugin validate warnings for names Claude Desktop’s managed marketplace sync would reject, and a prompt-audit subcommand on the claude-api skill for patterns aimed at older models. Adopting these three surfaces cuts IDE clutter, keeps secrets out of the sandbox filesystem, and catches plugin/prompt breakage before Desktop sync or model upgrades.

## Suggested actions
1. In VS Code, press Ctrl+Alt+F or run the command "Claude Code: Toggle Focus view" and leave Focus view on so tool activity stays hidden behind expandable per-turn summaries with the live running-tool indicator.
2. On Linux/WSL hosts, configure sandbox credential files with mode: "mask" (whole file or spans captured by an extract regex) so sandboxed commands only read sentinel copies while the sandbox proxy substitutes real values on egress; keep macOS on the deny fallback.
3. Invoke the prompt-audit subcommand of the claude-api skill on your prompt templates and tool descriptions and rewrite any patterns it flags as written for older models.
4. Run `claude plugin validate` on every local marketplace and plugin package and rename any marketplace or plugin name that warns it would be rejected by Claude Desktop managed marketplace sync.

## Config surfaces this release may change
- skills **(high confidence)** — check your repo before applying
- agent context files **(high confidence)** — check your repo before applying
- sandbox settings — check your repo before applying
- permission rules — check your repo before applying
- MCP servers — check your repo before applying
- settings files — check your repo before applying
- background and headless runs — check your repo before applying


## Your job
1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.