Any Working X (Twitter) Bots?

Lifeisnotgood

Power Member
Joined
Jun 27, 2016
Messages
531
Reaction score
381
Hi,
I've tried to find this info, but I didn´t find anything.
Does any X or Twitter Bot work anymore?

The bot should be very basic.
I'm fine with it liking certain posts 1-5 times a day, when I just open the software or browser. If a certain "word" appears in a post.

Thank you very much!
 
Okey, I got it myself!
So I made a Custom extension bot, that works at X.
I don't want to give any download link to this, because you can vibe code this yourself using https://claude.ai/
You can add your own features to it if you want!
I just needed that like feature thing only, because I don't want to check the feed, because it takes time from other things.
And I don´t get anything done.

Here is the prompt I used so you get the same extension Bot:

Build a Chrome extension called "X Keyword Liker" that automatically likes posts on X (Twitter) based on a keyword search. Here's exactly how it should work:


Core behaviour:



  • The user types a keyword into the popup UI and presses a Play button
  • When Play is pressed, the extension opens a new tab with https://x.com/search?q=<keyword>&f=live
  • It then scans visible posts on that page every ~8 seconds, and clicks the like button on any post whose text contains the keyword
  • If no matching post is found, it scrolls down to load more posts
  • Already-liked posts (where the like button has data-testid="unlike") are skipped
  • The session runs for exactly 5 minutes, then stops automatically
  • The user can also stop the session early with a Stop button
  • Maximum 5 likes per day (resets at midnight). The daily count persists in chrome.storage.local
  • When the session ends, the search tab is closed automatically

UI (popup.html + popup.js):


  • Dark terminal/cyberpunk aesthetic using JetBrains Mono and Syne fonts
  • Keyword text input field (disabled during active session)
  • Play/Stop button that toggles state
  • Live countdown timer showing time remaining in the session
  • A shrinking progress bar for the session duration
  • 5 heart "pip" icons that fill up as daily likes are consumed
  • Quota counter in the header showing how many likes remain today
  • Animated status dot (pulsing green when running, grey when idle)
  • Activity log showing timestamped entries for every like, scroll, session start/stop
  • Error banner for messages like "daily limit reached" or "no keyword entered"

Files needed:


  • manifest.json — Manifest V3, permissions: storage, scripting, tabs, activeTab, host permissions for x.com and twitter.com
  • background.js — Service worker managing session state, tab lifecycle, the like-tick loop, and daily count tracking in chrome.storage.local
  • content.js — Minimal sentinel script injected into X pages
  • popup.html + popup.js — The UI described above
  • icons/icon48.png and icons/icon128.png

Architecture:


  • Session state lives in the background service worker (survives popup close)
  • The background worker uses chrome.scripting.executeScript to inject a findAndLike() function into the X tab
  • findAndLike() queries article elements, checks [data-testid="tweetText"] for the keyword, clicks [data-testid="like"], and returns a result object { liked, postId, snippet } or { scrolled: true }
  • The popup communicates with the background via chrome.runtime.sendMessage with actions: getState, startSession, stopSession
  • The background pushes state updates to the popup via chrome.runtime.sendMessage({ action: "stateUpdate" })
  • A like-tick runs every 8 seconds via setTimeout chain, checks daily limit, injects the script, increments count on success
 
I made fully custom bot for one of my clients for his Crypto marketing Agency, and all I can say is that whatever public software you buy on the market can't beat any custom one on the long run. Never go with APIs, never go with selenium or playwright, never go with datacentar proxies and learn how to bypass cloudflare checks (hardest).

Your extension is okay but you will leavea lot of traces and eventually your acc will get banned.
 
Most public x bots get flagged instantly now because of their strict api pricing and anti-spam measures. You're better off using a browser extension or just manual engagement to keep your account safe from a shadowban
 
I made fully custom bot for one of my clients for his Crypto marketing Agency, and all I can say is that whatever public software you buy on the market can't beat any custom one on the long run. Never go with APIs, never go with selenium or playwright, never go with datacentar proxies and learn how to bypass cloudflare checks (hardest).

