session: move keeps the source project, so the session appears in both workspaces #53830

Description

Summary

Moving a session to a directory that belongs to a different project does not reassign the session's project. The session keeps the source project_id, the destination directory is added as another worktree of the source project, and the session is then returned by project-scoped listings — so in the desktop GUI the same session shows up under both the old and the new workspace.

Environment

• opencode version: 2.0.24
• OS: Windows 10.0.26300.9457 (win32 x64)
• Terminal: xterm-256color (TERM_PROGRAM/COLORTERM unset)
• Shell: cmd.exe
• Install/channel: npm global @opencode/cli@2.0.24 (latest)
• Active plugins: none

Reproduction

1. Create two independent git repos: A = %TEMP%\opencode\movetestA, B = %TEMP%\opencode\movetestB (each git init + one commit).
2. From A, create a session: opencode run "reply with the single word: pong". The new session's session_v2.project_id is the project for A.
3. Move it to B: POST /api/session/{id}/move with {"destination":{"directory":".../movetestB"}} (also reproducible through the built-in session-move tool, and /move where the command is available).
4. Inspect the database and the session-list API (details in Additional Context).

Expected Behavior

The session should be associated with the destination project (the project for B). At minimum, the destination directory should not become a worktree of the source project. The session should appear only in the new workspace.

Actual Behavior

• session_v2.project_id remains the source project for A; only session_v2.directory changes to movetestB.
• The source project gains a second worktree row for movetestB.
• The location-switched message records the source projectID for both the previous and the new location.
• GET /api/session?project=<A> returns the session; GET /api/session?directory=movetestA excludes it; GET /api/session?directory=movetestB includes it.
• In the desktop GUI the same session is listed under both the old and the new workspace.

Additional Context

Evidence after the move:

session_v2: { id: "ses_...", project_id: "<projectA>", directory: ".../movetestB" }

worktree (project "<projectA>"):
  - ".../movetestA"
  - ".../movetestB"

session_message type="location-switched":
  {
    "projectID": "<projectA>",
    "previous": { "location": { "directory": ".../movetestA" }, "projectID": "<projectA>" },
    "location": { "directory": ".../movetestB" }, "projectID": "<projectA>"
  }

API membership (searched the moved session id in each response):

GET /api/session?project=<projectA>          -> PRESENT
GET /api/session?directory=.../movetestA     -> absent
GET /api/session?directory=.../movetestB     -> PRESENT

Because both directories now resolve to the same project (through worktree), any project/worktree-scoped view lists the session for each directory. Real-world case: two non-git directories under the global project — every global session is listed under both.

Frequency: consistent (reproduced 100%).
Workaround: restart the desktop app, or close and reopen the project to force a refresh; the underlying association still spans both directories.

Related: #34359 (TUI migration umbrella), #39614 (V2 UI does not support workspaces), #31026 (preserve directory context after moving a session), #35012 (/move does not work).

Plugins

No response

OpenCode version

2.0.24

Steps to reproduce

1. Create two independent git repos: A = %TEMP%\opencode\movetestA, B = %TEMP%\opencode\movetestB (each git init + one commit).
2. From A, create a session: opencode run "reply with the single word: pong". The new session's session_v2.project_id is the project for A.
3. Move it to B: POST /api/session/{id}/move with {"destination":{"directory":".../movetestB"}} (also reproducible through the built-in session-move tool, and /move where the command is available).
4. Inspect the database and the session-list API (details in Additional Context).

Screenshot and/or share link

No response

Operating System

10.0.26300.9457 (win32 x64)

Terminal

xterm-256color (TERM_PROGRAM/COLORTERM unset), Windows Terminal