[Bug] CLI sessions cannot be resumed in Desktop app after recent update — "transcript has no cwd"
Resolved 💬 3 comments Opened Apr 2, 2026 by hongbanzang Closed Apr 5, 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?
Description
After a recent version update, CLI sessions started from a project directory
can no longer be resumed in the Claude Code Desktop app.
The desktop app shows an error dialog:
"CLI session <session-id> transcript has no cwd — cannot import"
This worked correctly before the update.
Steps to Reproduce
- Open a terminal and
cdinto a project directory - Run
claudeto start a session - Have a conversation and close the session
- Open Claude Code Desktop app
- Run
/resumeand select the CLI session
Expected Behavior
The CLI session is imported and resumed in the Desktop app as before.
Actual Behavior
An error dialog appears:
"CLI session <id> transcript has no cwd — cannot import"
Environment
- Claude Code version: 2.1.90
- Claude Desktop (for Mac) : 1.2.234
- OS: macOS
- Started from a specific project directory (cwd is definite)
Additional Notes
This is a regression. The same workflow worked fine before the recent update.
What Should Happen?
The CLI session should be imported and resumed in the Desktop app,
as it did before the recent update.
Error Messages/Logs
CLI session <session-id> transcript has no cwd — cannot import
Steps to Reproduce
- Open a terminal and
cdinto a project directory - Run
claudeto start a session - Have a conversation and close the session
- Open Claude Code Desktop app
- Run
/resumeand select the CLI session
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.90
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