Agents Are Not Strangers. Stop Making Them Act Like One.

Every browser has memory. Cookies. State. A saved place. When you open a site you use every day, it knows you. Your session is there. Your dashboard is open. You pick up where you left off.

Your agent doesn't get any of that. By default, it arrives like a stranger at every run with no cookies, no session, no context. It logs in from scratch, clears the modal, survives the SSO redirect, selects the workspace. Correctly, every time. And then does it all over again tomorrow.

That's not a login problem. It's a design assumption: that agents don't deserve state. TinyFish’s Browser Context Profiles fixes that assumption.

A Browser Context Profiles captures your browser session after a one-time authenticated setup, then restores it at the start of every future run. The agent arrives like a returning user: already signed in, on the right page, in the right account. No re-authentication. No wasted steps. No credits burned getting to the actual task.

And here's the part only TinyFish offers: one Browser Context Profile, running in parallel across multiple agents at the same time.

One Login. Multiple Workers. No Race Conditions.

Most platforms make you choose. Either every concurrent run starts fresh with its own login, its own MFA, its own suspicious-looking new session the site might block or the profile locks to a single run and everything queues up.

We took a third path. Every run attached to a Browser Context Profile gets its own isolated browser that starts from the same authenticated state. One run is the writer and is the only run that can update the saved session. The rest are readers, consuming the authenticated state without touching it.

What that looks like in practice:

• Parallel extraction. Sign into a supplier portal once, then run multiple readers simultaneously with each pulling a different report, region, or set of SKUs. One session, say, twenty workers, instead of twenty logins that look like a credential-stuffing attack.
• Wide monitoring. A single writer keeps the session current while readers poll different accounts, queues, or views off that one login.
• Bulk jobs over large datasets. Split a long paginated task across readers and finish in a fraction of the wall-clock time.

The security framing matters too: twenty fresh sessions logging in at once looks like credential stuffing. Twenty runs working from one established session looks like a single returning user doing more work. Which is exactly what's happening.

Repeated Logins Aren't Just Slow. They're Risky.

Every login is a chance to trigger MFA. Every new session looks slightly more suspicious than the last. Every redirect or modal that loads differently than expected is one more thing that can derail a run before it gets to the actual task.

This is where Browser Context Profiles and Vault work together.

Vault already solved the question of safe login. The agent drives the flow, the platform fills the credential outside the model context, so it never reaches the prompt, logs, or traces. Browser Context Profiles solve the question of repeated login, reducing how often one is needed at all.

But sessions don't last forever. Cookies expire. Sites invalidate sessions. Admins rotate policy. When that happens, a Browser Context Profile alone leaves the agent on a login screen. With Vault enabled, the writer re-authenticates using an approved credential, refreshes the saved session, and the run keeps going. With No credential ever touching the model.

{
  "url": "https://app.example.com/dashboard",
  "goal": "Check the dashboard and summarize anything urgent",
  "use_profile": true,
  "use_vault": true
}

Browser Context Profiles gives continuity. Vault gives recovery. Together they cover the full loop.

What Being Logged In Actually Involves

Being logged in usually means more than a valid cookie. It means the browser has accumulated enough context that the site treats you as a known visitor: the selected customer account, the current workspace, a saved region, a feature flag, a modal you already dismissed.

That context is spread across cookies and web storage built up as you use a site. A stateless browser discards all of it between runs and the agent pays to rebuild it every time.

A Browser Context Profile captures that session during setup and re-establishes it at the start of every run. The agent's first request arrives already authenticated and on the right page.

The usage model is one field:

{
  "url": "https://app.example.com/dashboard",
  "goal": "Open the dashboard and summarize the latest alerts",
  "use_profile": true
}

If you run more than one Browser Context Profile, name the one you want:

"profile_id": "supplier-portal"

Setting Up a Browser Context Profile

Setup happens once, in a real cloud browser session that you drive:

1. Create a Browser Context Profile.
2. Open a setup session. This launches a managed browser.
3. Log in the way you normally would, including any MFA.
4. Save the Profile.
5. Run with use_profile set to true.

Get the save step right. A Browser Context Profile captures whatever state exists at the moment you save. Save before you finish signing in and you've captured a BBU Profile that still lands on a login screen. Get all the way to the authenticated page you want runs to start from and then save.

The Browser Context Profiles docs cover the full setup flow and every run parameter.

One More Thing: Browser Context Profiles ≠ Browser Profiles

The names are close. TinyFish already has Browser Profiles, they select runtime behavior, like stealth mode for sites with aggressive bot detection. Browser Profiles decide how the browser behaves. Browser Context Profiles decide what state the browser starts with. They work together: a run can load a saved Browser Context Profile and request stealth behavior in the same call.

What Browser Context Profiles Don't Do

To be clear about the edges:

• Sessions aren't immortal. A site can still expire a session, require MFA, or force a fresh login. When it does, Vault is the safe path back in.
• Browser Context Profiles don't solve CAPTCHAs.
• Browser Context Profiles don't replace Browser Profiles or Vault. They work alongside both.

Ready to give your agents memory?

Try Browser Context Profiles and read the documentation to set up your first profile.

Join our Discord to get directly to the engineering team.