luna/twitter-cli-cookiefile
1
0
Fork 0
Code Issues Pull Requests Actions Releases Activity

Make cookie-file auth env-only for multi-account use
All checks were successful
CI / test (3.11) (push) Successful in 55s
Details
CI / test (3.10) (push) Successful in 1m58s
Details
CI / test (3.12) (push) Successful in 1m0s
Details

Browse Source
This commit is contained in:
Luna
2026-05-08 16:47:34 +02:00
parent bc82333e07
commit 4878d11b15
4 changed files with 8 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -174,22 +174,17 @@ twitter follow elonmusk --json
twitter-cli uses this auth priority:
1. **Environment variables**: `TWITTER_AUTH_TOKEN` + `TWITTER_CT0`
2. **Cookie file**: `TWITTER_COOKIE_FILE` or `config.yaml -> auth.cookieFile`
2. **Cookie file**: `TWITTER_COOKIE_FILE`
3. **Browser cookies** (recommended): auto-extract from Arc/Chrome/Edge/Firefox/Brave
If you already exported a Netscape-format `cookies.txt`, point the CLI at it:
```bash
export TWITTER_COOKIE_FILE=/path/to/cookies.txt
twitter whoami
TWITTER_COOKIE_FILE=/path/to/account-a.cookies.txt twitter whoami
TWITTER_COOKIE_FILE=/path/to/account-b.cookies.txt twitter whoami
```
Or in `config.yaml`:
```yaml
auth:
cookieFile: /path/to/cookies.txt
```
This keeps the CLI multi-account friendly: no cookie path is pinned in config, so each command can target a different account cleanly.
Browser extraction is recommended — it forwards ALL Twitter cookies (not just `auth_token` + `ct0`) and aligns request headers with your local runtime, which is closer to normal browser traffic than minimal cookie auth.