[BUG] Desktop app: Cannot view/restore archived conversations or resume past sessions

Resolved 💬 2 comments Opened Mar 20, 2026 by Zsy03021 Closed Apr 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?

When using the Claude Code desktop app (Windows) connected to a remote server via SSH, there are two issues:

Archived conversations disappear completely — After using "Archive" on a conversation, it is removed from the sidebar with no way to restore or view it. The word "Archive" implies the conversation is saved and retrievable, but it effectively behaves like "Delete".

/export fails for the current session — Running /export in an active conversation returns "No transcript data found for this session".

No /resume support in desktop app — The CLI supports --resume to list and restore past sessions, but the desktop app UI has no equivalent feature. The session .jsonl files exist on the server (~/.claude/projects/), but there is no way to load them in the desktop app.

What Should Happen?

Archived conversations should be viewable and restorable from the sidebar (e.g., an "Archived" filter)
/export should work for active sessions
/resume or equivalent should be availa

Error Messages/Logs

Steps to Reproduce

Open Claude Code desktop app on Windows
Connect to a remote server (SSH)
Have a conversation, then click "Archive"
The conversation disappears from the sidebar
No filter, search, or menu option to view archived conversations
/export on a new session returns "No transcript data found for this session"

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.78

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

_No response_

View original on GitHub ↗

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