-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Description
Issue Checklist
- I understand that issues are for feedback and problem solving, not for complaining in the comment section, and will provide as much information as possible to help solve the problem.
- My issue is not listed in the FAQ.
- I've looked at pinned issues and searched for existing Open Issues, Closed Issues, and Discussions, no similar issue or discussion was found.
- I've filled in short, clear headings so that developers can quickly identify a rough idea of what to expect when flipping through the list of issues. And not "a suggestion", "stuck", etc.
- I've confirmed that I am using the latest version of Cherry Studio.
Platform
Windows
Version
1.8.1
Bug Description
1、I installed the latest version of openclaw (3.13-61d171a) using npm. I checked the openclaw GitHub and confirmed that 61d171a is the latest version.
2、When I open Cherry Studio and then open the OpenClaw interface, it still tells me that my OpenClaw version is too low.
I have my reasons for needing to install OpenClaw directly using npm, such as integrating it with a custom communication tool within my company via a plugin. However, the OpenClaw.exe I tested installed via Cherry Studio did not support this.
Steps To Reproduce
1、I installed the latest version of openclaw (3.13-61d171a) using npm. I checked the openclaw GitHub and confirmed that 61d171a is the latest version.
2、When I open Cherry Studio and then open the OpenClaw interface, it still tells me that my OpenClaw version is too low.
I have my reasons for needing to install OpenClaw directly using npm, such as integrating it with a custom communication tool within my company via a plugin. However, the OpenClaw.exe I tested installed via Cherry Studio did not support this.
Expected Behavior
It tells me that my OpenClaw version is the latest and it supports startup.
Relevant Log Output
Additional Context
No response