claude-code - 💡(How to fix) Fix [BUG] Claude Code Desktop lost sessions, zombie processes, worktree fallback, usage spike, and /feedback unusable [1 comments, 2 participants]

Preflight Checklist

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

What's Wrong?

Summary

Claude Code Desktop on Windows has repeatedly lost sessions and worktree state over the past ~2 weeks. I also experienced abnormal usage-limit consumption while requests failed or sessions were unusable.

Anthropic support instructed me to use /feedback or /bug, but those commands do not work in the affected Desktop session.

Environment

• Plan: Claude Max 5x
• OS: Windows
• App: Claude Desktop / Claude Code Desktop
• Project path: Y:\gony_land
• Approximate period: last ~2 weeks
• Logs attached: Claude-logs-2026-05-04T10-06-21-717Z.zip

Request

Please investigate the attached logs and account-side usage records. I am requesting:

1. escalation to the Claude Code Desktop engineering/support team,
2. recovery or explanation of the abnormal usage-limit consumption,
3. refund or credit for the affected usage period,
4. guidance for safely cleaning corrupted Claude Code Desktop sessions on Windows without losing recoverable work.

What Should Happen?

What happened

1. Claude Code Desktop sessions disappeared or became unrecoverable.
2. Multiple claude.exe / claude-code processes remained after restart or quit.
3. Worktree state became inconsistent.
4. Usage limit suddenly dropped much faster than normal.
   • Normal terminal usage: around ~2% per task
   • Problem case: one failed/unusable task consumed around 10%
   • Another failed API/error case consumed around 27%
5. I hit the 5-hour usage limit and could not continue.
6. Support told me to use /feedback or /bug, but the command fails.

Error Messages/Logs

## Evidence from logs

The attached logs contain repeated evidence of local/runtime instability:

- `Utility process exited with killed`
- `Utility process exited with crashed`
- `Graceful shutdown failed, forcing termination`
- `Persistent RPC: connection ended ... EOF`
- `sdk-daemon disconnected`
- `Worktree ... was deleted; falling back to origin repo`
- `Migrated transcript ...`
- `Stopping 6 active session(s) on quit`
- `Stopping 3 active session(s) on quit`
- `EBUSY: resource busy or locked`
- `TypeError: Failed to fetch`
- `failed to obtain oauth token`
- `CLI requested token refresh after 401`

## /feedback problem

When I try `/feedback` in Claude Code Desktop, I get:

`/feedback can only be used in a local session of this desktop build.`

So I cannot submit the report through the channel that support instructed me to use.

## Expected behavior

- Desktop sessions should remain recoverable.
- Worktrees should not disappear or silently fall back to origin repo.
- Zombie/stale processes should not hold cwd/worktree handles.
- Failed API/session attempts should not consume abnormal usage.
- `/feedback` or `/bug` should work from the affected Desktop session, or support should provide another escalation path.

Steps to Reproduce

I do not have a 100% deterministic minimal reproduction yet, because the issue appears to depend on Claude Code Desktop's local session/worktree/daemon state over time.

However, this is the repeated pattern I experienced:

1. Install and use Claude Code Desktop on Windows with a Claude Max 5x account.

2. Open a project located at Y:\gony_land.

3. Start Claude Code Desktop sessions for normal coding work over multiple days.

4. Continue working through Desktop sessions where Claude Code creates or uses worktrees under:

   Y:\gony_land\.claude\worktrees\...

5. Quit or restart Claude Code Desktop, and in some cases restart Windows.

6. Reopen Claude Code Desktop and try to continue the previous session.

7. Observe that one or more of the following happens:

   • the previous session disappears or becomes unrecoverable,
   • multiple claude.exe / claude-code processes remain,
   • stale processes appear to hold the project cwd or worktree handles,
   • the worktree is deleted or becomes unavailable,
   • Claude Code falls back to the origin repo,
   • the transcript is migrated to a different project path,
   • API/RPC errors occur,
   • usage limit drops abnormally while the task fails or the session is unusable.

8. Try to report the issue from the affected Claude Code Desktop session using /feedback or /bug, as instructed by Anthropic support.

9. Observe that /feedback fails with:

   /feedback can only be used in a local session of this desktop build.

10. Check the attached logs. They contain repeated entries such as:

    • Utility process exited with killed
    • Utility process exited with crashed
    • Graceful shutdown failed, forcing termination
    • Persistent RPC: connection ended ... EOF
    • sdk-daemon disconnected
    • Worktree ... was deleted; falling back to origin repo
    • EBUSY: resource busy or locked

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.119 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information