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
docs: note the closed iframe gap in the X compose changelog entry
Claude0bfc1c91a2cb
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 13120a345..aa5caa464 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,7 +7,7 @@ This changelog was generated from the repository Git history and release tags. V## [Unreleased]### Fixed-- X: typing a post into X's compose window no longer fails, and no longer ends with "Stopped because the page kept changing". Before typing into X's editor, WebBrain clicks it once with a real mouse click. X answers that click by drawing its bold/italic bubble right where the click landed, over the middle of the empty editor, while its timeline behind the compose window keeps updating. WebBrain took those changes as the page changing under it, and since it checks what lies under the middle of an element to be sure it still has the right one, the bubble also made it lose the editor: it refused to type, and choosing Retry met the same bubble. That click now counts as part of the typing, and from then on the typing is checked against the editor itself rather than against what covers its middle: each step puts the focus back in the editor, and the text is sent only to the editor itself: if the page moves the focus elsewhere just before the text goes out, including into a frame such as an iframe, nothing is typed. When the bubble is still there from an earlier attempt and the editor still has the focus, WebBrain types into it, or presses keys in it, without clicking it again; clicking a control whose middle is covered is still refused. Your own clicking or typing, a changed reply setting, a replaced editor or a compose window that stops accepting input still stop it before any text is sent. Separately, the agent then tried the selector `[data-testid="tweetTextarea_0"]`, which on X names both the compose box and the hidden one on the timeline behind it. That can never be typed into safely, but because the timeline kept updating, each such decision was thrown away as out of date without an answer, the agent saw the same page and decided the same again, and after five rounds the run blamed the page. Such a call now answers for itself, saying the selector matches more than one element and to use the box the agent observed, and it no longer counts as the page changing. Still not fixed: in Chrome, typing by a selector that names only the compose box is refused while the timeline keeps updating, because finding the box by selector scrolls the page before the call has been checked. That refusal now says the page kept updating and to type into the box the agent observed, which works, instead of saying that WebBrain could not attach to the tab, which usually means DevTools is open. The click and the retry without a click are Chrome's way of typing; the selector answer and typing into a focused editor whose middle is covered apply in Chrome and Firefox.+- X: typing a post into X's compose window no longer fails, and no longer ends with "Stopped because the page kept changing". Before typing into X's editor, WebBrain clicks it once with a real mouse click. X answers that click by drawing its bold/italic bubble right where the click landed, over the middle of the empty editor, while its timeline behind the compose window keeps updating. WebBrain took those changes as the page changing under it, and since it checks what lies under the middle of an element to be sure it still has the right one, the bubble also made it lose the editor: it refused to type, and choosing Retry met the same bubble. That click now counts as part of the typing, and from then on the typing is checked against the editor itself rather than against what covers its middle. Each step puts the focus back in the editor, and the text is sent only to the editor itself; if the page moves the focus elsewhere just before the text goes out, nothing is typed. This also closes an older gap on pages where nothing covers the editor: if a page moved the focus into an iframe just before WebBrain's text went out, the text was typed into that iframe. When the bubble is still there from an earlier attempt and the editor still has the focus, WebBrain types into it, or presses keys in it, without clicking it again; clicking a control whose middle is covered is still refused. Your own clicking or typing, a changed reply setting, a replaced editor or a compose window that stops accepting input still stop it before any text is sent. Separately, the agent then tried the selector `[data-testid="tweetTextarea_0"]`, which on X names both the compose box and the hidden one on the timeline behind it. That can never be typed into safely, but because the timeline kept updating, each such decision was thrown away as out of date without an answer, the agent saw the same page and decided the same again, and after five rounds the run blamed the page. Such a call now answers for itself, saying the selector matches more than one element and to use the box the agent observed, and it no longer counts as the page changing. Still not fixed: in Chrome, typing by a selector that names only the compose box is refused while the timeline keeps updating, because finding the box by selector scrolls the page before the call has been checked. That refusal now says that the page changed and to type into the box the agent observed, which works, instead of saying that WebBrain could not attach to the tab, which usually means DevTools is open. The click and the retry without a click are Chrome's way of typing; the selector answer and typing into a focused editor whose middle is covered apply in Chrome and Firefox.- When the model provider rate-limits WebBrain (HTTP 429, or Anthropic's 529 "overloaded"), the step is now waited out and retried up to three times (about 5, 15 and 30 seconds, or longer if the provider asks), also when the limit arrives in the middle of a response, as OpenRouter and WebBrain Cloud report it, and for Anthropic (including Vertex), Azure OpenAI, AWS Bedrock and llama.cpp, whose limits ended Act runs at once. An answer you already saw part of is never generated again. A message such as "Rate limit exceeded" is no longer mistaken for an over-long conversation, so WebBrain no longer trims your conversation and asks you to start a new one. Older context is trimmed only when one request alone exceeds the provider's per-minute token limit, and then right away and only once; if the provider does not state its limit, one shortened retry is tried, and the conversation is shortened only if that retry succeeds. Each wait is lengthened at random by up to 20% so several runs do not retry at the same moment, and never comes sooner than the provider asks. An OpenAI "insufficient_quota" billing error now fails at once instead of being retried, and traces label rate limits as rate limiting even when the message mentions a quota.- The local vision fallback now also runs when an OpenAI-compatible provider such as Ollama or LM Studio rejects a screenshot as unsupported. The rejection's status was read from the wrong field, so the fallback never started.- Chat sites: a message is no longer sent to whoever's chat is open just because an e-mail address appears in that chat's earlier messages. When a chat showed no contact name at the top, WebBrain took such an address for the recipient; now it stops and says it cannot tell who the chat is with. An address shown in the conversation's own header, as in help-desk and CRM conversations, still identifies the recipient, while an address in the header's pinned text does not, and mail compose windows read their To, Cc and Bcc addresses as before. In Google Chat inside Gmail, an address mentioned in the chat is never taken as the recipient either: WebBrain stops before sending there, since nothing on the page reliably tells the chat's name from the names in its messages, while a Gmail compose window open over the Chat view still sends to its To, Cc and Bcc addresses.