{"version":"2.1.248","anchor":"claude-logs-no-longer-lets-replayed-output-corrupt-your-term","canonical_anchor":"claude-logs-no-longer-lets-replayed-output-corrupt-your-term","heading":"claude logs no longer lets replayed output corrupt your terminal","tier":"notice","area":"Background Jobs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-logs-no-longer-lets-replayed-output-corrupt-your-term","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `claude logs` no longer lets replayed output corrupt your terminal\n\nReplaying job output with `claude logs` can no longer garble your terminal.\n\n**What**\n\nCaptured 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.\n\n**Evidence**\n\n`{ replay: i, cursorAddressed: d } = tr(r.join(\"\"))`\n\n- Area: Background Jobs\n- Names: `claude logs`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}