Source: github.com/browserbase/stagehand/releases/tag/stagehand-python%404.4.0a0.dev1675
According to the release notes, the network-settling helper in actHandlerUtils.ts overwrote the browser's auto-attach configuration after act() ran. That could leave newly loaded cross-origin iframes invisible to Stagehand and unusable for later actions.
The fix removes the conflicting Target.setAutoAttach call and leaves attachment management to BrowserContext. A regression test checks that cross-origin iframes created after act() stay visible in snapshots and still support subsequent actions.
The change is a development build tagged in the browserbase/stagehand repository, and it is listed as pull request #3388.
Why it matters if you build agents
If your agent uses act() on pages that load cross-origin iframes, such as embedded payment or login forms, this build restores their visibility to later steps.
Agents that worked around the missing iframes by re-navigating or skipping those elements can check whether that workaround is still needed.
Because this is a prerelease tag, pin it deliberately and test it before relying on it in production.
Get stories like this every weekday
One short email with the day's agent tooling news.