Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

claude logs no longer lets replayed output corrupt your terminal

Replaying job output with claude logs can no longer garble your terminal.

You'll notice Improvements
JSON All of v2.1.248
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Background JobsArea: what it touches
ImprovementsKind: in v2.1.248,
ImprovementsSection of the release
What

Captured job output is filtered before being printed, so escape sequences in a job's output can no longer leave your terminal in a broken state. On a real terminal the replay is followed by a reset and, if the output moved the cursor, a reposition so your shell prompt lands at the bottom.

Evidence

{ replay: i, cursorAddressed: d } = tr(r.join(""))

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleclaude logs
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up claude logs, on Manage multiple agents with agent view. | `claude logs <id>` | Print the session's recent output | agent-view see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude logs, on Manage multiple agents with agent view.
Anthropic's release notes agreeFixed claude logs leaving mouse tracking, bracketed paste and the alternate screen switched on in the terminal it was run from

See this entry in the whole of v2.1.248 →

Feedback