---
title: "Claude Code ships two releases in a day; 2.1.191 lets /rewind cross a /clear"
date: 2026-06-25
lede_surface: Claude Code
summary: "Claude Code shipped 2.1.190 and 2.1.191 on June 24; the headline feature lets /rewind resume a conversation from before /clear, plus a ~37% streaming CPU cut."
tags: [Claude Code, MCP, Sandbox, Performance]
sources:
  - https://code.claude.com/docs/en/changelog
  - https://www.anthropic.com/news
  - https://www.anthropic.com/engineering
  - https://status.anthropic.com/
---

# The Dispatch — No. 002 · 2026-06-25

*Yesterday in Claude, Claude Code & Anthropic, in one morning read.*

A quiet day on the newsroom — no new product or research post landed June 24, and the
biggest Anthropic-ecosystem headline of the day was the company's legal filing against
Alibaba, which is The Wire's beat, not a Claude product change. Where yesterday actually
moved for builders was the Claude Code changelog: **two releases in a single day**, and the
later one carries a feature people have asked about for a while — **`/rewind` can now reach
back across a `/clear`.**

## Lede — Two Claude Code releases, one genuinely useful feature

Claude Code shipped both **2.1.190** and **2.1.191** on June 24, per the official
[changelog](https://code.claude.com/docs/en/changelog). 2.1.190 is a housekeeping point
release — its entry reads only "Bug fixes and reliability improvements" — but **2.1.191** is
the substantive one, and it leads with a rewind change that closes a long-standing gap.

Until now, running `/clear` was a one-way door: it reset the conversation and your
`/rewind` history went with it. 2.1.191 **"Added `/rewind` support for resuming a
conversation from before `/clear` was run,"** so an accidental clear no longer strands the
work you were mid-way through. For anyone who runs long, multi-hour sessions and treats
`/clear` as a soft reset, this is the difference between a recoverable misclick and a lost
thread.

The same release is unusually performance-heavy. It **"Reduced CPU usage during streaming
responses by ~37% by coalescing text updates to 100ms"** and trimmed long-session memory
growth from the terminal output cache — both of which matter most on the exact
long-running, high-token sessions where Claude Code has historically felt heaviest. What to
watch: whether the 100ms coalescing interval is noticeable on very fast terminals, and
whether the rewind-across-clear behavior becomes the default mental model for session
recovery the way `/rewind` itself did.

## The briefs

**01 · Agents and sandbox get safer defaults.** 2.1.191 makes stopping a background agent
mean it. The release **"Fixed background agents resurrecting after being stopped — stopping
an agent from the tasks panel is now permanent,"** ending a class of bug where a killed
agent could come back. It also softens a daily friction point: the **"sandbox network
permission dialog: hosts you allow with 'Yes' are now remembered for the rest of the
session instead of re-prompting on every connection,"** so an allowlisted host stays
allowed without a prompt storm.
([changelog](https://code.claude.com/docs/en/changelog))

**02 · MCP reliability gets a round of hardening.** The same release retries through
transient network failures in three places: capability discovery
(**"`tools/list`, `prompts/list`, `resources/list` now retries transient network errors
with short backoff"**), MCP OAuth (**"discovery and token requests now retry once after
transient network errors, and headless environments skip the browser popup and go straight
to the paste-the-URL prompt"**), and error messaging — **"HTTP 404 errors now show the URL
and point to your MCP config."** Collectively, fewer flaky-network failures and clearer
diagnostics when a server is misconfigured.
([changelog](https://code.claude.com/docs/en/changelog))

**03 · The smaller fixes worth knowing.** 2.1.191 also fixes scroll position jumping to the
bottom while you read earlier output mid-stream, `/voice` now explains itself when an org
policy disables it instead of showing a generic error, hooks with comma-separated matchers
(e.g. `"Bash,PowerShell"`) that **"silently never firing"** now fire, and a `/permissions`
Recently-denied approval now persists on close instead of being discarded.
([changelog](https://code.claude.com/docs/en/changelog))

## Watching

Whether the next 2.1.x cuts a feature release on top of the two June 24 point drops, and
whether June 23's Claude Tag — still the freshest thing on the newsroom — picks up its
promised expansion "beyond Slack." The Claude Platform release-notes page was unreadable to
the automated sweep (JS-rendered, no rendered fallback available), so any API-side change
dated June 24 is unconfirmed here rather than ruled out.