Openclaw X Guide: skip the official API and let AI
watch your Twitter / X signals for you

First install the `bird-twitter` skill from ClawHub, then install the `bird CLI` itself. If you are on Windows or in a standard Node.js environment, make sure Node.js is installed and run `npm install -g @steipete/bird`. If you are on macOS and already use Homebrew, you can run `brew install steipete/tap/bird` instead. These are alternative install paths, so do not run both. Windows users should ideally open PowerShell or Terminal in Administrator mode first, otherwise global installs often fail with permission errors.

# 1) Install the Bird Twitter skill from ClawHub
npx clawhub@latest install bird-twitter

# 2) Install the bird CLI itself
# Windows or general Node.js environments: make sure Node.js is installed, then run:
npm install -g @steipete/bird

# macOS: if you already use Homebrew, you can run:
brew install steipete/tap/bird

# Note: only choose one bird CLI install method based on your OS. Do not run both.

At this stage, the cleanest path is still the direct terminal command. Install the underlying toolchain first, then let Openclaw build on top of a setup that already works.

The most reliable path is to open browser developer tools yourself and grab `auth_token` and `ct0` from the X cookies. This is especially true on Windows, where browser cookie storage is often protected in ways that make direct AI extraction unreliable.

# After finding your auth_token and ct0, set them as environment variables in your terminal:

# macOS / Linux:
export AUTH_TOKEN='your_auth_token'
export CT0='your_ct0'

# Windows (PowerShell):
$env:AUTH_TOKEN="your_auth_token"
$env:CT0="your_ct0"

# Verify if the underlying engine is connected:
bird --auth-token "$AUTH_TOKEN" --ct0 "$CT0" whoami

Once you have those two values, put them into environment variables and move to the validation step. That lets you skip the official API and avoid a heavier OAuth setup.

Recommended

Method A: Let bird read browser cookies automatically

If your local browser environment is fairly standard and you are already signed into X, this is usually the smoothest route. bird can reuse the session from that same machine.

• Safari or native Chrome are usually the cleanest starting points.
• This feels closest to “I am already logged in, now let AI help me read the signal.”
• If you do not want to touch `auth_token` and `ct0`, try this path first.

More reliable / server-friendly

Method B: Manually capture auth_token and ct0

If you are on Arc, Brave, a remote server, or a Windows setup that keeps failing to expose cookies cleanly, go straight to the browser developer tools and grab `auth_token` and `ct0` yourself. It is usually faster.

1. Sign into x.com normally in your browser.
2. Press F12 to open Developer Tools and switch to the Application or Storage tab.
3. Open Cookies and select `https://x.com`.
4. Find `auth_token` and `ct0`, then configure them in your terminal using the environment-variable examples above.

# After finding your auth_token and ct0, set them as environment variables in your terminal:

# macOS / Linux:
export AUTH_TOKEN='your_auth_token'
export CT0='your_ct0'

# Windows (PowerShell):
$env:AUTH_TOKEN="your_auth_token"
$env:CT0="your_ct0"

# Verify if the underlying engine is connected:
bird --auth-token "$AUTH_TOKEN" --ct0 "$CT0" whoami

Do not paste auth_token or ct0 into chat logs, support tickets, screenshots, demos, or public docs. They are effectively the keys to your signed-in session.

Don't jump straight into searching a massive timeline. First, verify if the AI can correctly identify "who you are". You can ask directly in the Openclaw Web UI chat, or run the following command in your terminal: