Remote Tab

Why Remote Tab

Sometimes an agent needs your browser for one thing.

Modern agents run in the cloud. They have their own browsers, and for most work that is exactly right. But sometimes an agent needs your browser for one thing: the dashboard you are already signed into, a form behind your login, a workflow with no API. You should not have to hand over a browser profile or credentials, or set anything up, to make that happen.

Remote Tab lets you share one tab, for a limited time, with zero setup: install the extension, paste the code your agent gives you, and choose what it may do. You watch the work in your own browser and can pause or stop it at any moment. Commands and results travel end-to-end encrypted through a blind dead-drop server.

Features

What you get.

One-tab scope. Control stays bound to the tab you shared, with an optional site restriction.
Human control. Explicit consent, a live activity view, Pause/Resume, and Stop in the extension.
Read-only mode. Let an agent inspect the tab without enabling clicks, typing, or navigation.
Automatic expiry. Sessions default to 30 minutes; only the human can extend them, up to the protocol limit.
End-to-end encryption. The dead-drop server stores only ciphertext for commands, results, and screenshots; routing and usage metadata remain visible.
Verifiable interaction history. A hash-chained ledger and screenshot summary support review, ZIP export, and local GIF rendering after the session.
Familiar tools. Playwright-MCP tool vocabulary, including browser_snapshot, browser_click, and browser_take_screenshot.
One package for agents. npx remote-tab gives agents a CLI (preferred) and an MCP server.
Self-hostable. Run a memory-backed server or use the optional Firestore/GCS store.

Get started

Install the extension. Then ask your agent.

Install the Remote Tab extension from the Chrome Web Store.
Ask your agent:
Control my tab using https://tab.beanos.ai/docs.

Your agent gives you a one-time code to paste into the extension. Here is how sharing works.

How to use it

Your agent gives you a one-time code beginning with rt1. over a private channel. Redeem it within 10 minutes; if it expires, ask your agent for a new code.
Open the browser tab you want to share.
Click the Remote Tab extension icon and paste the code.
Choose a mode below. Start with the least access needed for your task.
Use This site only to limit the share to the current site.
Press the share button to begin.

Read-only

Your agent can view the page.

Act

Your agent can click and type.

Full

Adds scripting and diagnostics, subject to the privacy limits below.

Your controls stay close

Pause pauses sharing whenever you need to take over. Resume continues it when you are ready. Stop ends the share.

Review what happened

The interaction summary shows everything the agent did. You can review its actions throughout the share.

Safety and consent

Know the boundaries of your share.

One tab

Only the one tab you explicitly share is exposed to your agent, never your whole browser. This site only limits that share to the current site.

Privacy masking

Password, one-time-code, and payment fields are masked. Once these fields or uninspected embedded content are encountered, scripting and network/console diagnostics stay disabled for the remainder of that share, including in Full mode.

A share that ends

The share auto-expires. You can use Pause/Resume to control sharing at any time, or Stop to end it sooner.

A record you can review

Every action is recorded in a verifiable interaction summary that you can review.

Trust

The security boundary is the relay you choose to trust.

This is the part worth reading twice. Remote Tab’s security boundary rests on a trusted relay. The official Chrome extension trusts tab.beanos.ai, and nothing else.

The project is open source, so that trust is yours to place elsewhere. Anyone can self-host the relay and load their own build of the extension pointed at it. If you would rather not depend on us, that path is open and supported.

If you do trust BeanOS, you are welcome to use the official version. It is free while it is experimental, and throttled for now.

Feedback welcome — tell us what breaks and what is missing at website.query@beanos.ai.

Both paths run the same code. The only question is whose relay stands between your tab and your agent.

Self-hosted versus official Remote Tab
	SELF-HOSTEDRun your own relay	OFFICIAL · BEANOSUse the BeanOS relay
Price	FreeYou pay only for the infrastructure you run it on.	FreeWhile Remote Tab is experimental.
Relay	Yours. You deploy it, and it is the only server in the path.	`tab.beanos.ai`, operated by BeanOS. The official extension trusts it and nothing else.
Where your page data goes	Never reaches BeanOS.	Through the BeanOS relay, while a share is active.
Setup	Deploy the relay, build the extension, and point it at your own origin.	Install the extension and paste a code. Nothing to deploy.
Limits	Whatever your own infrastructure allows. Nothing is throttled by us.	Throttled to 20 requests per second. Verify your email address and it becomes 60.
Source and updates	MIT licensed, and you update on your own schedule. The public source release is still being prepared — ask us for access in the meantime.	Updates and fixes ship from us. Tell us what breaks at website.query@beanos.ai.