Slow by default
Warm up an X (Twitter) account: the ramp flottra runs
flottra warms up a new X account with a gate on its age: 3 actions a day for 3 days, likes only; 6 a day for 4 days, adding follows; 12 a day for 7 days, adding replies; no daily cap after 14 days. Anything past the phase is refused. The browser runs on your computer through your proxy.
Updated
Why it exists
Why new and bought accounts die in their first two weeks
A new X account that behaves like an old one is the easiest thing on the platform to spot. Warming is the habit of not doing that, and flottra applies it by default.
Most accounts lost in their first fortnight go for one of three reasons, none of them the tool. A burst: an account created this morning that follows sixty people before lunch. A shared address: five accounts signing in from one IP are related, and X can see it as plainly as you can. A fresh profile: a browser with no cookies and no history, arriving as if from a new machine on every visit. The long version, with what each one costs to fix, is in why X accounts get suspended.
Bought accounts carry all three before you touch them, plus a history you cannot see; aged X accounts explains why the creation date is the only thing you are actually buying. Accounts you make yourself start clean, and warming keeps them that way through the weeks when they are most fragile, which means doing very little, on purpose.
flottra does this with a gate rather than a routine. Every account in a workspace passes a check tied to how many days it has been there: three actions a day at first, more each phase, no daily cap after fourteen days. The browser runs on your own computer through the one proxy the account owns, so the address and the profile stay yours. Everything else on the features side of this site is slow for the same reason.
- 3
- actions a day in phase 1
- 14
- days to an open account
- 1
- proxy per account
- 0
- browsers on our servers
The ramp
Four phases in fourteen days
The default config, as every workspace starts with it. Age is counted from the day you added the account, and each phase permits a short list of kinds and a number of actions a day.
| Phase | Days | Actions a day | Allowed kinds |
|---|---|---|---|
| 1 | 1 to 3 | 3 | like, view profile, scroll, profile work |
| 2 | 4 to 7 | 6 | like, follow, view profile, scroll, browse, profile work |
| 3 | 8 to 14 | 12 | like, follow, reply, view profile, scroll, bookmark, profile work |
| 4 | 15 onward | no cap | everything |
Read the last column with one fact in mind: like, follow and reply are what a customer task runs on the hosted beta today. View profile, scroll, browse and bookmark are names the config carries for browse sessions that are not switched on yet, so in practice phase 1 means likes, phase 2 adds follows and phase 3 adds replies. Profile work (name, bio, avatar, header, username, password) is allowed from day one and spends none of the daily cap: setting up the profile is the first thing a person does with a new account.
Day five, six actions
Day five is phase 2. This account has done six things today, two likes and four follows, and six is the cap for the phase, so a seventh request is refused whichever path makes it. Phase 1 is stricter: three a day and no follows at all, because a day old account that follows anyone is the burst X looks for first. Phase 3 adds replies and doubles the cap to twelve. Phase 4 takes the daily cap away.
Where in the day the six land is not a setting. There are no quiet hours on the hosted beta and no per account clock, so the empty slots here are hours in which nothing was scheduled, not a rule. If you want an account silent overnight, schedule it that way; the gate counts, it does not keep time.
@wifhat_maxi · phase 2
day 5 · 6 of 6 actions
How it works
Add the account, give it a proxy, let the gate lift
Three steps, and the third one is mostly waiting.
- 01
Add the account
Username and password, and theauth_tokencookie if you have it. With a token the account starts active with a ready session. Without one it starts in warming, and the desktop app signs in with the password and the 2FA code the first time it runs a task for it. Either way the gate counts from the day you added it. - 02
Give it a proxy
One residential, mobile or ISP proxy, assigned to that account. The app refuses to open a browser without one, because the proxy address is what X sees as the account's location. Choosing proxies for X accounts covers what to buy. - 03
Let the gate lift
Paste follow targets, run pods on Pro or Team, or schedule through the MCP server. Everything is checked against the phase: three a day for three days, six for four, twelve for seven, no daily cap after fourteen. Anything past the phase is refused, not queued for later.
The config is JSON, edited on the Warming page of your workspace. Each phase has three fields: dailyMax, durationDays and allowed, the list of kinds the phase permits. The final phase carries -1 for both numbers: no cap, no end. Raise a cap, shorten a phase or add a kind to an earlier phase and the change applies to the next thing you schedule. One config covers every account in the workspace.
The same page lists the accounts whose status is still warming, with the phase stored on each, the actions counted today, the total, a trust score and when the account last acted. Two of those need a word. The gate takes the higher of the stored phase and the phase the account's age implies, so a stale 1 on a three week old account holds nothing back. And the trust score is written only by the operator's snapshot worker, which the hosted beta does not run, so it reads zero.
That matters for the graduation criteria in the default config: fourteen days, fifty actions and a trust score of 0.6. They describe a finished ramp, and the MCP server's warming status reports whether an account meets them. They do not move an account between phases; age does. Read them as a checklist, not a switch.
The gate
What the gate checks, exactly
One check, run before a task is written to the queue. It answers yes or no, and a no comes with a reason you can read.
- The kind. Is it on the phase's allowed list? A follow in phase 1 is not, and is refused with a message naming the phase and the list. Session checks are exempt; they touch nothing on X.
- The day's cap. For kinds that count as actions (likes, follows and replies, among those that run today), the gate adds the account's successful actions in the last 24 hours to the action tasks already queued. At the phase's daily maximum the next one is refused. A rolling 24 hours, not a calendar day, and queued work counts before it runs.
- The effective phase. The higher of the phase stored on the account and the phase its age implies, age being the days since it was added to the workspace. Raising the stored phase moves an account forward; lowering it does nothing, and the panel does not change it.
warming_status · @wifhat_maxi
- Stored phase
- 1
- Phase by age
- 2 (day 5)
- Effective phase
- 2
- Allowed
- like, follow, view_profile, scroll, browse_explore, profile work
- Daily cap
- 6
- Done in the last 24 h
- 4
- Queued
- 2
- Room today
- 0
The next action for this account is refused until one of the four done ones falls out of the rolling 24 hour window.
It applies to everything scheduled through pods, the Identity page and the MCP server, and to the hosted follow loop that auto follow describes, which asks the gate before each follow task. Pods and identity skip a refused member and run the rest. The MCP server returns a structured error with the phase, the cap, the last 24 hours and the queued count, so an agent can plan tomorrow instead of retrying.
Two consequences are worth knowing. The allowed list is the whole rule: a kind that is not on the phase's list is refused whatever the cap says, so if you remove profile_setup_bundle from a phase in the JSON, profile edits on accounts of that age are refused too. And the gate does not read status: an account added with an auth_token starts active, which is what the follow loop looks for, but a day old account is in phase 1 either way.
Scheduling through the MCP server also applies hourly caps per account, 12 likes, 6 follows and 5 replies by default, editable in Settings; they cover what an agent schedules, not the panel's own buttons. Nothing is counted at execution time: the desktop app runs what is queued, one task at a time, with human like delays inside each task.
Beta status
What runs today, and what is next
Written so a tester knows what to expect, and so this page can be checked against the product rather than the plan.
Runs today
- The gate: phase by age, the allowed kinds and the daily cap, on pods, the Identity page, the MCP server and the follow loop.
- The config: JSON per workspace on the Warming page, with the duration, the cap and the kinds of each phase.
- What a warming account can run on your computer: likes, follows, replies with text you supply, session checks, and profile work from day one.
- Password sign in with the 2FA code on the first task, for accounts added without an
auth_token. - Hourly caps on what an agent schedules through the MCP server.
Next
- Warming browse sessions: scrolling, search and explore that run on their own so a phase 1 account has something to do. Not built for the hosted beta yet; today the gate limits what you schedule and generates nothing.
- Quiet hours on each account's own clock. Not on the hosted beta: there is no per account timezone or activity window, and this page will say so the day there is.
- Automatic graduation from the criteria in the config, with a trust score that something updates. Today the phase moves with age alone.
- A phase override in the panel. Today the stored phase changes only through the MCP server's
warming_set_phase, which previews the jump before you confirm it.
The rules
What X says, and what this page does not claim
Warming keeps an account under thresholds X does not publish. It does not make anything allowed. X's automation rules, updated April 2026, are written against exactly the activity this page describes:
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 does automate likes, follows and replies. It does not claim those rules do not apply, and it does not claim compliance with them. What it does is refuse the shape of activity X names: a ramp for new accounts, a daily cap per phase, hourly caps on what an agent schedules, one task at a time per computer, 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 publishes, and the far lower ones worth running at, are in X rate limits.
Questions
Questions people ask about this
- How do I warm up a Twitter account?
- Give the account one proxy and a browser profile that persists, then keep it to a few actions a day for its first days: likes and reading first, follows after that, replies after the first week, and no bursts. In flottra this is a gate tied to the account’s age: 3 actions a day for 3 days, 6 a day for 4, 12 a day for 7, then no daily cap after 14 days. Anything past the phase is refused rather than queued.
- How to warm up an account?
- Warming any account means giving it a period of light, ordinary activity before it does the job you created it for, so that its first weeks look like a person finding their feet rather than a script starting at full speed. The ingredients are the same on every platform: a stable address, a browser that keeps its cookies, small daily counts that rise slowly, and uneven gaps between actions. flottra applies the counts for you and keeps the address and the browser on your own computer.
- What is the 4-1-1 rule on Twitter?
- The 4-1-1 rule is a content mix from social media marketing: for every six posts, four share other people’s content, one is a repost, and one promotes you. It is advice about what you post, not about how old an account is or how fast it acts, so it has nothing to do with warming. flottra does not enforce it. The warming gate counts actions and kinds per day; it never reads what a post says.
- How long does warming take in flottra?
- Fourteen days with the default config: three days at 3 actions a day, four days at 6, seven days at 12, and then phase 4 with no daily cap. Age is counted from the day you added the account to the workspace, so an account you add today is open on day 15. The config is JSON on the Warming page; shorten a phase or raise a cap and the change applies to the next task you schedule.
- Can I skip warming for an old account?
- Not from the panel. The gate counts age from the day the account entered the workspace, so a five year old account added today is treated as a day old one; there is no field for an acquired date in the panel or the MCP server today. The stored phase can be raised through the MCP server’s warming_set_phase, which previews how far ahead of its age the jump is and needs confirm. The effective phase is the higher of stored and by age, so raising works and lowering does nothing.
- Does warming post anything by itself?
- No. The gate limits what you and your agents schedule; it does not generate activity, and it never writes or sends a post. The warming browse sessions in the product, the scrolling and searching that would give a phase 1 account something to do, do not run on the hosted beta yet. The only thing that runs without you is the follow loop, which works through the targets you pasted, one follow at a time, and asks the gate before each one.
- What happens if I schedule more than the cap?
- It is refused, with a message naming the account, its phase and the cap, and nothing is queued for later. A pod run skips the refused member and continues with the rest; the Identity page does the same. Through the MCP server the refusal is a structured error carrying the phase, the cap, the actions in the last 24 hours and the queued count, so an agent can schedule tomorrow instead of retrying. Room comes back as actions age out of the rolling 24 hour window.