You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Background project-indexing run passes sessionID "dummy" (Expected a string starting with "ses") #43020
Since ~Aug 6, 2026, the opencode log (~/.local/share/opencode/log/opencode.log) records a recurring ERROR from what appears to be a background (non-interactive) run:
level=ERROR message=failed error="Error: Expected a string starting with \"ses\", got \"dummy\""
Stack traces resolve entirely into bundled opencode code (/$bunfs/root/chunk-*.js, e.g. datjqaqc.js:25, cdtnt4d.js:2) — not user plugins.
Context around each occurrence
The failing run immediately performs watcher-backend and project-copy-refresh work, i.e. a background project-indexing pass separate from active sessions.
A background task (project copy / watcher) invokes a session-scoped API with the placeholder sessionID dummy, which then fails session-ID validation (Expected a string starting with "ses").
Environment
opencode 1.18.18 (also observed on earlier 1.18.x)
Linux x86_64 (Arch), opencode installed via official script, runs as agent CLI in long-lived sessions
Occurrences: 10 between Aug 6-17, 2026 (latest Aug 17)
Expected behavior
Background runs should either use a valid session ID or not invoke session-scoped APIs; the error suggests an internal wiring gap rather than user misconfiguration.
Duplicate of #34144 (and #28486) as flagged — same dummy placeholder root cause. Unique evidence from this report (background project-indexing context, 1.18.18 affected, ~1/day frequency) added to #34144.
Activity
github-actions commentedon Aug 17, 2026
This issue might be a duplicate of existing issues. Please check:
"dummy"sessionID placeholder causingExpected a string starting with "ses"errors — root cause identified as a hardcoded"dummy"placeholder being passed to session-scoped APIs before a real session ID is availableExpected a string starting with "ses", got "dummy") in a background/startup context causing session history to disappearsatwareAG-ironMike commentedon Aug 17, 2026
Duplicate of #34144 (and #28486) as flagged — same
dummyplaceholder root cause. Unique evidence from this report (background project-indexing context, 1.18.18 affected, ~1/day frequency) added to #34144.