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

Resolved 💬 15 comments Opened Mar 8, 2026 by Natalie-NCO Closed Jun 6, 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?

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_

View original on GitHub ↗

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