X reply bots: auto-comments, AI replies, and what gets caught
X’s automation rules permit automated replies to people who opted in, one per interaction, prohibit unsolicited replies at volume, name keyword-triggered replies as not permitted, and require written approval for AI reply bots. Accounts get caught for identical text across accounts, links, volume and replies at the wrong hour. Surviving means rare, specific replies that differ per account.
Most of what is sold as a comment bot for X is the one kind of automation the rules name as not permitted, and what the rules do permit is narrower than the people selling it say. This page separates the two, quotes the rule for each, and describes what a reply engine that keeps its accounts looks like.
X, still Twitter to most search engines, says more about replies on its automation page than about any other action, and the tools in the search results do not quote it, so the rule comes first.
What X's automation rules say about replies
The automation rules page (marked "Updated April 2026", checked 19 September 2026) has a section on replies and mentions. The lines that matter, quoted:
- Unsolicited volume is out. "Automating these actions to reach many users on an unsolicited basis is an abuse of the feature, and is not permitted. For example, sending automated replies to posts based on keyword searches alone is not permitted." That second sentence is the standard comment bot: pick a keyword, reply to everything that matches.
- Opted in means they came to you. Automated replies are permitted when the recipient has opted in, "for example by replying to a post from your account, or by sending you a Direct Message", and there is a way to opt out.
- One per interaction. "you only send one automated reply or mention per user interaction".
- A follow is not consent. "a user following your account is not on its own a sufficient indication of user intent to receive an automated response."
- AI reply bots need permission. "the deployment or operation of any AI reply bot requires prior written and explicit approval from X."
The ground rule
One more line from the same page applies to every reply tool on the market. Under "Don't": "Use non-API-based forms of automation, such as scripting the X website. The use of these techniques may result in the permanent suspension of your account." Every browser-driven tool is that kind; the automation guide covers the difference.
The two kinds of reply automation
Replying to people who engaged with you
Someone mentions your account, or replies to one of your posts, and a tool answers them. This is the kind the rules describe as opted in: the person came to you. The constraints still apply: one automated reply per interaction, a way to opt out, and text that answers what they said. A generic thanks under every mention is opted in on paper and still reads as a bot.
This is what flottra's engage_notifications task does: it replies to mentions and to replies on the account's own posts, and to nothing else. It is the duller half of reply automation and the half that produces conversations.
Replying to other people's posts
The tool finds posts by strangers and replies to them. This is what "comment bot" means in practice, and it is the kind the rules describe as unsolicited when it reaches many users. Whether a slower version that picks a few posts a day from a feed is the same thing is a judgement the rules leave to X, and X does not publish where the line sits.
flottra's feed_reply task does this second kind, at a low rate. The account browses its own feed, and explore or search, the way a reader does; scores the posts it sees (a default minimum of five likes, keyword exclusions you set, an optional language filter, at most eight scroll passes); and replies to one. The cap is five replies an hour per account, a ceiling rather than a target. It runs in a real Chrome window on your own computer through your own proxy, so the ground rule above applies to it as much as to anything else on this page. Whether that makes a difference to X is your judgement, not a claim this page makes.
| Reply type | What the rules say | Risk | What it needs to survive |
|---|---|---|---|
| A mention, or a reply on your own post | Described as opted in; one automated reply per interaction, with an opt-out | Low | Text that answers what was said, one reply, no follow-ups |
| A few posts chosen from your feed | Unsolicited if it reaches many users; the page does not say where many starts | Rises with volume | Low rate, chosen posts, original text per account, no link |
| Every post matching a keyword search | Not permitted, in those words | High | Nothing; this is the pattern the rule names |
| One template from several accounts | Content spam under the authenticity policy | High, and it links the accounts | Nothing |
| AI-written replies, of any type above | Requires prior written and explicit approval from X | That of the row it belongs to, plus whatever the text gets wrong | A persona per account, a sensitivity filter, a person reading the drafts early on |
Why templated replies get caught
The oldest comment bot design is ten pleasant sentences and a random pick. "Great post, thanks for sharing" from thirty accounts is the same text posted in bulk, and X's authenticity policy (dated April 2025) has a name for it: "Content Spam: You may not share or post content in a bulk, duplicative, irrelevant or unsolicited manner that disrupts people's experience." It also ties the thirty accounts together, the same problem the suspensions guide describes for posts.
What follows is usually reply deboosting rather than a suspension. X's enforcement options page lists "Downranking the post in replies" among the ways it limits the visibility of posts that break its policies. The reply is still there, behind "Show more replies", and your own session still shows it in place, so check from a logged-out browser: the shadowban guide has the test.
A reply that is meant to survive is all of the following:
- Specific to the post. It refers to something the post said. That alone rules out templates.
- Short. One or two sentences. A long reply from a young account reads as content marketing.
- Different per account. Not a synonym swap. Two personas say different things about the same post, or reply to different posts.
- Without a link. A link is the clearest tell that the reply exists to send traffic somewhere.
- Without a call to action. "Follow for more" is the reply that gets reported, and reports are the one signal you cannot pace away.
- Rarer than you want. The number of replies you would like to send is the number that gets the account actioned.
AI replies: what the model does well, and badly
A language model removes the template problem. Given the post and a persona, it writes something on-topic and different every time, and thirty personas do not produce the same sentence. In flottra the text for a feed reply comes from smart_reply: a model prompted with a per-account persona and a length bias toward short replies. The text is generated per account, not broadcast from several.
What the model does badly is the list every operator learns the hard way:
- Confident nonsense. It answers a question in the post with a fact it made up, under your account's name.
- Sarcasm taken literally. A post that says the airline did a great job gets a sincere reply about the airline's great job.
- Sensitive posts. A cheerful on-topic reply under a post about a death or a layoff is the one that gets screenshotted and reported. The automation rules recommend filtering sensitive language in handles and text; do it before the model sees the post.
- The wrong language. A persona that writes English under a post in another language is obviously a bot to everyone in that thread.
None of this is fixed by a better prompt. It is reduced by the choosing rather than the writing: a minimum of engagement on the post, a stop list, a topic filter, a language filter, and a bot that is allowed to skip when unsure. The bot that skips most of what it is shown is the better bot.
The honest default for a new account
A person reads the drafts before they go out for at least the first weeks, and corrects the stop list and the persona against what the model actually misread. None of this makes the bot permitted: the approval rule above is one sentence, and if you have not asked X for that approval, you do not have it.
How many replies a day
The limits page (checked 19 September 2026) publishes one reply figure: "Posts: 50 original posts and 200 replies per day for unverified accounts. The daily update limit is further broken down into smaller limits for semi-hourly intervals." It gives no per-hour reply figure and does not state a different number for Premium accounts. The rate limits guide has the full table.
Two hundred is the technical ceiling and says nothing about the safe one. An account that sends two hundred replies a day is a reply bot by shape whatever the text says. A cautious operator runs a handful of replies an hour at most, fewer on a new account, and none in its first days: the warming ramp in the suspensions guide sends no replies for the first three days and stays in single digits a day for the whole three weeks.
Shape matters as much as the total. Evenly spaced replies describe a scheduler; replies at 03:00 on the account's own clock describe a scheduler in another timezone; forty replies and no original posts describe an account that exists to reply. Waking hours, uneven gaps and a plausible ratio of replies to posts cost nothing and remove tells that good text cannot.
What a reply engine that survives looks like
Put together, in the order that matters:
- Reply to your mentions and to replies on your own posts first. It is the opted-in kind, and it is where conversations come from.
- If you reply to strangers' posts, choose them: a minimum of engagement, a topic filter, a language filter, a stop list, and a feed rather than a keyword search.
- Write, or generate, text that is specific to the post, short, unlinked, and different for every account.
- Cap replies at a handful an hour, ramp new accounts from zero, keep to waking hours on the account's own clock, and vary the gaps.
- Give each account its own proxy and a persistent browser profile before you give it a reply schedule. Content is only one of the four signals in the suspensions guide. See choosing proxies for X accounts.
An automated like puts you in someone's notifications once; a reply that says something puts you in a conversation. Automate the choosing and the pacing, keep a person close to the text, and accept that the rules on replies are the most detailed of any action you can automate.
Questions
- Are Twitter bots allowed?
- Some are. X’s automation rules assume automation goes through the API, and they list what is not allowed even then: automated likes, bulk or aggressive following, unsolicited automated replies and mentions, unsolicited automated direct messages, and AI reply bots without X’s prior written approval. Scripting the X website instead of using the API is on the ground-rules list of things not to do. A comment bot that replies to posts matching a keyword search is named on the page as not permitted, in those words.
- Does Tweetbot still work?
- No. Tweetbot was a third-party client, an app for using your own account, not a reply bot, and it shut down in early 2023 when third-party clients lost their API access. If you found it while searching for a reply bot, it was never that kind of tool. What exists in 2026 is the official apps, API-based tools that operate under X’s automation rules, and browser-driven tools that the same rules describe as scripting the website.
- Can X detect auto-replies?
- X does not publish its detection rules, so nobody outside X can say what it checks. What is observable is which patterns get replies downranked and accounts locked: the same or nearly the same text from several accounts, replies to keyword matches on unrelated posts, links in replies, a steady rate through the night, and a young account replying at full speed. Detection is of the pattern, not of the tool. A short, specific reply from a warmed account at a human pace does not carry those tells.
- Are AI reply bots allowed on X?
- Not without permission. The automation rules, updated April 2026, say that the deployment or operation of any AI reply bot requires prior written and explicit approval from X. A tool that writes replies with a language model does not come with that approval attached, and if you have not asked X for it, you do not have it. Even with approval, an AI-written reply still has to meet the other reply rules: sent to someone who opted in, one per interaction, with a way to opt out.
- How many replies a day is safe on X?
- The only official figure is 200 replies per day for unverified accounts, split into semi-hourly buckets, and it counts every device and app together. That is the technical ceiling, not the safe one, and X publishes no per-hour reply figure and no separate number for Premium. A cautious operator runs a handful of replies an hour at most, fewer on a new account and none in its first days, and keeps them to waking hours on the account’s own clock.
- Why are my replies hidden behind "show more replies"?
- Most often because X has limited their visibility. Its enforcement page lists downranking a post in replies among the ways it restricts posts that break its policies; people call this reply deboosting or a shadowban. For operators the usual causes are the same text repeated across accounts, links in replies, a high reply volume from a young account, and reports from the people replied to. Check from a logged-out browser or a second account, because your own session always shows your own replies in place.
- Can I automate replies to my own mentions?
- This is the one kind of automated reply the rules describe as opted in: someone who replied to a post from your account, or sent you a direct message, has interacted with you, and you may send one automated reply per interaction as long as there is a way to opt out. A follow on its own does not count as consent. The text still has to answer what the person said; the same thanks under every mention is technically opted in and still reads as a bot.