[BUG] Failed to load session
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?
The error message: "Failed to load session" shows when trying to load my last session
The session URL or ID if visible: https://claude.ai/code/session_011KQCHtToWENAJjcbZFXWU8
When it started happening: The same day I ran out of credits around Dec 14th but I'm in a new month now with new credits so it should work
Browser/OS info: Chrome Version 143.0.7499.170 (Official Build) (64-bit)
I was working on "Set up Telegram Channel connection feature" chat and when I first clicked on it it seems to be trying to load but then fails.
The session was on branch claude/telegram-channel-connection-011KQCHtToWENAJjcbZFXWU8
Session failed to load after previous work was completed
What Should Happen?
It should load successfully like all the times before so I can continue the coding conversation. Since Claude Code doesn't seem to show exactly where I left off after I reload it day over day it's crucial I get this session working again so claude and confirm where we left off and continue the work.
Error Messages/Logs
Steps to Reproduce
1: Go right to https://claude.ai/code using a saved bookmark
- Click on the session title to the left
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Opus 4.5
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
8 Comments
i have a similar issue, created local folder with my files. New claude code chat, choose the folder, typed my prompts, hit enter and instantly "Failed to load session" message. New start of app or log out/in didnt help.
I encountered a similar issue after re-opening the local Claude app, navigating to one of my existing Code chats, and attempting to resume the conversation. Restarting the app multiple times did nothing to resolve the issue.
During this time I also wasn't able to create new Claude Code chats, with the submit button being greyed out even after selecting a local directory that had already been used / initialized previously.
This was only solved when I clicked the environment drop-down in a new chat session and re-selected "Local" (which was already selected; no other env is configured in my app) which instantly re-enabled the chat submit button for whatever reason, and also allowed me to continue with my other existing chats without getting the "Failed to load session" error.
I encountered the "Failed to load session" error when getting started with using Claude Code through Claude Desktop. In my case this simply turned out to be because I did not have Git installed (I wrongly assumed that if just working with local files Git would not be needed, but it is need for Bash commands). For me simply installing Git for Windows (with all the defaults) resolved things.
<html>
<body>
<!--StartFragment--><html><head></head><body><h1>Solution: "Failed to Load Session" Error in Claude Desktop App (Windows)</h1>
<h2>Problem Summary</h2>
<p>When attempting to use the Claude Code feature in the Claude Desktop app on Windows, users may encounter a <strong>"Failed to load session"</strong> error when trying to access local files or start a local coding session.</p>
<h2>Root Cause</h2>
<p>The "Failed to load session" error can occur due to <strong>missing dependencies</strong> that the Claude Desktop app requires for local sessions, specifically:</p>
<ol>
<li><strong>Git</strong> must be installed and accessible from the command line</li>
<li><strong>The target folder must be a Git repository</strong> — the Desktop app uses Git worktrees for local sessions and will fail if Git isn't initialized in the project folder</li>
</ol>
<p>While the Claude Desktop app bundles its own version of Claude Code internally, it relies on your system having Git properly installed and configured.</p>
<h2>Diagnostic Steps</h2>
<h3>Step 1: Verify Git is Installed</h3>
<p>Open PowerShell or Command Prompt and run:</p>
<pre><code class="language-powershell">git --version
</code></pre>
<p><strong>Expected output:</strong> A version number like <code>git version 2.52.0.windows.1</code></p>
<p><strong>If you get "not recognized as a command":</strong> Install Git from <a href="https://git-scm.com/downloads/win">https://git-scm.com/downloads/win</a></p>
<h3>Step 2: Verify Node.js is Installed (Optional but Recommended)</h3>
<pre><code class="language-powershell">node --version
</code></pre>
<p><strong>Expected output:</strong> A version number like <code>v24.12.0</code> (should be v18+)</p>
<p><strong>Note:</strong> The native Claude Code installer doesn't require Node.js, but many development workflows do. Install from <a href="https://nodejs.org/">https://nodejs.org</a> if needed.</p>
<h3>Step 3: Install Claude Code CLI for Diagnostics</h3>
<p>The Claude Desktop app bundles Claude Code internally but doesn't expose the <code>claude</code> command to your terminal. Installing the CLI separately allows you to run diagnostic commands.</p>
<p><strong>PowerShell:</strong></p>
<pre><code class="language-powershell">irm https://claude.ai/install.ps1 | iex
</code></pre>
<p><strong>Command Prompt:</strong></p>
<pre><code class="language-cmd">curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
</code></pre>
<h3>Step 4: Add Claude Code to Your PATH</h3>
<p>After installation, you may see a message like:</p>
<pre><code>Native installation exists but C:\Users\<username>\.local\bin is not in your PATH.
</code></pre>
<p><strong>Quick fix via PowerShell:</strong></p>
<pre><code class="language-powershell">[Environment]::SetEnvironmentVariable("Path", $env:Path + ";$env:USERPROFILE\.local\bin", "User")
</code></pre>
<p><strong>Or manually:</strong></p>
<ol>
<li>Press <code>Win + R</code>, type <code>sysdm.cpl</code>, press Enter</li>
<li>Click the <strong>Advanced</strong> tab</li>
<li>Click <strong>Environment Variables</strong></li>
<li>Under "User variables", select <strong>Path</strong> and click <strong>Edit</strong></li>
<li>Click <strong>New</strong></li>
<li>Add: <code>%USERPROFILE%\.local\bin</code></li>
<li>Click <strong>OK</strong> on all dialogs</li>
</ol>
<p><strong>Important:</strong> Close and reopen your terminal after updating the PATH.</p>
<h3>Step 5: Run Diagnostics</h3>
<pre><code class="language-powershell">claude doctor
</code></pre>
<p>This will show the health of your Claude Code installation. A healthy output looks like:</p>
<pre><code>Diagnostics
└ Currently running: native (2.x.x)
└ Path: native
└ Search: OK (bundled)
Updates
└ Auto-updates: enabled
</code></pre>
<h3>Step 6: Ensure Your Project Folder is a Git Repository</h3>
<p>This is the most commonly overlooked requirement. The Claude Desktop app's local sessions <strong>require the folder to be a Git repository</strong>.</p>
<p>Navigate to your project folder and check:</p>
<pre><code class="language-powershell">cd "path\to\your\project"
git status
</code></pre>
<p><strong>If you see "fatal: not a git repository"</strong>, initialize Git:</p>
<pre><code class="language-powershell">git init
git add .
git commit -m "Initial commit"
</code></pre>
<h2>Solution Summary</h2>
<p>To resolve the "Failed to load session" error:</p>
Requirement | How to Verify | How to Fix
-- | -- | --
Git installed | git --version | Install from git-scm.com
Folder is a Git repo | git status in project folder | Run git init
(Optional) Node.js 18+ | node --version | Install from nodejs.org
<h2>Key Takeaways</h2>
<ol>
<li><strong>The Claude Desktop app requires Git</strong> for local Claude Code sessions because it uses Git worktrees to isolate each session</li>
<li><strong>Non-Git folders will fail</strong> — you must run <code>git init</code> in any folder you want to use with local sessions</li>
<li><strong>The CLI and Desktop app are separate</strong> — installing the CLI (<code>claude</code> command) is useful for diagnostics but the Desktop app bundles its own version</li>
<li><strong>The error message isn't specific</strong> — "Failed to load session" doesn't clearly indicate that Git/repository issues are the cause, which can make troubleshooting difficult</li>
</ol>
<h2>Environment</h2>
<ul>
<li><strong>OS:</strong> Windows 10/11</li>
<li><strong>Claude Desktop App:</strong> Latest version</li>
<li><strong>Claude Code CLI:</strong> 2.1.6 (for diagnostics)</li>
<li><strong>Git:</strong> 2.52.0</li>
<li><strong>Node.js:</strong> v24.12.0</li>
</ul>
<hr>
<p><em>Hope this helps others encountering the same issue! The fix is straightforward once you know that Git repository initialization is required.</em></p></body></html><!--EndFragment-->
</body>
</html># Solution: "Failed to Load Session" Error in Claude Desktop App (Windows)
Problem Summary
When attempting to use the Claude Code feature in the Claude Desktop app on Windows, users may encounter a "Failed to load session" error when trying to access local files or start a local coding session.
Root Cause
The "Failed to load session" error can occur due to missing dependencies that the Claude Desktop app requires for local sessions, specifically:
While the Claude Desktop app bundles its own version of Claude Code internally, it relies on your system having Git properly installed and configured.
Diagnostic Steps
Step 1: Verify Git is Installed
Open PowerShell or Command Prompt and run:
Expected output: A version number like
git version 2.52.0.windows.1If you get "not recognized as a command": Install Git from https://git-scm.com/downloads/win
Step 2: Verify Node.js is Installed (Optional but Recommended)
Expected output: A version number like
v24.12.0(should be v18+)Note: The native Claude Code installer doesn't require Node.js, but many development workflows do. Install from https://nodejs.org/ if needed.
Step 3: Install Claude Code CLI for Diagnostics
The Claude Desktop app bundles Claude Code internally but doesn't expose the
claudecommand to your terminal. Installing the CLI separately allows you to run diagnostic commands.PowerShell:
Command Prompt:
Step 4: Add Claude Code to Your PATH
After installation, you may see a message like:
Quick fix via PowerShell:
Or manually:
Win + R, typesysdm.cpl, press Enter%USERPROFILE%\.local\binImportant: Close and reopen your terminal after updating the PATH.
Step 5: Run Diagnostics
This will show the health of your Claude Code installation. A healthy output looks like:
Step 6: Ensure Your Project Folder is a Git Repository
This is the most commonly overlooked requirement. The Claude Desktop app's local sessions require the folder to be a Git repository.
Navigate to your project folder and check:
If you see "fatal: not a git repository", initialize Git:
Solution Summary
To resolve the "Failed to load session" error:
| Requirement | How to Verify | How to Fix |
|-------------|---------------|------------|
| Git installed |
git --version| Install from [git-scm.com](https://git-scm.com/downloads/win) || Folder is a Git repo |
git statusin project folder | Rungit init|| (Optional) Node.js 18+ |
node --version| Install from [nodejs.org](https://nodejs.org) |Key Takeaways
git initin any folder you want to use with local sessionsclaudecommand) is useful for diagnostics but the Desktop app bundles its own versionEnvironment
---
Hope this helps others encountering the same issue! The fix is straightforward once you know that Git repository initialization is required.
When I've had this happen git was already installed and already working with Claude desktop, so missing git isn't always the root cause here. Since OP's description of the problem mentions that it's happening after trying to resume an existing Code session, I'm going to go out on a limb and guess that they aren't lacking git either.
You're correct about the initial post, however, it's clear you did not read my full answer and only the initial summary of the issue I experienced. git was only 1 of 5 issues.
I'm not using it in desktop mode (locally) just using it right from the Claude Code and Github site so this doesn't appear to be applicable.
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.