Trident Plugin

Permanent memory for OpenClaw agents. Lossless capture, intelligent routing, semantic recall, and disaster recovery in five tiers.

What to check before installing Trident: - Inspect the code and scripts: open index.ts, any scripts/install.sh, activate.sh, and plugin-manifest.json to see exactly what will run on activation (downloads, file writes, cron setup). - Verify binary sources and hashes: the plugin will download native binaries (Qdrant, FalkorDB). Confirm the exact download URLs and compare SHA256 signatures before allowing automatic setup. The qdrant example uses GitHub releases (reasonable); FalkorDB source is not consistently shown — confirm it. - Confirm where credentials are expected: docs reference embedding APIs and Qdrant API keys but the registry lists no required env vars. Decide how you will supply secrets (secure vault / environment) and ensure they are not stored in plaintext in config files. - Run in a sandbox first: if possible, test in an isolated VM/container with limited network and filesystem access to confirm behavior and outputs before enabling on your main agent. - Check template integrity and audit logs: the plugin claims SHA256 template verification and audit logging — verify these mechanisms are implemented and that the approval workflow prevents unverified templates from running automatically. - Consider disabling semantic recall initially: if you don't need vector search, keep semantic_recall_disabled until you review the binary installs, credential handling, and code. - Back up existing memory: before migrating or activating, back up ~/.openclaw/workspace/memory and any related files. Why I flagged this as suspicious (not outright malicious): the overall feature set fits the stated purpose, but there are inconsistent documentation claims and runtime behaviors (automatic binary downloads, scheduled execution, undeclared credential needs) that increase risk. If you can review the code and verify download URLs and signature checks, many of these concerns can be mitigated.

Type: OpenClaw Skill Name: project-trident-plugin Version: 2.0.0 The Trident plugin implements a complex, five-tier memory system that introduces high-risk behaviors, most notably the automatic downloading and execution of external binaries (Qdrant and FalkorDB) and the establishment of persistence via cron jobs for 'signal routing.' While these capabilities are plausibly required for the stated purpose of providing a persistent vector and graph-based memory, the combination of remote binary execution, broad file system permissions (~/.openclaw/workspace/), and background task scheduling creates a significant attack surface. The absence of the actual lifecycle scripts (install.sh, activate.sh) mentioned in the manifest prevents a full verification of the installation logic.