Hi, while building a shadow-only historical backfill workflow for TencentDB Agent Memory, I found that the seed workflow depends on the memory-tdai CLI being registered in OpenClaw.
Expected:
openclaw memory-tdai --help
openclaw memory-tdai seed --help
should be available after installing/enabling the TencentDB Agent Memory plugin.
Observed:
after upgrading OpenClaw, the official seed CLI was not registered, so historical seed / shadow backfill workflows could not run through the documented command path.
This blocks tools that rely on the official seed entrypoint instead of importing private plugin internals.
Related discussion/tooling:
Question:
Should the memory-tdai CLI registration be handled by this plugin package/manifest, or should this be fixed in OpenClaw's plugin command registration layer?
Happy to submit a PR once the expected registration boundary is confirmed.
Hi, while building a shadow-only historical backfill workflow for TencentDB Agent Memory, I found that the seed workflow depends on the
memory-tdaiCLI being registered in OpenClaw.Expected:
should be available after installing/enabling the TencentDB Agent Memory plugin.
Observed:
after upgrading OpenClaw, the official seed CLI was not registered, so historical seed / shadow backfill workflows could not run through the documented command path.
This blocks tools that rely on the official seed entrypoint instead of importing private plugin internals.
Related discussion/tooling:
Question:
Should the
memory-tdaiCLI registration be handled by this plugin package/manifest, or should this be fixed in OpenClaw's plugin command registration layer?Happy to submit a PR once the expected registration boundary is confirmed.