openclaw - 💡(How to fix) Fix [Bug] /reset and /new trigger empty-message LLM call → 400 error surfaced to user [1 participants]

When /reset or /new is triggered on a session that lossless-claw considers "already fresh" (no conversation history), OpenClaw fires a session-end lifecycle LLM call with an empty message array. Anthropic rejects this with 400: messages: at least one message is required. The fallback model is put into cooldown and the error surfaces to the user as: 3. Observe error message in Telegram If the session has no messages (already fresh), the session-end LLM call should be skipped. No error should be surfaced to the user. User sees error message. Session is actually clean and works fine on next interaction. "error": "LLM request rejected: messages: at least one message is required", "rawErrorPreview": "400 {"type":"error","error":{"type":"invalid_request_error","message":"messages: at least one message is required"}}",

TL;DR

Check for empty message history before firing the session-end LLM call on /reset or /new to prevent unnecessary requests that will be rejected.

Guidance

• Review the logic in OpenClaw that handles the session-end LLM call to ensure it respects the "already fresh" condition detected by lossless-claw.
• Modify the code to skip the LLM call when the message history is empty, as suggested in the issue.
• Verify that the session_end lifecycle no-op logging in lossless-claw is correctly indicating when a session is already fresh and the LLM call should be skipped.
• Test the updated logic with the steps to reproduce provided in the issue to ensure the error is no longer surfaced to the user.

Example

No code snippet is provided as the issue does not include specific code references, but the fix involves checking the message history before making the LLM call, potentially using a condition like if (messageHistory.isEmpty()) { skipLLMCall(); }.

Notes

The issue seems to be specific to the interaction between OpenClaw, lossless-claw, and the Anthropic model. The suggested fix should be applied with consideration of the overall system's behavior and potential side effects on other functionalities.

Recommendation

Apply the workaround by modifying the OpenClaw logic to skip the session-end LLM call when the message history is empty, as this directly addresses the root cause of the error and prevents unnecessary requests to the Anthropic model.