d3n4c3

coding, designing, and the leading edge.
🌈🎮🤙

[d3n4c3 @d3n4c3]

Hope this is true!

[Elon Musk @elonmusk]

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.

[d3n4c3 @d3n4c3]

@JoeyGilkey @spacexai @bot They really dropped the ball at the peak. This should be studied as the greatest mistake in the AI realm in all of history.

[d3n4c3 @d3n4c3]

@johnhelmuth_ @bot One can hope.

[d3n4c3 @d3n4c3]

@LailaDeeb1 @bot Hopefully soon.

[d3n4c3 @d3n4c3]

One of many reasons, but this one was one of the biggest because it would spin up token usage talking between your grokbot agent and a cursor agent to push simple changes rather than just make them on its own for those of us who already had a nice workflow. Also, it forced everyone to burn tokens setting up an entire new workflow using the cursor cloud agent.

[d3n4c3 @d3n4c3]

@MichaelHyatt @bot Was anyone denying this or calling people idiots? I think it was mostly unanimous that there was an issue with the grokbot agent capaiblites.
https://t.co/2HNG3FFfqp

[d3n4c3 @d3n4c3]

There wasn't even a problem though. Even if they did change the default model. It was running fine. Waiting for Grok 4.8 seems silly. They changed what Grokbot was capable of and forced it to do all code changes through cursor cloud agents. This caused a massive issue with people's existing workflows.
https://t.co/t9ewJdZFkm

[d3n4c3 @d3n4c3]

@soareso If it's restored back to how it was, I would give it one more chance. But that would be the last chance.

[d3n4c3 @d3n4c3]

@CarawayDJ Elon noticed the loss faster than most would though. So, there's some hope for a return to grace.

[d3n4c3 @d3n4c3]

@elonmusk @dneighbors @Texas_Twins_Dad Find out who made the change that forced the workflow issues and have them fix the problem.

[d3n4c3 @d3n4c3]

Finally, he sees it.

[Elon Musk @elonmusk]

@dneighbors @Texas_Twins_Dad I will dig into this today

[d3n4c3 @d3n4c3]

I thought you had a finger on the pulse boy was I wrong. 🤣

[Elon Musk @elonmusk]

@Texas_Twins_Dad Is it not one-click-easy to increase usage?

[d3n4c3 @d3n4c3]

@Jtyles @grok @elonmusk Yeah bro. I canceled my subscription yesterday. The grokbot team says they're going to fix it. I'll give them one more chance if they do. But if something like this happens again, I'll have no choice but to leave this ecosystem forever.

[d3n4c3 @d3n4c3]

Looks like the grokbot team isn't playin' around.

[matt palmer @mattyp]

@christopherbaer Yes I was going to go hike today, but this seemed more important

[d3n4c3 @d3n4c3]

This is great to see. Glad to hear this is potentially getting fixed. Why did the team remove the ability for the agents in Grokbot to push code changes to GitHub and deploy sites? I’m curious, what was the goal? It broke so many people’s basic workflows and caused unnecessary thrash between the bot and cursor cloud agents.

[d3n4c3 @d3n4c3]

@elonmusk Great news. I guess we shall see.

[d3n4c3 @d3n4c3]

@Kevin_Logan Dang. About time they noticed this!

[d3n4c3 @d3n4c3]

@RetroMoviesDB Dang man, these were the good old days.

[d3n4c3 @d3n4c3]

@FortniteStatus Yikes.