Skip to content

[BUG] Fullscreen rendering: blank screen after accepting plan with "clear context" #41337

Closed as duplicate

Description

@vnz

Description

When CLAUDE_CODE_NO_FLICKER=1 (fullscreen/alt-screen rendering) is enabled, accepting a plan with the "Yes, clear context and auto-accept edits" option causes the terminal to go completely blank — prompt, status bar, and all output disappear. The process continues running normally in the background (steady CPU usage, API calls proceeding), but the display never recovers.

Steps to Reproduce

  1. Set CLAUDE_CODE_NO_FLICKER=1 in settings or environment
  2. Enter plan mode (/plan or via a task)
  3. Approve the plan using "Yes, clear context and auto-accept edits" (Shift+Tab)
  4. Screen goes blank — no prompt, no status line, no output

Expected Behavior

After context clear, the alt-screen buffer should re-initialize and display the ongoing session normally.

Actual Behavior

The alt-screen buffer is not restored after the context clear. The terminal is completely blank. The Claude process continues working (confirmed via ps aux showing steady ~12.5% CPU). Killing and restarting is the only recovery.

Workaround

Use "Yes, auto-accept edits" (preserves context, no buffer reset) instead of the clear-context variant.

Environment

  • Claude Code v2.1.88
  • CLAUDE_CODE_NO_FLICKER=1
  • Linux (Debian 13)
  • Terminal: Kitty
  • Shell: Bash

Activity

  1. github-actions commented on Mar 31, 2026

    @github-actions

    Found 1 possible duplicate issue:

    1. [BUG] Fullscreen rendering: blank screen after accepting plan with "clear context" #41336

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. added
    duplicateThis issue or pull request already exists
    and removed
    bugSomething isn't working
    has reproHas detailed reproduction steps
    platform:linuxIssue specifically occurs on Linux
    on Apr 3, 2026
  3. github-actions commented on Apr 3, 2026

    @github-actions

    This issue has been automatically closed as a duplicate of #41336.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  4. github-actions commented on Apr 10, 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.

  5. locked as resolved and limited conversation to collaborators on Apr 10, 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

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions