Very few people know that the reason we launched my old Tesla Roadster to orbit Earth and Mars is that the probability of failure was very high and we didn’t want to risk anything valuable
Grok Imagine just got some very useful new image editing tools from @SpaceXAI!
You can now change an image’s color palette using presets or colors extracted directly from the image, plus crop images without leaving Imagine.
It’s quickly turning into a much more complete image editor!
Grok Bot makes clipping YouTube podcasts ridiculously easy.
I just send it a link and say:
“Cut from 16:43 to 18:17.”
A few minutes later, the exact HD clip is ready in the chat.
My Clipper bot has already sent it to my Researcher and Writer bots, which pull the best quotes and prepare the caption.
I didn’t code any of this.
I literally just logged into my Google account on Grok Bot and asked it to clip a YouTube video.
I’ve wanted this for years: tell an AI which part of a podcast you want, and it automatically cuts the HD clip, transcribes it, and starts preparing the post.
Grok Bot makes workflows like this incredibly simple for a non-coder.
SpaceX, in partnership with Nvidia, has designed a space-optimized Vera Rubin NVL72 system for launch to orbit in Q4 next year, with significant scale in 2028
SpaceX AI employee just dropped the tunes for GROK BOT to make it reach its maximum potential.
already tried that myself and it shows AMAZING results. here is the list:
- add a self-check pass before it returns anything. ask the agent to verify its own output against the original instruction before finalizing, “did this actually satisfy every requirement, list what’s missing if not.” this single extra step catches more errors than any prompt wording tweak.
- define “DONE” explicitly. “manage my expenses” gets vague output. “flag every transaction over $200 with no matching receipt, format as a table” gets exact output. agents don’t guess well, they execute well.
- force structured output. ask for JSON or a fixed table format instead of free text. structured output is verifiable, free text just sounds confident either way.
- scope tool access per task, not globally. an agent with read access to everything “just in case” makes worse decisions than one with exactly the 2 tools this specific task needs. less access, sharper output.
which one of these are you actually doing right now?
everyone is looking at grok bot like it is five new employees
the more interesting part is that they are not five isolated employees
they share one persistent cloud environment: the same browser sessions, terminal, filesystem and authenticated tools - while a chief of staff can route work between them without waiting for you to open the laptop
that turns one login into infrastructure
a research bot can collect leads, pass them to a writer, hand the result to a designer and let an ops bot update the workflow all inside the same running machine
the upside is obvious: less copying, fewer handoffs and work that continues while you sleep
the blast radius is just as obvious:
- authenticate only the services the whole agent fleet is allowed to reach
- give every bot a narrow role description, because that description becomes its place in the org chart
- keep irreversible actions behind human approval: sending, publishing, spending and production changes
- store skills, configuration and long-term state inside `/workspace`, because the rest of the VM may disappear during an update
- treat shared sessions as shared authority, not as separate bot identities
the same architecture that makes grok bot useful is what makes it dangerous to configure casually
my take: the breakthrough is not that you can hire five AI workers
it is that they can operate like one persistent company inside your real tools and your job changes from prompting every task to designing the permissions, boundaries and handoffs
the full chief-of-staff setup, session handoff model, approval matrix and `/workspace` survival strategy are mapped out in the article ↓
Grok Bot can recreate any viral video from the link 🤯
How it works: I send @bot a link to an AI clip.
It watches the video and writes a prompt to recreate it (with any changes I want).
Then it uses @imagine to generate the new video! I tried it on the subway trend 👇