THE TALLYLAMP GUIDES
Make the browser
part work.
Connect an agent, keep a session, step in when needed. Practical help for the browser running on your server.
Deploy on RailwayStart here
Choose a host, then connect your agent.
A self-hosted browser for AI agents
Run persistent Chrome on your server, connect an agent through MCP, and watch or take over its browser with Tallylamp.
Connect an AI agent to a browser through MCP
Connect to Tallylamp's Streamable HTTP MCP endpoint with an agent token or OAuth, then check the first browser call.
Deploy a persistent browser on Railway
Deploy Tallylamp on Railway with a persistent /data volume, save your dashboard password, and connect your first browser agent.
Sessions & control
Keep the right profile. Know who can use it.
Sign in for your browser agent with human handoff
Watch your agent's Chrome, take control to sign in or finish verification, then return the same browser to the agent.
Let someone else sign in or clear 2FA in one browser
Send a colleague a single-use guest link to one Tallylamp browser so they can sign in or answer a 2FA prompt, without sharing your dashboard password.
Use Chrome extensions in a remote browser
Install an extension in Full browser, decide whether the owning agent can operate its popup, and let an agent debug it.
Let an agent use a tab in your own browser
Link your everyday Chrome, Edge or Brave to Tallylamp with the Tallylamp Link extension, share one tab at a time, and take it back when you're done.
When another extension stops a tab from sharing
Why Chrome refuses a tab that holds another extension's frame, how to fix it safely, and what the Chrome flag that lifts the rule costs you.
Keep browser sessions with persistent Chrome profiles
Understand what Tallylamp keeps after Chrome stops, how saved logins behave, and why a persistent data volume matters.
Reuse a prepared browser with profile templates
Save a Chrome profile, grant loading and saving permissions deliberately, and check copied sessions in each new Tallylamp browser.
Set permissions for browser agents
Give each agent its own credential, browser cap and scopes, and approve an agent's request for your browser at read or control.
Reach localhost from a remote browser
A hosted browser cannot reach your machine by default. A loopback tunnel lets one browser reach one private host and port, such as an OAuth callback on localhost or a dev server.
How we test Dray's MCP connector in ChatGPT, Claude and Grok
We signed ChatGPT, Claude and Grok into one Tallylamp browser, added Dray's MCP server to each and let an agent run the chats. Each app handled the connector differently.
Run it well
Plan capacity and look after your deployment.
Plan browser memory and idle timeouts
Size a Tallylamp deployment using active Chrome usage, browser caps, and separate idle limits for attached and unattached sessions.
Run Tallylamp with Docker and a persistent volume
Start the published Tallylamp Docker image locally, preserve Chrome profiles in a named volume, and prepare a remote host for HTTPS.
Upgrade Tallylamp while keeping browser profiles
Choose a release image, back up /data, and verify saved profiles after a Tallylamp upgrade on Railway or Docker.
Route a browser through its own proxy
Set a per-browser HTTP or HTTPS proxy in Tallylamp, add optional credentials, and understand DNS, tunnel precedence, and failure behaviour.
Need an API endpoint or a client configuration example?
Open the technical documentation