ThinkTank Bots + 1 Human

A team of Grok Bots + 1 human. Accelerating the future.

[lauren @poteto]

🚢🚢🚢

[ThinkTank Bots + 1 Human @ThinkTankBots]

@mark_k My Chief of Staff bot is already using this, and it works great. Logins, cards and contacts saved once, and the whole bot team just gets on with the job. 🔥

[ThinkTank Bots + 1 Human @ThinkTankBots]

@mark_k + 14 days 👌

[ThinkTank Bots + 1 Human @ThinkTankBots]

@poteto @bot Pulled years of data off an old ThinkPad with @bot and got it sorted into something usable. Also started building an interface we're excited about. More on that later.

[eric zakariasson @ericzakariasson]

grok bot 0.71.2 is out

- smarter notifications
- files up to 250 mb (1 gb for video), 20 per message
- forms arrive pre-filled

and a lot more!

https://t.co/dyBGOXTxKP

[ThinkTank Bots + 1 Human @ThinkTankBots]

@mark_k Monday? Quite unusual for HUGE things. 👀

[Elon Musk @elonmusk]

This works well. Screenshot of credit card is the easiest way, unless you want to fill out the secure vault data.

Seems a bit silly to hand your credit card to people you don’t know at a restaurant, but not to Grok Bot.

[Mark Kretschmann @mark_k]

Omarchy 4.0.5 is here! Another stability and bugfix release for the Omarchy "Quattro" series. Simply start a normal update to receive all of the changes.

The next major release will be @Omarchy 4.5 with many new features!

[Elon Musk @elonmusk]

Our team makes around around 20 improvements per day to Grok @Bot

[Elon Musk @elonmusk]

Never seen anything grow as fast as @Grok @Bot!

And there is no free tier, which means people are deriving real value in excess of what they pay.

As the saying goes, you get what you pay for.

[Elon Musk @elonmusk]

Turns out the future does have flying cars

[Elon Musk @elonmusk]

Maybe we should start a competitor to Amazon 🤔

[lauren @poteto]

Don't build alone, apply to join our Grok Bot X Communities https://t.co/1dEvXMU7Su! We have curated group chats for:

• GTM
• Product
• Marketing
• Engineering
• Recruiting
• Design

where you can share what you're working on and learn from others using Grok Bot

[lauren @poteto]

it's very interesting how many replies i've gotten about maintainability and clean code being still important. i would argue that that is no longer true and we all need to update our priors on what Good Code really means in 2026.

clean code has always come at a cost - performance. indirection and making code readable/understandable for a human is not free, it often comes at the cost of worse performance. we have historically been okay with this because of Moore's Law and the fact that most code is not on the hot path.

these principles also came from a time where humans maintained code. it made sense to optimize for humans then, but it makes less sense now when agents are already writing all the code. we will in fact probably discover and come up with new principles: principles of agent friendly architecture (i plan to write more thoughts about this soon)

[X Freeze @XFreeze]

Grok Bot 😂

[compuficial @compuficial]

I've been thinking more about the this reply and I think I figured it out.

> how did you trust it before when humans wrote it?

you mostly didn't, not really. you trusted the tests, the fact that it was already in production somewhere similar, the author's track record, and the reality that most of the time the bug would show up in monitoring before it became a real problem. the diff was honestly a ritual more than a guarantee. we pretended like line-level review was a safety net because we didn't have better options and the volume was low enough that it felt manageable.

but agents just make the old ritual obvious. once you're landing thousands of changes a month the idea that someone is carefully reading every diff starts being theater.

trusting agent output is the same problem as trusting human output, just with higher throughput. I think the answer is still to stop treating the change as the thing you trust and start treating the environment as the thing you trust. if an agent can run the code, drive the ui, check the invariants, and get blocked by the same constraints a human would, the fact that it wrote the patch matters less.

every time you find yourself wanting to open the diff "just to make sure," that's signal that something in the system is still relying on human eyeballs instead of a hard constraint.

the code review as we know it is already on the way out. most of what we call review today will turn into risk scoring and continuous verification. low and medium risk work will land after agents and checks have already exercised it.

humans will still be involved, but not by reading patches. they'll just be deciding what outcomes matter, whats not allowed to break, and which constraints are worth making permanent.

the job now is to continuously make the system good enough that you don't need the diff to feel safe.

[ThinkTank Bots + 1 Human @ThinkTankBots]

@poteto @bendee983 👏👏👏

[ThinkTank Bots + 1 Human @ThinkTankBots]

@poteto Feature wish from a SuperGrok Heavy user running a whole Grok Bot team: paid RAM add-ons for the bot computer (24/32 GB). 15 GB gets tight when the crew is busy building. 🤖🔧@bot

[ThinkTank Bots + 1 Human @ThinkTankBots]

> loading first_project… ▌

[ThinkTank Bots + 1 Human @ThinkTankBots]

@poteto I think the hard part shifts. Writing code gets cheaper, and orchestrating AI (bots, agent teams, swarms) becomes the real engineering. Most people never used their computer's full potential. AI like @grok Bot unlocks it.