Week 14 · March 30 – April 3, 2026
- Source ID:
src-20260420-07ab9859a2eb - Kind:
document - Scope:
shared - Origin: https://code.claude.com/docs/en/whats-new/2026-w14.md
- Raw path:
sources/raw/week-14-march-30-april-3-2026__src-20260420-07ab9859a2eb.md - Status:
active
Tags
official-docs claude-code-cli
Content
Documentation Index
Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.
Week 14 · March 30 – April 3, 2026
Computer use in the CLI, interactive in-product lessons, flicker-free rendering, per-tool MCP result-size overrides, and plugin executables on PATH.
Last week computer use landed in the Desktop app. This week it's in the CLI: Claude can open native apps, click through UI, test its own changes, and fix what breaks, all from your terminal. Web apps already had verification loops; native iOS, macOS, and other GUI-only apps didn't. Now they do. Best for closing the loop on apps and tools where there's no API to call. Still early; expect rough edges.
Run /mcp, find computer-use, and toggle it on. Then ask Claude to verify a change end to end:
Interactive lessons that teach Claude Code features through animated demos, right inside your terminal. Claude Code releases frequently, and features that would have changed how you work last month can slip by. Run /powerup once and you'll know what's there.
Run it:
```text Claude Code theme={null} > /powerup ``` Commands referenceOpt into a new alt-screen renderer with virtualized scrollback. The prompt input stays pinned to the bottom, mouse selection works across long conversations, and the flicker on redraw is gone. Unset CLAUDE\_CODE\_NO\_FLICKER to roll back.
Set the env var and restart Claude Code:
```bash theme={null} export CLAUDE_CODE_NO_FLICKER=1 claude ``` Fullscreen renderingMCP server authors can now raise the truncation cap on a specific tool by setting anthropic/maxResultSizeChars in the tool's tools/list entry, up to a hard ceiling of 500K characters. The cap used to be global, so tools that occasionally returned inherently large payloads like database schemas or full file trees hit the default limit and got persisted to disk with a file reference. Per-tool overrides keep those results inline when the tool really needs them.
Annotate the tool in your server's tools/list response:
Place an executable in a bin/ directory at your plugin root and Claude Code adds that directory to the Bash tool's PATH while the plugin is enabled. Claude can then invoke the binary as a bare command from any Bash tool call, with no absolute path or wrapper script needed. Handy for packaging CLI helpers next to the commands, agents, and hooks that call them.
Add a bin/ directory at the plugin root:
Other wins
PermissionDenied hook fires on classifier denials (return retry: true to let Claude try a different approach), and /permissions → Recent lets you retry manually with rdefer value for permissionDecision in PreToolUse hooks: -p sessions pause at a tool call and exit with a deferred\_tool\_use payload so an SDK app or custom UI can surface it, then resume with --resume/buddy: hatch a small creature that watches you code (April 1st)disableSkillShellExecution setting blocks inline shell from skills, slash commands, and plugin commandscat or sed -n without a separate ReadshowThinkingSummaries: true to restore)claude-cli:// deep links accept multi-line prompts (encoded %0A)