For people who run many X accounts
Auto follow for X (Twitter), one real browser per account
flottra auto follow works from a list you paste: the handles each X account should follow. The scheduler hands them out one at a time; the desktop app on your own computer opens each profile in that account's own Chrome, through its own proxy, clicks Follow and confirms it. New accounts are held back by the warming gate.
Updated
What it does
A follow list per account, worked through one at a time
Search for a Twitter auto follow tool and page one is hosted services that sign in to your accounts from their own servers. flottra follows from your own computer instead, and only the handles you gave it.
You paste the handles an account should follow on that account's page in the panel: separated by spaces, commas or new lines, duplicates dropped, up to 500 in one paste. That list is the whole of the targeting. flottra does not choose targets for you on the hosted beta, does not work through a competitor's follower list, and does not sell followers.
From there the loop is mechanical and slow. Every five minutes the hosted scheduler looks at each active account that has a proxy and creates one follow task for its next target, never more than three open tasks per account. The desktop app on your computer picks the task up, opens the profile in that account's own Chrome profile through that account's own proxy, scrolls the page the way a person would, clicks Follow, and waits for the button to read Following before it reports success. The target is then marked followed, and the row appears on the Tasks page with its result.
- 10:22@jpegvaultfollow @nft_floor_watchqueued
- 10:17@wifhat_maxifollow @memecoin_radarrunning
- 10:12@degenrouterfollow @l2_bridge_statsdone
- 09:58@degenrouterfollow @perp_desk, Following not confirmedfailed
Four follow tasks the way the Tasks page lists them: one queued, one running, one done, and one that failed because the button never read Following. Example rows, not a screenshot.
Nothing runs on flottra's servers. The panel keeps the list and the schedule; the only browser involved is the one the app opens on your machine, and it opens through your proxy or not at all. That is the structural difference from most of the tools on page one for this search, which sign in to your accounts from the vendor's address space, next to every other customer's accounts. The shared address problem is covered in why X accounts get suspended.
How it works
How auto follow runs, step by step
Paste, hand out, follow. The first two happen in the panel; the third happens on your computer, in a real Chrome window.
- 01
Paste the targets
Open the account on the Accounts page and choose Add follow targets. Paste the handles; anything already queued for that account is skipped. The account needs a proxy assigned and the app paired on a computer, or nothing happens. - 02
The scheduler hands them out
Every five minutes the hosted scheduler creates one follow task for the next target of each active account with a proxy, and skips any account that already has three open tasks. It is a query on a timer: it never opens a browser. - 03
The app follows from the account's own browser
The desktop app opens the profile in that account's own persistent Chrome profile, through its proxy, browses, clicks Follow and confirms Following. One task at a time per computer, with human-like delays inside each task. If the app is closed or the laptop is asleep, tasks wait as pending and run when it is back.
- 1
- follow per account every five minutes, at most
- 3
- open tasks per account, at most
- 500
- handles per paste, deduplicated
- 1
- proxy per account, or the browser does not open
Two things a tester should know. An account added with its auth_token cookie starts active and joins the loop at once. An account added with a password only starts as warming and joins after the app has signed it in, which happens on the first task it runs for that account: the Test task on the Tasks page does it for the first account, and the MCP server can schedule a session check for any account. A follow that fails, because the profile did not load through the proxy or the button never changed, is kept with its reason on the Tasks page, and the target stays queued, so the scheduler offers it again on a later pass.
Pacing
New accounts are held back, every account is paced
The fastest this loop can go is one follow per account every five minutes. A new account goes much slower than that.
The warming gate decides what an account may do by its age. For its first three days an account may not follow at all: the gate allows likes, profile views and scrolling, three actions a day. Days four to seven allow follows, six actions a day in all. Days eight to fourteen allow twelve. After fourteen days the gate is open and the five minute cadence is the only brake left. The phases are editable per workspace as JSON on the Warming page, and the same gate applies to what pods and the MCP server schedule. Account warming explains the phases and what counts as an action.
Pods, on the Pro and Team plans, are the other way follow tasks are created. A pod is three to six of your own accounts pointed at one handle. The members are shuffled and staggered: the first fires after 20 seconds to 2 minutes, each next one after a random gap of 1 to 4 minutes, and a member that is suspended, locked, retired or refused by the warming gate is skipped. The stagger keeps a pod from landing six follows on one profile in the same second. It does not make six accounts following the same handle invisible; X follow bots and follow limits explains why the same list across accounts is a signal on its own.
Two honest limits of the pacing as it stands. Hourly caps exist per account, six follows an hour among them, but on the hosted beta they are enforced only when tasks are scheduled through the MCP server; the follow loop and pods rely on the cadence and the gate. And there are no quiet hours: the loop runs whenever the app is open, at whatever hour that is on your computer. If an account should rest, pause it through the MCP server or quit the app from its tray icon.
Beta status
What runs today, and what is next
So a tester knows exactly what to expect. Both lists are true to the code on 21 September 2026, and this page changes the day either one does.
If you searched for a Twitter growth tool or a follow unfollow tool, read the second list first: the unfollow half is not on the hosted beta.
What runs today
- Follow targets per account: paste up to 500 handles at a time, deduplicated against what is already queued.
- The hosted scheduler: one follow task per active account with a proxy every five minutes, at most three open tasks per account, with the warming gate holding new accounts back.
- The desktop app, Windows today: one persistent Chrome profile per account, that account's own proxy, one task at a time, human-like delays inside each task, and Following confirmed before a target is marked followed.
- Pods on Pro and Team: three to six of your accounts on one handle, shuffled and staggered.
- The Tasks page: every follow with its target, its state and, when it failed, the reason. Failed tasks are also filed on the Diagnostics page.
- The MCP server: an agent can seed the same targets and schedule the same follow tasks, with the hourly caps and the warming gate applied.
Next, not on the hosted beta yet
- Follow back check and unfollow after a cooldown. The routine exists, with a check after 72 hours and a 30 day cooldown as defaults, but it does not run for customers yet, so nothing is unfollowed.
- Automatic target discovery, such as following the followers of a seed account you name. Today every target is one you pasted.
- Bulk unfollow and pruning non-followers. If you searched for a mass unfollow tool, flottra is not one today.
This page and account warming describe what the hosted beta runs on its own today; the features overview lists everything, including what is still being switched on.
What X says
What X says about following, quoted
X's automation development rules, updated April 2026, apply to every follow tool, this one included. Quoted, with the date they were read.
You "may not follow or unfollow X accounts in a bulk, aggressive, or indiscriminate manner"; you "may not like posts or hide replies in an automated manner"; unsolicited automated direct messages are not permitted; and scripting the X website "may result in the permanent suspension of your account".
flottra is browser automation, and it automates follows. It does not claim those rules do not apply to it, and it does not claim to comply with them. What it does is pace everything and refuse bursts: one follow per account every five minutes at most, one task at a time on your computer, a warming gate that holds new accounts back, and one proxy per account. That reduces the rate at which accounts are locked or suspended. It does not make it zero, and nobody can.
The numbers X does publish, 400 follows a day and 5,000 following before a ratio applies, are technical limits, not the behavioural line. X follow bots and follow limits takes them apart and explains why follow and unfollow churn is what gets accounts actioned; X rate limits covers the other limits an account runs into; and why X accounts get suspended covers the signals that matter more than any total.
Compared
A typical auto follow tool, and this one
Most of the tools on page one for this search run from the vendor's servers. The differences below are structural, not a ranking, and no competitor prices were checked.
| A typical auto follow tool | flottra | |
|---|---|---|
| Where the browser runs | On the vendor's servers | On your own computer, one persistent Chrome profile per account |
| Whose IP | The vendor's, shared with its other customers | Your own proxy per account: residential, mobile or ISP; the browser does not open without one |
| How targets are chosen | A keyword, a hashtag or another account's follower list | The handles you paste per account, up to 500 a paste; automatic discovery is not on the hosted beta |
| Pacing | Usually a daily number you set | One follow per account every five minutes at most, one task at a time, and the warming gate for new accounts |
| When X changes its design | You wait for the vendor | A failed task shows its reason on the Tasks page; the fix ships as an app update, and the app checks for updates on start and every six hours |
| Price of entry | Varies by vendor | Free plan, two accounts, no card |
None of this is a promise about outcomes. It is where the browser sits, whose address it uses, who chose the targets, and how fast it is allowed to go. If those are the things you have been fighting with a hosted tool, the free plan covers two accounts and needs no card.
Questions
Questions people ask about this
- Can Twitter automatically follow?
- X offers no auto follow setting. It shows suggestions, but every follow is a click, and X's automation rules say tools may not follow accounts in a bulk, aggressive or indiscriminate manner. What people searching this usually want is a tool that clicks Follow for them. flottra does that from your own computer: you paste the handles an account should follow and the desktop app follows them one at a time, in that account's own browser, through its own proxy.
- How do I stop automatic following?
- If a third party tool has your login, revoke it: remove it from the connected apps in X settings if it used the API, or change the password and log out of other sessions if it drove a browser. In flottra the loop only follows the list you pasted and stops when that list is empty. To stop sooner, pause the account through the MCP server, which cancels its queued tasks, or quit the desktop app from its tray icon so nothing runs on your computer.
- How to bot Twitter followers?
- flottra will not do that. It follows a list of handles you choose, from your own computer, and it does not sell followers, likes or accounts. Tools that promise followers are the apps X's rules prohibit by name, and following or unfollowing accounts in bulk to make people follow back is what the same rules call aggressive and indiscriminate. What flottra automates instead is slow: a short list of related accounts per account, followed at a human pace.
- How many follows a day is safe on X?
- Nobody outside X knows. X publishes 400 follows a day as a technical limit and, on the same page, prohibits aggressive following without giving a number. What flottra enforces is shape: a new account gets no follows for its first three days, then 6 actions a day, then 12, and the gate opens after 14 days; at any age the scheduler creates at most one follow per account every five minutes. Treat that as a ceiling, and keep each list related to the account.
- Does flottra unfollow people who do not follow back?
- Not on the hosted beta. The follow back routine exists in the product, with a check after 72 hours and a 30 day cooldown before the same account can be followed again as defaults, but the part of the system that runs it is not deployed for customers yet, so nothing is unfollowed and nothing is pruned. Every follow is recorded per target with its date, so the routine has what it needs when it switches on. This page will say so the day it runs.
- Do I need a proxy for every account?
- Yes. The desktop app refuses to open a browser for an account that has no proxy, so an account without one never follows anyone. Residential, mobile and ISP proxies are accepted; data centre proxies are refused when you add them. One proxy per account is the rule the product recommends and the MCP prompts enforce. flottra does not sell proxies; you bring your own and paste them in bulk in the common formats.
- Will X ban my account for auto following?
- It can. X's automation rules say you may not follow or unfollow accounts in a bulk, aggressive or indiscriminate manner, and that scripting the X website may result in permanent suspension. flottra is browser automation and does not claim to comply. What it does is refuse the shape X names: at most one follow per account every five minutes, a warming gate for new accounts, one proxy per account. That lowers the rate at which accounts are locked or suspended; it does not make it zero, and nobody can.