.agents/hooks/agent-memory/MIGRATION.md

Signet OpenClaw Runtime Path Migration

Plugin vs Legacy Hooks

Signet supports two runtime paths for OpenClaw integration:

1. Plugin path (preferred): signet-memory-openclaw runtime plugin handles all memory operations directly.
2. Legacy hook path (compatibility): These handler.js files process /remember, /recall, and /context commands via daemon hook endpoints.

Switching to Plugin Path

Set the environment variable before starting OpenClaw:

SIGNET_RUNTIME_PATH=plugin

This disables legacy hooks so only the plugin handles memory operations. Both paths cannot be active simultaneously per session — the daemon enforces this via session claiming.

When to Use Legacy Path

Keep legacy hooks active (the default) if:

• signet-memory-openclaw is not configured as an OpenClaw plugin
• You need command-based /remember and /recall without plugin support

Safety

The daemon prevents duplicate capture/recall when both paths are configured by rejecting session claims from the second path (HTTP 409).