Claude would also be great for writing disposable, bespoke debug visualizations (for anyone still using an IDE). I'm undecided about AI for long-lived code but excited about it for disposable code.
That luggage-claim example is the key one: enabling a button proves the DOM changed, not that the upload succeeded. I would keep the network result, post-action DOM and screenshot in one ordered session. That is the narrower contract we built Jet Browser around; Playwright still wins when the task needs an existing Chrome profile.
Claude would also be great for writing disposable, bespoke debug visualizations (for anyone still using an IDE). I'm undecided about AI for long-lived code but excited about it for disposable code.
i have repos and repos full of one off dashboards and scratch work that i never see or use again
That luggage-claim example is the key one: enabling a button proves the DOM changed, not that the upload succeeded. I would keep the network result, post-action DOM and screenshot in one ordered session. That is the narrower contract we built Jet Browser around; Playwright still wins when the task needs an existing Chrome profile.