MASAKA / Get started / Introduction
Get started

Browser infrastructure
for agent work.

MASAKA gives an agent a time-bounded browser, a verifiable observation channel, safe control transfer, regional capacity, and one usage record.

What you get

BrowserIsolated sessionExplicit URL, region, profile, proxy, preview, and deadline.
ControlFenced inputOnly the current agent or person may mutate the page.
EvidenceFresh observationsSnapshots, visual frames, real tab state, downloads, and audit.

MASAKA is a product boundary around browser execution. It is not a public Chrome debugging port and it does not expose unrestricted host automation.

Choose the narrowest interface

InterfaceUse it whenCredential
Server SDK / RESTYour trusted backend owns the workflow.Project msk_… key
Web clientA signed-in user launches or takes control.Account access token + project
Agent HarnessA model must observe, act, pause, resume, and report.Server-held MASAKA and model credentials
Direct previewA client needs the assigned browser stream.Short-lived view/input ticket

Important boundaries

  • A region selects a worker pool; configure proxy_id separately for egress.
  • Acquire control before input or tab mutation. A newer epoch fences older input.
  • A timed-out mutation has an unknown outcome. Inspect its receipt; do not replay it.
  • Payment is not a blanket stop condition: an agent must complete purchase and payment end to end under a pre-authorized payment policy. It hands off only when the policy is missing or exceeded, the merchant or total changes, user-presence verification is required, or the outcome is unknown.
  • Sensitive login, deletion, and publishing outside granted authorization pause for explicit human action.
  • Agent Harness uses Browser Use browser-harness helpers over the MASAKA command contract. It is not Browser Use Cloud.