[BUG] "Failed to load session"

Resolved 💬 3 comments Opened Feb 14, 2026 by justalittlepotato Closed Feb 17, 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?

Claude Code tab in the Claude Mac desktop app fails to load sessions and hangs indefinitely. All previous chat history has disappeared after logging out and deleting the app and reinstalling and logging back in.

  • Code tab showed "Failed to load" on existing sessions or hangs on "Contemplating..." when starting a new session
  • All previous Code session history has disappeared after re-login
  • Regular chat tab works perfectly fine

Environment Info

  • Platform: macOS (Mac desktop app)
  • Date issue started: ~February 13, 2026
  • Note: Status page showed elevated errors on Opus 4.6, Sonnet 4.5, and Opus 4.6 Fast Mode around the same time. Issue persists despite status page now showing "Operational."

Additional Context

I had a substantial amount of work and session history built up over the past week. The session history loss occurred after logging out and back in while attempting to resolve the loading issue. This is particularly concerning as the chat interface itself suggested using /bug or /doctor to report issues, which is impossible when Code won't respond.

What Should Happen?

I should be able to talk in the sessions without an error.

Error Messages/Logs

Steps to Reproduce

Open Claude desktop app (Mac)

  1. Navigate to Code tab
  2. Sessions either fail to load or hang on "Contemplating..." indefinitely
  3. Regular Claude chat works normally in the same app

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1.3189 (1b7b58)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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