89b3eaf5da
Key improvements: - twitter-cookies now accepts BOTH formats: 1. Full cookie header string from Cookie-Editor export 2. Two separate values (auth_token ct0) Automatically detects which format was pasted. - New docs/cookie-export.md guide for server users Recommends Cookie-Editor Chrome extension (one-click export) Fallback: manual F12 → Network → Cookie header - Install guide now has two clear paths: Path A (local): --from-browser chrome (one command, all cookies) Path B (server): Cookie-Editor extension export (30 sec per site) - Better error messages with accepted format examples
1.4 KiB
1.4 KiB
Cookie Export Guide — For Server Users
Your Agent is on a server and can't access your browser directly. Here's how to export cookies from your local computer — fastest method first.
Method 1: Cookie-Editor Extension (Recommended — 30 seconds per site)
-
Install Cookie-Editor for Chrome: https://chromewebstore.google.com/detail/cookie-editor/hlkenndednhfkekhgcdicdfddnkalmdm (Also available for Firefox, Edge)
-
Go to the website (e.g. https://x.com) and make sure you're logged in
-
Click the Cookie-Editor icon in your toolbar
-
Click Export → Header String
-
Paste the result to your Agent
That's it! Your Agent will run:
agent-eyes configure twitter-cookies <your_pasted_string>
Sites to export:
| Site | URL to visit | What to tell Agent |
|---|---|---|
| Twitter/X | https://x.com | "Here are my Twitter cookies: [paste]" |
| XiaoHongShu | https://www.xiaohongshu.com | "Here are my XHS cookies: [paste]" |
| Bilibili | https://www.bilibili.com | "Here are my Bilibili cookies: [paste]" |
Method 2: Manual (No extension needed)
- Open the site in Chrome, make sure you're logged in
- Press F12 (or right-click → Inspect)
- Click the Network tab
- Refresh the page (F5)
- Click any request in the list
- In the right panel, scroll to Request Headers
- Find the line starting with
Cookie: - Copy the entire value after
Cookie: - Paste to your Agent