In this analysis
A browser sequence can manipulate the interface correctly while operating on the wrong record.
Browser work extended the small-model question
Opus 5.5 launched on September 22, 2026 and Sonnet 5.5 on September 28. The October 7 Haiku 5.5 announcement included browser use among its intended workloads. This makes a particular reliability issue visible: an individually plausible action can be wrong in the state reached by previous actions. A browser task is a sequence of observations and transitions, not a collection of independent clicks whose local plausibility automatically establishes a correct final outcome.
A control can change meaning after navigation
An illustrative task finds a specific draft invoice in an application. Opening a search result changes the page, and a later action must refer to the newly observed state. Reusing a location from the previous page can select an unrelated control. The error is not necessarily failure to recognize the original interface. It may be failure to update the action’s reference after navigation. A useful acceptance test therefore inspects whether each consequential operation is grounded in the state that actually preceded it.
Similar records make local confidence misleading
A search list may contain nearly identical names with different status or dates. Clicking a plausible row can lead to a perfectly readable but incorrect record. Subsequent actions may remain internally coherent while completing the wrong task. This is why end-to-end checking needs the target identity, not merely evidence that the browser reached a detail page. The observation is a general workflow risk rather than a reported Haiku failure. It shows how correct interface manipulation and correct task selection can diverge.
A nonconsequential fixture can expose composition
A practical illustrative fixture asks the agent to locate a draft and return its visible reference without submitting changes. The environment contains a similarly named archived record and a navigation transition that rearranges the list. Review the selected identity, the observations before each action and the final reported reference. No real invoice is altered, and no success rate is asserted. The fixture isolates navigation and identity consistency while leaving consequential submission for a separately authorized workflow with its own acceptance conditions.
Checkpoints should protect meaning
A useful checkpoint confirms that the current page still represents the intended object before a consequential step. It is more specific than mechanically asking for confirmation after every harmless interaction. The October launch provides a reason to explore economical browser assistance, but it does not remove this need for task-state consistency. The retrospective lesson is to evaluate composed actions through identity and outcome. Fast local decisions become valuable only when their sequence preserves what the user meant to accomplish across the changing interface.