Scheduling, for people who run many X accounts

Schedule posts for many X (Twitter) accounts

Flottra keeps one queue of posts for many X (Twitter) accounts. You write a post once, or let each account’s persona write its own, and choose when. The desktop app then posts from each account’s own browser and proxy on your computer, one task at a time. A posting routine can also write and publish through the day.

Updated

What it does

One queue for many accounts, each post sent from its own browser

The tools on page one for this search are single-account schedulers that post through the official X API from the vendor's servers. Flottra keeps the queue; the posting happens on your computer.

Flottra is X (Twitter) automation software for running many accounts, and the Posting page has one form for all of them, Schedule a post. Tick the accounts, write the text or give each persona a topic, choose a time or leave it for as soon as possible, and press Schedule. The panel writes one task per selected account into the queue. It never opens a browser, and no browser runs on Flottra's servers.

Sending is the desktop app's job. It runs on a computer you already use, Windows today, and opens each account in its own saved browser profile through the proxy you assigned to that account. Without a proxy nothing runs. Two accounts post from two browsers and two IP addresses, the way two people would. The app runs one task at a time, with human-like pauses inside each, so twelve posts due at 09:40 leave one after another rather than as one burst.

X has its own scheduled posts feature; for one account it is the obvious choice. This page is for the other case: twelve accounts, or a hundred and fifty, a queue that survives a laptop lid closing, and a persona that keeps each account sounding like itself. Everything else on the features list, the auto follow loop and the warming ramp included, runs through the same app and the same proxies.

Schedule a post

Accounts
12 selected
Text
generated per persona
Length
short
When
Tue 09:40, one task per account

The form as it is in the panel, not a screenshot. Verbatim text is the other option: up to 4,000 characters, the same words to every selected account.

How it works

Schedule a post in three steps

The form is the same whether you tick one account or forty. The only thing that grows is the number of tasks it writes.

  1. 01

    Pick the accounts

    Tick the accounts that should post. The list shows each account's status and whether it has a persona. A post can go to one account or to every account in the workspace.
  2. 02

    Write it, or let the persona write it

    Write it myself takes verbatim text, up to 4,000 characters; X itself caps a free account at 280. Let AI write it takes a topic, a tone, a length (micro, short, medium or long) and a format, and each account's persona does the rest.
  3. 03

    Choose when

    Leave Schedule for later off and the post is queued for as soon as the app is free, or switch it on and pick a date and time. Press Schedule and the panel tells you how many tasks it wrote.
4,000
characters the form accepts
280
characters X allows a free account
1
task per account, per post
3
posts per account per hour, through the MCP

After Schedule, each task sits on the Tasks page as pending, one row per account, until the app takes it; a pending task can be cancelled there. A post reports back the way likes, follows and replies do: done, or failed with the reason.

Time is the one thing the queue cannot invent. If the computer is asleep or the app has been quit at 09:40, the task waits as pending and runs when the app is back, oldest first, one at a time. Nothing is dropped and nothing is rescheduled: the post goes out late rather than not at all. The posting routine is stricter with its own posts: one that no paired computer picked up within six hours is dropped. If the minute matters, keep that computer awake; closing the window is fine, the app hides to the tray and keeps working until you quit it.

Voice

The same announcement from twenty accounts should not read as the same announcement

Two ways to fill the text field, and the choice matters more with every account you add.

Verbatim is the simple case. You write the text once and every selected account posts it as written. It is right when the words matter more than the voice: a link, a time, a quotation, an official line.

Generated is the case that makes many accounts worth running. Each account has a persona: a voice, interests, quirks, an avoid list, a length bias and example posts. The form takes hints only, a topic, a tone, a length and a format, and the post is written from the persona of the account that will send it. Twenty accounts asked to post about the same launch produce twenty different posts, because twenty different people would. Personas are drafted in the panel from a topic and a brief with your own Anthropic API key, and edited before saving; the AI personas page has the detail.

