workflow is removed. but this functionality is awesome

[Yi (hyharry)]

i saw the workflow functionality of browseros is removed in a recent merge #656 . hope it will be back soon.

[Sharif (Shaerif)]

I agree it was good, seems like need to be redone.
I agree the workflow was valuable, but its removal requires clarification.

[Nikhil (shadowfax92)]

Thanks for flagging this, and sorry for the quiet removal. Honest reason: workflows just weren't being used by many people, so we deprecated them in #656 to keep the codebase lean while we focus elsewhere. Not a knock on the idea — it mostly came down to usage.

That said, I think there's a real, better "navigate" experience hiding in here, and it's something we'd like to bring back in a stronger form down the line rather than shipping the old version again.

Would help me a lot to hear it from you both: what were the key things you were actually using workflows for? Concrete use cases are exactly what'll shape a better version when we revisit it.

[Yi (hyharry)]

Thanks for ur reply. Your point is right for making browseros more like a browser and keep it lean on usage. I am more from developer side and the idea is to make my playwright or other automation easy. One can certainly use CC or codex to achieve it. However, I want to stay within opensource and local deployed environment.