Win-CodexBar can automatically extract browser cookies for providers that use web authentication (Claude, Cursor, Kimi, etc.).
| Browser | Encryption | Status |
|---|---|---|
| Chrome | DPAPI + AES-256-GCM | ✅ Automatic |
| Edge | DPAPI + AES-256-GCM | ✅ Automatic |
| Brave | DPAPI + AES-256-GCM | ✅ Automatic |
| Firefox | Unencrypted SQLite | ✅ Automatic |
- CodexBar reads the browser's cookie database from its standard location
- For Chromium-based browsers, cookies are encrypted with Windows DPAPI — CodexBar decrypts them using the current user's credentials
- Only cookies for enabled providers are extracted (e.g.,
claude.ai,cursor.com) - Cookies are stored in-memory and refreshed on each provider poll
- Open Settings → Providers tab
- Select the provider you want to configure
- In the provider detail pane, find the Browser Cookies section
- Choose your browser from the dropdown and click Import
If automatic extraction fails (e.g., browser is locked, profile is encrypted, or running in WSL):
- Open your browser and navigate to the provider's website (e.g.,
claude.ai) - Open DevTools (F12) → Network tab
- Refresh the page and click any request to the provider
- Copy the
Cookieheader value from Request Headers - In CodexBar Settings → provider detail → Browser Cookies, paste the value
- "Cookie decryption failed": Close the browser and retry — some browsers lock the cookie database while running
- Empty cookies: Make sure you're logged into the provider's web interface in that browser
- WSL: Chromium DPAPI cookies cannot be decrypted from WSL. Use manual cookies or CLI-based auth instead