04 / 04

Your agents, in a real browser.On your terms.

Melaya agents drive Chrome, Edge, or Brave on your machine: reading pages, clicking, typing, and verifying each step. You pick the target, watch every move live, approve what matters, and stop it cold anytime.

← Back to home

Billing · InvoicesDashboard

Ready

Download this quarter's paid invoices, and pause before anything leaves the page.

Listening to you

Billing

Invoices

Search invoicesExport center

InvoiceCustomerDateAmountStatus

INV-1043NTNorthwind TradersSep 02$1,980.00Paid

INV-1042GXGlobex CorpAug 28$640.00Paid

INV-1039ACAcme ComponentsAug 14$3,200.00Paid

Showing 3 paid this quarter · 24 total

Billing / Exports

Export center

SelectedINV-1043INV-1042INV-1039

FormatPDF

RangeQ3 2026

Download 3 PDFs

Agent has controlReads page structure, not fragile pixelsStop

You pick the targetengine, tab, and profile chosen in trusted UI, never by the model

Site allowlistagents act only on origins you grant, enforced at the browser boundary

Watch it livea live mirror, a persistent control indicator, and one-click emergency stop

Any modelhosted or local models; the browser always stays on your machine

An agent that browses the way you do.Under rules you set.

Most of the web has no API. Browser Control gives Melaya agents careful hands on real pages: research, forms, back-office portals, and repetitive web work, all inside a governed session you can watch. They drive Chrome, Edge, or Brave on your machine, and nothing consequential happens without your yes.

Reads the page as a compact structural snapshot with stable element references, not brittle pixel guesses.

Clicks, types, scrolls, and navigates one verified step at a time, re-checking the page after every action.

Pauses for your approval before anything consequential: submitting, uploading, downloading, or crossing to a new site.

Hands control to you for sign-in, CAPTCHA, and payment, then resumes from a fresh view of the page.

The model never chooses what it controls. You do.

Engine, tab, and profile are selected in trusted Melaya UI, and confirming issues a short-lived, single-use session grant. Listing tabs, attaching, and switching are not agent tools at all; they simply do not exist on the model side.

Trusted target

Engine

TabOpen freely / specific pageAlready-open tab · Coming soon

ProfileDedicated Melaya profileReal profile · Coming soon

SourceLocal runnerExtension · Coming soon

Confirm issues a signed, single-use, short-lived session grant

See exactly what the agent sees, and what it does

The mirror shows the controlled browser with the agent's element references overlaid, and every tool call streams beside it. No black box: the same references drive the run and the audit trail.

Orders · supplier portalInventoryLIVE

Orders / New

New purchase order

SupplierAcme Components Ltd

Quantity12

Delivery date2026-09-01

Submit order

agent · browser toolsLIVE

browser.get_screen_tree()
Reads the page: 42 elements, refs @e1 to @e42
browser.click("@e7")
Focuses the quantity field
browser.input_text("@e7", "12")
Types the order quantity
browser.submit("@e12")
Pauses: submit requires your approval

Autonomy you can dial, approvals you can trust

Choose Safe, Payments-only, or Autonomous per automation, the same autonomy model as Mobile Agents. Whatever the mode, the guardrails below never switch off.

Typed effects: sending, publishing, uploading, downloading, purchasing, and new-origin navigation each carry their own approval rule.

One approval ledger across web, phone, and pipelines, re-verified at the moment of execution, not just when queued.

Page text is treated as untrusted data. A web page cannot talk the agent into new permissions or cross-site disclosure.

Credentials are never typed by the model: sign-in, CAPTCHA, and payment always hand over to you.

Dangerous destinations (local network, internal services, file URLs) are blocked at the browser boundary by default.

Chrome, Edge, or Brave. Your machine, your choice.

The runner detects the browsers installed on your machine and you choose which one each session uses. The browser, its profile, and its data never leave your computer.

Detected engines

Google Chrome

The default engine, launched in a dedicated profile your agents cannot escape.

Detected

Microsoft Edge

First-class on Windows fleets; same trusted picker, same guardrails.

Detected

Brave

Fully supported, including Shields; pick it like any other engine.

Detected

Two ways in. You stay in control either way.

Run a fresh browser from inside Melaya, or bring Melaya to the browser you already use. Same governance, same live view, same one-click stop.

01Available now

Launch inside Melaya

Open a dedicated, controllable browser straight from your runner. Nothing to install, ready in seconds.

Open Browser Control

02For your own browser

Add the browser extension

Install the Melaya extension in your own Chrome, Edge, or Brave to drive the tabs you already have open, with approvals in the popup.

Get the extension

Questions people actually ask

The short version: you stay in charge, the browser stays on your machine, and nothing consequential happens without you.

What is Browser Control?

A governed way to let Melaya agents use a real web browser: they read the page structure, click, type, and navigate, while you watch live, approve consequential actions, and can stop everything with one click.

Which browsers are supported?

Google Chrome, Microsoft Edge, and Brave are first-class engines. Your runner detects what is installed and you pick which one to launch.

Can an agent open my banking tab or my email?

No. Agents cannot list, open, switch, or close your tabs. You select the target in a trusted picker, sessions run in a dedicated profile with no personal logins, and every session is scoped to the sites you allow.

Where does the browser actually run?

On your machine, through the Melaya runner. The browser and its data stay local; you choose the AI model separately, including local models.

What about logins, passwords, and payments?

Agents never type credentials or payment details. For sign-in, CAPTCHA, or checkout the agent pauses and hands control to you, then resumes after you finish.

Can it use my everyday browser and existing sessions?

That is the extension path, and it is coming soon. Today Browser Control launches a dedicated, controllable browser; the extension will add already-open tabs and real-profile sessions with approvals in the extension popup.

Give your agents the web, keep the keys

Launch a controllable browser from your runner, grant a session in the trusted picker, and watch your first web automation work.

Open Browser Control Read the docs

Local execution. Dedicated profiles. Approvals on every consequential action.

Join the community