openclaw - 💡(How to fix) Fix Control UI 404 on api/v1/status endpoint missing in 2026.4.2 [1 participants]

TL;DR

Avoid using the Debug tab in the Control UI dashboard to prevent the 404 error caused by polling the non-existent /api/v1/status endpoint.

Guidance

• Verify that the issue is resolved by not using the Debug tab or by implementing a temporary workaround to avoid polling the /api/v1/status endpoint.
• Check the Gateway API documentation to see if there are any alternative endpoints that can be used to retrieve the required status information.
• Consider updating the Control UI dashboard to handle the case where the /api/v1/status endpoint does not exist, such as by displaying an error message or using a different endpoint.
• Test the workaround by leaving the Control UI dashboard on a different tab and verifying that the 404 error is no longer occurring.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

This workaround may not be a permanent solution and the root cause of the issue should be investigated further to determine why the /api/v1/status endpoint was removed or is not available in OpenClaw 2026.4.2.

Recommendation

Apply workaround: Avoid using the Debug tab in the Control UI dashboard until a permanent fix is available, as this will prevent the 404 error from occurring.