Your extension is okay but you will leavea lot of traces and eventually your acc will get banned.
Thanks for the tip!
Yeah I will use the same IP all the time. Same browser. Same cookies.
Damn, even if this basic bot will give ban :(

Maybe I just have to manually search the things what I like then.
 
For 1-5 likes/day the extension is fine. If X starts blocking it, the cleanest fallback is Playwright with the stealth plugin and a dedicated Chrome profile — much harder to fingerprint than extensions since it behaves like a real browser session. Add randomized delays between actions (8-15 sec) and never run it in bursts.
 
Youll have to be careful so it doesn't get flagged
Okey, I got it myself!
So I made a Custom extension bot, that works at X.
I don't want to give any download link to this, because you can vibe code this yourself using https://claude.ai/
You can add your own features to it if you want!
I just needed that like feature thing only, because I don't want to check the feed, because it takes time from other things.
And I don´t get anything done.

Here is the prompt I used so you get the same extension Bot:

Build a Chrome extension called "X Keyword Liker" that automatically likes posts on X (Twitter) based on a keyword search. Here's exactly how it should work:


Core behaviour:



  • The user types a keyword into the popup UI and presses a Play button
  • When Play is pressed, the extension opens a new tab with https://x.com/search?q=<keyword>&f=live
  • It then scans visible posts on that page every ~8 seconds, and clicks the like button on any post whose text contains the keyword
  • If no matching post is found, it scrolls down to load more posts
  • Already-liked posts (where the like button has data-testid="unlike") are skipped
  • The session runs for exactly 5 minutes, then stops automatically
  • The user can also stop the session early with a Stop button
  • Maximum 5 likes per day (resets at midnight). The daily count persists in chrome.storage.local
  • When the session ends, the search tab is closed automatically

UI (popup.html + popup.js):


  • Dark terminal/cyberpunk aesthetic using JetBrains Mono and Syne fonts
  • Keyword text input field (disabled during active session)
  • Play/Stop button that toggles state
  • Live countdown timer showing time remaining in the session
  • A shrinking progress bar for the session duration
  • 5 heart "pip" icons that fill up as daily likes are consumed
  • Quota counter in the header showing how many likes remain today
  • Animated status dot (pulsing green when running, grey when idle)
  • Activity log showing timestamped entries for every like, scroll, session start/stop
  • Error banner for messages like "daily limit reached" or "no keyword entered"

Files needed:


  • manifest.json — Manifest V3, permissions: storage, scripting, tabs, activeTab, host permissions for x.com and twitter.com
  • background.js — Service worker managing session state, tab lifecycle, the like-tick loop, and daily count tracking in chrome.storage.local
  • content.js — Minimal sentinel script injected into X pages
  • popup.html + popup.js — The UI described above
  • icons/icon48.png and icons/icon128.png

Architecture:


  • Session state lives in the background service worker (survives popup close)
  • The background worker uses chrome.scripting.executeScript to inject a findAndLike() function into the X tab
  • findAndLike() queries article elements, checks [data-testid="tweetText"] for the keyword, clicks [data-testid="like"], and returns a result object { liked, postId, snippet } or { scrolled: true }
  • The popup communicates with the background via chrome.runtime.sendMessage with actions: getState, startSession, stopSession
  • The background pushes state updates to the popup via chrome.runtime.sendMessage({ action: "stateUpdate" })
  • A like-tick runs every 8 seconds via setTimeout chain, checks daily limit, injects the script, increments count on success
 
Most of those old-school bots are dead since elon took over and locked down the api. You’re way better off just using a simple automation script or browser extension to save yourself from getting your account banned
 
X automation still works perfectly as long as you operate within the limits and with properly warmed accounts. Most public tools fail because they use API posting and bad IPs.

Your extension approach is better than most public bots, but there are traces. X fingerprints extension behavior differently than natural browsing. The DOM queries, timing patterns, and lack of proper mouse movement give it away.

For 1-5 likes/day you'll probably be fine, but if you want something that lasts: mobile emulation beats browser extensions. Tools like Playwright with stealth work but still leave fingerprints compared to proper device emulation.

The key isn't the tool, it's the behavior patterns. Real users don't search keywords and like posts in perfect intervals. They scroll randomly, pause, switch tabs, have varying session lengths. Your extension does none of that.

Don't use datacenter proxies or VPNs. Residential minimum, mobile preferred if you want to scale beyond basic liking
 
Thanks for all the good tips!
I think I have to manually like some posts. So then it´s safe.
Of course, I have to give maybe 5 minutes to this each day.
 
Most basic automation tools get flagged instantly. I'd skip the bots and just set up manual alerts because it's not worth risking a permanent account ban for such a small task
 
yeah there are ready-to-use templates or you can build your own flows, both options exist

1776074015741.png
 
Yes, for that kind of light action, ready-made RPA templates are usually enough. If you already tried building your own bot with Claude, Custom RPA is a better fit when you want something more stable or easier to use across multiple accounts.

RPA.jpg
 
Twitter (X) has clamped down hard on the type of automation you're describing. If a script or browser extension tries to "auto-like" based on a keyword, the platform's advanced fingerprinting usually flags it within hours.
 
Back
Top