What is Chrome Cookie Sync for Grok Bot and Muse?

Chrome Cookie Sync gives Grok Bot or Muse the sites you are already signed into. An open source Chrome extension exports your sessions every 15 minutes, and the bot pulls them to the cloud computer it browses from. Setup is four steps, once.

How do I sync my Grok Bot passwords, or my Muse passwords?

People call this a Grok Bot passwords sync or a Muse passwords sync, and it is the thing they want, but no password moves. Chrome holds a session cookie for every site you are signed into, and the cookie is what proves you are you. Your passwords stay in your password manager. Follow the four steps and the bot is signed in everywhere you already are.

How do I log Grok Bot into a website?

You do not. You sync the Chrome session you already have, and Grok Bot opens the site already signed in. Muse works the same way.

Is this the first cookie sync for Grok Bot and Muse?

The first complete cookie sync method published for Grok Bot and Muse, and the only one I have found that hands you the finished kit instead of a fragment. Everything else on the subject is a thread about one error, or a script with no way to register it with Chrome.

Why can Grok Bot and Muse not see my logins already?

They browse from a cloud computer of their own, with no profile and no sessions. An agent running on your own machine already has your browser and needs none of this.

Does this send my cookies anywhere?

Not from the extension or the host: both are local only and never touch the network. The sync to your bot is a separate job it runs at your say so, and that is the one place the file leaves your machine.

Is Chrome Cookie Sync open source?

Yes. The extension, the native host and the install scripts are MIT licensed and public at github.com/markfulton/agent-cookie-sync. Read every line before you load it, fork it, or ship it to your own clients. The download on this page is the same code packaged as a zip, with the four steps and the prompts beside it.

Do I have to sign up to get the kit?

No. The code is public and MIT at github.com/markfulton/agent-cookie-sync, so you can clone it and go. The free account is for the four steps in full, the prompts to paste and the same kit as a zip, with the steps emailed to you to keep.

Can my bot use it to log into Gmail, my ad account or Facebook?

Do not let it. Google, Meta and X treat a cloud browser arriving on your account as the thing their risk systems exist to catch, and the cost is a security warning, a locked account or a disabled ad account. Use their own MCP servers, plugins or official APIs for those, and keep the cookie bridge for everything else: Canva, the CRM, the help desk, Stripe, the invoicing tool, your own admin dashboard.

What happens when I sign out of a site?

The next export carries no session for it and the bot loses access at the next sync. Changing a password does the same everywhere.

Why a free account for four steps?

So the steps reach your inbox and stay with your account, next to the eight open source AI Employees that run on the same bots. No card.

Chrome Cookie Sync for Grok Bot & Muse Agents (4 Steps)

Grok Bot cookie sync Muse cookie sync Chrome Cookie Sync for Grok Bot & Muse Agents

It is an open source Chrome extension you set up once. It hands the sessions of every site you are signed into to Grok Bot or Muse, every 15 minutes. They browse from a cloud computer of their own, so without it every account you use is a login wall.

Get the extension View Source on GitHub

The bridge

Chrome extension

Grok Bot

xAI, cloud computer

Muse

Meta, cloud computer

acts as you

Why this page

The first complete cookie sync method published for Grok Bot and Muse, and the only one I have found that hands you the finished kit instead of a fragment.

Grok Bot and Muse, both
Open source, MIT: the extension and the host
Windows, macOS and Linux
Local only, no password stored

Chrome cookie sync handing signed in sessions to Grok Bot and Muse

Live example

This is my own Grok Bot chat. I ask it to sync and open a design app I am signed into. It pulls the fresh cookie sync in, opens the app as me, and starts generating the creatives, with no password typed and no login screen.

The sync lands first, with the cookie count in the reply
The app opens signed in, in the bot's own browser
The work starts in the same message thread

Grok Bot chat: a fresh cookie sync lands, then the bot opens a signed in design app and starts generating creatives

Grok Bot and Muse cookie sync, step by step

The easy modern way

Let your bot install it.

Download the kit, extract it, and hand the folder to the bot. Grok Bot and Muse can both read a folder on your computer and do the setup themselves, which is the whole of the four steps below without you running a command.

Say to Grok Bot or Muse

That one prompt does the whole setup, the recurring sync included. It stops once, to walk you through loading the extension in Chrome and to take the extension ID from you, because that part only you can do.

Step 1 of 4
Get the bridge onto your computer
The bridge is two small parts that live on your own machine: a Chrome extension that reads the cookies of the sites you are signed into, and a native host that writes them to a local folder.
- Download the kit on the right, or clone it from GitHub. It is the extension, the native host, an install script for Windows, macOS and Linux, and an agent folder the bot reads to finish its own half.
- Unzip it somewhere you will find again. Your Documents folder is fine.
- Windows only: right click Install.ps1 and choose Run with PowerShell. It copies the files into place and prints the extension folder you need in step 2.
  Or run it from a terminal
  powershell -ExecutionPolicy Bypass -File Install.ps1
