What's happening
When a user runs login, the CLI sends its version to Supermemory as cli_version in the auth URL. That value is hardcoded in src/services/auth.ts:165:
So every release since 2.0.10 identifies itself as 2.0.10 at login. The current release is 2.0.15 (package.json, and npm view opencode-supermemory version), but login still says 2.0.10.
The correct version is already available
This is the same class of bug as #64. #65 fixed it by making package.json the single source of truth: scripts/sync-version.mjs runs on every build and test and generates src/version.ts (export const PLUGIN_VERSION = "2.0.15"). The rest of the plugin already uses that constant:
| Where |
Uses |
Update check (src/index.ts:241, src/v2/runtime.ts:145) |
PLUGIN_VERSION ✅ |
sm_plugin_version on saved memories (src/services/client.ts:433) |
PLUGIN_VERSION ✅ |
cli_version at login (src/services/auth.ts:165) |
"2.0.10" ❌ |
The login value was added in #60 (2026-07-26), a week before #65 landed, so it was missed. As a result, the same install tags its memories 2.0.15 but reports 2.0.10 when it logs in.
Evidence in the wild
The log in #72 (2026-08-19, pnpm dlx opencode-supermemory@latest login) shows cli_version=2.0.10, when latest on npm was already 2.0.12.
Reproduce
Safe to run: the auth URL points at a dead local address and times out after 3 seconds, so nothing reaches Supermemory.
export HOME=$(mktemp -d)
export SUPERMEMORY_AUTH_URL=http://127.0.0.1:9/auth SUPERMEMORY_AUTH_TIMEOUT=3000
grep '"version"' package.json
node dist/cli.js login | grep -o 'cli_version=[0-9.]*'
Actual: "version": "2.0.15", then cli_version=2.0.10
Expected: cli_version=2.0.15, and it should follow package.json automatically on every release.
Impact
Low for users: login works either way. But any server-side use of cli_version (version adoption, support triage, deprecating old clients, compatibility checks) has been getting a wrong, frozen value since July.
What's happening
When a user runs
login, the CLI sends its version to Supermemory ascli_versionin the auth URL. That value is hardcoded insrc/services/auth.ts:165:So every release since 2.0.10 identifies itself as 2.0.10 at login. The current release is 2.0.15 (
package.json, andnpm view opencode-supermemory version), but login still says 2.0.10.The correct version is already available
This is the same class of bug as #64. #65 fixed it by making
package.jsonthe single source of truth:scripts/sync-version.mjsruns on every build and test and generatessrc/version.ts(export const PLUGIN_VERSION = "2.0.15"). The rest of the plugin already uses that constant:src/index.ts:241,src/v2/runtime.ts:145)PLUGIN_VERSION✅sm_plugin_versionon saved memories (src/services/client.ts:433)PLUGIN_VERSION✅cli_versionat login (src/services/auth.ts:165)"2.0.10"❌The login value was added in #60 (2026-07-26), a week before #65 landed, so it was missed. As a result, the same install tags its memories
2.0.15but reports2.0.10when it logs in.Evidence in the wild
The log in #72 (2026-08-19,
pnpm dlx opencode-supermemory@latest login) showscli_version=2.0.10, whenlateston npm was already 2.0.12.Reproduce
Safe to run: the auth URL points at a dead local address and times out after 3 seconds, so nothing reaches Supermemory.
Actual:
"version": "2.0.15", thencli_version=2.0.10Expected:
cli_version=2.0.15, and it should followpackage.jsonautomatically on every release.Impact
Low for users: login works either way. But any server-side use of
cli_version(version adoption, support triage, deprecating old clients, compatibility checks) has been getting a wrong, frozen value since July.