Claude Code v2.1.179

Two new validation messages are now shown when --json-schema is passed invalid input:

• If the value is not parseable JSON: Error: --json-schema is not valid JSON: <parse error detail>
• If the JSON is valid but not an object (e.g., an array or string): Error: --json-schema must be a JSON object

Previously these failures silently continued with an undefined schema object.

When installing a plugin that specifies a SHA pin and verification fails, the error message is now specific about what went wrong:

SHA pin verification failed: expected HEAD to be <expected-sha>, got <actual-sha>.
The pinned commit may have been removed upstream, or a ref with the same name exists.
Refusing to install.

If the underlying git rev-parse call itself fails, the got field shows (rev-parse failed) so the root cause is always clear.

The /ultrareview command now fetches additions, deletions, and changedFiles from GitHub before attempting the review. If the PR is too large, you get an early, clear error:

PR #42 is too large for ultrareview (85 files, 3,200 lines).
Split it into smaller PRs, or run `claude` on a narrower local diff.

The local-diff too-large message was also improved — it no longer suggests pushing a PR:

Before: "Push a PR and use claude <PR#>, or pass a closer base branch…" After: "Pass a closer base branch (claude <branch>) to narrow the scope, or split the change."

When scanning recently-added files, Claude now passes four safety flags to git:

-c core.fsmonitor=
-c core.hooksPath=/dev/null
-c core.pager=
-c log.showSignature=false

This prevents fsmonitor daemons from slowing the call, local git hooks from running, pagers from blocking output, and commit-signature verification from failing on machines without GPG. The call was occasionally slow or broken on repos with heavy hook setups.

Claude translates Windows-style NUL redirections (e.g., 2>NUL) into /dev/null for cross-platform compatibility. This substitution is now skipped if the command contains <, $, or a backtick — characters that indicate shell expansion or redirection contexts where a static replacement would produce incorrect results.

When exiting a git worktree, if the original working directory no longer exists (e.g., it was deleted while Claude was running in the worktree), Claude now tries fallback locations in order: the original worktree path, the home directory, and the process root. A clear message is shown:

The original directory /path/to/old-dir no longer exists, so the session is now in /home/user.
Consider restarting Claude from an existing directory.

If the fallback landed back in the worktree itself, the suggestion to restart is omitted.

Three new user-facing messages now appear when a streaming connection is lost:

• Mid-response (after some content was already delivered): Connection closed mid-response. The response above may be incomplete.
• During thinking (before any content): Connection closed while thinking, before producing a response. Try again.
• Network-level errors (ECONNRESET, EPIPE, etc.): Connection to the API was lost (<error_code>). This is usually temporary — try again.

Previously these all surfaced as generic error messages.

When a remote session receives a 401 response and OAuth token refresh fails, the client now retries the refresh up to oauth_retry_max_attempts times with exponential backoff. During each attempt, the status shows:

OAuth refresh failed — waiting for a fresh login (1/3)

If all attempts fail: OAuth token refresh failed — re-authenticate, then re-enable Remote Control.

The artifact WebFetch tool now probes the sharing status of an artifact before reading it. The mode is now shown in descriptive human-readable form instead of raw enum values:

• "owner" → "a private page on claude.ai"
• "org" → "a page shared with your organization"
• "users" → "a page shared with specific users"
• Live-shared → "on claude.ai (viewers see updates immediately)"
• Unknown mode → "others (unrecognized share mode — treating as shared)"

Several improvements to how usage-credits-gated models (Fable 5) behave when consent hasn't been given:

• When Fable 5 is set as a teammate's default model but consent is missing, the teammate panel now shows: "Fable 5 needs usage-credits consent — /model to set up" instead of a silent failure
• A new model_consent_fallback system event is emitted when the gated model falls back to another, carrying the choice (consent/switch_default/cancelled), original_model, fallback_model, and whether the saved default was rewritten
• The model picker shows a "Reset model to the workspace default" option when relevant

Internally, the status bar spinner state (responding/thinking/tool-input, compacting status, turn effort) is now tracked per agent ID in a keyed store instead of a single global singleton. This is a prerequisite for correct multi-agent displays where parallel agents each need their own status line. Spinner state for removed agents is cleaned up automatically.

When a tool result or file listing is too long for the context window and must be truncated, the cutoff now shows:

... and 42 more (truncated for prompt size)

Previously the list was silently cut with no indication of how much was omitted.

If saving the machine ID to disk fails (e.g., permissions issue), Claude now falls back to an in-memory ID for the current session rather than leaving the field empty. A warning is logged: getOrCreateMachineID: could not persist machineID: <error>.

• Worktree cleanup (process.chdir) now catches and logs errors instead of crashing if the original directory is gone during teardown (search for "Could not chdir to original directory while cleaning up worktree:")
• Worktree keep (process.chdir) similarly catches errors gracefully (search for "Could not chdir to original directory while keeping worktree:")
• git core.hooksPath resolution now canonicalizes relative paths before writing them back, preventing the wrong path being stored when core.hooksPath is specified as a relative reference

Features with infrastructure added but not yet enabled for users.