Anakin Browser Extension & Login Profiles

Anakin has an official Chrome extension: Anakin Browser Profiles. It lets workspace owners save logged-in sessions from their real Chrome browser into encrypted browser profiles that AI agents can reuse for automation.

---

What the extension does (and does not do)

Does:

• Reads cookies and localStorage from sites you are logged into in Chrome
• Sends encrypted session data to your Anakin workspace as a named browser profile (e.g. linkedin)
• Pairs securely with your Anakin account via a one-time ticket (never stores your Clerk password in the extension)

Does not:

• Give agents direct access to your local browser or screen
• Run automation on your computer — agents still use Cloudflare Browser Run on Anakin servers with the saved session cookies

---

Setup (5 steps)

1. Install Anakin Browser Profiles (Chrome Web Store or sideload from extensions/anakin-browser/dist)

2. Open Settings → Integrations → Connect extension on tryanakin.app (or ?extension_auth=1)

3. Sign in to Anakin if prompted — you should see "Browser extension connected"

4. Log in to the target site in normal Chrome (e.g. LinkedIn)

5. Extension popup → confirm profile name → Save to Anakin

---

How agents use profiles

Agents call listBrowserProfiles to see saved profiles, then useBrowser or captureWebPage with profileName (e.g. linkedin) for logged-in automation.

| Method | Best for |

|--------|----------|

| Extension | LinkedIn, Google, Microsoft, banks — real browser fingerprint |

| Guided login | Simple sites that tolerate remote automation |

| Cookie JSON import | CI, one-off imports |

For LinkedIn profile access, the extension + browser profile path is recommended over guided login or OAuth API posting alone.

---

Troubleshooting

• Extension not detected: Reload extension on chrome://extensions; refresh Settings → Integrations
• Sign-in failed: Ensure you are logged into tryanakin.app before connecting
• No cookies saved: Grant site permission when the extension prompts; confirm you are logged in on an HTTPS tab

See also: Browser Use Guide in workspace docs.