Repository navigation
Service crashes on missing session file (NotFoundError) #7773
Description
Activity
same issue here
Additional Context: Often Caused by #8538
In many cases I've observed, the session file exists but is looked up in the wrong directory due to project ID mismatch (#8538).
Evidence from SDK/server debugging
# Session actually exists here: $ find ~/.local/share/opencode/storage/session -name "ses_4288bb2f8ffe*.json" /home/user/.local/share/opencode/storage/session/eb6c255.../ses_4288bb2f8ffebHuFX7NUnv4i80.json # But the error shows lookup in global/: NotFoundError: Resource not found: /home/user/.local/share/opencode/storage/session/global/ses_4288bb2f8ffebHuFX7NUnv4i80.json
The session was created with the correct project-specific path, but subsequent operations (via SDK calls without directory context) resolve to
global/and fail.Relationship to #8538
This crash is often a symptom of #8538 (session lookup uses wrong project ID). Fixing #8538 would prevent many of these crashes because the session would be found.
Still Valuable as Defense-in-Depth
Even after #8538 is fixed, graceful error handling here is valuable for:
- Truly deleted/corrupted sessions
- Race conditions during session cleanup
- Manual file system modifications
Suggested: Return
nullor a typed error that callers can handle, rather than crashing the service.Update: I've submitted PR #9474 to fix #8538 with cross-project session lookup.
- added a commit that references this issue
on Jan 19, 2026 To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
Bug Report: Service crashes on missing session file (NotFoundError)
Version: 1.1.13
Environment:
Description:
The
opencode webservice crashes with an unhandledNotFoundErrorwhen attempting to access a session file that doesn't exist. The error is not gracefully handled, causing the entire process to exit.Error:
Expected behavior:
Missing session files should be handled gracefully - either by:
Actual behavior:
Unhandled exception crashes the web server process.
Suggested fix:
In
src/storage/storage.ts:204, wrap the file read in a try-catch or check for file existence before reading, returning a graceful error instead of throwing.Workaround:
Configure systemd service with
Restart=alwaysto auto-recover from crashes.