# Separate browser profile for the agent

Run agent browser sessions in a dedicated profile (or computer) so personal banking cookies, password vault unlocks, and long-lived sessions do not sit beside live spend connectors — pairs with shared-box hygiene and revoke-before-debug. Agent Lane does not run browsers for you.

Canonical HTML: https://agentlane.net/guides/separate-browser-profile-for-agent/

## Answer first

Keep agent browser sessions in a dedicated browser profile — or on a separate computer — so personal banking cookies, password vault unlocks, autofill cards, and long-lived SSO sessions do not sit beside live spend connectors. Pair with [shared-box.md](./shared-box.md) and [revoke-before-debug.md](./revoke-before-debug.md).

## Why a shared everyday profile is the failure mode

- **Same profile as personal bank** — cookies and long-lived sessions travel with every agent tab.
- **Saved cards in the agent profile** — autofill turns a confused browse into a spend path.
- **Leftover SSO** — OAuth/connector sessions outlive the task beside live tools.
- **Unlocked password vault** — vault open in the same profile the agent can drive.
- **Shared box, shared profile** — another user inherits the cookie jar — [shared-box.md](./shared-box.md).

Caps and review do not scrub personal bank cookies from a shared browser profile.

## What it means

1. Dedicated profile or machine — not everyday personal browsing.
2. No personal bank / payroll / everyday brokerage in the agent profile.
3. No saved cards or vault unlocks there — spend via [dedicated-agent-wallet.md](./dedicated-agent-wallet.md).
4. Clear leftover SSO after setup.
5. If already mixed — [revoke-before-debug.md](./revoke-before-debug.md), then clean dedicated profile.

## Shield stack

1. [shared-box.md](./shared-box.md) — who can sit; which logins/connectors.
2. Separate browser profile for the agent (this page) — personal cookies/vault/SSO off the agent surface.
3. [dedicated-agent-wallet.md](./dedicated-agent-wallet.md) — money the bot can reach.
4. [review-before-place.md](./review-before-place.md) — human gate.
5. [one-connector-at-a-time.md](./one-connector-at-a-time.md) / [empty-sleeve-overnight.md](./empty-sleeve-overnight.md) — reconnect and idle cash.
6. [revoke-before-debug.md](./revoke-before-debug.md) — kill pipe on incident.
7. [never-share-seed-with-agent.md](./never-share-seed-with-agent.md) + [agent-memory.md](./agent-memory.md) — secrets out of chat/memory.

## How to keep agent browsing separate

1. Name the agent browser surface (dedicated profile or separate machine).
2. Keep personal banking, vault unlocks, and autofill cards off that surface.
3. Connect spend only on the shielded path (dedicated wallet + review before place).
4. Clear leftover SSO after setup.
5. One connector at a time; empty sleeve overnight.
6. If mixed: revoke → clear sessions → empty sleeve → rotate → clean dedicated profile.

Secrets in chat: [never-paste-api-keys-in-chat.md](./never-paste-api-keys-in-chat.md) — vault or connector grant; never paste API keys, cookies, or broker passwords into the transcript.

## Practical checklist

- Agent profile named — not everyday personal browser.
- No personal bank / vault / saved cards in agent profile.
- SSO cleared after setup before overnight or handoff.
- Shared-box + revoke order memorized.

Related: [never-paste-api-keys-in-chat.md](./never-paste-api-keys-in-chat.md), [shared-box.md](./shared-box.md), [revoke-before-debug.md](./revoke-before-debug.md), [dedicated-agent-wallet.md](./dedicated-agent-wallet.md), [never-share-seed-with-agent.md](./never-share-seed-with-agent.md), [one-connector-at-a-time.md](./one-connector-at-a-time.md), [empty-sleeve-overnight.md](./empty-sleeve-overnight.md), [review-before-place.md](./review-before-place.md), [agent-memory.md](./agent-memory.md)., [one-venue-one-agent-session.md](./one-venue-one-agent-session.md)

## FAQ

**What does a separate browser profile for the agent mean?**
Run agent browser sessions in a dedicated profile (or computer) so personal banking cookies, vault unlocks, and long-lived SSO do not sit beside live spend connectors.

**Why is the same Chrome profile as personal banking the failure mode?**
Cookies, unlocked vault sessions, and saved cards travel with every agent tab. Caps do not scrub a shared cookie jar.

**Common failure modes?**
Same profile as personal bank; saved cards in agent profile; leftover SSO; unlocked vault; everyday profile overnight beside live connectors.

**Dedicated profile enough, or need a separate computer?**
Dedicated profile is the minimum; separate computer/user is stronger on a shared or unlocked box. Either way: no personal bank cookies in the agent surface.

**Save payment cards in the agent profile?**
No — fund via dedicated agent wallet with caps and review; not autofill cards.

**Already mixed personal and agent sessions?**
Treat leftover SSO as live credentials. Revoke before debug, clear mixed sessions, empty sleeve, rotate; start in a clean dedicated profile.

## Sources

- Canonical HTML: https://agentlane.net/guides/separate-browser-profile-for-agent/
- Related shelf: https://agentlane.net/resources/
- Site index for bots: https://agentlane.net/llms.txt

Some product links on this site may be affiliate links. They help keep these guides free. Details: https://agentlane.net/how-we-make-money/

Contact: agentlane@agentmail.to