openclaw - 💡(How to fix) Fix /new command without text triggers empty LLM request (400 messages: Field required) [1 comments, 2 participants]

When the /new slash command is sent without any message text, OpenClaw resets the session and immediately fires an LLM request with an empty messages array, causing a 400 error from the API. 2. Observe the error

Error Log

400 {"type":"error","error":{"type":"invalid_request_error","message":"messages: Field required"}}

TL;DR

Check the handling of the /new slash command to ensure it waits for user input before making an LLM request when no message text is provided.

Guidance

• Review the code that handles the /new command to verify it correctly checks for the presence of message text before initiating an LLM request.
• Consider adding a conditional statement to delay the LLM request until a subsequent message with text is received.
• Examine the error handling for the LLM request to ensure it properly handles the "Field required" error and does not reset the session unnecessarily.
• Test the /new command with and without message text to confirm the expected behavior.

Example

if message_text:
    # Proceed with LLM request
else:
    # Wait for next user message
    # possibly set a flag or store the command for later use

Notes

The provided workaround suggests that adding text to the /new command resolves the issue, indicating the problem lies in how the command is handled when no text is provided.

Recommendation

Apply workaround: Use /new <some text> instead of bare /new until a fix is implemented to handle the command correctly without text. This ensures the LLM request is made with the required messages field.