Workaround for Windsurf IDE: How to force-unarchive and restore broken Codex chat sessions manually

[vmbbz]

🛠️ Guide: How to Force-Unarchive & Restore Bugged Windsurf Chat Sessions

If your Windsurf editor sidebar lags, bugs out, or freezes up completely so that you cannot click your profile icon to open your archived threads—you can force-unarchive them directly through your local system files.

Because Windsurf saves individual chat history locally as raw log structures, you can manually correct the tree directory to trick the editor into forcefully indexing it back onto your primary screen.

---

Step 1: Extract the Archived Log File

1. Close Windsurf completely to prevent background write blocks.
2. Open Windows File Explorer and head straight to your local user settings:
   C:\Users\<Your-Username>\.codex\archived_sessions\
3. Locate the missing conversation file. It will be a large .jsonl data block named explicitly by timestamp (e.g., rollout-2026-05-28T...).
4. Highlight it and press Ctrl + X to cut it.

Step 2: Manually Drop it Into the Active Timeline Tree

Windsurf dynamically reads your history pane chronologically by parsing folders labeled: Year > Month > Day.

1. Navigate back out and open the active workspace directory:
   C:\Users\<Your-Username>\.codex\sessions\
2. Drill down through the numbers to accurately match the specific digits embedded in your file string. For a session matching May 28, 2026, drill straight to:
   📁 2026 ➡️ 📁 05 ➡️ 📁 28
   (Note: If the terminal day number folder doesn't exist yet, simply right-click -> Create New Folder, and title it using the two-digit day number).
3. Open that day folder, right-click, and press Ctrl + V to dump the JSONL file right inside.

Step 3: Clear the Editor UI Layout Cache

Windsurf holds an app state cache for all its visual sidebar elements. You must clear these folders so the editor resets its configuration indices on the next initialization loop.

1. Tap Win + R to trigger the Run prompt, paste %APPDATA%, and press Enter.
2. Locate and open the Windsurf directory, then click into the Cache path.
3. Permanently nuke both of these target folders to clear out corrupt workspace layout memory:
   • 🗑️ Cache_Data
   • 🗑️ No_Vary_Search

Step 4: Relaunch and Verify

1. Open Windsurf.
2. Tap open your sidebar panel.
3. The editor will automatically crawl the local tree paths, see the newly dropped session log in the matching day slot, and repopulate the entire thread instantly into your primary history sidebar!

IN MY CASE THE ARCHIVED FILE WAS IN THE 28 FOLDER (DAY)

The .codex/sessions directory is organized chronologically by year, month, and day (Year > Month > Day). Your archived file has the date 2026-05-28 in its name (rollout-2026-05-28...).To restore it properly, you need to match this folder structure exactly:Step 1: Place the File in the Correct FolderOpen the folder named 28 seen in my sample images below .Paste your rollout-2026-05-28T... JSONL file directly inside that folder.

Then follow Step 3 to clear cache.
P.S. Close editor whilst doing this..

[hoodrichpirobo]

The safer version of this workaround is: use Codex’s own unarchive command first, and only move JSONL files manually as a last resort.

Codex sessions are stored locally under:

~/.codex/sessions
~/.codex/archived_sessions

On Windows:

C:\Users\<you>\.codex\sessions
C:\Users\<you>\.codex\archived_sessions

The official restore path is:

codex unarchive <session-id>

The session id is usually the UUID at the end of the rollout filename:

rollout-2026-05-28T12-34-56-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.jsonl
                                  ^ this UUID is the session id

So the first thing I would try is:

codex unarchive xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

or, if you know the exact thread name:

codex unarchive "My session name"

Then reopen Windsurf and check the Codex sidebar again. Also check the thread filter: if only some sessions are visible, switch the thread list/filter to chronological/all threads.

Only if the CLI command fails or the Windsurf UI is corrupted would I use the manual file move approach.

Manual recovery checklist:

1. Fully close Windsurf/Codex first.
2. Back up the whole Codex state folder before changing anything:

C:\Users\<you>\.codex

3. Find the archived rollout file in:

C:\Users\<you>\.codex\archived_sessions

4. Move it to the active sessions date path that matches the filename:

C:\Users\<you>\.codex\sessions\YYYY\MM\DD

Example:

rollout-2026-05-28T...

goes here:

C:\Users\<you>\.codex\sessions\2026\05\28

5. Reopen Codex/Windsurf.

If the session still does not appear, run:

codex doctor

and look for thread inventory / rollout DB warnings. Recent Codex versions keep a thread inventory database as well as the JSONL rollout files, so manually moving files can leave metadata out of sync. That is why codex unarchive <session-id> is preferred: it updates the thread state through Codex instead of only moving a file on disk.

Clearing the Windsurf cache can help if the UI is stale, but I would treat that as a UI refresh step, not the main restore mechanism. The main restore mechanism should be:

codex unarchive <session-id>