[FEATURE]: Fail gracefully when using --continue flag on a project with zero sessions #25989

Activity

1. github-actions

   assigned

   rekram1-node

   on May 6, 2026
2. github-actions commented on May 6, 2026

   

   github-actionsBot

   on May 6, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • opencode -c hangs indefinitely in directories with no prior sessions #23437: Same root cause — opencode -c in a directory with no prior sessions triggers the "dummy" sessionID validation error and leaves the TUI in a broken state. That issue is closed but describes the identical scenario and error you're seeing.

   Please review #23437 and let us know if your issue is still present or if it was addressed differently.
3. kagura-chen commented on May 6, 2026

   

   kagura-chen

   on May 6, 2026

   Contributor

   More actions

   I'd like to work on this. The root cause is in the TUI's app.tsx: when --continue is used, the initial route is set to sessionID: "dummy", and the effect that resolves the actual session simply does nothing when no sessions exist — leaving the invalid "dummy" route active.

   The fix: in the createEffect that handles --continue, when no session is found and sync has loaded, navigate to the home route instead. This matches run.ts behavior which already gracefully falls back to creating a new session.
4. Kushalk0677 commented on May 6, 2026

   

   Kushalk0677

   on May 6, 2026

   More actions

   Solved it -

   #26000
5. rekram1-node commented on May 6, 2026

   

   rekram1-node

   on May 6, 2026

   Collaborator

   More actions

   

   This has been fixed, it beahves as expected
6. rekram1-node

   closed this as completedon May 6, 2026
7. superDuperCyberTechno commented on May 7, 2026

   

   superDuperCyberTechno

   on May 7, 2026

   Author

   More actions

   

   This has been fixed, it beahves as expected

   This is not the behavior I see...

   
8. superDuperCyberTechno commented on May 12, 2026

   

   superDuperCyberTechno

   on May 12, 2026

   Last edited by superDuperCyberTechno

   Author

   More actions

   @rekram1-node

   v1.14.48 introduces a regression with the following being dumped to the home screen...

   Error: Expected a string starting with "ses", got "dummy"
       at <anonymous> (/$bunfs/root/chunk-w8ygwpb0.js:25:10123)
       at <anonymous> (/$bunfs/root/chunk-w8ygwpb0.js:35:4256)
       at <anonymous> (/$bunfs/root/chunk-pyddsvgn.js:2:117604)
       at ~effect/Effect/successCont (/$bunfs/root/chunk-w8ygwpb0.js:25:7736)
       at runLoop (/$bunfs/root/chunk-w8ygwpb0.js:25:2045)
       at evaluate (/$bunfs/root/chunk-w8ygwpb0.js:25:1435)
       at <anonymous> (/$bunfs/root/chunk-w8ygwpb0.js:25:24200)
       at <anonymous> (/$bunfs/root/chunk-fbmkme8a.js:4:19972)
       at new Promise (native:1:11)
       at <anonymous> (/$bunfs/root/chunk-fbmkme8a.js:4:19842)
       at fetch (/$bunfs/root/src/cli/cmd/tui/worker.js:2:3220)
       at <anonymous> (/$bunfs/root/chunk-wy5bppnp.js:2:
   

   For anyone reading, this erroneous behaviour can be bypassed with the following bash function...

   run_opencode() {
     session_exists=$(opencode session list --format json -n 1)
     if [[ -n "${session_exists}" ]]; then
       opencode --continue
     else
       opencode
     fi
   }