[BUG] Archived Code session cannot be unarchived - equivalent to permanent deletion

[Natalie-NCO]

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?

I accidentally archived a Claude Code session when I was trying to rename it. There’s no way to unarchive it. When I open the archived session, there are no three dots or any option to unarchive. When I try to reactivate it by sending a message, I get “Failed to send message - An unknown network error has occurred.”

This is equivalent in functionality to deleting the session - I’ve permanently lost access to it from one accidental tap.
I believe this is a recent change. I recently updated to the latest app version, and prior to that update I had unarchived Code sessions multiple times without any issue.

This happened on iPhone, using the Claude mobile app (latest version as of 8 March 2026).

What Should Happen?

You need to reinstate the previous mechanism for unarchiving an archived session - three dots menu with “unarchive”.

Error Messages/Logs

Steps to Reproduce

Steps to recreate:
1. Open the Claude mobile app on iPhone
2. Go to your list of Claude Code sessions
3. Swipe left on a Code session (or tap the three dots) and select “Archive”
4. Open the archived session
5. Try to find an unarchive option — there are no three dots or any menu to unarchive
6. Try sending a message to reactivate the session — get “Failed to send message - An unknown network error has occurred”
7. The session is now permanently inaccessible with no way to recover it

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Unknown - first downloaded around End Feb 2026.

Claude Code Version

Unknown

Platform

Anthropic API

Operating System

Other

Terminal/Shell

Other

Additional Information

No response

[Natalie-NCO]

This is a major UX flaw in the mobile app. It should NEVER be that easy to accidentally lose all access to a session. This is now a major worry for any sessions in use going forward and an extreme frustration considering I was able to Unarchive sessions before the latest app update.

[Natalie-NCO]

Update: I now am unwilling to Archive sessions, just in case I need to access them at some point in the near future, meaning my Idle category is getting clogged up with no longer active threads, but too important to lose access to by Archiving - which makes even having an Archivinf feature irrelevant if it’s not safe to use.

[PBartrina]

Just found myself with the same issue. Accidentally archived an important session and I am unavailable to make it active again.
I've tried session dropdown menu (only shows Archive, not unarchive), using the session, unexistent context menu form the session list.

[Natalie-NCO]

It’s crazy isn’t it?! Were you able to unarchive sessions prior to the last update? I swear this has only started since I updated the app a couple of days ago

[PBartrina]

There is a way by editing the session files manually, but we should be able to do it through GUI

[SugaCrypto]

I built a GUI tool that lets you view, restore, and delete archived Cowork sessions from your browser.

It reads the session JSON files directly and provides a simple web UI to manage them — no manual JSON editing required.

Restore archived sessions (sets isArchived to false)
Permanently delete sessions you no longer need
Works on macOS, Windows, and Linux
No external dependencies (Python 3.8+ only)
Bilingual UI (English / Japanese)
https://github.com/SugaCrypto/cowork-archive-manager

Hope this helps until the bug is fixed!

[ericinsf]

Another victim of this unbelievably bad bug. Just wanted to add another voice.

Much work lost. Little faith remaining.