OpenClaw integration

I hit several OpenCoven ↔ OpenClaw integration issues while getting Coven Cave connected:

>

1. Coven Cave 0.0.112 invoked openclaw agent with --session-key, but OpenClaw 2026.5.3-1 expects --session-id. This produced:

unknown option '--session-key'

>

1. The default familiar was configured as openclaw_agent = "default", but my OpenClaw default agent ID is actually main. Error:

Unknown agent id "default"

>

1. When OpenClaw needed a scope upgrade, Coven surfaced this poorly as:

_The "openclaw" agent bridge returned no text._
The real issue was a pending OpenClaw device approval for operator.write.

>

1. Relaunching Coven Cave left multiple stale server.mjs sidecar processes running, so fixes didn’t apply until I manually killed the old sidecars.

>

Suggested fixes:

• Detect OpenClaw CLI version/capabilities and use --session-id vs older flags appropriately.
• Resolve the default OpenClaw agent via openclaw agents list --json instead of assuming default.
• Surface pairing/scope approval errors explicitly in the UI.
• Ensure app relaunch kills stale bundled sidecar processes.
• Parse OpenClaw JSON robustly or separate stderr/stdout so gateway notices don’t become “no text.”