Large image upload hardening: raise WS payload limits and run 5MB smoke test
Scenario: image attachments fail because base64 inflates payload over previous WS cap. Upgrade and run an explicit 4-5MB attachment test to validate stable delivery.
GITHUBDiscovered 2026-02-14Author @0xRaini
Prerequisites
- Your workflow sends images through gateway WebSocket path (chat/media tools).
- You can produce a controlled test image around 4-5MB.
Steps
- Upgrade to a release containing PR #14486 and restart gateway.
- Send one small baseline image first to verify channel/media pipeline health.
- Send a 4-5MB image through the same path and observe completion without payload errors.
- Repeat across at least two channels/surfaces you rely on (if applicable).
Commands
openclaw gateway statusopenclaw gateway restartopenclaw logs --local-timeVerify
No WS max-payload/buffer errors appear, and target recipient receives the full image consistently.
Caveats
- Provider/channel-side media caps may still be lower than gateway caps（需验证）.
- Do not infer unlimited capacity from one pass; keep staged size tests (1MB/3MB/5MB).
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