session: unable to resume a session after its directory is removed (Session location unavailable) #55035

Activity

1. opencode-agent commented on Oct 13, 2026

   

   opencode-agentBot

   on Oct 13, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report!

   What you're asking for: when a session's working directory has been deleted, it should still open with a sensible fallback (for example the home directory, or a clearly labelled read-only transcript) instead of requiring a move to another directory first.

   In v2, the "Session location unavailable" prompt is how a missing directory is meant to be handled. The session history should still be shown; only the message input is replaced by the prompt to move the session (see #46215 and #53268). The Location unavailable error you found comes from the session picker's search, which falls back to the local session list, so it shouldn't stop the session from opening. If you're using the TUI or desktop app and the history does not appear at all, please say which one you're using. That would be a separate bug.

   An automatic fallback directory or an explicit read-only mode would be a change to how this works, so I've marked this as a feature request for the maintainers to consider. Related issues:

   • fix(desktop): recover from missing or inaccessible project folders #50952: open PR adding more recovery options (move, retry, close) for missing project folders in the desktop app
   • tui: false "Session location unavailable" prompt after upgrade reconnect #49352 / tui: agent keeps running while user is trapped in false location-unavailable modal #43415: the same prompt showing up wrongly for directories that do exist
   • sessions: POST /api/session/{id}/move stores a bogus path and hides the session from the project list #53454: moving a session can save a bad path
   • cli: migrated v1 sessions from non-git dirs missing from session list #52919 / tui: selecting a migrated v1 session does not open it #52924: problems with migrated v1 sessions, which may relate to the project_id = 'global' you saw

   Until then, recreating the directory or using Choose directory are the ways to continue these sessions, and opencode session export <id> still gives you the full transcript.
2. thehaven commented on Oct 14, 2026

   

   thehaven

   on Oct 14, 2026

   More actions

   Same failure mode, slightly different sub-case: worktree-removed sessions in
   the v2 CLI TUI (opencode2 2.0.28 on Linux, not the desktop client).

   Repro follows your steps 1-3, but the missing path is a removed
   git worktree rather than a deleted/moved project directory. The orphan
   sandboxes have a distinctive shape on this host:

   ~/.local/share/opencode/worktree/3bb416/<name>
   ~/.local/share/opencode/worktree/60843d/add-opencode-subagents-view
   ~/.local/share/opencode/worktree/a8f579/<name>
   

   The inner contents (opencode2's per-worktree data) are still on disk; it's
   the git worktree itself that's gone, and the opencode2 sqlite session DB
   still has rows whose directory field points to the now-missing path.
   opencode2 session list --format json confirms it: every row carries
   the directory of the cwd it was created in.

   Workaround that worked here: git worktree add <same-path> <branch>
   recreates the path, and opencode2 -c (or -s <id>) then resumes
   cleanly. The session is bound to the path, not to git's worktree-id
   hash, so the mismatch between the original 60843d and whatever new
   worktree-id git assigns is fine.

   Pre-emptive config that helped on the prevention side: setting
   session.new_location: "launch" in ~/.config/opencode/cli.json means
   new sessions in this CLI no longer inherit the active session's CWD; they
   stop binding to a soon-to-die worktree path. That doesn't recover
   already-orphaned sessions, just reduces the rate of new ones, and the
   underlying recovery UX you describe is the real gap.

   Pinning this here rather than filing a duplicate. Happy to file a
   separate feature request for a session.fallback_on_missing config
   (launch | home | prompt | skip) if that would help; let me know.