Twitter Scheduler for Posting to Your X Account

An X account you own publishes text posts and image posts today through your own logged in browser session. Each run picks today's story from trends and available material, writes the post fresh and renders it into a format, and then it goes out as your account.

X
How it publishes todayAn X account you own publishes text posts and image posts today, through your own logged in browser session on the machine that runs the posting worker.
What is not supported yetThreads, replies, reposts, likes, follows, DMs, polls and video posts are not supported, and no official API route is in place.
What changes when the API is certifiedWhen we are certified for the official X API the delivery route changes underneath the same pickers, formula and approval gate, and this page is updated to say so.
On this page
  1. How does a post reach my X account?
  2. Do I have to give you my X password?
  3. Do you use the official X API?
  4. Which kinds of X post work today?
  5. What is not supported on X yet?
  6. Can I get restricted on X for using automation?

How does a post reach my X account?

Through the same steps every post goes through, and then out via a browser that is already signed in to your account. Nothing is routed through a shared or third party account.

  1. The scheduled job runs, and the run picks today’s story from trends and the material available, dropping the thin candidates.
  2. The post is written fresh and rendered into a text or image format that declares its text limits.
  3. A post that fits publishes to your account on schedule; a post that breaks the format’s text limits is parked for a person instead of posting.

X rewards short, plain text, so the text formats here are tight by design: a hook line and a body that fits the character limit are limits the format declares, and a post that breaks them does not go out. Every run is logged with its status and how long it took, and a per post record of why one story beat another is designed, not built yet. The same engine runs Facebook, Instagram and TikTok, and the status of every platform is on platforms.

Do I have to give you my X password?

No. You sign in to your own account in your own browser, and we never ask you to hand over credentials for storage.

The session belongs to you and the account belongs to you, so the post goes out as your account acting as itself. If you change your password, you sign in again, and nothing on our side needs to know what it was.

Do you use the official X API?

Not today. We hold no official API certification, and posting happens through your own logged in session.

X publishes rules about automated posting and has changed them more than once, so we say the route out loud, per platform, rather than implying an integration we do not hold. When certification exists the delivery route changes and this page says so.

Which kinds of X post work today?

Single text posts and single image posts. Both have run daily on real accounts.

Threads, polls and video posts are not started. A thread is several posts chained together rather than one, and we would rather add it once the single post has run long enough on your account to trust. Until then the answer is no, stated here rather than discovered later.

What is not supported on X yet?

Threads, polls, video posts, replies, reposts, likes, follows and DMs. Everything from replies onward is outside on purpose.

We do not automate engagement of any kind. Automated replying, reposting, liking and following is where account restrictions usually start, and we would rather lose the feature than carry that risk into an account you own. Threads, polls and video are simply not started.

Can I get restricted on X for using automation?

Nobody can promise immunity, and any tool that does is guessing with your account. Browser session posting is a grey area, and we will not describe it as approved or compliant.

What we do is keep the behaviour slow and capped. Volume is capped per account per day, timing is varied rather than landing on the same second, one posting session runs per machine, and a post that breaks its format’s text limits is parked rather than forced out. Combined with never touching replies, reposts, likes, follows or DMs, that is a quiet pattern of activity. The full set of controls, and what we cannot promise, is on trust and account safety. The whole run is on how it works, and the rest of the questions are on the FAQ.

Not yet

  • No official X API certification is in place. Publishing happens through your own logged in browser session.
  • Threads, replies, reposts, likes, follows, DMs, polls and video posts are not supported, and we do not plan to automate engagement of any kind.

By Content OS team, Content OS. Updated .

Join the waitlist