Marco d'Amore (@mdamore9)

We hear all your feedback, especially on usage limits and model routing and will be improving things overnight. Over the coming weeks many improvements to the harness and routines will further enable you to get much more out of each subscription. @bot team is dedicated to bringing you the very best product in a way that is also sustainable - it’s on us to make that possible

Elon Musk Verified account @elonmusk 2d

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.
View quoted post on X

Marco d'Amore @mdamore9 Oct 23

damn @poteto

Marco d'Amore @mdamore9 Oct 11

“really small focused team working on it” —> “just 200 people”

David Senra Verified account @davidsenra Oct 11

Meta built Muse with just 200 people.

“The whole executive team, everyone knew that this was probably going to be one of the most important products that Meta would ship this year.”

“But we had the restraint organizationally to make sure it was a really small focused team working on it... because we knew it was a single work of art.”

“This is even now starting to plague a lot of the AI labs. They become this Frankenstein, almost Cronenberg amalgamation of a bunch of different people's points of view.”

“It's sort of like PM hell, where every PM has a thing that they're trying to jam into the product.”

“Muse had to be the exact opposite. There's one clear point of view.”

— @alexandr_wang

View quoted post on X

Marco d'Amore @mdamore9 Oct 8

After my onsite interview at Cursor I remember telling my wife "these people are so ambitious it actually rewired my brain"

lauren Verified account @poteto Oct 8

you should be more ambitious
way more ambitious
View quoted post on X

Marco d'Amore @mdamore9 Oct 7

@bot team keeps cooking with @bot

lauren Verified account @poteto Oct 6

i just automated our release and QA process!
using Grok Bot i made two Team Bots: sandcastle, my release manager, and poteto, my engineer bot. i added them to Slack and made a new channel for managing releases.

first i tell sandcastle that i want to do a cut. it'll DM all the contributors with links to their PRs so they know what goes in the next release and can DM the bot back if they have any blockers or objections.

sandcastle then kicks off the build, watches it automatically, and starts up an automated fuzz swarm. usually this is 10+ agents running on Grok 4.7 xhigh to run the build, click around and use it like a real user (using our verification skills and feature map), some are directed while a few are "chaos monkey" clicking things randomly to see what breaks.

whenever it finds an issue, i tell it to @ mention my engineer bot poteto, to spin up a Cursor Project to own triaging and fixing all the high pri issues. depending on the severity i may ask it to cherry pick the fix into our release branch and cut a patch release, or if it's a pre-existing issue i still fix it but include in the next release instead

that's one more tedious task that Grok Bot now handles for our team

View quoted post on X

Marco d'Amore

Latest posts 5