Open-source AI browser agent for Chrome and Firefox (monorepo) ðŸ§
JavaScript ai-agentai-agentsai-toolsbrowser-aibrowser-automationbrowser-extensionchrome-aichrome-devtoolschrome-extensionchrome-extensionsfirefox-addonfirefox-addonsfirefox-extensionfirefox-extensionsgemmagemma4minimaxoffline-aioffline-llmqwen
Update changelog
Codex release-state teste53e98014e1b
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex b840fc98f..4514e296e 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,7 @@ This changelog was generated from the repository Git history and release tags. V## [Unreleased]### Fixed+- 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.diff --git a/dist/webbrain-chrome-40.7.1.zip b/dist/webbrain-chrome-41.0.1.zipsimilarity index 93%rename from dist/webbrain-chrome-40.7.1.ziprename to dist/webbrain-chrome-41.0.1.zipindex fce0436ac..5506f5663 100644Binary files a/dist/webbrain-chrome-40.7.1.zip and b/dist/webbrain-chrome-41.0.1.zip differdiff --git a/dist/webbrain-edge-40.7.1.zip b/dist/webbrain-edge-41.0.1.zipsimilarity index 93%rename from dist/webbrain-edge-40.7.1.ziprename to dist/webbrain-edge-41.0.1.zipindex ea0b7922c..8ee97af6b 100644Binary files a/dist/webbrain-edge-40.7.1.zip and b/dist/webbrain-edge-41.0.1.zip differdiff --git a/dist/webbrain-firefox-40.7.1.zip b/dist/webbrain-firefox-41.0.1.zipsimilarity index 94%rename from dist/webbrain-firefox-40.7.1.ziprename to dist/webbrain-firefox-41.0.1.zipindex 85f70f51f..aacb707e1 100644Binary files a/dist/webbrain-firefox-40.7.1.zip and b/dist/webbrain-firefox-41.0.1.zip differdiff --git a/dist/webbrain-zim-xapian-v0.95-corresponding-source.zip b/dist/webbrain-zim-xapian-v0.95-corresponding-source.zipindex 4b58dc262..38a2471ae 100644Binary files a/dist/webbrain-zim-xapian-v0.95-corresponding-source.zip and b/dist/webbrain-zim-xapian-v0.95-corresponding-source.zip differ