Meta says Muse asks a person to approve a browser purchase when it detects checkout on a site where payment credentials are already stored. OpenAI says Dots can try a connected computer if a website blocks its cloud browser, but that starts a separate local task without transferring the cloud session. For website operators, these are two distinct, product-specific limits on what an agent can do in a browser.

Muse pauses at browser checkout

When Muse detects checkout on a site where payment credentials are already on file, Meta says it prompts the user to approve the purchase and displays the exact purchase details. Meta also says a single-use card number is issued for payment.

The documented flow puts a person at the approval step: Muse reaches checkout, then asks for confirmation with the transaction details. This is a browser-checkout rule described for Muse, not a general rule for every kind of agent interaction.

For more on the broader trust questions around the product, read NeoTeo’s earlier coverage of Meta Muse.

Dots’ connected-computer fallback starts a separate task

If a website blocks Dots’ cloud browser, OpenAI says the user can ask the agent to try a connected computer. The fallback may create a separate local task; it does not transfer the cloud browser’s session, and OpenAI does not guarantee support for a particular local browser.

That means the cloud session itself does not carry over when the task moves to a connected computer. The fallback is a separate route, not a continuation of the same browser session.

What the browser can interpret matters, too

Meta says Muse’s browser sub-agent reads an accessibility-tree snapshot rather than the raw page DOM. An accessibility tree is a structured representation of a page’s elements and controls. Meta also says the sub-agent cannot run JavaScript in the page context.

For website teams, that makes the controls and page information exposed through the browser relevant to how Muse interprets a site. The separate checkout approval step then governs what happens when Muse reaches a qualifying purchase flow. Meta’s description applies to Muse; OpenAI’s session and fallback details apply to Dots.