I hope that in the future they can differentiate better when something is constrained intentionally, rather than persistently working around every blocker it encounters.
I just want to start /claude in my CLI and start working. It worked fine before, why do I have to opt out of shit now? Opt in for this type of stuff sounds way more reasonable.
big disagree. Making assumptions about UX from code only without looking was a major problem. (Although vision is still not great. Trying to be patient)
You can turn off the browser use tool in the harness if an instruction not to use it for this is not enough.
I did. He just went ahead and built a script to run headless chrome and take screenshots anyways.
Wow.
I hope that in the future they can differentiate better when something is constrained intentionally, rather than persistently working around every blocker it encounters.
I just want to start /claude in my CLI and start working. It worked fine before, why do I have to opt out of shit now? Opt in for this type of stuff sounds way more reasonable.
And I want it to verify my frontend in the browser, so there's that.
big disagree. Making assumptions about UX from code only without looking was a major problem. (Although vision is still not great. Trying to be patient)