Skip to content

Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠

Changelog: a verified password entry no longer ends a batch

Claude6cbfe3189472
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9a5c76f37..a3669d619 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -25,7 +25,8 @@ This changelog was generated from the repository Git history and release tags. V
- Stopping a task while WebBrain was waiting for page navigation to settle now stops it immediately. The pending settle step previously kept waiting and could let the run continue after you chose Stop.
- Mastodon: replying to toots in a narrow window no longer posts the same reply several times and stops before the next toot. There, a toot's Reply button opens the composer at /publish, and after posting Mastodon goes back to the previous column by itself. WebBrain took both page changes for something you did, so it reported each click's outcome as unknown; the agent then concluded its reply had not been posted, wrote it again, and never reached the next toot. In Chrome, a page's own Back is now told apart from your browser's Back button: the page a click opens counts as that click's verified effect, and a click after which the page goes back by itself counts as delivered, to be checked on the page. The Mastodon notes now cover replies (start with the prefilled @mentions once, check the reply under the toot before any retry) and stay active on Favourites, Bookmarks and the other columns. Firefox still treats a page's own Back as yours until its Back button reporting is verified.
- Finishing a form you asked WebBrain not to submit no longer takes most of a minute. The completion check removed every line that mentioned a password, so "fill out this form with a random password … don't submit" reached its judge as "[credential omitted]", and so did the approved plan and the agent's summary. Seeing only an unsubmitted signup form, the judge answered "pending" again and again; in the trace it took four attempts and about 50 seconds, ending only when a slow screenshot check ran out of time. The active model's check, which already holds these texts in the conversation, now receives every line of them, with only addresses shortened and bearer tokens and entered passwords hidden, as in all judge evidence. A decision model on this device, or WebBrain Cloud's own while WebBrain Cloud is also your provider, receives that same copy; any other decision model keeps whole-line redaction, and when that leaves it without the task, it is no longer asked while the active model can judge. A password WebBrain typed into a password field during the run is now hidden in the text judges receive, such as the agent's summary or a field a "show password" control revealed, unless the typing tool could not tell what kind of field it was; other entered values stay visible, so a judge can still catch a mistyped one. The judges are told that a task asking not to submit is complete once the staged values match, that a hidden value neither proves nor disproves an entry, and, for each recorded entry, whether its field read back what was entered, whether it is a credential field and which field it targeted; a credential field's line in the page evidence keeps its role and reference. Staged field edits are judged from the accessibility tree first: a screenshot shows passwords only as dots, and the focused field's blinking caret made each one stale before its verdict returned.
-- Filling several known form fields now takes one `browser_batch` instead of one model turn per field. The Act prompts still said to fill one field at a time and to click each field before typing, and the planner named only `set_field`; they now send already observed fields, including those in the latest page observation, through one batch with one `set_field` per field. Entering a required password still ends a batch, so password fields go last and anything left follows in the next turn. The completion check now also counts the actions inside a batch, which it did not see before.
+- Filling several known form fields now takes one `browser_batch` instead of one model turn per field. The Act prompts still said to fill one field at a time and to click each field before typing, and the planner named only `set_field`; they now send already observed fields, including those in the latest page observation, through one batch with one `set_field` per field. A verified password entry continues the batch like any other text field, so a login's username, password and button can run in one batch. The completion check now also counts the actions inside a batch, which it did not see before.
+- Logging in with one `browser_batch` (username, password, Log in) no longer stops at the button with "The browser changed during action preparation" after you approve the submit card. The page monitor carried a verified entry into the batch's checks for every text field except a password, so the button's form no longer matched what it had observed, and the click waited for another model turn. A password field now counts like any other text field; its typed value is checked inside the page monitor and never leaves it. When a click is refused because its binding changed, the trace note now names the reason. Chrome and Firefox.
## [40.8.0] - 2026-10-16