ANTHROPIC PUB_DATE: 2026.04.01

CLAUDE CODE 2.1.89 SHIPS AFTER 2.1.88 SOURCE LEAK; RELIABILITY FIXES LAND AND "COMPUTER USE" PREVIEW EXPANDS SCOPE

Anthropic briefly leaked the Claude Code CLI source via v2.1.88, then shipped v2.1.89 with key reliability fixes while "computer use" rolls on in preview. Per ...

Anthropic briefly leaked the Claude Code CLI source via v2.1.88, then shipped v2.1.89 with key reliability fixes while "computer use" rolls on in preview.

Per reporting, v2.1.88’s npm package exposed a source map that revealed the CLI’s TypeScript codebase; Anthropic called it a packaging error with no customer data involved (Ars Technica, analysis via Data Studios).

v2.1.89 focuses on stability and control: a nasty StructuredOutput schema cache bug (~50% failure with multiple schemas) is fixed, long‑session memory leaks are patched, LSP zombie processes now auto‑restart, and permission hooks add finer control. See the notes on defer/retry hooks, non‑blocking MCP in -p mode, and UI/Windows fixes in the release page.

Separately, "computer use" (macOS, research preview) lets Claude drive GUIs from the CLI for build validation and end‑to‑end UI testing; it requires v2.1.85+, Pro/Max, and interactive sessions docs.

[ WHY_IT_MATTERS ]
01.

The leak is a supply‑chain and trust red flag; adversaries and competitors can study internals while the community pores over guardrails and tools.

02.

v2.1.89 removes high‑impact failure modes (schema cache, memory leak, LSP restart), directly improving reliability for agent pipelines and CI use.

[ WHAT_TO_TEST ]
  • terminal

    Hammer multi‑schema StructuredOutput workflows and long‑running sessions to confirm failure drops and memory stays flat post‑upgrade.

  • terminal

    Exercise PreToolUse/PermissionDenied hooks with deferred tool calls and auto‑mode retries, and verify non‑blocking MCP behavior in -p mode.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Purge 2.1.88 from caches and lock to 2.1.89+. Audit your own build to ensure source maps aren’t shipped in production artifacts.

  • 02.

    Review permissions policy with new defer/retry hooks; log and gate risky commands. Rebaseline /stats after token undercounting fix.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Consider "computer use" for lightweight GUI E2E tests on macOS in dev benches; keep it out of headless pipelines for now.

  • 02.

    Design agent flows assuming MCP can be non‑blocking; add explicit retries on denials and structure tool schemas to avoid cache edge cases.

SUBSCRIBE_FEED
Get the digest delivered. No spam.