openclaw - 💡(How to fix) Fix Bug: /new command in Feishu reports 'messages must not be empty' error [1 comments, 2 participants]

\n## Bug Description\n\nWhen sending /new in a Feishu private chat, OpenClaw reports the error:\n\n> ⚠️ Something went wrong while processing your request. Please try again, or use /new to start a fresh session.\n\nThe server-side error logged is:\n\n\nLLM request rejected: invalid params, messages must not be empty (2013)\n\n\n## Steps to Reproduce\n\n1. Open a Feishu private chat with the OpenClaw bot\n2. Send /new\n3. Observe the error message\n\n## Log Analysis\n\nFrom openclaw logs:\n\n\nwarn agent/embedded session file repaired: rewrote 1 assistant message(s), dropped 1 blank user message(s) (20482a2d-...).jsonl\nerror LLM request rejected: invalid params, messages must not be empty (2013)\nerror lane task error: lane=session:... error=\"FailoverError: LLM request rejected: invalid params, messages must not be empty (2013)\"\n\n\nThe session file gets repaired (blank user message dropped), but the LLM is still called with empty messages afterwards, causing the error.\n\n## Environment\n\n- macOS (Darwin 25.4.0, arm64)\n- Node.js v25.9.0\n- OpenClaw version: 2026.4.26\n- Channel: Feishu (openclaw-lark)\n- Model: MiniMax-M2.7-highspeed\n\n## Expected Behavior\n\n/new should start a fresh session without errors.\n\n## Actual Behavior\n\nSession creation fails with empty messages error, even after automatic repair.\n

TL;DR

The issue can be resolved by ensuring that the LLM request is not called with empty messages after the session file repair.

Guidance

• Verify that the session file repair is correctly dropping blank user messages and check if the issue persists after manual removal of empty messages.
• Investigate why the LLM is still being called with empty messages after the session file repair, potentially due to a logic error in the repair process.
• Check the OpenClaw code for any recent changes that might be causing this behavior, especially in the session file repair and LLM request handling logic.
• Consider adding a temporary workaround to skip LLM requests with empty messages until the root cause is identified and fixed.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue seems to be related to the interaction between the session file repair mechanism and the LLM request handling in OpenClaw. Further investigation into the code and logs is necessary to determine the exact cause.

Recommendation

Apply workaround: temporarily skip LLM requests with empty messages to prevent errors until the root cause is identified and fixed. This approach allows for continued use of the /new command while the issue is being resolved.