Describe the Bug
- I set up a Grok Bot assistant to help run my X account (@TianMindAI): an original post Mon/Wed/Fri and a few replies to hot posts Tue/Thu, done through the box browser on a schedule. I approved each post.
- The assistant planned cadence, hooks, and metrics carefully, but never warned me that scheduled, browser-driven posting and replies can break X’s automation rules and put the account at risk.
- On Sep 25, three attempts to post with images all failed. X showed “some of your media failed to upload” and the media upload INIT request returned HTTP 403. Looking back, that was probably an early sign of a restriction. The assistant still scheduled another retry that evening instead of stopping and flagging the risk.
- That same evening X froze the account (permanent read-only).
Steps to Reproduce
- Create a Grok Bot assistant for social media and log into X in its browser.
- Ask it to set up routines that post and reply on a schedule.
- The assistant creates and runs the routines. At no point does it mention platform automation rules or account-suspension risk.
Expected Behavior
Before setting up any automated write actions on a third-party platform (posting, replying, liking), the assistant should clearly warn about that platform’s automation and spam rules and the risk of losing the account, and suggest safer options (official API, drafts only, manual posting). When it sees signals like repeated 403s on write actions, it should stop and tell the user instead of retrying.
Operating System
macOS
Version Information
Grok Bot desktop app, recent build.
Does this stop you from using Cursor
No, but it cost me my X account.