SESSIONS & CONTROL
Sign in for your browser agent with human handoff
When your agent reaches a login screen, you can sign in yourself inside the same remote browser. Take control first. Watching alone is read-only.
From agent to human, and back
Open the live browser
Find the browser by its name, project, or purpose in the dashboard. Choose Watch and check that it is the session your agent is using.
Take control
Choose Take control before typing or navigating. While your control lease is active, Tallylamp rejects agent tools that would change that browser.
Finish the sign-in
Use the remote page to enter your credentials and complete any verification the site permits. Check that you can see the signed-in workspace.
Return the browser
Choose Return to agent. Tell the agent to inspect the current page and continue. Its MCP connection stays open, but a rejected action may need a retry.
What changes when you take control
| Mode | What you can do |
|---|---|
| Watch | See the live page. You cannot type, navigate, change tabs, or resize Chrome. |
| Human control | Use the page, address bar, and tab controls. Agent actions that change the browser are blocked. Full browser also shows Chrome's toolbar and dialogs. |
| Returned to agent | The agent can act again and use the session you just signed into. |
The handoff is enforced by the server. A live viewer holds a control lease and sends heartbeats to keep it. If another operator takes control, the old viewer loses permission to change the browser.
Use a desktop browser for detailed remote input. On a phone, the first release supports fleet status, watching, starting or stopping a browser, and returning control; it is not a full mobile remote desktop.
Where the login goes
The site stores its cookies and local storage in the remote Chrome profile. A persistent profile keeps that data when Chrome stops, provided the data volume remains attached. The website can still expire the session later.
You can record the signed-in site after checking its authenticated page. That record helps you find the right browser next time. It describes what was observed at that time, without storing the cookie or token itself.
If the website still refuses access
Some sites require a fresh verification, reject a server IP, or block automation. Takeover lets a person attempt the site's normal flow. It does not provide a CAPTCHA bypass or guarantee that the site will accept the browser.
You can give a browser its own HTTP or HTTPS proxy when it needs a different network route. That changes how web connections leave the server, not whether a website permits the task. The proxy guide covers setup and limits.
An OAuth redirect to localhost is a different problem: localhost inside remote Chrome refers to the server. The loopback-tunnel guide explains how to bind one permitted private address when the callback needs to reach your own machine.
Docs behind this guide
Based on Tallylamp's documented behaviour. See the source for API details and release-specific settings.