Skip to content

[BUG] bash_progress events not compacted, causing multi-MB transcripts and resume hang #19199

Closed as not planned

Description

@dchaplinsky

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Preflight Checklist

What's Wrong?

Session transcripts become bloated with bash_progress events from long-running commands, causing session resume to hang.

When a Bash command runs for an extended period, Claude Code records a progress event to the session transcript every second. After a 2-hour session, the transcript reached 31MB
with 85% being progress updates. Attempting to resume causes the UI to hang indefinitely.

Evidence

  $ ls -lh ~/.claude/projects/-workspace/<session-id>.jsonl
  31M

  $ wc -l ~/.claude/projects/-workspace/<session-id>.jsonl
  6204 lines

  $ grep -c '"type":"progress"' ~/.claude/projects/-workspace/<session-id>.jsonl
  5275 lines  # 85% of transcript

Each progress event looks like:

{"type":"progress","data":{"type":"bash_progress","output":"","elapsedTimeSeconds":142,...}}

Relationship to Existing Issues

What Should Happen?

Progress events should not be persisted to the transcript (they're transient UI state), or should be compacted on session end.

Error Messages/Logs

Steps to Reproduce

  1. Start a Claude Code session
  2. Run a long-running bash command (30+ minutes)
  3. Exit and try to resume

Expected: Session resumes normally
Actual: UI hangs while loading the bloated transcript

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.12 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Terminal.app (macOS)

Additional Information

I'm running Claude code in the sandboxed environment (Linux Docker on Mac Os X)

Activity

  1. heathdutton commented on Jan 21, 2026

    @heathdutton

    Adding a bit more context. This issue still exists in 2.1.14 and makes this unusable for projects with a mountain of python dependencies (if it tries to get out of dependency hell it results in latency hell).

  2. github-actions commented on Feb 27, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  3. github-actions commented on Mar 7, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions