ZodError: Part IDs missing 'prt' prefix in chat.message hook

[putueddy]

Bug

OpenCode v1.2.27 validates that all part IDs must start with "prt" prefix. The chat.message hook in opencode-supermemory creates parts with IDs that don't have this prefix, causing a ZodError on every user message submission.

Error

ZodError: [
  {
    "origin": "string",
    "code": "invalid_format",
    "format": "starts_with",
    "prefix": "prt",
    "path": ["id"],
    "message": "Invalid string: must start with \"prt\""
  }
]

at createUserMessage (/$bunfs/root/src/cli/cmd/tui/worker.js:189861:35)

Root Cause

In dist/index.js, the chat.message hook creates two parts with non-compliant IDs:

1. Line ~14548 (nudge part):

   id: `supermemory-nudge-${Date.now()}`,

2. Line ~14582 (context part):

   id: `supermemory-context-${Date.now()}`,

Both are pushed/unshifted into output.parts, which OpenCode then validates with a Zod schema requiring id to start with "prt".

Fix

Prefix the IDs with prt_:

id: `prt_supermemory-nudge-${Date.now()}`,

id: `prt_supermemory-context-${Date.now()}`,

Environment

• OpenCode: v1.2.27
• opencode-supermemory: v2.0.4
• macOS (arm64)

[walioo]

I reproduced this again and can confirm it still happens after upgrading OpenCode itself.

Re-verified environment

• OpenCode: 1.3.2 (upgraded from 1.2.27)
• opencode-supermemory: 2.0.5
• oh-my-opencode: 3.13.1
• superpowers: git install
• OS: Windows

Repro command

opencode run "hello" --print-logs --log-level DEBUG --format json

What I verified

I did plugin bisection:

• OpenCode only -> no error
• OpenCode + superpowers only -> no error
• OpenCode + opencode-supermemory only -> reproduces
• OpenCode 1.3.2 + opencode-supermemory -> still reproduces

So this is not fixed by upgrading OpenCode from 1.2.27 to 1.3.2.

Stronger root-cause evidence from 1.3.2 logs

OpenCode now logs the invalid part directly before save:

ERROR service=session.prompt ... issues=[{
  "origin":"string",
  "code":"invalid_format",
  "format":"starts_with",
  "prefix":"prt",
  "path":["id"],
  "message":"Invalid string: must start with \"prt\""
}] part={
  "id":"supermemory-context-1774527919595",
  "sessionID":"ses_2d5e4d58fffeD2v4ZbZGALkWe4",
  "messageID":"msg_d2a1b2b00001rCjM75zbYAgw6O",
  "type":"text",
  "text":"[SUPERMEMORY] ...",
  "synthetic":true
} invalid user part before save

Then OpenCode throws the same schema error:

Invalid string: must start with "prt"

This seems to confirm the plugin is injecting a synthetic text part with an id like supermemory-context-..., but current OpenCode expects part IDs with the prt... prefix.

If helpful, I can also provide the full debug log, but the key incompatibility appears to be the synthetic part ID format itself.

[MaheshtheDev]

this has been resolved with latest version of the package