You'll notice
Useful3 Signal2
Replaying job output with claude logs can no longer garble your terminal.
What's wrong with this entry?
Anonymous. No account, no email.
claude logs
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background