openclaw - 💡(How to fix) Fix [Bug]: Telegram /new and /reset reset context but still trigger empty OpenAI Responses API error [4 comments, 4 participants]

In OpenClaw 2026.4.26, Telegram /new and /reset reset the context according to /status, but still return an empty OpenAI Responses API error to Telegram. 5. Observe the OpenAI Responses API error in Telegram. 7. Observe that the context appears to have been reset despite the error. /new and /reset appear to reset the context successfully according to /status, but Telegram still receives this error: Telegram error shown after /new or /reset: 05:51:18+09:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"embedded_run_agent_end","tags":["error_handling","lifecycle","agent_end","assistant_error"],"runId":"be644cab-63b8-458c-8b51-9eca26ff0ffa","isError":true,"error":"One of "input" or "previous_response_id"or 'prompt'or 'conversation_id' must be provided.","failoverReason":null,"model":"gpt-5.5","provider":"openai-codex","rawErrorPreview":"One of "input" or "previous_response_id"or 'prompt'or 'conversation_id' must be provided.","rawErrorHash":"sha256:f4df43227553","providerRuntimeFailureKind":"unclassified"} embedded run agent end

• The error appears only after /new or /reset. Severity: Annoying / misleading. The context reset appears to succeed, but Telegram still shows a provider error. Consequence: Users may think the reset failed even though /status indicates the context was reset. It also creates noisy embedded runner error logs. This does not appear to be a general Telegram, Gateway, provider, or model outage because normal Telegram chat works before and after the error. reset succeeds according to /status, but an empty OpenAI Responses API error is still surfaced to Telegram

TL;DR

The issue can be fixed by modifying the /new and /reset commands to handle the OpenAI Responses API request correctly, ensuring that the required parameters are provided.

Guidance

• Review the code handling the /new and /reset commands to ensure that they properly reset the context and provide the necessary parameters for the OpenAI Responses API request.
• Verify that the input, previous_response_id, prompt, or conversation_id parameters are being passed correctly in the API request.
• Check the error handling mechanism to prevent the empty OpenAI Responses API error from being surfaced to Telegram.
• Consider adding logging to track the parameters being passed in the API request to help diagnose the issue.

Example

No code snippet can be provided without more information about the implementation, but the fix likely involves modifying the code that handles the /new and /reset commands to properly handle the OpenAI Responses API request.

Notes

The issue seems to be specific to the /new and /reset commands and does not affect normal Telegram chat functionality. The fix should focus on ensuring that these commands correctly handle the OpenAI Responses API request.

Recommendation

Apply a workaround to modify the /new and /reset commands to handle the OpenAI Responses API request correctly, as upgrading to a fixed version is not mentioned in the issue.