I lost all sessions.

[heebo1974]

Any ideas why I just lost all sessions.
I had approx 10 pinned sessions.
Today those all just disappeared.

[heebo1974]

I was able to find those session ids with help of the opencode!! :)
But those don't come up with ctrl+p switch session.
Anyway I can pin those again.

It seems that correct command is opencode session list.

Anyway I don't understand why sessions disapperared at first place.

[heebo1974]

No there is something wrong. If I resume those old sessions, those won't come back to the session list.
I can use them with the id, but those id won't be saved in the sessionlist. I had to save those locally to my pc.

[magnusoverli]

Thanks for reporting this. There is not much to go on yet, but your follow-up is useful: if the old sessions can still be resumed by ID, then the raw session data is probably not gone.

My current theory is that the session list / pinned-session metadata has been reset, corrupted, moved, or changed format, while the underlying session files still exist. That could happen if OpenCode changed how it indexes sessions, if the add-on was restarted or killed while writing state, or if the effective project/workspace identity changed.

Could you run these from inside the OpenCode add-on terminal and paste the output?

opencode --version
opencode debug paths
opencode session list
ls -la /data/.local/share/opencode
ls -la /data/.local/state/opencode 2>/dev/null || true
find /data -maxdepth 4 -iname "*session*" -o -iname "*state*"

Also helpful:

• Did this happen after an add-on update, restart, crash, or Home Assistant restore?
• If you create a new session and pin it, does it survive an add-on restart?
• Does opencode session list show the missing old sessions, or only the IDs you found manually?

I do not think this is necessarily the add-on deleting sessions. The add-on stores OpenCode data under /data, which should persist across restarts/updates. This looks more like OpenCode's session index or pinned/recent-session state getting out of sync with the actual stored sessions, but the diagnostics above should help confirm that.

[heebo1974]

opencode --version
1.15.13

opencode debug paths ->
home /data
data /data/.local/share/opencode
bin /data/.cache/opencode/bin
log /data/.local/share/opencode/log
repos /data/.local/share/opencode/repos
cache /data/.cache/opencode
config /data/.config/opencode
state /data/.local/state/opencode
tmp /tmp/opencode

opencode session list
Error: Unexpected error, check log file at /data/.local/share/opencode/log/2026-06-02T170134.log for more details
Executable not found in $PATH: "less"

ls -la /data/.local/share/opencode
total 27412
drwxr-xr-x 6 root root 4096 Jun 2 20:01 .
drwxr-xr-x 5 root root 4096 May 29 12:34 ..
-rw------- 1 root root 2397 May 31 18:10 auth.json
drwxr-xr-x 2 root root 4096 Jun 2 20:01 log
-rw-r--r-- 1 root root 27996160 Jun 2 19:59 opencode.db
-rw-r--r-- 1 root root 32768 Jun 2 20:01 opencode.db-shm
-rw-r--r-- 1 root root 4152 Jun 2 20:01 opencode.db-wal
drwxr-xr-x 2 root root 4096 May 14 14:02 repos
drwxr-xr-x 3 root root 4096 May 14 14:04 storage
drwxr-xr-x 2 root root 4096 Jun 1 20:07 tool-output

ls -la /data/.local/state/opencode 2>/dev/null || true
total 32
drwxr-xr-x 3 root root 4096 May 29 18:24 .
drwxr-xr-x 3 root root 4096 May 14 14:01 ..
-rw-r--r-- 1 root root 303 May 29 18:24 kv.json
drwxr-xr-x 2 root root 4096 Jun 2 19:59 locks
-rw-r--r-- 1 root root 511 Jun 1 20:50 model.json
-rw-r--r-- 1 root root 6020 Jun 2 19:59 prompt-history.jsonl
-rw-r--r-- 1 root root 324 May 28 21:09 session.json

find /data -maxdepth 4 -iname "session" -o -iname "state"
/data/.local/state
/data/.local/state/opencode/session.json

Did this happen after an add-on update, restart, crash, or Home Assistant restore?
-Unfortunately I don't remember anymore the situation.

If you create a new session and pin it, does it survive an add-on restart?
Tested it now, and it will survive. But if I open some old ids those can't be pinned. We you can pin, but does not stay in the list.

Does opencode session list show the missing old sessions, or only the IDs you found manually?
Only that error which already posted.

[heebo1974]

I will now going to update that new 1.9.1 version of opencode addon.

[magnusoverli]

Thanks for the extra diagnostics. That helps narrow this down.

