Add a separate example that keeps OpenClaw conversations, workspace files and memory on a Drive while each message runs in a fresh sandbox from the official image. Includes an authenticated HTTP controller, Redis request tracking and a Vercel Functions adapter. The existing Slack/Codex integration stays in place.
Validated build/typecheck and 47 local tests, plus a protected deployment with three fresh workload VMs sharing one Drive. Conversation and memory recall, duplicate requests, competing admission and auth/body rejection passed. Measured request times were 29.6s, 26.5s and 25.6s, including startup and shutdown; this is not a speed comparison with the Slack integration. Phase durations derived from Redis timestamps were 11.4–13.8s for gateway startup, 6.4–9.0s for model work and 3.0–4.0s for shutdown/detach. Reproducible test and redacted results are included under examples/drives.
Test deployment: https://openclaw-drives-preview-hcom1y80s.playground-vercel.tools (Vercel authentication and API control token required). It runs in a separate test project and does not require merging this PR.
This example has no Slack event handler or delivery. Native gateway crash recovery can require the five-minute ownership lease to expire; uncertain turns are never automatically replayed. Continuous operation, active-tool interruption and VM power loss remain unverified.
Activity
5Review the following changes in direct dependencies. Learn more about Socket for GitHub.
| Diff | Package | Supply Chain Security | Vulnerability | Quality | Maintenance | License |
|---|---|---|---|---|---|---|
| @vercel/sandbox@3.5.0 | ||||||
| @types/node@24.3.0 | ||||||
| typescript@5.9.2 | ||||||
| @vercel/queue@0.7.0 | ||||||
| @vercel/connect@2.3.3 |
The latest updates on your projects. Learn more about Vercel for GitHub.