Use This X + OpenClaw Setup To Write Viral Tweets

You need an OpenClaw agent before you can connect X to it. You can run OpenClaw on your own computer, on another machine, or on a hosted server.

For most readers, Hostinger OpenClaw is the simplest path because it gives you an always-on agent without putting the setup on your personal computer.

Pro tip: You can use a Hermes Agent too. The X setup is the same, but this guide uses OpenClaw as the default example.

If you use Hostinger, make sure you can reach the VPS terminal. You will need that later when xurl gives you a login link for the X OAuth flow.

Open the X Developer Console, create a new app, and save the keys when X shows them.

Do not overthink the word "app" here. You are not building a web app or mobile app for customers. The app is just the wrapper that lets your bot connect to X through the API.

Set the app permissions based on what you want OpenClaw to do:

• Use Read if you only want research.
• Use Read and Write if you want OpenClaw to draft and post tweets from the account.
• Do not enable Direct Message access unless you actually need it.

For the app type, choose:

Web App, Automated App or Bot

That is the option made for this kind of bot connection.

In the app auth settings, add this callback URL:

http://localhost:8080/callback

Then set the website URL to:

https://x.com

This callback URL matters because xurl runs the auth flow locally on the machine where the agent is installed. In the recording, the confusing part was not the X app setup. It was remembering that the OAuth login has to happen from the machine where OpenClaw or Hermes is actually running.

Before installing the X skill, ask OpenClaw to update itself. Then have it install xurl.

Use this prompt:

Update yourself, install the xurl X skill, and tell me what I need to configure locally before you can use X.

OpenClaw should tell you what it needs next, usually the app name, client ID, client secret, and X handle.

Do not paste secrets casually into an agent chat. Save the credentials securely and enter them through the local setup flow where xurl expects them.

This is the part that makes the setup feel more annoying than it should.

The OAuth link needs to be generated from the machine where OpenClaw runs. If OpenClaw is on your laptop, run the xurl auth flow there. If OpenClaw is on Hostinger, open:

VPS > Manage > Terminal

Then run the xurl auth flow from that terminal. It should give you a login link. Click that link, log into X, authorize the app, and finish the setup.

This means you do not need a full desktop GUI on the VPS. You just need terminal access and the link that xurl gives you.

Once auth succeeds, test the connection with a tiny approved action. If you want the safest first test, ask OpenClaw to read account or timeline context before you ask it to post.

The point is not just "OpenClaw can tweet now." The useful part is giving OpenClaw repeatable X jobs.

Start with a simple daily research workflow:

Every day at 7am, review my saved X list or bookmarks.

Pick one or two posts that are most useful for:
- new AI use cases
- OpenClaw upgrade ideas
- reply opportunities
- tweet ideas for my account

For each one, explain why it matters, summarize the core idea, and draft either:
- three possible replies
- one standalone tweet
- one short thread outline

Do not post anything until I approve it.

You can also use the connection for more focused tasks:

Look at the accounts I follow in [TOPIC].
Find five patterns people are discussing this week.
Turn those patterns into tweet ideas for [AUDIENCE].

Or:

Review my X bookmarks from the last [LOOKBACK_DAYS] days.
Group them by theme.
Pick the strongest idea and draft a post in my normal tone.

The safest setup is to let OpenClaw research, draft, and package ideas first. Once you trust the workflow, you can decide when posting should be manual, approval-based, or fully automated.