[BUG]

Resolved 💬 2 comments Opened Mar 30, 2026 by NotMeNowToday Closed Apr 2, 2026

Preflight Checklist

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

What's Wrong?

BUG REPORT: Project Threads Removed During Claude Updates
Submitted: March 29, 2026
User: Desert Hot Springs, CA (~75, former IT architect/data warehousing)

================================================================================
ISSUE SUMMARY
================================================================================

Active Project threads are automatically removed from Projects during Claude updates,
despite the update notification appearing AFTER the removal has already occurred.

================================================================================
OCCURRENCE PATTERN
================================================================================

This bug has occurred CONSISTENTLY across THREE separate updates:

  1. Update to version 1.19310 (March 27, 2026)
  2. Update (version unknown) (March 28, 2026)
  3. Update to version 1.19493 (March 29, 2026)

FREQUENCY: 100% reproduction rate across all observed updates

================================================================================
EXPECTED BEHAVIOR
================================================================================

When Claude updates:

  1. Update is staged for application
  2. User sees notification: "Update available - relaunch to apply"
  3. User relaunches Claude
  4. Update applies
  5. Active Project threads REMAIN in the Project

================================================================================
ACTUAL BEHAVIOR
================================================================================

When Claude updates:

  1. Update applies IMMEDIATELY (no staging)
  2. Active Project thread is REMOVED from Project automatically
  3. User sees notification: "Relaunch to apply update" (but update already applied)
  4. Thread has already disappeared from Project chat list
  5. User must manually re-add thread to Project

CRITICAL ISSUE: The notification asks user to "relaunch to apply" AFTER the update
has already been applied and thread removal has already occurred.

================================================================================
SEQUENCE DIAGRAM
================================================================================

EXPECTED:
[Update Available] → [User Relaunches] → [Update Applies] → [Threads Persist]

ACTUAL:
[Update Applies Immediately] → [Thread Removed] → [Notification Shows "Relaunch"] → [User Manually Re-adds Thread]

The notification is appearing AFTER the action it claims to trigger.

================================================================================
IMPACT
================================================================================

SEVERITY: Medium-High for users with active Project workflows

  1. WORKFLOW DISRUPTION: Users lose active context mid-session
  2. DATA LOSS RISK: If user doesn't notice thread removal, work could be lost
  3. CONFUSION: Notification message misleads about update state
  4. MANUAL RECOVERY: User must remember to check and manually re-add threads after EVERY update

================================================================================
USER ENVIRONMENT
================================================================================

  • Platform: Claude.ai web interface (Desktop)
  • Browser: [User to specify - Chrome/Firefox/Safari/Edge]
  • OS: [User to specify - Windows/Mac/Linux]
  • Project Type: Bible Study Commentary (Ephesians 1-6)
  • Thread Activity: High-frequency, multi-session work with governance rules and custom instructions

================================================================================
REPRODUCTION STEPS
================================================================================

  1. Create a Project in Claude
  2. Start an active conversation thread in that Project
  3. Wait for a Claude system update to occur
  4. Observe: Thread is removed from Project before "relaunch" notification appears

NOTE: This appears to be triggered by any system update, not user-initiated actions.

================================================================================
TECHNICAL HYPOTHESIS
================================================================================

Possible causes (from IT architecture perspective):

  1. TIMING BUG: Update process executes thread cleanup before presenting relaunch UI
  2. STATE MANAGEMENT: Project thread associations cleared during update staging
  3. ASYNC ISSUE: Update application and notification display are out of sequence
  4. CACHE INVALIDATION: Project metadata cleared prematurely during update process

If Claude AI is being used to write the update deployment code, the bug may be in
how the AI-generated code handles:

  • Update staging vs. application timing
  • Project state persistence during updates
  • Thread-to-Project association preservation

================================================================================
SUGGESTED FIX
================================================================================

  1. STAGE updates WITHOUT applying them immediately
  2. PRESERVE Project thread associations during update staging
  3. APPLY update only AFTER user relaunches
  4. VERIFY Project threads persist post-update before showing success

OR

  1. If immediate application is required, SUPPRESS thread removal during updates
  2. Add Project thread restoration to post-update recovery process

================================================================================
WORKAROUND (Current)
================================================================================

After each Claude update:

  1. Check Project chat list
  2. If active thread missing, manually re-add it via thread menu → "Add to Project"
  3. Verify governance rules and custom instructions still active

================================================================================
ADDITIONAL NOTES
================================================================================

  • Bug has occurred consistently across multiple update versions
  • User has documented this pattern across three separate incidents
  • The issue is reproducible and predictable
  • User is willing to provide additional details or testing if needed

================================================================================
CONTACT INFO
================================================================================

User prefers response via Claude.ai interface or email associated with account.
Willing to participate in bug verification testing if needed.

