migrate from clawdbot to openclaw #5
Conversation
Migrate plugin from Clawdbot to OpenClaw following the upstream rename. Updated peer dependency from `clawdbot >=2026.1.24` to `openclaw >=2026.1.29` Changed plugin ID to `openclaw-supermemory` Updated all imports from `clawdbot/plugin-sdk` to `openclaw/plugin-sdk` - Renamed env var from `SUPERMEMORY_CLAWDBOT_API_KEY` to `SUPERMEMORY_OPENCLAW_API_KEY`
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
|
|
||
| function defaultContainerTag(): string { | ||
| return sanitizeTag(`clawdbot_${hostname()}`) | ||
| return sanitizeTag(`openclaw_${hostname()}`) |
There was a problem hiding this comment.
Bug: Changing the default containerTag from clawdbot_{hostname} to openclaw_{hostname} will cause users on the default configuration to silently lose access to their existing memories after upgrading.
Severity: HIGH
Suggested Fix
To prevent silent data loss for existing users, implement a fallback mechanism. The application should first check for memories using the new openclaw_{hostname} tag, and if none are found, it should then check for the old clawdbot_{hostname} tag. This would provide backward compatibility during the transition period. Alternatively, add a prominent warning to users upon upgrade, informing them of the change and guiding them to manually configure their containerTag if they wish to access old memories.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: config.ts#L56
Potential issue: The default value for `containerTag` has been changed from
`clawdbot_{hostname}` to `openclaw_{hostname}`. Since the container tag acts as a
namespace for all memory operations, this change will cause existing users who rely on
the default configuration to silently lose access to all their previously stored
memories upon upgrading. The application will not crash or show any warnings; it will
simply connect to a new, empty memory namespace, effectively resulting in unintentional
data loss for this subset of users.
Did we get this right? 👍 / 👎 to inform future reviews.
Merge activity
|
Migrate plugin from Clawdbot to OpenClaw following the upstream rename.
clawdbot >=2026.1.24toopenclaw >=2026.1.29openclaw-supermemoryclawdbot/plugin-sdktoopenclaw/plugin-sdkSUPERMEMORY_CLAWDBOT_API_KEYtoSUPERMEMORY_OPENCLAW_API_KEY