ai-powered-markdown-translatorArticle translated from fr to en with gpt-5.4-mini.
The v2.1.143 update to Claude Code, released on the night of May 15 to 16, 2026, strengthens plugin management and improves token cost visibility for developers. On the media side, Kling AI makes its debut at the Cannes Film Market.
Claude Code v2.1.143: plugins, context cost, and macOS fixes
May 15, 2026 (10:28 PM UTC) — Claude Code v2.1.143 introduces several targeted improvements around plugin management, background sessions, and agent tooling.
Key new features:
| Feature | Detail |
|---|---|
| Plugin dependency enforcement | claude plugin disable refuses if a dependent plugin is active, with a suggestion to disable in sequence |
| Projected context cost | Token cost estimate (per turn and per invocation) visible in the /plugin panel |
worktree.bgIsolation: "none" | Allows background sessions to edit the working directory directly without going through EnterWorktree |
claude agents: new flags | --add-dir, --settings, --mcp-config, --plugin-dir, --permission-mode, --model, --effort |
| Background session model preservation | Background sessions keep the model and effort level defined after waking from inactivity |
Notable fixes: the macOS bug blocking access to files under ~/Documents, ~/Desktop and ~/Downloads even with Full Disk Access granted is resolved. Infinite-loop stop hooks now end the session after 8 consecutive blocks (configurable via CLAUDE_CODE_STOP_HOOK_BLOCK_CAP). PowerShell now gets -ExecutionPolicy Bypass by default (opt-out via environment variable).
Briefs
- Kling AI at the Cannes Film Market 2026 — The Chinese video generation tool will hold a conference on the main stage of the Palais des Festivals on May 18, 2026 (3:30 PM–5:30 PM CEST), covering its role in high-end cinematic creation and its next international steps. 🔗 source
What this means
The projected context cost feature addresses a concrete need from heavy Claude Code users: knowing how much each turn costs before confirming it. It is a first step toward better control of spending in long-running agentic workflows.
The worktree.bgIsolation: "none" setting reflects an evolution in the philosophy of background sessions — less default isolation for teams that prefer direct access, with the option to return to the previous secure behavior.