Loading video...

Video Failed to Load

Go Home

BREAKING: SpaceXAI has launched the Grok Bot Marketplace, making it easy for anyone to add ready-made AI teammates to Grok Bot. • 69 public bots • 43 creators • 10 categories • Easy one-click installation It includes bots for engineering, marketing, operations, sales, recruiting, design, product and more. SpaceXAI...

83,423 views • 14 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

whoever leaked this has bigger balls than sense SpaceXAI shipped five hireable workers for $200 a month, then wrote the catch into its own Grok Bot documentation and left the page up: all five run on one computer, so one sign-in hands the browser session, the files and the command-line credentials to every one of them the NSA, CISA and the cyber agencies of the UK, Canada, Australia and New Zealand had published the opposite instruction 103 days earlier: no broad or unrestricted access, low-risk and non-sensitive work only i ran four of mine on one account for a week, counting what each could reach: eleven signed-in apps, one browser profile, and deleting a bot left all of it standing Grok Bot is worth hiring five times over, and you can draw its blast radius before the second one exists: - sign in for the bot that needs the site, then open the others and see what they reach: that session is theirs the moment it exists - give each bot its own account on the app, since the docs tell you in writing to stop using separate bots as a security boundary - put the stop line in the description, as an approval controls the proposed action and leaves whatever already ran where it landed - cap the spend outside the product, because there is no bot-specific spend cap yet and the audit view of what they did is still coming - keep the money and the customer replies in your own hands, and let the other four start from scratch each morning on work that cannot bite one sign-in is also why this pays: five names finish inside your real tools instead of handing you drafts to paste my take, and it is the uncomfortable one: your real limit on Grok Bot is how many logins you will put on one machine, and the hiring was always the easy half bookmark this, the five descriptions that let bots hand work to each other and the one folder that survives an update are written out in the article ↓

Argona

695,630 views • 1 month ago

I'M SHOCKED – ALMOST NOBODY IS USING GROK BOT THE RIGHT WAY. A LEAD ENGINEER AT SPACEX AI JUST DROPPED A 1-HOUR COURSE ON HOW IT'S ACTUALLY DONE. HERE'S ALL OF IT IN 60 SECONDS. The mistake almost everyone makes: they hand Grok Bot random one-off tasks. That's it. That's the whole reason it still feels like a chatbot to you. Here's the system he teaches instead – five parts: → ROLE – stop assigning tasks, create permanent roles. Chief of Staff, Inbox Manager, Researcher, Developer, Reviewer. A bot with a job title beats a bot with a to-do list → TOOLS – connect each bot to what it actually needs: Gmail, Slack, Calendar, Notion, GitHub. It does the work on its own persistent cloud computer → SKILL – teach it your workflow. Write the instructions, or just record yourself doing the job once – Grok Bot turns that demonstration into a reusable skill → ROUTINE – anything you repeat becomes a routine. It runs on a schedule or fires off an event, with your laptop closed → TEAM – group the bots together. The lead bot delegates, the specialists work in parallel, and you set approval rules before anything sends an email, moves a calendar or pushes code The one honest catch: a new bot still needs context and some hand-holding on its first few runs. But that's the entire system. Role → Tools → Skill → Routine → Team. Everyone else is still typing one-off prompts into Grok Bot and wondering why nothing compounds. Bookmark this & read the full breakdown in the article below ↓

SCOTTY BEAM

97,697 views • 27 days ago

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 ↓

monokern

1,016,600 views • 28 days ago

WTF, GROK BOT JUST MADE AI AGENTS AVAILABLE TO LITERALLY ANYONE – CREATING CONTENT HAS NEVER BEEN THIS EASY, EVEN IF YOU'VE NEVER MADE ANYTHING BEFORE Content was never a talent problem. It's a headcount problem. One person doing research, design, copy, analytics, timing and publishing – that's six jobs. The switching between them is what kills consistency, not a lack of ideas. Here's what one of these setups actually looks like. A Chief of Staff sits in the middle and routes every task. Nothing lands on the human. → Researcher tracks what's actually moving and pulls real sources instead of guesswork → Writer turns that research into finished copy, ready to review → Visualiser gets fed a few reference visuals once, then ships everything in that style → Analyst reads the numbers and tells the rest of the team what worked → Scheduler owns timing and holds the queue → Publisher ships it The part that makes it work: every agent on Grok Bot gets its own persistent computer, browser and file system – and they all share memory. So the research is already sitting inside the draft before the draft starts. No copy-pasting between tools. No approving every step. No human in the middle. You can even teach an agent a repetitive task by recording yourself doing it once. Start recording, do the thing, stop. It learns the pattern. And that's the real shift. Nobody needs AI to tell them what to post. They need it to delete the 40 steps between the idea and the post. Everyone has a backlog of things they've meant to make for months. This is what starts clearing it. Full breakdown of the setup in the article below ↓

SCOTTY BEAM

4,818,742 views • 1 month ago

so I wired Nous Research Hermes Agent up so it can live as a Grok Bot GROKBOT inside the grokbot app (private net / Tailscale). two ways, pick based on how your Hermes host runs: Hermes SSH Relay — Desktop-primary, no API gateway. SSH ask-relay, simplest “talk to hermes from inside grokbot app”. Hermes API Fleet — gateway + native API on :8642. better when you want parallel fleet asks / less hop overhead. same repo ⬆️ (docs for both) Grokbot Bot Templates: Hermes SSH Relay: Hermes API Fleet : what it unlocks: chat your hermes agent from grokbot UI, run herdr-style fleet ops from one place, keep hermes brains on the Mac while grok handles the front door. top 3 uses we care about: • identity bots per host so you always know who you’re talking to • easy orchestration across the Hermes fleet without jumping SSH by hand • bridge + connector pattern for hermes ↔ grokbot comms without stuffing secrets in the template Ps, imho: Dont point grok at writing into hermes memory plugins unless you mean to. (I let mine READ hermes Hindsight memory but not write to it) With this I now have a single CHIEF OF STAFF I talk to as a grokbot who orchestrates across 7 hermes machines, and 20+ grokbots, all running various coding harnesses, AI pipelines, GTM, AEO/SEO/GEO, UGC, seamlessly. I'm even having grokbot tell my chief Hermes Agent to run long horizon kanban goals. I'm also using a dedicated bot to keep my entire hermes fleet updated, maintained, pruned, local LLM optimized etc. I'll drop some of those templates over the next few days... follow with notis. Oh and shit a token usage window maximizer I'll share soon...burning it in this week, so far, have been blasting at 10x the rate across a dozen harnesses/subs. This is greatest unlock EVER in 7 months of harness jockeying. I am finally ONLY a HUMAN making decisions, ideating, all via a single grok bot Chief of Staff. Valhalla!

PixelRainbow

58,835 views • 3 days ago