One thing is now clear: the opencode session list error is caused by the add-on image not having less installed. OpenCode tries to use less as a pager for the interactive table output. That is an add-on packaging gap on our side, and we should fix it, but I do not think it explains the Ctrl+P/pinned-session behavior by itself.

For the missing sessions, my current suspicion is an upstream OpenCode session-picker/list filtering issue rather than the add-on deleting data. This is not confirmed yet, but it looks related to these upstream OpenCode threads:

• TUI /sessions picker only shows recent sessions anomalyco/opencode#13877
• fix(tui): request root sessions in session dialog anomalyco/opencode#26432

The pattern there is similar: sessions still exist in opencode.db and can be opened by ID, but the TUI session picker only shows a filtered subset, for example recent sessions or sessions matching the current project/path. If a pinned session is no longer included in that filtered list, it can look like pinning does not stick even though the raw session is still present.

Could you run these from inside the add-on terminal and paste the output? The first one avoids the missing less problem:

opencode session list --format json
opencode db "select id, title, datetime(time_updated/1000, 'unixepoch') as updated, directory, path, project_id, parent_id from session where parent_id is null order by time_updated desc limit 100;"

Also useful if you can check one or two of the old session IDs that you can still open manually:

opencode db "select id, title, datetime(time_updated/1000, 'unixepoch') as updated, directory, path, project_id, parent_id from session where id in ('PASTE_OLD_SESSION_ID_HERE');"

And two quick behavior checks:

• After updating the add-on, does a newly created and pinned session still survive an add-on restart?
• Are the missing sessions older than roughly 30 days, or were they created from a different folder/workspace than the current /homeassistant session?

Please do not delete or manually edit opencode.db; the goal is just to inspect whether the missing sessions differ by age, directory, path, or project_id.

[heebo1974]

[
{
"id": "ses_1b5b6b8d2ffeygEOGaaWq4JHTm",
"title": "LVV-logiikka",
"updated": 1780422560433,
"created": 1779362776878,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_176b435d2ffexj7m0bFdNsLwKR",
"title": "Test session",
"updated": 1780419911604,
"created": 1780419906093,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1957ca113ffebOlkpA7fxUiIcv",
"title": "Frigate tweakkausta",
"updated": 1780322569721,
"created": 1779903454957,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1b01eaf66ffezO0Jqd20H7qPFl",
"title": "Autojen esilämmityslogiikan tarkistus",
"updated": 1779990534393,
"created": 1779456626841,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1b557ceccffeceJ2as8NwXwzu4",
"title": "Lattialämmitysten logiikan tarkistus",
"updated": 1779990365769,
"created": 1779368997172,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_19066b6edffeyTVN19xbEwRfDI",
"title": "Kadonneiden opencode-sessioiden palautus",
"updated": 1779988921066,
"created": 1779988777235,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1906f5aa0ffeHopdgmbmdlJUNd",
"title": "LVV päiväanalyysi",
"updated": 1779988500086,
"created": 1779988211039,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1aac062f3ffeKGsrGyuO5V8mEB",
"title": "Jumiwatchdogin tarkoitus",
"updated": 1779546994256,
"created": 1779546692876,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1afdbab32ffeKV0ln77zyMf4GC",
"title": "New session - 2026-05-22T14:43:38.829Z",
"updated": 1779522469822,
"created": 1779461018829,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1b4870257ffesODQEXgZZyyQ7A",
"title": "AGENTS.md:n SSH-kohdan poistaminen käytöstä",
"updated": 1779453979463,
"created": 1779382681000,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1b585018affedCFtySMEKBjGcV",
"title": "ILP-viilennyksen toiminnan ja logiikan arviointi",
"updated": 1779368251072,
"created": 1779366035061,
"projectId": "global",
"directory": "/homeassistant"
},
{
"created": 1779366035061,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1b598eb58ffeM4mCDeM3gqzbYN",
"title": "Epäilyttävien lokien korjaus",
"updated": 1779365522894,
"created": 1779364730023,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1ce71ae92ffeoCWmdLk5vAUiuj",
"title": "New session - 2026-05-16T16:11:11.085Z",
"updated": 1778948111837,
"created": 1778947871085,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1ce79a01cffeakBivcrTwbL1RV",
"title": "New session - 2026-05-16T16:02:30.499Z",
"updated": 1778947670305,
"created": 1778947350499,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1d4813370ffeebGnZW87rOa1vw",
"title": "New session - 2026-05-15T11:56:30.740Z",
"updated": 1778846519776,
"created": 1778846190740,
"projectId": "global",
"directory": "/homeassistant"
},
{
"id": "ses_1d9d796efffe9px66adS4RGJAS",
"title": "List directory contents",
"updated": 1778757906988,
"created": 1778756643088,
"projectId": "global",
"directory": "/homeassistant"
}
]

