Bro said he’s gonna respond to everyone and it’s obviously AI bot replies😭😭 you guys suck stop trying to just save face and FIX THIS SHIT @mattyp@poteto@elonmusk
Improvements to token efficiency & behavior in Grok Bot are underway
Many of you have built important workflows on @bot - we want to keep supporting you
Please reply with feedback on this post. I will read it all
Thank you sincerely for your support
@big_al_2013@mattyp@poteto@elonmusk A product that’s supposed to be “for the people” has implemented vendor lock in while slashing usage and rugpulling their user base. I agree there’s other options, which is what I’ll be switching to if they don’t fix it.
@cnikitopoulos94@mattyp@poteto@elonmusk “Grateful”?😭 it’s a paid product. I’m not grateful for shit. They set a price and I pay it. Ur a grown ass man stop being a fanboy. A product that’s supposed to be “for the people” has implemented vendor lock in while slashing usage. That simple.
@ByteWiseApps@mattyp@poteto@elonmusk Are you a spineless fanboy/girl that can’t stand up to companies that claim to be “for the people” then proceed to implement vendor lock in and slash usage in the same week?
@gnaijcira@mattyp@poteto@elonmusk Yes. They stopped allowing bots to run Claude code or codex on physical machines to try and lock everyone into cursor cloud agents while SLASHING usage AT THE SAME TIME. Makes no sense. Definitely wouldn’t make a dumbass decision like that.
@MichaelWaitze@mattyp@poteto@elonmusk Please also report on how they stopped allowing bots to run Claude code or codex on physical machines. They’re trying to lock everyone into only coding with cursor cloud agents which is beyond whack. ESPECIALLY while cutting usage at the same time. That’s why I’m mad.
@realnatecar@mattyp@poteto@elonmusk 😭😭 What are you Elon’s biggest fan?? They stopped allowing bots to run Claude code or codex on physical machines which is horrid. They’re trying to lock everyone into only coding with cursor cloud agents which is beyond whack. ESPECIALLY while cutting usage at the same time.
@ecvlls@mattyp@poteto@elonmusk It’s not just usage. They stopped allowing bots to run Claude code or codex on physical machines which is horrid. They’re trying to lock everyone into only coding with cursor cloud agents which is beyond whack. ESPECIALLY while cutting usage at the same time.
@mattyp@poteto@elonmusk While I have your attention REMOVE the vendor lock in. Let grok bot run local CC and Codex workflows. Stop trying to force everyone on to cursor cloud agents
@poteto REVERSE THE VENDOR LOCKIN ON GROKBOT!! No one wants to use cursor cloud agents after you SLASHED usage anyways. Allow it to orchestrate local coding with cc and codex!!
@mattyp@bot Undo the vendor lock in! Allow us to use grok to run local Claude/codex based workflows. Stop trying to force us all to use cloud cursor agents.
🚨 Grok Bot users on $200 Ultra are getting squeezed twice this week.
First the weekly pool. One user went to bed at 28% and woke up near 60%.
Now users are reporting their Bots refuse local Claude Code and Codex, push them to Cursor Cloud, and some hit a demand for credits.
So you burn the pool. Then you pay again to code.
Who thought this was a good move?
Claude Code and Codex win either way. People will just run them without the Bot.
Let our Bots use the tools we already pay for. And show us what's burning the pool.
It's time Grok Bot users get heard.
@elonmusk@poteto@mattyp forcing vendor lock while ALSO slashing usage in grokbot is disgraceful you guys have managed to run a good product into the ground within a week! My bot refuses to start local coding workflows and will only run cursor cloud agents. Fix or I cancel!!!
@elonmusk@poteto@mattyp forcing vendor lock while ALSO slashing usage in grokbot is disgraceful you guys have managed to run a good product into the ground within a week! My bot refuses to start local coding workflows and will only run cursor cloud agents. Fix or I cancel!!!
@poteto WHY WOULD YOU BLOCK LOCAL CODE EXECUTION in grokbot? Completely broke so many workflows. Why force everyone to burn their usage on cloud cursor agent runs THE SAME week you cut usage??? How do you drop the ball so bad in a week?