2026-08-09 · Morgan Ellis · 835 words
Social media automation tools we refuse
Unofficial schedulers and engagement bots are refused here. Authorized rooms still use official tools. This is a commercial query with a hard no.

The commercial query wants a stack. A scheduler that is not the platform's. A growth panel that likes and follows while you sleep. A cloud browser to hold the session. The answer here is no.
Authorized profiles still exist. Official tools still exist. Unofficial engagement machines do not get a MaskWright recipe.
What I mean by unofficial
If the platform ships Creator Studio, Business Suite, a native scheduler, or an ads API, that is official. If a third party asks for your password, a cookie dump, or a browser extension that clicks inside the site, that is unofficial.
Unofficial tools live on the wrong side of browser automation versus a real profile. They are UI bots against a login. Some of them rent the browser. Browserless and Browserbase are not operator profiles. Some of them wrap a model. Agent browsers versus operator profiles. Some of them want MCP as the pipe. MCP is not a local profile.
The custody test is simple. Who holds the session after you close the lid? If the answer is a vendor disk, a Chrome extension you did not write, or a panel that asked for the password, the tool is unofficial even when the landing page says "safe."
The jobs I skip, not a brand list
I will not name a shopping list. Listicles go stale. The jobs do not. I skip auto-follow, auto-like, auto-comment, mass DM and scraped lead inboxes, unofficial schedulers that keep your session on their disk, view or watch-time farms, and captcha solving so the farm can continue. Captcha solvers are not research.
Those jobs burn the account you were trying to save time on. They also ask this app to become a stealth host for a UI bot. That is not launch and isolate.
LinkedIn is a distinct query with the same no. LinkedIn automation tools we refuse. This page does not soften into a company-page hygiene note.
| Job | Official door | Unofficial helper |
|---|---|---|
| Schedule posts | Platform suite / native composer | Cookie panel on a vendor disk |
| Ads reports | Ads API | Headed clicker in the ads UI |
| Reply to comments | A person, or a listed partner | Auto-comment bot |
| Grow follows overnight | Not a product we write | Auto-follow stack |
What a local profile is still for
A brand account you own can live in an isolated profile on Windows. You open it. You post with the official UI or the official business suite. You close it. Another brand does not share those cookies.
That is isolation. It is not automation. MaskWright 0.1 will start the profile. It will not queue the likes. It will not keep a session warm on a timer. It will not click while you sleep. MaskWright is not an agent runtime.
A desk with three authorized brands can have three profiles. A person moves between them. Bulk start opens the windows. It does not write the comments.
Scripts that talk to an official API belong in a scripts folder, not in the profile. Local scripts stay outside work rooms. A Python client against Ads Manager reporting is not a like-bot. A headed script against the consumer feed is.
Official tools I will point at, without a ranking
Meta Business Suite and the official Instagram professional tools. TikTok Ads Manager and Business Center. YouTube Studio and Brand Accounts. LinkedIn Campaign Manager and licensed seats. X's official ads and API products. First-party schedulers those platforms ship. Partner programs the platform lists, when the job is data or ads, not a scraped inbox.
I will not rank unofficial Chrome extensions against those. I will not call a cookie-based third-party dashboard "safer if you use a profile." The dashboard still holds the session. The profile only changes which local folder the extension or the paste came from. Custody did not move back to you.
If a platform does not offer a scheduler, the remaining option is a person in the profile. That is slower. It is also how the account stays yours. Paying a person to post in the official UI is still official. Paying a panel to hold the cookie is not.
Growth teams still have real work: brand profiles, ads profiles, community profiles, a person who replies. Isolation helps that work. An unofficial like-bot does not. If a hire asks for "the tool everyone uses to grow," send them to the official suite and to the platform roles they already pay for.
The ethics sit under Automation. This page is the commercial no for social automation. Official tools and owned profiles. Nothing that clicks while you sleep.
FAQ
Is a platform-listed partner unofficial?
If the platform lists it for ads or data, that is a different contract than a growth panel that asked for your password. Read the partner terms. Do not treat a cookie paste as a partner program.
Can MaskWright schedule posts?
No. 0.1 opens profiles. You post in the official UI, or you use the platform's own scheduler.
Related notes
- LinkedIn automation tools we refuseAutomation
- MCP is not a local profileAutomation
- Browserless and Browserbase are not operator profilesAutomation
- Agent browsers versus operator profilesAutomation
- MaskWright is not an agent runtimeAutomation
- Local scripts stay outside work roomsAutomation
- Browser automation versus a real profileAutomation
- Captcha solvers are not researchAutomation