Enable cloud storage for LanceDB memory

## What changed OpenClaw added cloud storage support to its memory-lancedb module on 18 May 2026. The update lets durable memory indexes run on remote object storage instead of local disk.

Users configure the feature through the existing YAML file and CLI setup. Supported targets include standard S3-compatible buckets and similar object stores.

## Why it matters Local disk memory created single points of failure on VPS instances that restart or get replaced. Cloud-backed indexes reduce data loss risk while keeping the agent self-hosted.

The change strengthens OpenClaw for Vibe Builders who run agents across multiple machines or want simple backup paths. It pressures purely local tools to add similar durability options or lose ground on long-running personal agents.

## How to use it Update to the latest OpenClaw release through the standard CLI command. Edit the YAML configuration to point memory-lancedb at an S3-compatible endpoint and supply the required credentials.

Restart the agent and verify the memory index appears in the remote bucket. Test a short conversation to confirm recall works after a restart.

## Watch for Confirm the feature works reliably with common providers like AWS S3 and DigitalOcean Spaces over the next month. Watch for silent fallback to local disk under high load. The next expected move is support for additional vector stores beyond LanceDB.