Start with the job, not the browser
Define the user job for a browser automation before writing the agent prompt or selecting a tool.
The move: define the job before you define the clicks. Job A job statement names the progress the user needs. For browser automation, it should include the business object, the action, and the success condition. 'Update a portal' is too vague. 'Submit 30 verified supplier tax forms and return an exception list for the ones that fail validation' is a job. Evidence Browser agents need evidence because web pages are full of misleading signals: loaded screens, disabled buttons, stale banners, and partial saves. Evidence tells the agent what counts as real completion: a confirmation ID, a changed status, an exported…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in