These answers help you start and finish a browser run safely. For current limits and prices, consult the live setup reference and pricing endpoint.
Is this an Agent that completes every task by itself?
No. Baizhi Cloud Browser provides a cloud browser runtime, control handoff, saved website state, and file delivery. Your Agent understands the task and prepares the result; a CDP client clicks, types, and reads pages.
Can MCP alone operate a web page?
MCP manages browser runs. Your Agent still needs the CDP address for that run and a client such as Playwright or Puppeteer for page actions. Do not create duplicate runs via MCP and HTTP for one task.
What happens when I need to sign in?
Your Agent sends the human-action link for the current run. Sign in on that page, then use the return-control action. The Agent obtains a new control address for the same run and checks the page. Closing the page alone does not return control.
Will a saved sign-in last forever?
No such guarantee. A later run can load successfully saved state, but the target site may require authentication again. Check the page in the new run.
Does a download automatically reach my local machine?
No. Your Agent must query artifacts, retrieve bytes, and verify length and SHA-256 before the run ends. The remote browser and Agent do not share a filesystem.
Does closing Playwright stop billing?
No. Explicitly end runs your Agent created and confirm the browser reaches released. Check final billing separately. Consult current pricing for time spent waiting, in human control, or disconnected.
Will it automatically bypass every CAPTCHA or site restriction?
We make no such promise. Access and sign-in requirements depend on each site's rules and the page's actual state.