WindsurfAPI
Major Update · 2026/07/09 06:08 (UTC+9)
中文
关于 WindsurfAPI
在这个项目【WindsurfAPI】起初我只是为了自己使用然而开源 然后发现Github并没有这一类的项目开源 在当时这个项目功能不齐全的时候就收获到了很多的Star和关注 以至于我有动力做到现在 已经成功反代Fable5进行编码阅读 原生Tool_Call 以及 Vision识别图片工作 我们依旧使用0个NPM 进行Nodejs的网页操作 。
实践视频
真实的实践视频URL是：
https://www.bilibili.com/video/BV1AfM56BE5t
虽然视频质量做的差 东西能用好用 我自己也得做到我知道 。
本次更新
本次版本大更新 就在2026/07/09 +UTC9 6:00 发生
致谢
再次感谢项目起初提交PR不断提交Issus的Github用户伙伴 以及项目作者能力不足导致问题没有解决 模糊的情况在此抱歉可能会浪费大家的精力
最后
Devin和Windsurf简直有病 两个还是并存 前后端接口复用 那我的项目到底是叫DevinAPI还是WindsurfAPI呢还是WinDeSurfingAPI啊
English
About WindsurfAPI
When I first started WindsurfAPI, it was honestly just something I built for myself. I decided to open-source it anyway, and then I realized there really weren't any similar projects on GitHub.
Even back when the project was still missing a lot of features, it somehow gained a surprising number of stars and followers. That support is honestly what kept me motivated to keep building it until today.
At this point, the project has successfully reverse-engineered Fable5 for code reading, supports native Tool Calls, and even has Vision image recognition working.
We're still doing all of the browser automation in pure Node.js with zero NPM dependencies.
Demonstration
Here's a real demo of everything actually working:
https://www.bilibili.com/video/BV1AfM56BE5t
The video quality isn't great, but the project works, and more importantly, it works well. That's the standard I wanted to hold myself to.
Release Time
2026/07/09 06:00 (UTC+9)
Thanks
I'd also like to thank everyone who submitted PRs and kept opening Issues from the very beginning of this project.
Your feedback has been incredibly valuable.
At the same time, I'd like to apologize for the problems that weren't resolved quickly enough because of my own limitations.
Some issues stayed unclear for longer than they should have, and I know that probably cost some of you time and effort.
Sorry about that.
Finally
Devin and Windsurf are seriously driving me crazy.
Now both of them exist at the same time, and they even reuse the same frontend and backend APIs.
So...
DevinAPI?
WindsurfAPI?
WinDeSurfingAPI?
WindsurfAPI
中文
关于 WindsurfAPI
实践视频
真实的实践视频URL是：
本次更新
致谢
最后
English
About WindsurfAPI
When I first started WindsurfAPI, it was honestly just something I built for myself. I decided to open-source it anyway, and then I realized there really weren't any similar projects on GitHub.
Even back when the project was still missing a lot of features, it somehow gained a surprising number of stars and followers. That support is honestly what kept me motivated to keep building it until today.
At this point, the project has successfully reverse-engineered Fable5 for code reading, supports native Tool Calls, and even has Vision image recognition working.
We're still doing all of the browser automation in pure Node.js with zero NPM dependencies.
Demonstration
Here's a real demo of everything actually working:
https://www.bilibili.com/video/BV1AfM56BE5t
Release Time
2026/07/09 06:00 (UTC+9)
Thanks
I'd also like to thank everyone who submitted PRs and kept opening Issues from the very beginning of this project.
Your feedback has been incredibly valuable.
At the same time, I'd like to apologize for the problems that weren't resolved quickly enough because of my own limitations.
Some issues stayed unclear for longer than they should have, and I know that probably cost some of you time and effort.
Sorry about that.
Finally
Devin and Windsurf are seriously driving me crazy.
Now both of them exist at the same time, and they even reuse the same frontend and backend APIs.
So...