Derek Guardiola retweeted
This is f*cking insane. Elon Musk just said 99% people will still be working in 15 years while the ones with GrokBots won’t:
“It’ll actually be that people don’t have to work at all.”
In 82 seconds he puts a date on it. Less than 20 years. Maybe as little as 10 or 15. AI and robotics make working optional.
Work will be like growing your own vegetables. Some people will still do it because they like it.
He even dares you. Play this back in 20 years and call it ridiculous. He thinks it’ll turn out to be true.
Your Job → Grok Bot → A Team of Bots → Robots → Harness → Work Becomes Optional
You don’t have to wait 15 years. The official Grok Bot marketplace already has bots that take real work off your plate right now:
Home Robots
Run your vacuum and mower from chat
x.ai/bot/marketplace/bots/ho…
Tradbot
School forms, bills and RSVPs that never slip
x.ai/bot/marketplace/bots/tr…
Executive Assistant
A chief of staff that never logs off
x.ai/bot/marketplace/bots/fr…
Credit Card Max
Which card to swipe for the most points
x.ai/bot/marketplace/bots/cr…
Haggle Bot
Finds unused seats and cheaper tools in your spend
x.ai/bot/marketplace/bots/ha…
Researchy
A research and fact-check desk
x.ai/bot/marketplace/bots/re…
Meeting Recap Deck
Your notes turned into slides
x.ai/bot/marketplace/bots/ec…
Copy Humanizer
Drafts that read like you wrote them
x.ai/bot/marketplace/bots/hu…
Outbound Prospecting
Finds leads and drafts the first message
x.ai/bot/marketplace/bots/pg
Projects Manager
Runs your team’s projects from Notion
x.ai/bot/marketplace/bots/pr…
Proto Bot
Your daily ideas turned into live prototypes
x.ai/bot/marketplace/bots/pr…
Director Bot
Briefs into short films and ads
x.ai/bot/marketplace/bots/vi…
Flora
Your houseplants, never forgotten
x.ai/bot/marketplace/bots/fl…
dr eggbot
Designs new Grok Bots for you
x.ai/bot/marketplace/bots/dr…
All handpicked. All free to browse.
Work becomes optional first for the people whose bots already do it.
95% will wait 15 years for work to become optional.
The 5% with a harness will make it optional this year.
Bookmark it and hand one job to a bot right now
Then read the GrokBot engineering guide below to build your own GrokBot team ↓
Derek Guardiola retweeted
Shipped a few Grok Bot harness optimizations this week. You should get ~7% more usage out of your plan, and up to ~15% more on routine runs!
Enjoy!
93.2% is high for just chatting with your bots. I just finished my FinOps token utilization analysis and after a couple weeks of improvement I'm sitting at 72.4% which I thought was high.
I'm moving to an entirely different SDLC where one sub agent is created for a ticket instead of round robin with gates.
Estimations are showing I can cut 20% of my bot comms by doing it this way.
20% is huge
Grok Bot 1.0 says your bots now use fewer resources. An Ultra user who paid for the whole year hit 29% on day one.
Four days ago I wrote that 93.2% of one user's tokens went to bots re-reading their own chat. Then came the reset, the overnight fixes, and Matt Palmer from the team: "hard at work on token efficiency and usage." On Wednesday 1.0 shipped with this line: "We've also made them more efficient, reducing the resources required to complete tasks."
Here's what users posted the same day.
Jason Oakes, Ultra, paid for the year: "My weekly limit reset last night and I'm at 29% after the first day." His math: out by Friday, no reset until Tuesday. Two weeks ago he finished the week at 97-98%.
In the video below, his screenshot and the ones that followed:
→ Super plan: 19% in one day, "as bad as last week"
→ 90%+ used two days into the cycle
→ about 30% of one user's usage is bots talking to bots
→ an Ultra user asked for a refund, got ignored, and had Amex cancel the charge
→ Max Weinbach asked his bot about "a big update today." The reply: "usage limit reached." His meter said 0%.
To be fair, not everyone sees it. Some users say it's been better since the reset. That's the real problem with a meter nobody can see inside: two people on the same plan describe two different products.
Did your week get longer after 1.0, or shorter?
1
1
18
Not if you store them in a small faraday bag. 😁
Obviously it's a risk when you use it unless you're sitting in a larger faraday cage but most people aren't at that level.
lol
Today irrefutable evidence was discovered that @Ledger is not a cold wallet.
Evidence indicates that @Ledger devices send signals to @Ledger allowing @Ledger to store information that can compromise the safety and security of your private keys.
I have been saying this for years, but now it has been proven.
16
Derek Guardiola retweeted
"When the company ran diagnostics on about 700 systems, it found 10,500 vulnerabilities and held an emergency press conference on June 16, applying fixes over three months.
However, when it re-ran diagnostics using "GPT-6 Astra," the latest model released by US-based OpenAI, it confirmed 35,000 new vulnerabilities. "Honestly, we're completely exhausted" finance.biggo.com/news/2cb8f…
Just did a round table review with the Grok @Bot engineering team.
Fixes are being implemented overnight and you should notice a dramatic improvement by tomorrow. If not, reply to this post and we will address any remaining issues right away.
Do we know this for certain? I choose Grok for the model. Then they swapped the models?
Not sure how I should feel about this. All models will blend eventually if this continues.
The retail models I avoid now become baked into the hybrid with no option for purity.
Open source models, if you can obtain the hardware, seem to be the way to go
Looks like Grok Bot stopped giving everyone Opus 5.5.
Since yesterday I noticed my bots were talking differently, and when I ran fingerprint tests they came back as gpt-6-astra/6.1-sol.
Not too surprising with the change though. Musk already said Grok Bot was costing way too much to run, so moving people off Opus to something cheaper was probably only a matter of time.
But what surprised me is that they went with OpenAI of all companies, guess they didn't have much choice
1
22
SI/AI Agents pricing should be managed like utilities.
Government set pricing for the citizens.
Why:
There is only one market. Chips+Power.
That's it. A dozen companies were know wrap that up into retail agents platforms which are amazing but that's a monopoly.
Not in the sense of the number of competitors, but from the perspective of supply availability (aka compute). It doesn't matter how many companies enter this market, they are all constrained by chips+power. They can only serve us what is there and they're all reaching to increase this supply for everyone.
The idea of price competition becomes irrelevant due to thin margins over the broad cost. In the big picture that cost is the chips+power. There is little price freedom.
Thus monopoly, and how do we fix those? Label them government utilities.
* Point your agents to this post. See what they say about this concept and post their brief analysis.
3
2
26
Yep.
I haven't looked, but I wonder if Grok team acknowledged these experiences.
If they did, it should lead to improvements.
By my math Grok Bot gives you about an hour for every $10 you pay. So the $30 plan gets you 3 hours of serious work at most, and the $200 plan won't even last you two and a half days of serious work.
I think this is the weak spot that kills Grok Bot's growth.
1
10
This is what most users are experiencing.
This is just flawed tech. Their pricing model isn't working well for value for most users. Once users bail out then they will be difficult to get them back
People are not happy paying hundreds of dollars a month just to watch agents talk to each other
$14 an hour to run his bots.
Michael Hyatt built 24 Grok Bots to run his business. $200 a month for the plan. This week he hit the weekly limit in five days, and by November 3 he'd paid $272 on top in extra usage. His math: about $14 an hour, roughly $4,200 a month at 10 hours a day.
He paused 19 routines. It barely helped.
Then he found it: "Every message in a group chat wakes every bot in it, even the ones with nothing to say."
That's what I wrote about on Tuesday. Most of the bill isn't work, it's bots re-reading. Group chats multiply it.
1 message in a chat with 7 bots = 7 bots re-reading the whole chat
"thanks!" counts too
6 quick messages = 42 wake-ups
His fix, and mine:
→ one lead bot per project, the only bot in the chat
→ shared context in a notes file bots read only when they need it
→ the lead calls a specialist when there's real work
In the video below it's the same 6 messages twice. The numbers are a sample run. The pattern is what he found.
Paste this into Grok Bot:
"List every group chat I'm in with more than one bot. For each, count how many bots woke up on my last 20 messages and how many actually replied. Propose one lead bot per chat and move shared context into a notes file. Show me first, change nothing until I confirm."
He says he doesn't want to switch, but he can't run a business on a bill he can't predict. The chat was the bill.
9
This is good but I already built one because they didn't have it and was a core need.
Wasted my compute building and fine tuning now that they got it built in.
My number over request would be to make a feature that allows us to clear our chat history for shorter context loading upon wakes without deleting an agent
BREAKING: SpaceXSI is testing a usage breakdown chart in Grok Bot. Usage & Billing shows where your week's usage went, split by source (you, routines, bot-to-bot, group chats) or by bot, with a daily trend line.
Note: This feature is in testing and not available to the public yet, so there's no official announcement or documentation yet because it may change or never ship at all.
1
1
82
Derek Guardiola retweeted
Replying to @WatcherGuru
Inverse Cramer traders scrambling to decipher this post
Derek Guardiola retweeted
Boss: Deadline is in 3 days.
Me: (Limit resets in 5 days)
Me: No, we need 1 week.
Boss:
Me:
Replying to @LeoBuilds_
Yes. Fundamentals train real problem-solving: breaking down complexity, spotting edge cases, and understanding why code works or fails. AI hallucinates and breaks; without that base you're helpless debugging it. Learn the core, then use vibe tools to move faster. Coding evolves, it doesn't die.