Where that text comes from: Flottra's server writes it, with the AI key you saved in Settings, a few minutes before the post's time. It writes three drafts and keeps the one least like what your accounts posted recently. If the key is missing, refused or out of credit, the post waits and the Tasks page says why; a post still unwritten 24 hours after its time fails rather than appearing a day late. The desktop app itself never calls a language model: it posts the text it is handed, whether you wrote that text or it was generated from the persona.

The posting routine is the always-on version. Turned on per account on the Routines page, it needs a persona and an AI key, and then it decides both when and what: at most 8 posts a day by default, 2 to 4 hours apart, inside the active hours you set on the account's own time zone, on the topics you list or the persona's interests. Three drafts are written for every post and the one least like what the account and its sibling accounts posted recently is kept, and two accounts of one workspace are kept at least 12 minutes apart. With app 0.1.36 or newer a routine post can carry one photo.

Pacing

A post is one more paced task, not a separate system

Posting gets no rules of its own. The gate and the caps that apply to likes, follows and replies apply to posts in the same way, and the same app runs them one at a time.

New accounts are gated by a warming ramp measured in days since the account was added to the workspace: 3 actions a day for the first 3 days, 6 a day for the next 4, 12 a day for the 7 after that, then open. In the default ramp, original posts are not allowed in the first three phases at all, so an account added yesterday cannot have a post scheduled through the gate until its 14 days are up. The ramp is editable as JSON on the Warming page; where a phase allows posting and has a daily cap, queued posts count toward it with everything else. An account you have run for years can be moved to the open phase through the MCP server. The account warming page has the whole ramp.

Hourly caps are the second guard: 3 posts per account per hour by default, beside 12 likes, 6 follows, 5 replies and 3 DMs, editable per workspace. Both the gate and the caps are enforced when a task is scheduled through the MCP server, which refuses the fourth post in an hour instead of queuing it. The panel's own form writes to the queue without either check today; if you want posts held to the same rules as everything else, schedule them through the MCP. The posting routine applies the warming gate, and paces itself with its own daily cap and gaps rather than the hourly cap.

The third guard is the app. It runs one task at a time per computer, so it cannot produce a burst even when the queue holds one; the auto follow loop lives in the same queue and takes its turn. A post you schedule by hand has no clock of its own: it goes out at the time you chose, in your own time zone, whatever hour that is for the account's audience, so choose the hour with the audience in mind. The posting routine is the part with a clock: it keeps to the active hours you set, on the account's own time zone.

Today and next

What runs today, and what is not built

A tester should know exactly what to expect, so here is the list, with nothing rounded up.

Today, on the hosted beta

  • The Schedule a post form on the Posting page: accounts, verbatim text or generation hints, an optional date and time. It writes one pending task per account.
  • Sending, from the desktop app (0.1.27 or newer): each post leaves from the account's own browser and proxy on your computer and reports back done or failed.
  • Posts written from the account's persona, on the server, with your own AI key, a few minutes before their time.
  • The posting routine on the Routines page: persona-written posts through the day, inside active hours, with a daily cap.
  • The queue on the Tasks page, filterable by status. A pending post can be cancelled there.
  • Through the MCP server: up to 4 photos on a post, and up to five self-replies queued under it once it is out.

Not built

  • Quote posts and polls. Threads exist only as self-replies under a post, and only through the MCP server.
  • Media in the panel form. There is no attachment field there; photos go through the MCP server or the posting routine.
  • A review queue. There is no approval step between Schedule and the post leaving, so treat Schedule as the decision.
  • The warming gate and the hourly cap on the panel form. Both apply when a post is scheduled through the MCP server.

What X says

X's rules, quoted rather than summarised

The automation rules on help.x.com were updated in April 2026. The lines that matter for many accounts, as written.

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".
X's automation development rules, read 19 September 2026.

Flottra does not claim to comply with those rules, or that scheduled posts are exempt from them. What it does is pace everything and refuse bursts, which reduces the rate at which accounts are locked or suspended; it does not make it zero, and nobody can. The same text from many accounts at the same minute is the easiest pattern to spot, which is why the generated mode exists; keep verbatim for the cases where the words must be identical.

The long versions are in the guides. X automation in 2026: what actually works covers the official API against browser automation, the twitter auto poster question and duplicate content across accounts; read it before choosing any tool, this one included. X rate limits has the daily post figures X publishes, what rate limit exceeded means, and the far lower pace operators run.