id title updated directory path project_id parent_id
ses_1b5b6b8d2ffeygEOGaaWq4JHTm LVV-logiikka 2026-06-02 17:49:20 /homeassistant global
ses_176b435d2ffexj7m0bFdNsLwKR Test session 2026-06-02 17:05:11 /homeassistant homeassistant global
ses_1957ca113ffebOlkpA7fxUiIcv Frigate tweakkausta 2026-06-01 14:02:49 /homeassistant global
ses_1b01eaf66ffezO0Jqd20H7qPFl Autojen esilämmityslogiikan tarkistus 2026-05-28 17:48:54 /homeassistant global
ses_1b557ceccffeceJ2as8NwXwzu4 Lattialämmitysten logiikan tarkistus 2026-05-28 17:46:05 /homeassistant global
ses_19066b6edffeyTVN19xbEwRfDI Kadonneiden opencode-sessioiden palautus 2026-05-28 17:22:01 /homeassistant homeassistant global
ses_1906f5aa0ffeHopdgmbmdlJUNd LVV päiväanalyysi 2026-05-28 17:15:00 /homeassistant homeassistant global
ses_1aac062f3ffeKGsrGyuO5V8mEB Jumiwatchdogin tarkoitus 2026-05-23 14:36:34 /homeassistant global
ses_1afdbab32ffeKV0ln77zyMf4GC New session - 2026-05-22T14:43:38.829Z 2026-05-23 07:47:49 /homeassistant global
ses_1b4870257ffesODQEXgZZyyQ7A AGENTS.md:n SSH-kohdan poistaminen käytöstä 2026-05-22 12:46:19 /homeassistant global
ses_1b585018affedCFtySMEKBjGcV ILP-viilennyksen toiminnan ja logiikan arviointi 2026-05-21 12:57:31 /homeassistant global
ses_1b598eb58ffeM4mCDeM3gqzbYN Epäilyttävien lokien korjaus 2026-05-21 12:12:02 /homeassistant global
ses_1ce71ae92ffeoCWmdLk5vAUiuj New session - 2026-05-16T16:11:11.085Z 2026-05-16 16:15:11 /homeassistant global
ses_1ce79a01cffeakBivcrTwbL1RV New session - 2026-05-16T16:02:30.499Z 2026-05-16 16:07:50 /homeassistant global
ses_1d4813370ffeebGnZW87rOa1vw New session - 2026-05-15T11:56:30.740Z 2026-05-15 12:01:59 /homeassistant global
ses_1d9d796efffe9px66adS4RGJAS List directory contents 2026-05-14 11:25:06 /homeassistant global

id title updated directory path project_id parent_id
ses_1b5b6b8d2ffeygEOGaaWq4JHTm LVV-logiikka 2026-06-02 17:49:20 /homeassistant global

id title updated directory path project_id parent_id
ses_1957ca113ffebOlkpA7fxUiIcv Frigate tweakkausta 2026-06-01 14:02:49 /homeassistant global

---

After updating the add-on, does a newly created and pinned session still survive an add-on restart?
Yes all newly created and pinned survive restart.
But if I open old session with command:
opencode --session ses_1b5b6b8d2ffeygEOGaaWq4JHTm
Then the list shows this opened session and the newly created, but not those other old sessions.

Are the missing sessions older than roughly 30 days, or were they created from a different folder/workspace than the current /homeassistant session?
Hmm. Good question. :) I don't know. Probably same folder and there might be some sessions older than 30 days.

[magnusoverli]

Thanks for running all of that and for the detailed follow-up. This confirms the most important part: the sessions are not gone. They are still present in opencode.db, and opencode session list --format json can see them.

So I do not think the add-on deleted any session data. The remaining behavior looks like the upstream OpenCode session picker/list filtering issue we discussed: the TUI only shows a subset of sessions until an older session is opened directly by ID, even though the database still contains the full set. That matches the upstream reports and the open upstream fix here:

• TUI /sessions picker only shows recent sessions anomalyco/opencode#13877
• fix(tui): request root sessions in session dialog anomalyco/opencode#26432

Since the session data is intact and the picker behavior appears to be upstream OpenCode rather than this add-on deleting or losing data, I am going to close this issue here. Once upstream OpenCode releases a fix for the session picker, the add-on should pick it up through the bundled OpenCode version.

Thanks again for helping narrow this down.