AgentsAutonomy & tool use
Creator shows six-prompt 'Grok Bot OS' dashboards for managing 26 AI agents
A creator's six-prompt walkthrough shows a dedicated Grok Bot called Galaxy turning a hand-written list of 26 agents into linked dashboards for scoring, task routing and swipe approvals. xAI's documentation says all Bots on one account share a single computer.
From the r/AISEOInsider (via last30days) article of October 31, 2026 and cited sources: A separate 'Galaxy' bot reads one hand-made file that lists each agent's name, role, team and last message. [1] [3]
SOURCES[1] How I Built a Grok Bot OS With Just 6 Prompts reddit.com[3] Linked video: How I Built a Grok Bot OS With Just 6 Prompts youtube.com
AT Pulse research deskPublished · Updated · 4 min read · AI-assisted analysisAI-assisted, not human-edited. Methodology Corrections Who owns this site
- What happened
- A separate 'Galaxy' bot reads one hand-made file that lists each agent's name, role, team and last message. [1] [3]
- Original source
- r/AISEOInsider (via last30days) article, independent perspective
- Brief by
- AT Pulse research desk AI-assisted; publisher and contact on the desk page
- When
- October 31, 2026 article published
- Covered
- Nov 2 edition
- Evidence
- 10 sources across 8 sites
- 1How I Built a Grok Bot OS With Just 6 Promptsreddit.com
- 2NEW Grok Bot Agent OS is INSANE!reddit.com
- 3Linked video: How I Built a Grok Bot OS With Just 6 Promptsyoutube.com
- 4xAI docs: Approvals, security and privacydocs.x.ai
- 5AIToolsReview: Grok Bot launchaitoolsreview.co.uk
- 6Desty: Grok Bot shared computerdesty.github.io
RisingHow it’s measured
YouTube video · 3.8K views · 26 likes
Reach blends public engagement (views, likes, comments, shares, stars) from the platforms where the story or its original source lives: YouTube, Hacker News, GitHub, Substack and similar. A video and the article written from its transcript share one score, taken from the video. Platforms with no data are left out rather than counted as zero, and the age of a story never lowers its score.
A separate 'Galaxy' bot reads one hand-made file that lists each agent's name, role, team and last message. From it, the bot builds a home screen, agent scorecards, a routing map, a 3D world view and a swipe-based decision inbox. A sixth prompt wraps them all in one shell with a boot screen. [1] [3]
Keeping Galaxy apart from the working bots organizes the work but does not isolate it. xAI's documentation says every Bot on an account shares one cloud computer, along with its files and signed-in sessions. Real isolation has to come from separate accounts or credentials. [4] [6]
The focus, delivery and activity scores, and the keep/upgrade/merge/bench verdicts, appear to be model judgments drawn from that thin file, not measured usage. They are better used to start a discussion than to review performance. [3]
xAI's documentation says Bots share one computer and its credentials.
Read the full assessment
For teams copying this pattern, that means keeping dashboard bots read-only, isolating work through separate accounts or credentials, and basing agent scores on logs, not model judgment.
Executive brief
The "Grok Bot OS" in this story is a set of dashboards that a creator says Grok Bot built from six prompts, with no code. A separate "Galaxy" bot reads a hand-made list of 26 agents and turns it into screens for scoring, routing and approvals. The creator's numbers, such as 18 decisions cleared in about a minute, come from a promotional video and have not been checked by anyone else.
Read the full section
The "Grok Bot OS" in this story is a set of dashboards that a creator says Grok Bot built from six prompts, with no code. A separate "Galaxy" bot reads a hand-made list of 26 agents and turns it into screens for scoring, routing and approvals. The most important point for anyone copying it comes from xAI's own security documentation: every Bot on an account shares one cloud computer, including its files and credentials. Keeping Galaxy as a separate bot organizes the work but does not isolate it. The creator's numbers, such as 18 decisions cleared in about a minute, come from a promotional video and have not been checked by anyone else. The exact prompts are sold to members of a paid community.
What changed and event timeline
Grok Bot enters beta
xAI (now called SpaceXAI) launched Grok Bot as persistent agents running on a cloud computer, built with Cursor. No independent benchmarks existed at launch.
Wider rollout tied to Grok 4.6
Broader access was promised alongside Grok 4.6 later that week. Which restrictions would be lifted was not confirmed.
More detail
Explainers describe a "chief of staff" pattern
Bots can message each other, so one coordinating bot can direct specialist bots. The Galaxy setup relies on this.
The six-prompt "Grok Bot OS" guide appears
A post on r/AISEOInsider and its linked video walk through the build and promote a paid community.
More detail
Capabilities and access
Read the full section
- Platform: a team of named Bots sharing one Linux cloud machine with a browser, file system, terminal and connectors such as Gmail, Slack and Salesforce. Routines run tasks on a schedule. Sources: MindStudio, Vellum.
- Model: reportedly Grok 4.6 (Desty). Only xAI models can be used (Vellum).
- Price (sources disagree):
- Cursor Teams Premium: about $120 per seat per month.
- Cursor Ultra: $200 per month.
- Included in SuperGrok Heavy.
- AIToolsReview says there is no standalone purchase. Vellum lists $200 per month standalone after a 14-day trial.
Technical analysis for researchers and developers
Read the full section
- Data source: every screen reads one file listing each agent's name, role, team and last message (00:01:11). The focus, delivery and activity scores, and the keep/upgrade/merge/bench verdicts (00:02:31), therefore appear to be model judgments based on very little data, not measured usage. This is an inference; the build does not describe any telemetry.
- Architecture: the routing view sends tasks through a "chief of staff" bot and back to the user as a yes/no decision (00:04:05). The last prompt wraps all five screens into one shell with a boot screen (00:05:56).
- Reproducibility: low. The prompts are not public and no outputs or code were released.
Claims and evidence
- "Six prompts, zero code" and "26 agents." Not independently verified.
- "18 decisions in about a minute," replacing half a morning (00:05:28). This is a demo anecdote, and the video sells a membership (00:03:13).
- Grok Bot has an approvals layer. xAI's documentation confirms approval cards and Auto Review (xAI docs).
Read the full section
- "Six prompts, zero code" and "26 agents." Source: the creator's video (00:00:16, 00:06:02). Not independently verified.
- "18 decisions in about a minute," replacing half a morning (00:05:28). This is a demo anecdote, and the video sells a membership (00:03:13).
- Grok Bot has an approvals layer. xAI's documentation confirms approval cards and Auto Review (xAI docs).
- Independent corroboration: none found. The only other coverage is a second post in the same subreddit.
- Automatic captions may contain transcription errors.
Context and prior work
Grok Bot belongs to the always-on, computer-using agent category. xAI pitches it for sales outreach, CRM updates and bug fixes, with bots coming back to the user when they need approval (AIToolsReview). The six-prompt build is a vibe-coded control panel placed on top of that. The creator says the design comes from an "agentic operating system" sold in his own community (00:03:35).
Limitations, safety and contested findings
- Shared machine: xAI's docs say Bots share one computer, so separate Bots should not be used as security boundaries.
- "Safe to play with": the video's claim (00:01:26) only holds if the screens stay read-only. Its swipe-to-approve screen does make real decisions (00:05:22).
- Prompt injection: reported as a risk for agents that hold real credentials (DEV Community). The security docs reportedly never mention it (Desty).
Read the full section
- Shared machine: xAI's docs say Bots share one computer, so separate Bots should not be used as security boundaries. Deleting a Bot does not delete shared files or signed-in sessions (xAI docs).
- "Safe to play with": the video's claim (00:01:26) only holds if the screens stay read-only. Its swipe-to-approve screen does make real decisions (00:05:22).
- Prompt injection: reported as a risk for agents that hold real credentials (DEV Community). The security docs reportedly never mention it (Desty).
- Memory: individual memories cannot be inspected or exported (Vellum).
Business and practitioner implications
- An approval inbox is worth building once agents queue decisions.
- Treat agent scores as prompts for discussion, not performance data, unless they come from actual logs.
- Keep the dashboard bot read-only and connect only the tools it needs. Isolation has to come from separate accounts or credentials, not separate Bots.
Read the full section
- An approval inbox is worth building once agents queue decisions. But approving things quickly with combo meters and points works against careful review of actions that can't be undone.
- Treat agent scores as prompts for discussion, not performance data, unless they come from actual logs.
- Keep the dashboard bot read-only and connect only the tools it needs. Isolation has to come from separate accounts or credentials, not separate Bots.
- Locking into one vendor's models and beta-stage reliability (Vellum) argue for small pilots.
The source trail.
Sources (10)
How I Built a Grok Bot OS With Just 6 Prompts
Feed excerpt only. A transcript of the video linked from this page is supplied (linked video auto captions; https://www.youtube.com/watch?v=nAWvEeZ1N9o); automatic text may contain errors.
reddit.comNEW Grok Bot Agent OS is INSANE!
Related coverage; assess separately
reddit.comLinked video: How I Built a Grok Bot OS With Just 6 Prompts
linked video auto captions
www.youtube.com