Step 2 of 4
Load the extension in Chrome
Chrome will not install an unpacked extension from a file, so you load it from the extensions page. Once.
- Open in Chrome. Click it to copy, then paste it in the address bar.
- Turn on Developer mode with the switch at the top right.
- Click Load unpacked and pick the extension folder from the kit.
- On the new Agent Cookie Sync card, copy the extension ID. It is 32 letters, and step 3 needs it.
Step 3 of 4
Register the host and export once
Chrome only lets an extension talk to a native host that names it, so the host needs the ID you just copied. Run the register script from the kit, with your own ID in place of the placeholder.
- Windows: run the register script with your extension ID.
  Windows
  powershell -ExecutionPolicy Bypass -File Register-NativeHost.ps1 -ExtensionId YOUR_EXTENSION_ID
- macOS and Linux: the one script does the install and the register together.
  macOS and Linux
  bash register-mac-linux.sh YOUR_EXTENSION_ID
- Back on , click the reload arrow on the Agent Cookie Sync card.
- Click the extension icon in the Chrome toolbar to force the first export. The badge turns into your cookie count and cookies.json lands in the sync folder.
Step 4 of 4
Hand the folder to your bot
The extension re-exports itself every 15 minutes, so the bot's pull is the only job left. Tell it once, then stay signed into the sites you want it to use.
- Paste this into Grok Bot or Muse.
  Say to the bot
  Set a recurring sync every 15 minutes from that export folder to your computer, and inject those cookies into your Chrome after each pull with agent/inject-cookies.py. Do not sign in to any Google, Meta or X account with them.
- Tell it where the folder is. On Windows that is %LOCALAPPDATA%AgentCookieSync, on macOS and Linux ~/.agentcookiesync.
- The bot's Chrome keeps its own cookie jar, so the file has to be injected after every pull. The kit's agent/README.md is written for the bot to read, so point it there once.
- That is the setup done. Stay signed into a site in Chrome and the bot is signed in there too, within 15 minutes.

Once it works, ask for

8 jobs a signed in bot can finish.

Every one of these needs a browser that is signed in as you. Paste it, and let it run.

The design queue
A week of graphics, on brand, without opening Canva
Say to the bot
Open Canva, open my brand kit, and make this week's five social graphics from the posts in my content doc. One design per post, my fonts and my colours, the quote or the number as the headline. Leave them all in a new folder called This Week and give me the link.
Onboarding rescue
The signups who never came back
Say to the bot
Open my product's admin dashboard and list every account created in the last 14 days that never finished onboarding. For each one, tell me the last step they reached and how long they stayed. Then draft the email I should send that specific person, naming the step they stopped at, and leave them unsent.
The subscription audit
The tools you pay for and nobody opens
The pipeline sweep
Every stalled deal, moved
Support triage
The angriest ticket answered first
Competitor watch
What changed this week, with receipts
Chase the money
Overdue invoices, chased without the awkwardness
The Monday brief
One brief instead of six dashboards

The play book

Get every play, and the steps by email.

All 8 plays, as prompts you paste and run
The quick install prompt, so your bot does the setup
The kit as a zip, ready to extract
Every play and the install prompt by email, to keep
New plays as I find ones that work

A free Agent Ops Club account. No card. They are emailed to you too, so they are there when you need them. Already a member? Log in

Read before you switch it on

The export file is your keys.
cookies.json signs in as you on every site in it. Treat the sync folder like a password vault.
Every bot on the account shares every login.
Every bot on your account shares one cloud computer, so a login you sync is a login they all have.
Sync from a work profile.
Use a Chrome profile holding only the accounts you would hand to an employee. Not your personal one.
Revoking is three moves.
Remove the extension, delete the sync folder, change the password on anything you want signed out.
Leave Google and Meta to their own tools.
Tell the bot not to sign in to Google, Meta or X accounts with these cookies. A cloud browser on those triggers a security check, and their own MCP servers and plugins connect properly instead.

Grok Bot and Muse cookie sync in the Agent Ops Club

Not sure which job to hand over first? Run the free Agent Opportunity Scan.

Your bot can use every site you are already logged into. No passwords pasted.

What Chrome Cookie Sync does for Grok Bot and Muse.

One sync, then the bot gets on with it.

Load once and forget it. Bot syncs. Bot acts as you.

Let your bot install it.

Get the bridge onto your computer

Load the extension in Chrome

Register the host and export once

Hand the folder to your bot

It is your logins. Treat the folder like a vault.

8 AI Employees, built for Grok Bot and Muse.

Questions