================================================================================
END OF REPORT
================================================================================

Submitted via: [Thumbs down button feedback / Support ticket / Community forum]

What Should Happen?

BUG REPORT: Project Threads Removed During Claude Updates
Submitted: March 29, 2026
User: Desert Hot Springs, CA (~75, former IT architect/data warehousing)

================================================================================
ISSUE SUMMARY
================================================================================

Active Project threads are automatically removed from Projects during Claude updates,
despite the update notification appearing AFTER the removal has already occurred.

================================================================================
OCCURRENCE PATTERN
================================================================================

This bug has occurred CONSISTENTLY across THREE separate updates:

  1. Update to version 1.19310 (March 27, 2026)
  2. Update (version unknown) (March 28, 2026)
  3. Update to version 1.19493 (March 29, 2026)

FREQUENCY: 100% reproduction rate across all observed updates

================================================================================
EXPECTED BEHAVIOR
================================================================================

When Claude updates:

  1. Update is staged for application
  2. User sees notification: "Update available - relaunch to apply"
  3. User relaunches Claude
  4. Update applies
  5. Active Project threads REMAIN in the Project

================================================================================
ACTUAL BEHAVIOR
================================================================================

When Claude updates:

  1. Update applies IMMEDIATELY (no staging)
  2. Active Project thread is REMOVED from Project automatically
  3. User sees notification: "Relaunch to apply update" (but update already applied)
  4. Thread has already disappeared from Project chat list
  5. User must manually re-add thread to Project

CRITICAL ISSUE: The notification asks user to "relaunch to apply" AFTER the update
has already been applied and thread removal has already occurred.

================================================================================
SEQUENCE DIAGRAM
================================================================================

EXPECTED:
[Update Available] → [User Relaunches] → [Update Applies] → [Threads Persist]

ACTUAL:
[Update Applies Immediately] → [Thread Removed] → [Notification Shows "Relaunch"] → [User Manually Re-adds Thread]

The notification is appearing AFTER the action it claims to trigger.

================================================================================
IMPACT
================================================================================

SEVERITY: Medium-High for users with active Project workflows

  1. WORKFLOW DISRUPTION: Users lose active context mid-session
  2. DATA LOSS RISK: If user doesn't notice thread removal, work could be lost
  3. CONFUSION: Notification message misleads about update state
  4. MANUAL RECOVERY: User must remember to check and manually re-add threads after EVERY update

================================================================================
USER ENVIRONMENT
================================================================================

  • Platform: Claude.ai web interface (Desktop)
  • Browser: [User to specify - Chrome/Firefox/Safari/Edge]
  • OS: [User to specify - Windows/Mac/Linux]
  • Project Type: Bible Study Commentary (Ephesians 1-6)
  • Thread Activity: High-frequency, multi-session work with governance rules and custom instructions

================================================================================
REPRODUCTION STEPS
================================================================================

  1. Create a Project in Claude
  2. Start an active conversation thread in that Project
  3. Wait for a Claude system update to occur
  4. Observe: Thread is removed from Project before "relaunch" notification appears

NOTE: This appears to be triggered by any system update, not user-initiated actions.

================================================================================
TECHNICAL HYPOTHESIS
================================================================================

Possible causes (from IT architecture perspective):

  1. TIMING BUG: Update process executes thread cleanup before presenting relaunch UI
  2. STATE MANAGEMENT: Project thread associations cleared during update staging
  3. ASYNC ISSUE: Update application and notification display are out of sequence
  4. CACHE INVALIDATION: Project metadata cleared prematurely during update process

If Claude AI is being used to write the update deployment code, the bug may be in
how the AI-generated code handles:

  • Update staging vs. application timing
  • Project state persistence during updates
  • Thread-to-Project association preservation

================================================================================
SUGGESTED FIX
================================================================================

  1. STAGE updates WITHOUT applying them immediately
  2. PRESERVE Project thread associations during update staging
  3. APPLY update only AFTER user relaunches
  4. VERIFY Project threads persist post-update before showing success

OR

  1. If immediate application is required, SUPPRESS thread removal during updates
  2. Add Project thread restoration to post-update recovery process

================================================================================
WORKAROUND (Current)
================================================================================

After each Claude update:

  1. Check Project chat list
  2. If active thread missing, manually re-add it via thread menu → "Add to Project"
  3. Verify governance rules and custom instructions still active

================================================================================
ADDITIONAL NOTES
================================================================================

  • Bug has occurred consistently across multiple update versions
  • User has documented this pattern across three separate incidents
  • The issue is reproducible and predictable
  • User is willing to provide additional details or testing if needed

================================================================================
CONTACT INFO
================================================================================

User prefers response via Claude.ai interface or email associated with account.
Willing to participate in bug verification testing if needed.

