Skip to content

Windows + OpenCode Desktop v1.3.13: plugin fails to load with getVercelOidcToken export error #20663

@starkiller43

Description

@starkiller43

Description

### Description

`open-mem` fails to load as an OpenCode Desktop plugin on **Windows** with **OpenCode v1.3.13**.

OpenCode shows a session error popup on startup, and logs indicate that the `open-mem` plugin fails to load due to a `getVercelOidcToken` export error.

The same setup works after downgrading OpenCode Desktop to **v1.3.12**, so this may be an OpenCode regression, but I’m reporting it here too because `open-mem` is the plugin that triggers it.

---

### Environment

- OS: **Windows**
- OpenCode Desktop: **v1.3.13** -> broken
- OpenCode Desktop: **v1.3.12** -> works
- open-mem: **0.14.2**

---

### Plugin config

```json
{
  "plugin": [
    "oh-my-opencode@latest",
    "open-mem"
  ]
}
Error log

From OpenCode Desktop log:

service=plugin path=open-mem target=file:///C:/Users/<USER>/.cache/opencode/node_modules/open-mem/dist/index.js error=Export named 'getVercelOidcToken' not found in module 'C:\Users\<USER>\.cache\opencode\node_modules\@vercel\oidc\dist\index.js'. failed to load plugin
Dependency versions found in OpenCode plugin cache
From C:\Users\<USER>\.cache\opencode\node_modules\:

open-mem: 0.14.2
ai: 6.0.141
@ai-sdk/gateway: 3.0.83
@vercel/oidc: 3.1.0
I also verified that the actual cached file:

@vercel/oidc/dist/index.js

does contain getVercelOidcToken.

So the issue may be related to module resolution / ESM-CJS interop at runtime, not a literally missing function in the file.

What I tested
Rebuilt dashboard assets locally
Reinstalled / reconfigured open-mem
Cleared OpenCode plugin cache
Downgraded OpenCode Desktop from v1.3.13 to v1.3.12
After downgrading to v1.3.12, the issue disappeared.

Conclusion
This looks like a compatibility problem between:

OpenCode Desktop v1.3.13
open-mem
transitive dependency chain involving ai -> @ai-sdk/gateway -> @vercel/oidc
It may not be an open-mem bug alone, but I wanted to report it because open-mem is the plugin that triggers the failure.

If useful, I can provide the exact OpenCode log file contents.

### Plugins

_No response_

### OpenCode version

_No response_

### Steps to reproduce

_No response_

### Screenshot and/or share link

_No response_

### Operating System

_No response_

### Terminal

_No response_

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions