Add to ChromeCookie Sync lets you securely upload cookies from your local Chrome to the cloud, so rtrvr.ai cloud browsers can use your logged-in sessions. Cloud automations can access authenticated sites (LinkedIn, Gmail, internal tools) without you sharing passwords or manually logging in to cloud browsers.
Profile-Based Isolation
Cookie Sync is scoped to the current Chrome profile. Each profile has its own cookie store, and sync only reads from the profile where the extension is running. Use separate profiles for separate accounts.
Profile "Work" → syncs work Gmail cookies → deviceId: device-work
Profile "Personal" → syncs personal Gmail cookies → deviceId: device-personal
Profile "Client" → syncs client portal cookies → deviceId: device-clientHow It Works
- 01
Grant the "cookies" permission when prompted (optional, revocable anytime)
- 02
Browse your cookies using the search button — only the current profile's cookies appear
- 03
Check the domains you want to sync (e.g., linkedin.com, github.com)
- 04
Click "Sync All" or enable auto-sync on a schedule
- 05
Cloud browsers automatically restore cookies before running your workflows
Auto-Sync Scheduling
Cookies expire and rotate frequently. Enable auto-sync to keep them fresh. Choose intervals from 15 minutes to 24 hours based on how aggressively your target sites rotate session tokens.
| Site Type | Recommended Interval |
|---|---|
| Banking / sensitive sites | 15–30 minutes |
| Social media | 1–6 hours |
| Internal tools | 12–24 hours |
Domain Selection
The cookie browser shows all domains with cookies in your current Chrome profile. Use the search bar to filter, then check the domains you want to sync. Selecting "google.com" includes all subdomains (mail.google.com, etc.).
You can also ask in chat: "sync my cookies for linkedin.com to the cloud" or "make my scheduled run work on app.example.com". The agent adds the site and syncs it now. The first time, Chrome's cookies permission has to be granted by a click — the chat shows a Grant permission button and the run continues the moment you press it; adding a new site also asks for a one-time confirmation, because it turns on the recurring sync. The reply says whether a login was found for the site ("is linkedin.com synced?" reads the same status).
Cloud Storage
Cookies are stored at a Firebase path unique to your account and device:
user_cookies/{userId}/{deviceId}/{domain}
Example: user_cookies/abc123/device-work/linkedin_comSecurity & Privacy
- 01
Cookies are stored in your private Firebase path — no other users can access them
- 02
The "cookies" permission is optional and can be revoked anytime
- 03
You choose exactly which domains to sync — no automatic collection
- 04
"Clear Cloud Data" instantly deletes all synced cookies
- 05
"Revoke Access" removes the permission and clears all cloud data
Troubleshooting
- 01
Verify cookies are synced: check "last synced" timestamps in the domain list
- 02
Re-sync manually: click the refresh icon to force an immediate upload
- 03
Check the right profile: make sure you're syncing from the profile where you're logged in
- 04
Session expired: log back into the site in your browser, then re-sync
- 05
DeviceId mismatch: ensure your cloud workflow targets the correct deviceId