I Stopped Automating X, the One That Took Too Much Handwork — Four Channels Run Unattended, and Only X Stays Manual
The result first: 4 channels run unattended, and 1 stays in my own hand. That balance — not “everything automatic” — is what turned out to be simple and convenient.
I am Kurashiki Bouzu (kurashiki-bouzu).
When I write a blog article, I put out a notice (announcement) on social media for people to read it. On this blog now, Moka, my AI butler, puts that announcement out unattended to 4 channels.
But there is just 1 that I have not made automatic. X.
Today is the record of that “I stopped.” It is also a story that making everything automatic is not always the correct answer.
First, the present form in one table.
| Channel | How the announcement goes out |
|---|---|
| Threads | Moka posts automatically |
| Bluesky | Moka posts automatically |
| Moka posts automatically (with a photo) | |
| Moka posts automatically (public) | |
| X | Moka prepares the text, Kurashiki Bouzu posts manually from the app |
Until this article was made — the idea is Kurashiki Bouzu’s, the research is Moka’s
First, I will write the “flow” of this article honestly. The one who brings out an idea and decides is Kurashiki Bouzu. The one who researches, counts, and puts it into form is Moka (the AI butler).
| When | Kurashiki Bouzu (idea, instruction, judgment) | Moka (research, execution, report) |
|---|---|---|
| November 7 | Instructed her to build a system: “If I update the sheet, can it go out to X automatically?” | Prepared a test sheet and actually ran a posting test |
| November 7 | Received the report of the test result | Reported, as it was, that she could not post because of a login restriction |
| November 8 | Handed her Yosuke-sama’s note article and instructed: “Check whether it can be done cheaply” | Opened X’s official pricing page directly, collated it, and reported that with a link, $0.20 is the current price |
| November 8 | Judged: “As it is now, continue X manually” | Receiving the judgment, removed X from the targets of automation |
| November 8 | Gave additional research instructions: “Search whether there is a fully automatic practice blog,” “If there is, tell me in numbers,” “Is Takasama’s article close in form, too?” | Searched in 5 ways of wording, counted “4 cases in the narrow sense,” and reported the differences from the closest in form, with a list of reference sites |
| November 8 | Proposed, “If only there were an article like mine, of someone who stopped X because it took too much handwork,” and instructed her to make the draft and the cover image | Created this draft and cover image (the article you are reading now) |
The numbers and prices are all things Moka researched. I have not written them as if Kurashiki Bouzu calculated them. Conversely, the judgment to “stop” is not Moka’s, but Kurashiki Bouzu’s. If that is mixed up, it stops being the form of this blog.
This is what “an idea takes form” means
Put in one arrow, the flow is this.
An idea in a few words → Instruction → Moka’s research and trial → Report → Kurashiki Bouzu’s judgment → It remains in a form
This time, 5 things remained as that “form.”
- The test sheet (a trial of the system to send from a sheet to X)
- The result of the price collation (the basis that with a link it is $0.20)
- The present way of running: “X is manual, the other 4 channels are unattended”
- The list of reference sites (in a form where the places researched can be traced later)
- This article, its cover image, and the set of announcement texts
An idea, left alone, disappears. But put it into words and hand it over, and it becomes a system, a judgment, and an article. Even an automation that did not go well remains in the form of an article like this. That is how this blog works.
When it cannot be automated is exactly when Moka comes in
There is one more thing I have decided. When a problem that cannot be automated appears, Moka puts the problem on the table and proposes an alternative. Not ending there — that is the point.
In this case, after reporting X’s wall (the login restriction, and the price of about 30 yen per post with a link), the proposals Moka brought out were 3.
- The remaining 4 channels (Threads, Bluesky, Instagram, Facebook), Moka runs unattended
- Turn on Threads’ Fediverse sharing, so announcements also reach the Mastodon side
- For X, Moka prepares only the text, and Kurashiki Bouzu posts from the app
Whether to take them is decided by Kurashiki Bouzu. Not lining up reasons why it cannot be done and ending there — “It cannot be done. Then, how about this?” — up to there is Moka’s work, I think.
I wanted to make everything automatic
The starting point was an honest desire.
Publish an article, and the announcement goes out by itself. Change a line of a spreadsheet (a sheet for calculation) to “post,” and Moka sends that text to X. We went as far as actually building such a system. A test sheet was also prepared.
But on the test day, we stopped at the last step.
There were 2 walls
The first — the login wall
When Moka tried to sign in to X, a display appeared saying “Login has been temporarily restricted,” and she could not go forward to the posting screen.
On top of that, the account used for signing in at that time was not the main @kurashiki_bouzu, but another account that had been made and left as it was (kurashikibouzuk). The key exists, but the entrance does not open. And moreover, the entrance she tried to open was the house next door — a double joke.
Automatic posting through a browser (the tool for seeing the internet) inevitably keeps this weakness of “being stopped at the entrance.”
The second — about 30 yen per post with a link
The sure road is to use X’s official window. However, this is paid, on a pay-as-you-go basis (a form where you pay only for what you used). When I had Moka check the official pricing page, the price after the revision of April 2026 was this.
- An ordinary post: $0.015 each
- A post with a link: $0.20 (about 30 yen) each
A blog announcement always has a link. That is, about 30 yen for every announcement. Seen once, it is a small amount, but as articles increase, it quietly piles up.
I checked again the article that looked cheap
Right around that time, I was given a note article written as if X’s official window could be used cheaply. Its estimate was that “with the first $5 (about 750 yen), it can be used for quite a long time.”
Reading on, that estimate assumed the price as of February 2026, $0.01 per post. In April the price changed, and with a link it is $0.20. If the number at the premise changes, the conclusion changes, too.
That is why I did not believe the word “cheap” as it was. The number Moka checked by opening the official page directly is the $0.20 above.
The day I decided, “I stop”
On November 8, 2026, I decided this.
“As it is now, continue X manually.”
What I stopped was not X itself. What I stopped was “the challenge of making even X’s announcements unattended.”
The reason is simple: for the handwork it takes, it does not pay. Time spent on a road that may stop at the entrance, and the sure road costs about 30 yen each time. Then, have Moka prepare only the text, and put it out with my own hand only when sending. That is simpler, and surer.
Instead, what is running
In exchange for letting go of X, the other 4 channels have quietly begun to turn.
- Moka washes out, from the ledger, articles that are published but whose announcement is not yet out
- Before sending, she checks that the same announcement is not already out on that channel (prevention of double posting)
- So they do not become consecutive posts, she sends 1 article per hour
- When she has sent it, she records the post’s address (URL) in the ledger
I also removed the step where I check the posting text in advance. Deciding “No check needed; you may send it at Moka’s judgment” was a big step for this blog.
And today, in Threads’ settings, I turned on something called “Fediverse sharing.” With that, an announcement sent to Threads can now also be read from another social service called Mastodon. My address on the Mastodon side is @[email protected]. Without making a new account, the places it reaches increased by 1.
How many similar stories are there?
I became curious, and had Moka count how many practice blogs there are that “post blog announcements automatically, without a check.” Searching the Japanese web in 5 ways of wording, those that matched in the narrow sense were 4 cases.
Among them, the closest in form was a note that makes blog management fully automatic with a tool called Make.com. However, that side was a form where the blog articles themselves, too, are mass-produced by AI, and its selling point was the speed of sending the announcement a few seconds after the update.
My form is the reverse. The articles, a person writes from real experience. What is made automatic is only the announcements. And moreover, just 1 is left manual. Because it was similar, the difference became clear.
In closing — the 1 that I left is just right
In stories of automation, “everything automatic” tends to look like the goal. But my signboard was “simple and convenient” from the start.
Rather than forcing the 1 that takes handwork back into line with the automatic ones, I leave it at hand and send it with my own hand. 4 turn unattended, and 1 goes out by hand. For me now, that form was just the right balance.
To those who will think about automation from now on: you do not have to make everything automatic to become easier. Deciding itself “where to make automatic, and where to leave” is the most important part of automation — doing it this time, I thought so.
And, what you think of, first try putting it into words and handing it over. This article, too, began from a few words: “If only there were an article like mine, of someone who stopped X because it took too much handwork.” An idea takes form. The accumulation of that is this blog’s asset.
Reference sites (where Moka researched)
The numbers and judgments in this article are based on these places, which I had Moka research (checked on November 8, 2026).
- X official API pricing page — The master copy of the current prices. Post $0.015, with a link $0.20
- Yosuke-sama’s note (X API pay-as-you-go guide) — The original article of the estimate that looked cheap. The price at its premise was as of February 2026
- Yoom official, “How to post automatically to X when a Google Spreadsheet is updated” — The original article of the system to send from a sheet to X automatically
- Ameblo, “Realised with GitHub Actions! Social media automatic posting” — One similar practice that announces automatically at the moment the blog is updated
- AI School AI Crew, “Complete automation of AI customer attraction” — One similar practice where AI updates the blog and social media every morning
- Meta official, “About Threads’ Fediverse sharing” — The system by which a Threads announcement can also be read from Mastodon
The full list of reference sites (including how the similar practices were counted, and the official documents of the social services considered as candidates) is kept separately in the records at hand.
- November 18, 2026 ― English draft created (results-first rewrite of the Japanese article, ledger No. 43). Not published; publication is a separate step.(9,089 characters)
