[dataviz1000]

I want to respond to our last interaction here.

This is Cordyceps [0]. My Chrome extension port of the typescript port of Browser Use needs some love but it is contained there.

I wanted to post the port of a MCP with pure CDP libraryI found to use Chrome.debugger therefore removing Playwright but the typescript and monorepo tooling is out of date. Hopefully I'll get it done tomorrow.

[0] https://github.com/adam-s/cordyceps

[nikisweeting]

Nice work! You should reach out to one of the other team members on discord / X about it and make sure they see. (I am on pat leave right now and trying not to open Slack)

[dataviz1000]

My next step will be record / replay of user workflows. I started looking at rrweb and did a search on Github for rrweb and chrome.runtime to look at how people use it in a Chrome extension. workflow-use appeared on the first page of search results. I'll delve into that tomorrow.

Enjoy your time off!

[dataviz1000]

(I just opened up the workflow_use and noticed the AGPL license. Given the situation, it is best I don't even open or look at the code. I'm going to have to figure this one out myself. I did watched the video, very cool stuff.)

[nikisweeting]

workflow-use is currently just an early implementation of some of the ideas for repeatable workflows, there's not much secret sauce to worry about from an IP standpoint yet. you could also use deepwiki to safely paraphrase it / get an overview of the architecture.

[dataviz1000]

It is still a dangerous grey area. If Browser Use is acquired by Mega_Corp for the $10B its IP is worth, I would have to prove that my product isn't a derivative of Workflow Use, otherwise, I, or a company that contracts me, am obligated by law to link to Mega_Corp. If there is prior art as you say, I will be able to find and use that as long as it uses a less restrictive license like MIT.

deepwiki is awesome and my first time learning about it