[BUG] Windows: Claude startup welcome/header UI not visible in some folders

[Baouse]

Summary

On Windows, Claude Code startup welcome/header UI is not visibly persistent in some folders, while it appears in others. Claude still works (prompt, /help), so this looks like a terminal rendering/startup UI bug.

Environment

• OS: Windows 11
• Shell/terminal: PowerShell + Windows Terminal
• Claude Code version: 2.1.39
• Account type: Claude Pro

Reproduction

1. Run:
   • cd <REPO_PATH_A>
   • claude
2. Run:
   • cd <REPO_PATH_B>
   • claude

Expected

Startup welcome/header UI should appear consistently in both folders.

Actual

• In one folder, trust/setup flow appears.
• In another folder, Claude works (Claude >, /help works), but startup welcome/header is not visibly persistent (appears missing/cleared).

Notes

• This is not correlated with folder file count alone.
• Behavior is folder-dependent on same machine/session.

Troubleshooting already done

• claude --setting-sources user
• Reset project trust/onboarding flags in <HOME>/.claude.json
• pwsh -NoProfile
• claude --no-alt-screen
• Cleared env styling vars (NO_COLOR, TERM, FORCE_COLOR variants)
• Verified functionality is intact (prompt commands work)

Additional context

• Startup debug logs show different startup paths between folders.
• Looks similar to prior Windows terminal welcome/banner visibility regressions.

[Baouse]

Follow-up with concrete repro matrix and host details.

Terminal host details

• Windows 11
• PowerShell (pwsh) in Windows Terminal
• Also tested pwsh -NoProfile
• Claude Code 2.1.39

Minimal repro matrix

Folder	Characteristics	Command	Observed
<REPO_PATH_A>	empty/new folder	cd <REPO_PATH_A> && claude	trust/setup screen appears
<REPO_PATH_B>	has .claude/ config + hooks + project files	cd <REPO_PATH_B> && claude	Claude prompt works, but startup welcome/header UI is not visibly persistent

Isolation steps already run

• claude --setting-sources user
• reset project trust/onboarding keys in <HOME>/.claude.json
• pwsh -NoProfile
• claude --no-alt-screen
• terminal env variants (NO_COLOR, TERM, FORCE_COLOR)

Important nuance

This appears to be a UI/render persistence issue, not a functional failure:

• Claude > prompt works
• /help works
• commands execute normally

[Baouse]

Adding exact artifact checklist for maintainers.

Suggested logs/artifacts to collect from reporter

1. claude --version output
2. claude doctor output
3. Terminal host/version details:
   • Windows Terminal version
   • PowerShell version ($PSVersionTable)
4. Latest Claude debug logs from:
   • <HOME>/.claude/debug/*.txt
   • Especially sessions launched from:
     • <REPO_PATH_A>
     • <REPO_PATH_B>
5. If requested, startup captures from both folders using:
   • claude -d startup

Current known local paths (redacted)

• Global state file: <HOME>/.claude.json
• Debug folder: <HOME>/.claude/debug/
• Repro folders: <REPO_PATH_A>, <REPO_PATH_B>

[Baouse]

Adding a consolidated list of fixes/workarounds attempted that did not resolve this startup UI issue.

Attempted fixes (no change)

• Updated/validated CLI version and re-tested startup behavior.
• Ran claude doctor and confirmed basic health checks.
• Ran with user-only settings source:
  • claude --setting-sources user
• Reset per-project trust/onboarding flags in global Claude state and re-tested.
• Started from clean shell:
  • pwsh -NoProfile
• Disabled alt-screen behavior:
  • claude --no-alt-screen
• Tested terminal env variants:
  • unset NO_COLOR
  • varied TERM
  • set FORCE_COLOR
• Re-tested with debug startup mode:
  • claude -d startup
• Compared behavior in multiple folders with different characteristics.

Observed outcome after all attempts

• Claude remains functional (Claude >, /help, normal command execution).
• Issue appears limited to startup welcome/header UI visibility/persistence in certain folder contexts.
• This points to a rendering/startup UI path issue rather than core CLI functionality.

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Welcome screen stops appearing in all project directories after rapid session launches #25268
2. [BUG] The startup screen is not displaying correctly. #25007
3. Welcome screen appears for 1-2 seconds then clears intermittently (v2.1.37 Windows CLI) #24015

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

[Baouse]

Not a duplicate. Please keep this issue open.

Why this differs from the suggested duplicates:

• This report is specifically folder-dependent on Windows: one folder consistently shows trust/setup flow while another folder in the same environment shows missing/non-persistent startup welcome/header UI.
• Core CLI functionality remains intact (Claude >, /help, normal command execution). The failure is in startup UI visibility/persistence path, not general startup crash/freeze.
• Reproduced after isolations already attempted: --setting-sources user, pwsh -NoProfile, --no-alt-screen, trust/onboarding state reset, env var variants.

This issue has a stable repro pattern and is materially different from generic startup-display/flicker reports.

Request: keep this issue open as a distinct Windows TUI startup rendering/state-path bug.

[github-actions]

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