================================================================================
END OF REPORT
================================================================================

Error Messages/Logs

BUG REPORT: Project Threads Removed During Claude Updates
Submitted: March 29, 2026
User: Desert Hot Springs, CA (~75, former IT architect/data warehousing)

================================================================================
ISSUE SUMMARY
================================================================================

Active Project threads are automatically removed from Projects during Claude updates, 
despite the update notification appearing AFTER the removal has already occurred.

================================================================================
OCCURRENCE PATTERN
================================================================================

This bug has occurred CONSISTENTLY across THREE separate updates:
1. Update to version 1.19310 (March 27, 2026)
2. Update (version unknown) (March 28, 2026)
3. Update to version 1.19493 (March 29, 2026)

FREQUENCY: 100% reproduction rate across all observed updates

================================================================================
EXPECTED BEHAVIOR
================================================================================

When Claude updates:
1. Update is staged for application
2. User sees notification: "Update available - relaunch to apply"
3. User relaunches Claude
4. Update applies
5. Active Project threads REMAIN in the Project

================================================================================
ACTUAL BEHAVIOR
================================================================================

When Claude updates:
1. Update applies IMMEDIATELY (no staging)
2. Active Project thread is REMOVED from Project automatically
3. User sees notification: "Relaunch to apply update" (but update already applied)
4. Thread has already disappeared from Project chat list
5. User must manually re-add thread to Project

CRITICAL ISSUE: The notification asks user to "relaunch to apply" AFTER the update 
has already been applied and thread removal has already occurred.

================================================================================
SEQUENCE DIAGRAM
================================================================================

EXPECTED:
[Update Available] → [User Relaunches] → [Update Applies] → [Threads Persist]

ACTUAL:
[Update Applies Immediately] → [Thread Removed] → [Notification Shows "Relaunch"] → [User Manually Re-adds Thread]

The notification is appearing AFTER the action it claims to trigger.

================================================================================
IMPACT
================================================================================

SEVERITY: Medium-High for users with active Project workflows

1. WORKFLOW DISRUPTION: Users lose active context mid-session
2. DATA LOSS RISK: If user doesn't notice thread removal, work could be lost
3. CONFUSION: Notification message misleads about update state
4. MANUAL RECOVERY: User must remember to check and manually re-add threads after EVERY update

================================================================================
USER ENVIRONMENT
================================================================================

- Platform: Claude.ai web interface (Desktop)
- Browser: [User to specify - Chrome/Firefox/Safari/Edge]
- OS: [User to specify - Windows/Mac/Linux]
- Project Type: Bible Study Commentary (Ephesians 1-6)
- Thread Activity: High-frequency, multi-session work with governance rules and custom instructions

================================================================================
REPRODUCTION STEPS
================================================================================

1. Create a Project in Claude
2. Start an active conversation thread in that Project
3. Wait for a Claude system update to occur
4. Observe: Thread is removed from Project before "relaunch" notification appears

NOTE: This appears to be triggered by any system update, not user-initiated actions.

================================================================================
TECHNICAL HYPOTHESIS
================================================================================

Possible causes (from IT architecture perspective):

1. TIMING BUG: Update process executes thread cleanup before presenting relaunch UI
2. STATE MANAGEMENT: Project thread associations cleared during update staging
3. ASYNC ISSUE: Update application and notification display are out of sequence
4. CACHE INVALIDATION: Project metadata cleared prematurely during update process

If Claude AI is being used to write the update deployment code, the bug may be in 
how the AI-generated code handles:
- Update staging vs. application timing
- Project state persistence during updates
- Thread-to-Project association preservation

================================================================================
SUGGESTED FIX
================================================================================

1. STAGE updates WITHOUT applying them immediately
2. PRESERVE Project thread associations during update staging
3. APPLY update only AFTER user relaunches
4. VERIFY Project threads persist post-update before showing success

OR

5. If immediate application is required, SUPPRESS thread removal during updates
6. Add Project thread restoration to post-update recovery process

================================================================================
WORKAROUND (Current)
================================================================================

After each Claude update:
1. Check Project chat list
2. If active thread missing, manually re-add it via thread menu → "Add to Project"
3. Verify governance rules and custom instructions still active

================================================================================
ADDITIONAL NOTES
================================================================================

- Bug has occurred consistently across multiple update versions
- User has documented this pattern across three separate incidents
- The issue is reproducible and predictable
- User is willing to provide additional details or testing if needed

================================================================================
CONTACT INFO
================================================================================

User prefers response via Claude.ai interface or email associated with account.
Willing to participate in bug verification testing if needed.

================================================================================
END OF REPORT
================================================================================

Submitted via: [Thumbs down button feedback / Support ticket / Community forum]

Steps to Reproduce

