npm: opencode-ai (v1, latest=1.19.5) is not deprecated and silently breaks after Desktop v2 migrates the shared database #63044

Summary

The npm package opencode-ai still resolves to the v1 CLI (latest = 1.19.5) and is not deprecated. Once OpenCode Desktop v2 has started on the same machine, that CLI can no longer run any database command: every one of them dies with Database is not empty and has no session table, which reads like database corruption instead of a version mismatch. Deprecating opencode-ai (pointing at @opencode/cli) would stop this recurring trap at the source.

Environment

• opencode version: 1.19.5 (npm [email protected], the npm latest tag) and opencode v2.2.6 (OpenCode Desktop, %APPDATA%\ai.opencode.desktop\cli\2.2.6-x64\opencode-cli.exe)
• OS: Windows 11 Pro, 10.0.26200, win32 x64
• Terminal: OpenCode Desktop app; failures reproduced from PowerShell 7 and cmd.exe
• Shell: C:\WINDOWS\system32\cmd.exe
• Install/channel: npm global prefix D:\npm-global ([email protected]) + Desktop install
• Active plugins: none (only ~/.config/opencode/AGENTS.md and opencode.jsonc exist, no plugins entry)

Reproduction

1. npm install -g opencode-ai — installs what npm still advertises as latest (1.19.5), with no deprecation warning.
2. Install and use OpenCode Desktop 2.2.6. It creates/migrates the shared data directory ~/.local/share/opencode/opencode.db (table session becomes session_v2; the file contains 13 sessions at the time of writing).
3. From a terminal, run any of:
   • opencode stats
   • opencode session list
   • opencode db path

Expected Behavior

One of:

• opencode-ai is marked deprecated on npm with a message pointing to @opencode/cli / anomalyco/tap/opencode-v2, so nobody installs the v1 CLI by accident; or
• the v1 CLI detects that the database was migrated by a newer version and prints an actionable message, for example: "this data directory was migrated by OpenCode v2; run the v2 CLI (@opencode/cli) or set OPENCODE_DATA_DIR to a separate directory".

Actual Behavior

$ opencode --version
1.19.5

$ opencode db path
Error: Unexpected error
Database is not empty and has no session table

$ opencode stats
Error: Unexpected error
Database is not empty and has no session table

$ opencode session list
Error: Unexpected error
Database is not empty and has no session table

opencode db path cannot even report which database it is opening, so there is no way to confirm the collision from the CLI side. opencode-cli.exe 2.2.6 reads the same file fine (opencode stats → 13 sessions, 519 steps, 35.3m tokens), so nothing is actually corrupted.

Additional Context

This is the same underlying failure as the closed reports #53221, #55731, #56583, #59727 and #61106 — all of which were closed with the answer "install the v2 CLI instead". The number of duplicates suggests the message users see is not the real problem; the real problem is that npm install -g opencode-ai is still a valid, undocumented-as-legacy install path that produces a permanently broken CLI on any machine that also runs Desktop v2.

Database state when the error occurs (read with sqlite3 in read-only mode, no writes):

tables: account, account_state, blob, blob_ref, control_account, credential, event,
        event_sequence, instruction_blob, instruction_entry, instruction_state, job, kv,
        migration, permission, project, project_directory, schedule, session_inbox,
        session_message, session_part, session_v2, workspace, worktree

There is no session table, only session_v2, which is exactly what the v1 error message checks for.

If keeping the v1 package on npm is intentional, a deprecation notice alone would likely eliminate most of the duplicate reports, since npm install prints it at install time.