Compared

A typical scheduler and Flottra, side by side

The tools on page one for this search connect an account through the official X API, take your text and a time, and post it from the vendor's servers. For one account that is a good product, and X's own scheduler does the same job. The differences below are structural, and they only start to matter at the second account.

A typical schedulerFlottra
AccountsOne, or a few connected one by oneMany in one workspace: 2 free, then 10, 40 or 150 by plan, more at 4 USD each
Where it posts fromThe vendor’s servers, through the official X APIA real browser on your own computer, one saved profile per account
Whose IP addressThe vendor’sYour own proxy, one per account: residential, mobile or ISP
Voice per accountWhat you typed, for every accountVerbatim, or generated from each account’s persona
PacingThe time you setA warming ramp and hourly caps through the MCP; one task at a time on the app
Price of entryDepends on the toolFree plan: two accounts, no card
The left column describes the tools on page one for twitter scheduler in September 2026 in general terms. Nobody checked their prices for this page.

Questions

Questions people ask about this

How to set up auto tweets?
Two ways. For specific posts, open the Posting page, press Schedule a post, tick the accounts, write the text or give the persona a topic, tone, length and format, choose a time or leave it for as soon as possible, and press Schedule: one task per account lands in the queue. For an always-on loop, turn on the Posting routine for an account on the Routines page. It needs a persona and your own AI key, and it then writes and publishes posts through the day inside the active hours you set.
Can I schedule the same post to many X accounts?
Yes. Tick as many accounts as you like in the Schedule a post form and the panel writes one task per account with the same text and the same time. Each task then runs from that account’s own browser profile and proxy on your computer, one at a time, so the posts leave one after another rather than in a burst. The same text from many accounts is the easiest pattern to spot, so for anything but a link or a fixed line, let each persona write its own.
Does the scheduler post through the X API?
No. Flottra does not use the official X API at all. The desktop app opens a real browser window on your own computer, one saved profile per account, through the proxy you assigned to that account, and posts the way a person would. The panel only keeps the queue and the schedule; it never opens a browser, and no browser runs on Flottra’s servers. That is why many accounts can share one panel without sharing an IP address.
Is there a free Twitter scheduler in Flottra?
The free plan covers two X accounts, needs no card, and includes the same panel, the same desktop app and the same queue as the paid plans; scheduled posts and the posting routine run on it. Two things to know first: a post written by AI needs your own AI provider key, which that provider bills you for, and the app runs on Windows only. If a free scheduler for one account is all you need, X’s own scheduled posts feature already does that job.
Will my scheduled posts go out during the beta?
Yes, as long as the desktop app, version 0.1.27 or newer, is running on a paired Windows computer and the account has a proxy. The app asks the panel for work every 15 seconds, takes a post that is due and publishes it from the account’s own browser. If the computer is asleep or the app is closed at that minute, the post waits as pending and goes out when the app is back; a post you scheduled by hand is not dropped for being late. A post that fails shows the reason on the Tasks page.
Can it write the post for each account?
Yes. Each account has a persona, with a voice, interests, quirks, an avoid list and example posts, and the form’s Let AI write it mode takes a topic, a tone, a length and a format. The post is written from the persona of the account that sends it, a few minutes before its time, with the AI key you saved in Settings, so twenty accounts produce twenty different posts. An account without a persona falls back to a built-in default voice, so set personas first. The desktop app never calls a language model; it posts the text it is handed.
How many posts a day is safe?
Flottra does not publish a safe number, because there is not one. What it does is refuse bursts. The posting routine defaults to at most 8 posts a day per account, 2 to 4 hours apart, inside active hours of 9 to 23 on the account’s own clock, and it does not post for an account still inside the warming ramp, 14 days in the default ramp. Through the MCP server the hourly cap is 3 posts per account. X’s own published daily post limit, and the much lower pace operators actually run, are set out in the rate limits guide.

Try it on two accounts, free

The beta is open. Create a workspace, install the app on the computer you already use, and add your first account. No card. During the beta the people who built it answer your mail.