[Bug] All sessions are gone

[ddanielcruzz]

I ran the command /compact, it seemed stuck so I proceeded to quit the app and when I re-opened and try to list my sessions I found out all of them were gone 🥲

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• bug: /compact is not interruptable #2928: bug: /compact is not interruptable - similar issue where compact gets stuck
• BUG: Compact + Queue interaction #2609: BUG: Compact + Queue interaction - issues with compact causing problems
• Session automatically compacted, destroying the entire working context #2945: Session automatically compacted, destroying the entire working context - compact destroying session context
• compact zaps plan #1548: compact zaps plan - compact causing data loss

The common pattern is that the /compact command can get stuck or cause unexpected behavior that results in loss of session data. Several users have reported similar issues where /compact appears to hang and requires force quitting the app, sometimes leading to session loss.

Feel free to ignore if none of these address your specific case.

[rekram1-node]

@ddanielcruzz all your sessions, everywhere?

[rekram1-node]

is there any chance this was in a project that didnt have any commits yet and then you did an initial commit?

[ddanielcruzz]

Hey @rekram1-node

1. I used opencode for only one project, so all my sessions were related to that project.

2. The repository had many commits. I initially started my session in a specific branch, but later switched to another branch to work on something else. I forgot to switch back and continued chatting. The responses were not accurate, which made me realize I was in the wrong branch. After switching back, I encountered a context window error, even though the TUI showed about 60% of the context in use, which was unusual. I decided to run /compact, but it got stuck, so I quit. After that, all my sessions were gone.

[rekram1-node]

@ddanielcruzz just wanna see the "damage" so to speak can you run a few commands and see if data is still there for me?

id=$(git rev-list --max-parents=0 --all)
ls ~/.local/share/opencode/storage/session/${id} # if this is empty then run next ls command and show output if possible
ls ~/.local/share/opencode/storage/session

git rev-list --max-parents=0 --all

^^ Run this in your project, it will give the project id, that can then be used to list sessions^^

[ddanielcruzz]

Hi @rekram1-node the latest data if from 2 days ago, so sadly my data is gone.

I encountered another issue where I closed a session as I added a new local MCP, once I re-opened I couldn't find the session in the list.

Running the commands you shared I have two directories, is that normal?.

I'm using git town to keep branches in sync as well as worktrees to have multiple instances of opencode in different branches. Not sure if it's related

[rekram1-node]

when u say running the commands shared which command and what was output?

[ddanielcruzz]

Running ls ~/.local/share/opencode/storage/session gives me two directories

[rekram1-node]

what if u use the id one?

[ddanielcruzz]

Running these two

id=$(git rev-list --max-parents=0 --all)
ls ~/.local/share/opencode/storage/session/${id}
# output
/.local/share/opencode/storage/session/7b9ebd75da850e8f2ce0013a13d973314c3c26c1\n97d5b7390b6695f5f8189e90aac11e97c707b93f\n15175d963f0ed863af3d3c0f6287ef8ab81db034\na8e844dad56388522ddbaa68a3285570d5cef7b3": No such file or directory (os error 2)

ls ~/.local/share/opencode/storage/session
# outputs two direcotries

[sjswerdloff]

I'm having a similar problem, but not related to compaction. I did compact, without interruption. I was able to continue, with no problem. Then I exited and restarted, and no sessions. started with dev (v.0.14.x?) yesterday, had this problem, updated to v.0.15.0 today, no joy. However a "new" session that I started is showing up as available. The old session ses_625e82ae4ffeJuaY06cCPYUQ3X.json was gone from the previous project subdirectory:
./session/4b0ea68d7af9a6031a7ffda7ad66e0cb83315750
and was in ./session/global

[rekram1-node]

there is a known issue that if you have a git repo without any commits, have sessions (they will be in global storage) then once you make commits you kinda “lose them” since the repo has commits and is no longer tracked in global

we ofc should handle this but does that sound like what may have happened for you?

[sjswerdloff]

there is a known issue that if you have a git repo without any commits, have sessions (they will be in global storage) then once you make commits you kinda “lose them” since the repo has commits and is no longer tracked in global

we ofc should handle this but does that sound like what may have happened for you?

#3123 fixed my problem.
My first commit in the repo I was working in: Date: Mon Oct 13 16:44:45 2025 +1300
Problem occurred after that, so I started working on a fix for it with first commit in opencode branch Date: Mon Oct 13 18:17:05 2025 +1300

So, no, I don't think it had to do with a git repo without commits. It looks like a straight forward migration/backward compatibility issue. Not that at 0.x you owe anyone backward compatibility, but... for me, if I couldn't fix this quickly, I would have given up on opencode, which would have been a shame because it is exactly the kind of tool I have been looking for and really want to use (across a variety of LLMs, and support for Cerebras was a huge bonus, the qwen-code fork that supported Cerebras was not playing well with newer commits to qwen-code). Huge gratitude to the maintainers and contributors of opencode.
I used a Gemini in gemini-cli to help me find and fix (#3123) and it threw in the "--continue" type behaviour as an automatic thing (which works for me, I have what is perhaps a different approach than some/many) but isn't really appropriate given that --continue is an option) so you probably want to remove that particular part of it.
I'm using a Claude Sonnet 4.5 (the session that got lost), and I'm really happy with how opencode works compared to Claude Code (and the stability/lack of unasked for automatic updates), and look forward to using it for gemini and qwen (without the sticky release issues or visible tearing when trying to avoid that issue).