Viewing profile — cosinusalpha

Do you experience any context pollution with that approach?

Yes, you can create isolated environments using the "--session NAME" flag. It isolates cookies and local storage for that specific run. Since it's a V1 release, there might be some…

Thanks! I actually tried a raw HTML when I was exploring solutions. It worked for "one-off" tasks, but I ran into major issues with replayability on modern SPAs. In React apps, the…

I actually think the CLI approach helps with those boundaries. Because webctl commands are discrete and pipeable (e.g. webctl snapshot | llm | webctl click), the "authority" is res…

Thanks! To clarify: webctl allows you to manually interact with the browser window at any time. It even returns "manual interaction" breakpoints to stdout if it detects an SSO/logi…

I am also not sure if MCP will eventually be fixed to allow more control over context, or if the CLI approach really is the future for Agentic AI. Nevertheless, I prefer the CLI fo…

A background daemon holds the session state between different CLI calls. This daemon is started automatically on the first webctl call and auto-closes after a timeout period of ina…

I don't have an objective benchmark yet. I tried several existing solutions, especially the MCP servers for browser automation, and none of them were able to reproducibly solve my …

To be honest, I hadn't seen that one yet! The main difference is likely the targeting philosophy. webctl relies heavily on ARIA roles/semantics (e.g. role=button name="Save") rathe…

Hi HN, I built webctl because I was frustrated by the gap between curl and full browser automation frameworks like Playwright. I initially built this to solve a personal headache: …