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

Polish public-facing docs
All checks were successful
CI / test (3.10) (push) Successful in 1m9s
Details
CI / test (3.11) (push) Successful in 1m8s
Details
CI / test (3.12) (push) Successful in 27s
Details

Browse Source
This commit is contained in:
Luna
2026-05-08 17:11:10 +02:00
parent 9b789e24cb
commit 7956158d9b
2 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -6,7 +6,7 @@
A terminal-first CLI for Twitter/X: read timelines, bookmarks, and user profiles without API keys. A terminal-first CLI for Twitter/X: read timelines, bookmarks, and user profiles without API keys.
> **Fork note:** This repository is a private fork of [`public-clis/twitter-cli`](https://github.com/public-clis/twitter-cli) with extra cookies.txt auth support, multi-account usage via per-command `TWITTER_COOKIE_FILE=...`, and a repo-local OpenClaw skill. > **Fork note:** This repository is a fork of [`public-clis/twitter-cli`](https://github.com/public-clis/twitter-cli) with added Netscape `cookies.txt` auth support, multi-account usage via per-command `TWITTER_COOKIE_FILE=...`, and a repo-local OpenClaw skill.
## More Tools ## More Tools
@@ -197,9 +197,9 @@ This keeps the CLI multi-account friendly: no cookie path is pinned in config, s
Examples: Examples:
```bash ```bash
TWITTER_COOKIE_FILE=/root/twitter_cookies/space.txt twitter whoami --json TWITTER_COOKIE_FILE=/path/to/account-a.cookies.txt twitter whoami --json
TWITTER_COOKIE_FILE=/root/twitter_cookies/betternews.txt twitter whoami --json TWITTER_COOKIE_FILE=/path/to/account-b.cookies.txt twitter whoami --json
TWITTER_COOKIE_FILE=/root/twitter_cookies/bundesamt.txt twitter whoami --json TWITTER_COOKIE_FILE=/path/to/account-c.cookies.txt twitter tweet 1234567890 --json
``` ```
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. 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.

10
skill/SKILL.md
View File

@@ -5,7 +5,7 @@ description: Use the local twitter-cli fork with cookies.txt authentication for
# Twitter CLI (cookie-file, multi-account) # Twitter CLI (cookie-file, multi-account)
Use the local fork in `/root/projects/twitter-cli`. Use this repository checkout.
## Rules ## Rules
@@ -17,7 +17,7 @@ Use the local fork in `/root/projects/twitter-cli`.
## Basic pattern ## Basic pattern
```bash ```bash
cd /root/projects/twitter-cli cd <repo-checkout>
. .venv/bin/activate . .venv/bin/activate
TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter whoami --json TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter whoami --json
``` ```
@@ -25,13 +25,13 @@ TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter whoami --json
## Examples ## Examples
```bash ```bash
TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter tweet 2051661976330269086 --json TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter tweet 1234567890 --json
TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter user Space_Banane --json TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter user someuser --json
TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter post "hello world" TWITTER_COOKIE_FILE=/path/to/account.cookies.txt twitter post "hello world"
``` ```
## Notes ## Notes
- The fork already supports Netscape-format `cookies.txt` via `TWITTER_COOKIE_FILE`. - The fork already supports Netscape-format `cookies.txt` via `TWITTER_COOKIE_FILE`.
- Repo: `https://gitea.reversed.dev/luna/twitter-cli-cookiefile` - Repo-local skill path: `skill/SKILL.md`
- If auth fails, verify the cookie file still contains fresh `auth_token` and `ct0` values for the target account. - If auth fails, verify the cookie file still contains fresh `auth_token` and `ct0` values for the target account.