cli.ts file can not be executed

[JoInterest]

Plugin Version

63d4750

OpenClaw Version

2026.3.13

Bug Description

Bug 回報資料（英文）

Issue: LanceDB Pro CLI (cli.ts) Cannot Run Standalone

Environment:

• OS: Linux 6.17.0 (x64)
• Node.js: v22.22.1
• Plugin version: 63d4750 (latest, 2026-03-21)
• Platform: OpenClaw plugin installed at /home/friday/.openclaw/workspace/plugins/memory-lancedb-pro/

Problem Description:

The cli.ts file cannot be executed as a standalone CLI tool. All attempts to run it directly fail with module resolution errors.

Root Causes (multiple):

1. No entry point: cli.ts has no main() function and no if __name__ == "__main__" guard. It only exports createMemoryCLI(), a factory function that expects a pre-constructed CLIContext object.
2. Missing bin in package.json: The package declares no CLI binary, so there's no canonical way to invoke it via npx or a global command.
3. src/store.js does not exist at runtime: cli.ts imports ./src/store.js and ./src/retriever.js using .js extensions, but only .ts source files exist in src/. The OpenClaw plugin uses jiti for on-the-fly TypeScript compilation, which works for the plugin runtime but not for standalone CLI execution.
4. No tsconfig.json for standalone compilation: Attempting to compile with tsc fails with strict TypeScript errors (8 errors including type mismatches and implicit any).

Attempted Fixes:

| Attempt                                   | Result                | Notes                                             |
| ----------------------------------------- | --------------------- | ------------------------------------------------- |
| node cli.ts                               | ❌ Error               | Tries to import .js files that don't exist        |
| npx tsx cli.ts                            | ❌ No output           | Silent failure, exits code 0 but produces nothing |
| npx jiti cli.ts                           | ❌ Error               | jiti loader not exported in package.json exports  |
| node --import jiti/register cli.ts        | ❌ No output           | Silent failure                                    |
| tsc compilation                           | ❌ 8 TypeScript errors | Strict mode type errors in source files           |
| Add tsx as devDependency + npx tsx cli.ts | ❌ No output           | CLI runs but produces no response                 |

Minimal Fix Required (any one of):

1. Add a standalone entry point: Create a src/cli-main.ts that constructs the CLIContext and calls createMemoryCLI(), then export it as the bin in package.json.
2. Or: Export main() from cli.ts: Add a function that can be called directly with the necessary context.
3. Or: Add tsconfig.json + build step: Compile .ts → .js so cli.ts can find its imports.

Error Messages:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/friday/.../memory-lancedb-pro/src/store.js'

(node:internal/modules/esm/resolve:275)
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './loader' is not defined by "exports"

Impact:
Users cannot invoke memory-lancedb-pro recall or any other CLI command directly. The recall functionality is only accessible through the OpenClaw plugin framework (via memory_recall tool registration), not as a standalone CLI.

Expected Behavior

N/A

Steps to Reproduce

N/A

Error Logs / Screenshots

Embedding Provider

None

OS / Platform

ubuntu 24.04

[AliceLJY]

Hi @JoInterest — thank you for this really detailed and well-researched bug report! The effort you put into trying multiple approaches and documenting each one is genuinely impressive, and it helps us understand the problem much better.

You've identified a real gap here — cli.ts was designed as an internal module that gets wired up through the OpenClaw plugin framework (via jiti for on-the-fly TS compilation), and we didn't provide a proper standalone entry point. That's a fair criticism and something we should address.

Your analysis of the root causes is spot-on:

• No standalone main() or entry guard
• No bin declaration in package.json
• The .js import extensions assume the plugin runtime environment
• No tsconfig.json for standalone compilation

The three fix paths you suggested are all reasonable. We're leaning toward option 1 (a dedicated src/cli-main.ts entry point with a bin export) as it would be the cleanest solution without disrupting the existing plugin integration.

A couple of quick questions to help us prioritize:

• Is standalone CLI access a blocker for your workflow, or is the OpenClaw plugin integration (via openclaw memory-pro ...) working for you as an alternative?
• Are there specific CLI commands you need outside the plugin context?

We'll work on a proper fix. Thanks again for taking the time to dig into this so thoroughly — it's incredibly helpful!

[JoInterest]

Hi @AliceLJY,

Thank you for the detailed response and for confirming the root causes — I really appreciate the thorough analysis on your end as well!

To answer your questions:

1. Is standalone CLI access a blocker?
It's not a hard blocker since the OpenClaw plugin integration is working for my daily workflow. However, having a standalone CLI would be very helpful for faster debugging and testing without needing to go through the full plugin framework. It would also make it easier for other developers to experiment with the package independently.

2. Specific CLI commands needed?
The main commands I'd need in standalone mode are memory recall and memory store — essentially the core read/write operations. Having a simple entry point like cli-main.ts with proper bin export (Option 1) would cover everything I need.

Looking forward to the fix! Let me know if there's anything I can help with on my end.

Best,
JoInterest

[AliceLJY]

Hi @JoInterest,

Thanks for the clear answers — that helps a lot!

Since memory-lancedb-pro is designed specifically as an OpenClaw plugin, standalone CLI support isn't really on our roadmap. The plugin integration (openclaw memory-pro ...) is the intended usage path.

That said, adding a standalone entry point is fairly straightforward — if you'd like to fork and add a cli-main.ts with bin export, you're welcome to submit a PR and we'd be happy to review it.

You might also want to check out RecallNest — it's built with standalone CLI usage in mind and supports the recall / store workflow you're looking for out of the box.