BUG REPORT: Project Threads Removed During Claude Updates
Submitted: March 29, 2026
User: Desert Hot Springs, CA (~75, former IT architect/data warehousing)

================================================================================
ISSUE SUMMARY
================================================================================

Active Project threads are automatically removed from Projects during Claude updates,
despite the update notification appearing AFTER the removal has already occurred.

================================================================================
OCCURRENCE PATTERN
================================================================================

This bug has occurred CONSISTENTLY across THREE separate updates:

  1. Update to version 1.19310 (March 27, 2026)
  2. Update (version unknown) (March 28, 2026)
  3. Update to version 1.19493 (March 29, 2026)

FREQUENCY: 100% reproduction rate across all observed updates

================================================================================
EXPECTED BEHAVIOR
================================================================================

When Claude updates:

  1. Update is staged for application
  2. User sees notification: "Update available - relaunch to apply"
  3. User relaunches Claude
  4. Update applies
  5. Active Project threads REMAIN in the Project

================================================================================
ACTUAL BEHAVIOR
================================================================================

When Claude updates:

  1. Update applies IMMEDIATELY (no staging)
  2. Active Project thread is REMOVED from Project automatically
  3. User sees notification: "Relaunch to apply update" (but update already applied)
  4. Thread has already disappeared from Project chat list
  5. User must manually re-add thread to Project

CRITICAL ISSUE: The notification asks user to "relaunch to apply" AFTER the update
has already been applied and thread removal has already occurred.

================================================================================
SEQUENCE DIAGRAM
================================================================================

EXPECTED:
[Update Available] → [User Relaunches] → [Update Applies] → [Threads Persist]

ACTUAL:
[Update Applies Immediately] → [Thread Removed] → [Notification Shows "Relaunch"] → [User Manually Re-adds Thread]

The notification is appearing AFTER the action it claims to trigger.

================================================================================
IMPACT
================================================================================

SEVERITY: Medium-High for users with active Project workflows

  1. WORKFLOW DISRUPTION: Users lose active context mid-session
  2. DATA LOSS RISK: If user doesn't notice thread removal, work could be lost
  3. CONFUSION: Notification message misleads about update state
  4. MANUAL RECOVERY: User must remember to check and manually re-add threads after EVERY update

================================================================================
USER ENVIRONMENT
================================================================================

  • Platform: Claude.ai web interface (Desktop)
  • Browser: [User to specify - Chrome/Firefox/Safari/Edge]
  • OS: [User to specify - Windows/Mac/Linux]
  • Project Type: Bible Study Commentary (Ephesians 1-6)
  • Thread Activity: High-frequency, multi-session work with governance rules and custom instructions

================================================================================
REPRODUCTION STEPS
================================================================================

  1. Create a Project in Claude
  2. Start an active conversation thread in that Project
  3. Wait for a Claude system update to occur
  4. Observe: Thread is removed from Project before "relaunch" notification appears

NOTE: This appears to be triggered by any system update, not user-initiated actions.

================================================================================
TECHNICAL HYPOTHESIS
================================================================================

Possible causes (from IT architecture perspective):

  1. TIMING BUG: Update process executes thread cleanup before presenting relaunch UI
  2. STATE MANAGEMENT: Project thread associations cleared during update staging
  3. ASYNC ISSUE: Update application and notification display are out of sequence
  4. CACHE INVALIDATION: Project metadata cleared prematurely during update process

If Claude AI is being used to write the update deployment code, the bug may be in
how the AI-generated code handles:

  • Update staging vs. application timing
  • Project state persistence during updates
  • Thread-to-Project association preservation

================================================================================
SUGGESTED FIX
================================================================================

  1. STAGE updates WITHOUT applying them immediately
  2. PRESERVE Project thread associations during update staging
  3. APPLY update only AFTER user relaunches
  4. VERIFY Project threads persist post-update before showing success

OR

  1. If immediate application is required, SUPPRESS thread removal during updates
  2. Add Project thread restoration to post-update recovery process

================================================================================
WORKAROUND (Current)
================================================================================

After each Claude update:

  1. Check Project chat list
  2. If active thread missing, manually re-add it via thread menu → "Add to Project"
  3. Verify governance rules and custom instructions still active

================================================================================
ADDITIONAL NOTES
================================================================================

  • Bug has occurred consistently across multiple update versions
  • User has documented this pattern across three separate incidents
  • The issue is reproducible and predictable
  • User is willing to provide additional details or testing if needed

================================================================================
CONTACT INFO
================================================================================

User prefers response via Claude.ai interface or email associated with account.
Willing to participate in bug verification testing if needed.

================================================================================
END OF REPORT
================================================================================

Submitted via: [Thumbs down button feedback / Support ticket / Community forum]

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1.9493

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