openclaw - 💡(How to fix) Fix Sandbox media staging: hardcoded 5MB MEDIA_MAX_BYTES limit prevents large file transfers [1 participants]

Summary

The sandbox media staging logic hardcodes MEDIA_MAX_BYTES = 5 * 1024 * 1024 (5MB), which prevents files larger than 5MB (e.g. large PPTs, PDFs, media files) from being copied into the sandbox container. There is no configuration option to override this limit.

Current Behavior

In dist/store-*.js and dist/plugin-sdk/store-*.js, the constant is hardcoded:

const MEDIA_MAX_BYTES = 5 * 1024 * 1024;

When a file exceeds 5MB, the staging step fails and the file cannot be made available inside the sandbox. This blocks many real-world use cases — generated PPTs, large images, audio/video files, etc.

Expected Behavior

• The MEDIA_MAX_BYTES limit should be configurable (e.g. via an environment variable like OPENCLAW_MEDIA_MAX_BYTES or a config field)
• The default should be significantly higher (50MB–100MB or more) to accommodate common file types
• At minimum, the hardcoded value should be raised from 5MB to something more practical

Workaround

Currently requires manually patching dist/store-*.js and dist/plugin-sdk/store-*.js after every npm update openclaw:

sed -i "s/const MEDIA_MAX_BYTES = 5 \\* 1024 \\* 1024/const MEDIA_MAX_BYTES = 500 * 1024 * 1024/" dist/store-*.js dist/plugin-sdk/store-*.js
openclaw gateway restart

This is fragile and must be re-applied after every update.

Suggestion

Make MEDIA_MAX_BYTES configurable, e.g.:

const MEDIA_MAX_BYTES = parseInt(process.env.OPENCLAW_MEDIA_MAX_BYTES) || 100 * 1024 * 1024;