openclaw - 💡(How to fix) Fix [Bug]: Canvas returns 401 Unauthorized on Windows despite correct token (v2026.4.5) [1 comments, 1 participants]

Running OpenClaw v2026.4.5 (3e72c03) on Windows 11. The gateway starts successfully and reports auth=token, but the canvas UI at http://127.0.0.1:18789/__openclaw__/canvas/ always returns {"error":{"message":"Unauthorized","type":"unauthorized"}} regardless of what token configuration is used. {"error":{"message":"Unauthorized","type":"unauthorized"}} returned for all canvas requests despite valid token Browser returns: {"error":{"message":"Unauthorized","type":"unauthorized"}}

TL;DR

• Verify the token configuration and authentication mode in the OpenClaw gateway settings to ensure proper token validation.

Guidance

• Check the OpenClaw documentation for the correct token format and authentication mode configuration to ensure compatibility with the Anthropic API.
• Verify that the token is being passed correctly in the URL parameter token when accessing the canvas UI.
• Test the authentication mode none to isolate if the issue is token-specific or a broader authentication problem.
• Review the gateway logs for any authentication-related errors or warnings that could indicate a configuration issue.

Example

• No specific code snippet can be provided without more details on the token configuration and authentication setup.

Notes

• The issue might be related to a change in the token validation logic in OpenClaw version 2026.4.5 or an incompatibility with the Anthropic API.
• Further investigation into the gateway logs and the Anthropic API documentation may be necessary to resolve the issue.

Recommendation

• Apply workaround: Temporarily switch to authentication mode none to test if the issue is specific to token authentication, and then revisit the token configuration and validation logic.