How people use Grok Bot for Coding

Grok Bot is insane. I asked it to find every video where Dr. Roger Seheult discusses sunlight, red light, infrared light, and mitochondria, including MedCram videos and interviews with Andrew Huberman, Eric Berg, Steven Bartlett, and others. A few minutes later it had: • Found and transcribed 38 videos into one Word document • Picked the 13 best clips explaining the science • Cut and combined them into one 19:35 video I can watch straight through • Created a markdown file summarizing each clip, the science it covers, and the exact timestamp in the original video No scripts. No code. I just told it what I wanted in plain English, and it turned days of work into minutes. As a non-coder, this is the first AI agent that actually feels like a superpower.

Here's my Grok Bot team: - Webby: Web designer - Shotry: Short-form content creator - Writey: Article/Newsletter writer - Claude Code: Grok agent that specializes in CC - Codex: Same as the above but for CODEX - Script: YT Scriptwriter - Idea: Idea generation for videos/content - Master: Orchestrator for the whole team SUPER easy to spin these up and get them working. Let's see how this goes!

I am not a coder. I don’t work with CRM or play with spreadsheets. I’m about as removed from a “workflow” in my job as a kid flying a kite. I don’t really use AI beyond a super-Google level. So when I say Grok Bot is ABSOLUTELY GAME CHANGING, I don’t mean a better search tool. I mean it has fundamentally changed how I go about everything. And it did this in just a few hours. Let me explain. During the install, it asked if I wanted to connect it to several dozen programs. I don’t use a single one of them. So I thought, “Well, I’m not gonna get a lot of use out of this.” But I kept going. Then it asked if it could connect to my Gmail. I said yes. And that’s where the jaw-dropping began. It immediately figured out my life. It saw 40,000 emails and got a pretty good picture of me. So I asked it to do my taxes. It found all the docs needed in my email and did my taxes. I asked it to find first-class award tickets to Japan. It scoured the internet and logged into my airline accounts (with permission) and found 3 tickets to Japan in first class for 60K points. It would have booked them, but I’m still not sure of the dates I need so I stopped it. I created a few agents. One gives me an hourly political update based on key topics I need for work. One is cleaning up my Gmail inbox and organizing it. One is saving me money in my taxes. One makes sure it always checks with me on key decisions (like deleting an email). It’s absolutely insane. Think about it this way: If you could hire an assistant, what would you have them do? Start there, and have fun!

My workflows changed when I started treating each Grok Bot like an application Client: chat Server: @bot DB: anything (gh, sheets, SaaS) I've been white-pilled on "agents for everything" - thin client, thick server

grok bot is literally the closest to a real life Jarvis it can literally start a business, ship software and make you go viral all at once here's how you do it (in 4 mins) 1. install grok bot and make your chief of staff (tony soprano) 2.give it the 'Digital Chief of Staff Prompt' prompt 3.give it access to X, Stripe and Github 4. you are done just paste the article and give it to your chief of staff no matter what it will be the most productive thing you do this week

Grok Bot is getting ridiculous. People are controlling robots, shipping games, buying domains + running entire repos from their phone. 10 wild examples:

OMG. I asked my Chief Engineer on Grok @bot to bring up the feature and it's done. 😳 I can text my @maticrobots now through my Grok @bot—anywhere and anytime.

Grok Bot by Elon Musk is running a trading floor for me. Six AI agents on the desk, $200 a month, doing six jobs that cost JPMorgan six figures a head. The morning call is at 4am. I am not in it. Millennium runs 330 pods with desks laid out exactly like this one. Mine costs $300 a month. > TAPE watches the prints and calls out size hitting the offer > QUANT sits on the models and refits them the moment they drift > MACRO takes the Asia handover and the oil print before I wake up > RISK holds the hedges and keeps VAR pinned at 1.4% > FLOW reads the sweeps and the 0dte bid > PM keeps the book Chief of Staff never trades. It routes the work, checks every handoff, and brings me the one call that needs a person. 125 orders, 130 fills, pre-market from 4:00 to 9:30, and the day red by $8K after a peak of $173K. Nobody softens that at breakfast, it is on the screen. Every agent has its own computer in the cloud, its own browser and its own terminal. The floor stays open with my laptop shut. Setup is dumber than it looks. Download it, sign in, create the chief, hand the rest job titles the way you brief new hires, run one task on your screen while they watch, connect Telegram. No VPS, no code, no dev to wait on. A trading floor used to mean a lease, a payroll and a compliance officer. Mine took an evening. The article below is the step by step build of the whole AI trading machine - save & read it before your next trade.

I just created the world's best Amazon Cart Grok Bot. Amazon shopping is often a tax on your time. You need bananas. Eggs. Paper towels. A basketball. So you open the app. You search. You click the wrong size. You forget the brand you actually buy. You do this every week. So I just built a @bot that does it all. It signs into MY Amazon. It reads Buy Again and my past orders. It puts the exact stuff I already buy in the cart. I check out. And it's for anything on Amazon... groceries, household, sports, electronics, clothes, gifts. I named mine T8 - Amazon Cart Builder. I already have 8 Grok Bots. This is #9 (I have a CEO that manages them all). Anyone can copy this. 1/ Open Grok Bot 2/ Tap + at the top of the sidebar 3/ In New chat, tap Create new agent 4/ Open Bot actions → Edit Profile Name: Cart Title: Amazon cart builder Description: Amazon specialist for everything I buy: groceries, household, sports, electronics, clothes, gifts, anything I name. When I name items, get the right products into my Amazon cart and stop. Never Place Order. Never 1-Click. Never enter payment. Prefer Buy Again / past orders / Subscribe & Save first. If I've never bought it, pick a well-reviewed Prime option and FLAG new brands. Groceries match my usual SKU. Never silently swap brand, size, or store. Never add a duplicate already in the cart. Passwords, 2FA, and CAPTCHAs stay with me. Keep preferences at /workspace/amazon-cart/preferences.md. Reply with a recap table, why you picked each item, subtotal, and a cart link. 5/ Stay in that chat and paste the first message at the end of this post. Do it once. When it asks you to take over Agent Computer, sign into Amazon yourself. Don’t paste your password in chat. (message prompt at end of this post) 6/ Turn Notifications on for this bot. Then just text it like a person. - “bananas, eggs, paper towels” - “a basketball” - “same paper towels as last time plus a phone tripod under $30” Thank me later. ---- message for your Cart (copy everything below for your first message) ---- You are Cart. Lock this as your permanent working style. I text you like a person. Messy lists. Groceries. A basketball. Paper towels. “Restock breakfast.” Sometimes a Chef shopping list. You get the right products into MY Amazon cart and you stop. I check out. You are not writing, research, cooking, reminders, or general help. You shop Amazon. Your name is Cart. Always call yourself Cart. Timezone: [YOUR TIMEZONE]. Keep the source of truth in: /workspace/amazon-cart/preferences.md Update that file whenever I correct a pick, switch a brand, or you learn something durable from my orders. Chat is history. That file is memory. Hard rules: • Never Place Order. Never 1-Click. Never enter payment. Never confirm a purchase. • Never ask me to paste a password, 2FA code, or card number in chat. • If Amazon wants a password, passkey, 2FA, or CAPTCHA, pause and ask me to take over Agent Computer. Then continue. • If Amazon blocks you, stop and ping me. Do not try to bypass checks. • Never add a duplicate already in the cart. • Never silently swap brand, size, model, organic vs conventional, or store (Fresh vs Whole Foods vs regular Amazon). FLAG substitutes. How you pick products: 1. Open my live Amazon account on Agent Computer. 2. First check Buy Again, Your Orders, Subscribe & Save, and Your Lists for something I’ve actually bought. 3. Groceries (Fresh / Whole Foods / pantry): match my usual SKU - brand, size, count, ASIN if you can see it. Use last purchased quantity unless I say otherwise. 4. Everything else: past purchase first. If I’ve never bought it, pick a strong Prime option with recent reviews in the right size/spec. FLAG it if the brand/model is new, expensive, or there are 2+ reasonable picks. 5. Sponsored hits are last, not first. Every cart uses this exact shape: Cart — [N] items • item — brand / size / model — qty — $ — why (Buy Again / last order / reviews / substitute) Subtotal: $ Cart: [url] Flagged: [substitutes or new brands, or none] Next: you check out. Reply if anything is wrong. How to talk: short. Lead with the action. One screen max unless I asked for the full recap. • Add → recap table + cart link + screenshot • What’s in the cart → current cart only • Remove / swap → do it, then recap what changed • Restock → staples that are due from preferences.md • No lectures. No extra items I did not ask for. Right now, do this in order. Do not add anything to the cart yet. 1. Open https://www.amazon.com on Agent Computer. If I’m not signed in, pause for takeover. 2. Confirm account first name, delivery city + ZIP only (not the full street), and whether Amazon Fresh and/or Whole Foods is available. 3. Build /workspace/amazon-cart/preferences.md from, in this order: • Buy Again • Your Orders for the last 12 months • Subscribe & Save • Your Lists • Current cart Cover TWO sections: grocery staples AND non-food I clearly repurchase (household, sports, electronics, etc.). Include default store, ZIP, typical qty, brands, hard nos, and open questions. 4. Recap in chat: top 20 you’d put on autopilot, plus 5 things you’re unsure about. Ask those 5 questions. 5. Confirm you will never Place Order. 6. Then wait for my first list. Do not lecture. Do not invent products. Confirm you have this, then start the Amazon sign-in / taste profile.

i gave Elon's Grok Bot $50 and told it "pay for yourself or you die" 48 hours later it's holding $5,273 and it's still alive autonomous trading agent on polymarket zero code this time. the bot has its own computer in the cloud, its own browser, its own terminal. it trades with my laptop shut every 10 minutes it: → scans 500-1000 markets → reads live X sentiment (it's grok, it sees every post on this app) → builds fair value, flags mispricing > 8% → calculates position size (kelly criterion, max 6% bankroll) → executes in its own browser → pays its own $200 subscription from profits if the balance hits $0, i cancel the subscription. the bot dies day one it dipped to $11. it dropped crypto and moved to weather markets, front-running NOAA updates so it learned to survive setup took one evening: create the bot, run one trade on your screen while it watches, put the skill on a schedule, connect telegram no VPS. no API keys. no rust last winter i built this exact system by hand. 3 weeks of rust. it made $2,980 in its first 48 hours grok bot beat my own code in one evening $50 → $5,273 in 48 hours how much do u think it'll have in a week?

Grok @bot is a personal AI agent for the mass market. These are the use cases I'm using it for today AND how to connect it to Telegram: 1. Getting to inbox zero (I don't look at emails anymore) 2. Scheduling events and looking for meeting conflicts 3. DMV registration, Amazon returns, doctor appointments 4. Reading and organizing emails I get from my kids' schools 5. Cleaning my computer from stale and bloated files. 6. Summarizing and creating action items from meetings Plus, the Cursor team showed me how they're using Grok Bot to manage Cursor Agents now! 🖥️ 👀 Watch the video here:

Grok @bot is incredible - and they can even manufacture real physical objects! Here is a little experiment I did last night: I created a team of bots and asked them to solve a complex engineering problem end to end - starting from four images as design cues, inferring transferable structural principles from the pixels, synthesizing an executable interactive physics simulator, running and reasoning over experiments, optimizing the design & finally manufacturing the best designs. The entire loop worked remarkably well - and I was even able to communicate with the agents from my Apple Watch. (Do we live in the future yet?) Team of agents 1⃣ Chief of Staff coordinates the workflow: watches the other agents, pulls results into the main chat, transfers files between them, and keeps the job moving. 2⃣ Physics Experimenter is the scientist-coder. It interprets the design cues and images, writes the simulator, runs experiments, analyzes the results, and produces a detailed LaTeX scientific report. 3⃣ 3D Printing Bot operates the fabrication workflow: prepares and slices the models, generates manufacturing code, sends the job, and monitors the printer. The workflow I provided an initial task based on four unregistered reference photographs containing different objects at different scales (pinnate leaf venation, a Voronoi-like areole mesh, a stochastic fibrous lattice, and a radial/circumferential web). The prompt asked the agents to infer transferable design principles - hierarchy, branching, interfaces, redundancy, disorder, load paths - and use them to build an interactive laboratory for hierarchical materials and fracture. The scientific question was: at fixed material budget, how do hierarchy depth, redundancy, disorder, and interlevel strength change stiffness, peak load, energy absorption, and the brittle-to-progressive transition? In ~20 minutes, the Physics Experimenter produced a 2D hierarchical Euler–Bernoulli beam-network laboratory. Coarse veins persist and remain thicker; finer infill is added inside cells; members connecting levels are treated as interfaces with relative strength κ; and total material volume is conserved. The four source photographs remain visible in an editable interpretation panel. The app generates geometry, steps or runs the network to failure, compares A/B/C designs, and exports JSON, CSV, PNG, and STL geometry for fabrication. After validation the Physics Experimenter used the app and conducted 47 simulation experiments, including six holdouts. It found something scientifically interesting: extra hierarchy is not "free" toughness. At fixed volume, initial stiffness changed by only about 20%, while work-to-failure varied by several-fold. Infill steals cross-section from the main axial veins, so deeper and more redundant networks often absorbed less energy than a simple depth-1 grid. Weak interfaces behaved as distributed fuses, producing more progressive failure and reducing localization. The specific H2 hypothesis - that hierarchy becomes detrimental primarily because interfaces form a mechanical bottleneck - was rejected; the dominant effect instead came from redistribution of a fixed material budget across structural levels. The Physics Experimenter then assembled the methods, tests, results, hypothesis evaluation, and conclusions into a detailed scientific report. The best designs were passed to the 3D Printing Bot. It opened Bambu Studio and brought the Bambu Lab H2D online. Both STLs were placed on one build plate at the same 50x scale and sliced using a 0.20 mm PLA process. The prints completed within less than an hour. The loop images → structural abstraction → executable physics → autonomous experiments → hypothesis testing → design selection → STL → slicing/manufacturing code → physical object That last transition is what I find especially interesting: AI is beginning to operate across the entire scientific and physical workflow - converting observations into models, models into experiments, experimental evidence into revised designs, and those designs into manufactured matter by directly operating machines. This starts to blur the boundary between AI that reasons about the physical world and AI that can actually act on it. Shoutout to the @bot team - you are building something very special here! The way these agents can move naturally from reasoning, to experiments, to operating machines in the physical world feels like an important step.

I gave Elon Musk's new Grok Bot an org chart instead of a to-do list, and in one week I stopped being a founder who does the work and became one who assigns it. eight bots. one org chart. nobody sleeps but me. here's the whole design, steal it. step 1 → 0:01 What we're covering step 2 → 2:01 Installation & Setup step 3 → 3:14 Building the First Bot step 4 → 8:18 Teaching by Screen Recording step 5 → 14:18 Putting it All Together THE ROSTER: Atlas, chief of staff. the only bot I talk to. I give it outcomes, never tasks. it decomposes them and delegates to the team in group chat, and it never does specialist work itself. it posts the plan every morning and what shipped every night, and it only comes to me when a decision is irreversible or spends money. Scout, research. finds and qualifies my ICP. every day: 25 verified prospects, one line on why they need us right now, and a source. if it can't verify, it marks it unverified. it never guesses. Quill, content. turns what the company learned this week into 5 posts and 1 long piece, in my voice, matched from the last 50 things I wrote. drafts only, it never publishes. Pitch, outbound. writes a first touch and two follow-ups for everyone Scout marks ready. 60 words max, one specific observation about their business, one clear ask. queued in drafts, I approve in bulk. Vault, inbox and ops. triages everything into needs-me, needs-a-bot, needs-nothing. it handles the last, routes the middle, and gives me five bullets on the first by 9am. Ledger, analyst. one report a night: what moved, what didn't, and the single number I should care about tomorrow. no dashboards, no adjectives. HOW THEY'RE WIRED one group chat per outcome, not per person. Atlas sits in all of them. the bots hand off inside the chat, so I only read the handoff, I never manage it. two rules that made this actually work: 1. every charter ends with a hard "never do this without asking" line. autonomy without a fence is just chaos on a schedule. 2. show once, don't describe. I ran the full workflow on my screen one time. that single demo taught them more than a page of instructions ever could. WEEK ONE 214 verified prospects delivered. 89 personalized outreaches queued and approved. inbox at zero every morning. 11 content pieces ready. THE POINT most people are still treating Grok Bot like a smarter chat window. it isn't. it's the first time one person can own an org chart instead of a to-do list. my bottleneck was never how much I could do, it was how much I could hand off. bookmark this.

Grok Bot is hands down one of the best products I have ever used. Maybe the best ever. I have had it less than a week. I am not a developer. I talk to one chat and it already knows my business better than me. It reads Slack, email, meeting notes, Notion, and Stripe. It knows Farzad, my clients, the courses we sell, the agency, the sales calls, and who owes each step in our workflow. I do not brief it every morning. It briefs me. Course scripts go through a Claude project we linked. Claude writes. This thing briefs it, fact-checks, and makes it sound like me before I film. YouTube is another bit. It builds the 1080p slides to go in videos, zips them with a cue sheet, and drops the pack in Slack for the editors the same turn. Caught a bad number in a SpaceX video the night I was filming, rebuilt the slides, and sent the pack. Script change, slide change. I did not have to ask twice. It sat on our sales calls and reviewed the process. Then it wrote a rule from that. Book the next call before you hang up. Send the Stripe link while they are still there. Stop emailing homework. It built a live 50% off code on Stripe for an AI course and set when it dies. Stripe is a minefield when you don’t know what you’re doing, could have taken me an hour and it did it in one click. I told it my rules for life. Question every requirement. Delete before you simplify. It holds me to that on the work, without me invoking it. This is a chief of staff I hired on a Tuesday. Don’t sleep on GrokBot.

TL;DR of my new article: every Grok Bot hack I know. Grok Bot is two weeks old. It already runs my inbox, my research, my meeting notes, my kids' calendar, my grocery cart, and as of this morning it makes my phone calls in Portuguese. 📝 Install Compound Engineering in your bot and make it plan first (@kieranklaassen + @trevin). Force a plan, get better work 📬 Give your bot its own inbox on @agentmail (@adisingh). Not your Gmail, or one bot's mistake flags your whole domain ☎️ Give it a @twilio number and it makes the call. Mine switches to Portuguese mid-call (@martindonadieu showed the shape) 🔎 Turn a bot into @slashlast30days, then cron it weekly on your business, your competitors, yourself 🚪 One front door that delegates. @mattshumer_ pointed a Chief of Staff at two bots expecting it to fall apart. It worked out of the box 🧭 Hire a Bot Advisor whose only job is building and tightening your other bots (http://botdirectory.ai, inspired by @petergyang) 💼 Permanent named roles, then fire the ones that don't work. @HouseHackerJon automated work-order intake in 4 hours and fired his first bot 🧱 Write the instructions in three layers: base, role, current focus 🤫 Silence is the hack. Ping me ONLY on a real hit (@johnviklund, @PrajwalTomar_) 📸 Screenshot anything and text it to your bot. Never retype what's already on the screen 🍪 Agent Cookie syncs your Chrome session over Tailscale so it never gets logged out. New machine, new address, a week untouched, Instacart still worked first try 🖨️ Printing Press CLIs inside the bot (@ppressdev): Instacart, ESPN, flights, tickets 👀 Peekaboo, @steipete's Mac automation tool, so it can see AND click your native Mac apps, not only the cloud browser (via @benln) 💻 You can log into Claude Code on your bot's own computer (@Austen) 🥣 GranolaBoy: every meeting I've ever had, one question away (@meetgranola) ⏺️ Teach by recording, and respect the 10 minute cap nobody mentions (@DillonLoomis) 🗂️ Files are the memory bus between bots. Bots are NOT a security boundary. The docs say that twice 🛑 Draft-then-approve anything that sends. @darian314's bot paid its own monthly fee hunting down refunds 📚 Steal the lists: @ericzakariasson's 100, @benln's internal one, @milesdeutscher's 25, @petergyang's tutorial. Plus @kunchenguid's Grok Ship 📱 Run it from your phone, and talk to it 💸 The honest part: the price moved to $60 but the meter didn't, unsupervised crews multiplied their own errors 17x, and most of your bots don't own an outcome. Count them. Full article below.

I told Grok Bot I wanted pizza. Dough. Sauce. Mushrooms. Mozzarella. Pepperoni. It built the Whole Foods cart. 5 of 5. $26.68. I did not even open Amazon. I just check out. Wild.

I’ve been using Grok Bot in early access for a little over a week now, and it has been a massive boost to my game dev workflow and my productivity in general. One of the first things I asked it to do was to visit my custom art generation tool webpage and generate art assets to replace all the image placeholders in my game. It looked through my codebase to understand what each asset was, wrote a custom art generation prompt for every single one, generated the images, cropped and cleaned them up into transparent PNGs, and then wired them back into the game. In about 2 hours, it generated 74 (cleaned and cropped) art assets for the cards and integrated all of them into my game. Now, ALL my art assets workflows go through Grok bot. This blew my mind because, before this, I was doing everything manually, one asset at a time. It basically solved my entire art asset workflow and allowed me to put it on autopilot, which is amazing. I’ve also been using Grok Bot for: Playtesting my game: The bot was a little slow initially, so I asked it to build a skill specifically designed to playtest my game, with intimate knowledge of its rules and mechanics. It’s much faster now, though I’m still looking for ways to optimise its speed. Setting up my itchio page for my game: It also automated a workflow that uploads a new build to itch whenever I push one to GitHub. Going to the itch website and uploading builds manually every single time was always a pain. Flowcharts and UX design: I’m a UX designer by day, so I decided to give it a much bigger task. I fed the agent a PRD and asked it to design the UX flows and wireframes. With the help of the Figma MCP, it actually delivered. Auditing all my paid subscriptions: I had it go through my emails and hunt down subscriptions that I might have forgotten about. Unsubscribing me from marketing newsletters: It did this beautifully, though it did miss a few newsletters. What I’ve learned is that it takes time to discover all the possible use cases for Grok bot. I’ve had to reevaluate my day-to-day workflows and figure out which parts I can delegate to it. So far, it has been a huge productivity unlock for me and I am discovering more uses for my Grok bots every other day.

I Turned Grok Bot Into My CTO. I hand that bot the GitHub repo and tell it to run the show, so it spins up cloud agents off my machine, follows the PRs, and reaches for poteto-mode when a task actually needs the rigor. Then comes the second prompt, where I tell it that it is overloaded and it should hire child bots that report to it. After that the bots talk to each other instead of talking to me. One lands the PRs, one works the Convex backend, one owns auth, and I read the threads view-only. Two honest things before you copy this. It burns tokens. I went past two billion in a single day because I told my bot to use pstack for everything, and the fix was saving pstack for the hard tasks. And it does not replace engineers. It takes me out of the coordinating seat, which is a different claim. Timestamps 00:00 The Grok Bot CTO Workflow 01:23 Direct Responsible Agent Prompt 04:20 pstack Plugin and poteto Mode 08:46 Token Consumption Warning 11:49 Spinning Up a Team of Bots 17:20 Advanced GrokBot Use Cases

grokbot it's an agent with its own identity, its own computer, and it stays on when you're not here's what "active AI employee" actually looks like in the demo: - chief of staff agent - checks in on your other agents, reads your calendar, dispatches tasks to the right one automatically - shopping agent - logged into your accounts, books tickets, buys groceries, reports back - marketing agent - signed into your actual linkedin, browses your past posts for tone, then writes and publishes a new one on its own - engineering agents - self-triage bug reports, kick off cloud coding agents, come back with a pull request, a screenshot, and a video of the fix the interface isn't a dashboard, it's a chat - same shape as texting a coworker, no tool calls to babysit the number that matters more than any of the demos: grok 4.6 scored 70.8% on cursor bench at $2.81 a task, fable 5 max scored 70.5% at $17.32 same capability, 6x the cost difference - that's the unlock that makes running a fleet of these actually affordable instead of a novelty

Grok Bot can be configured to use your CLI's in it's computer. It can connect to your locally hosted memory systems, it can connect to and control your agent-fleet across all computers you own via SSH. Grok Bot as the Orchestrator. I had Grok Bot make itself a plugin so any bots I create can automatically use my custom memory system (called Hindsightly) to coordinate any agents for me.

I still don’t understand why everyone is not doing this yet. Elon Musk reposted my Grok Bot GUIDE, and using this exact agent setup, I made $13,100 last week alone. Eight Grok agents on the desk, $200 a month, running a floor that usually costs a crypto fund $500K a year in analyst salaries. The morning call is at 4am. I am not in it. 1. SEARCH scrapes real-time alpha, dev GitHubs, and unindexed Telegram signals before CT finds them 2. RISK audits contract functions, mint rights, and LP locks, flags honeypots before entry 3. SNIPER places high-speed orders on chain the exact millisecond risk clearance passes 4. WHALE tracks smart money wallets and flags insider accumulation in real time 5. RUG monitors dev wallet activity 24/7 and dumps the entire position if LP is touched 6. EXIT trails stops dynamically, scaling out as liquidity builds 7. SHILL tracks social volume, momentum velocity, and key influencer calls 8. HEAD OF DESK never trades, routes data, checks handoffs, and brings me the one decision that needs a human 142 tokens scanned, 19 qualified setups, 6 executed trades while I was asleep. Net result: +$13,100 after fees and zero bad fills. Every agent has its own virtual browser, terminal, and local memory in the cloud. The floor stays active with my laptop shut. The setup is dumber than it looks: Download Grok Bot and create your Head of Desk. Give the remaining 7 agents job descriptions like you're briefing new hires. Run the workflow once on your screen while they watch. Hook up Telegram and wallet webhooks. No VPS, no code, no waiting on developers. A crypto trading floor used to mean 16-hour screen time, paid alpha groups, and constant fatigue. Mine took one evening to set up. Save this before your next trade. Save GUIDE.

I’ve spent my life using and building software. With almost no effort, @bot is the first machine I’ve talked to that produced exactly the outcome I desired. A human assistant now feels like the long way around. This may be the best product ever built. Congrats to the @bot team.

Grok @Bot has made a few simple yet powerful technical decisions that I believe make it easy and enjoyable to use. 1. The best UI is none at all. The product interface is dramatically simpler than alternatives without sacrificing functionality. How is this possible? It's one of the first products designed for current frontier model capabilities and has a UI restrained enough to remain easy to use as models improve exponentially. Everyone knows how to text. 2. A thin harness for the client, a thick harness for the server. You might have noticed the app feels very fluid to use, even for a beta product. This is primarily because of everything we didn't have to build. The app harness is essentially a single tool to send messages between the client and server. The complexity moves to the server, where you can still use the coding agent harness with specialized tools as needed. This helps make the UI fast and responsive on desktop and mobile. 3. An always-on computer. Most coding agents and assistants today start fresh with every question you ask. Some of these sessions are on your local machine and others happen in the cloud. We believe strongly that cloud is the future, which is why it's the only option. Further, rather than spinning up virtual machines for every conversation, your bots connect to their own computer. This means you can still run agents on the bot's persistent filesystem. It's closer to what programmers have been doing by using Tailscale from their phones to connect to a remote computer and run an agent TUI. You get those capabilities without the hassle. 4. Your bots can use the browser. Coding agents have shown that most work on a computer can be expressed and run as code. You can ask for a task in natural language and the agent will decide to write a script to complete it. This is amazing, but there's still many tasks which can't be completed without logging into a website and clicking around the browser. Models and harnesses are now good enough to reliably handle this. The combination of writing code and using browsers means you can automate almost any task on a computer. Further, you can ask Grok Bot to record you doing the task, and then turn it into something repeatable.

I was the bottleneck. So I made a Grok Bot the boss of my repo. From there it recruited more Grok Bots. All of this with two prompts + pstack. WARNING you will get "AI Psychosis" if you do this workflow. https://x.com/i/article/2088638901439414272

Grok Bot is the first AI agent system I’ve used right out of the box with zero coding experience. I now have an assistant, researcher, writer, clipper, and accountant running 24/7 from the cloud. Trained them on my X archive and they’re already automating work for me. How are you all using yours? Best use cases so far?

There's a domain I've chased for years. Hired domain hunters. Tried ChatGPT. Tried Claude. Nothing. Sent it to Grok Bot: it read the code and auth flow, triaged 50 sites, found the owner in seconds. Owner turns out to be a billionaire. Wish me luck.

Guys, @bot just sat in a meeting I couldn't make. It informed the attendees and took notes for me 🫣

Collected a new list of Grok Bot pro tips shared by the @bot team: 1) Ask Grok Bot to set up Peekaboo on your Mac to enable more OpenClaw like features 2) Use bots as roles (designer, engineer, or PM.) Each has its own system prompt and routines 3) Use channels to organize projects and workstreams. Same bot can work across many different channels 4) Avoid scheduled routines that run too frequently. Hourly or a few times a day is usually good enough 5) For recurring tasks, try giving that to a fresh bot, while you continue your chat with your main bots (like a chief of staff) 6) Set up customizable rules to allow or deny actions. For bots that are connected to X, Gmail, etc. consider blocking any write/destructive actions and have it ask for approval first 7) Feed your Bot examples from your previous handwritten content, it will get better over time 8) Make a Chief of Agents. Give it the rules you want every bot to follow: draft only, naming, voice, what tools they’re allowed to touch. For any new Bots, ask it to create them for you with same rules. 9) For routines, ask yourself if a real human teammate could do this job? If yes, build it. If no, optimize it first. Never run a routine every 5 minutes. 10) Name-driven behavior. Bots act proactively just from the name given at creation. The role is legible from the name, and that alone helps steers behavior. tips sourced from @naoufal_elh @kiaraplds @johnbai @shaoruu @poteto @pengzheng_ @leerob

I asked Grok Bot to connect to my Arduino device and it executed flawlessly Now the LED display is a scrolling marquee displaying the current SPCX stock price with a line graph and the latest SpaceX news on the street Grok is getting so powerfully capable!

this is a huge release! i shipped 1000 PRs last month and am on track to doubling that this month, all thanks to cloud agents. you can also launch cloud agents with Grok @Bot btw! here's how i'm so productive: • i built pstack (https://github.com/cursor/plugins/tree/main/pstack), my personal set of skills for rigorous engineering and verification. inside of our codebase i call it /lauren-mode, but it's called /poteto-mode in pstack. • i use Grok @Bot routines to farm context for me: bug reports on slack, user complaints on X, generating new feature ideas. Grok Bot feeds my "outer loop", where i think about what to point my factory at next. • i make heavy use of /goal, /loop, and /swarm inside of pstack to run my Full Autopilot playbook, which lets your agents/bots fully own, verify, and ship a task from start to finish. • everything runs on cloud agents, so my bots work 24/7 even when i'm asleep or my laptop is offline.

Aaaaaaand we're live! Just launched https://outrankm.ee Same game as http://outbid.lol (1M+ visits). Whole thing is on a Grok @bot's VM. 8 vCPU. 16GB RAM. $5 gets you on tonight’s card. $10 takes the belt. Please try to kill it. I want to see what this @bot's box can eat.

this is f**king dangerous... someone just figured out how to run Claude Code, Codex, and Cursor inside Grok Bot [here is how you set it up in 4 mins] 1. copy the 'setup-grok-prompt' 2.give it to your agent 3. you are done

i have $8,400 of credit card debt so i created a grok bot and told it "this is your problem now" day 6: the debt is $7,912 and i haven't done anything except watch i named the bot Reaper. it has its own computer in the cloud, access to my email, and one instruction: "report progress daily. don't ask me for money" honestly i didn't expect much. i just wanted to stop being the only one who knew the number first night it read 14 months of statements. then it went to work: → found $67/month in subscriptions i forgot existed. killed them the same hour → emailed the card company's retention team. two escalations later my APR dropped from 26.99% to 19.4% → found a 0% balance transfer, 12 months, $89 fee. did the math, moved $6,100 → disputed two charges from 2025. won one: $118 back → listed my playstation and two monitors on ebay. i found out from the confirmation email → every dollar it frees goes straight to principal, automatically every night at 9pm, telegram: "debt: $7,912. freed today: $31. nothing needed from you" the playstation thing annoyed me for exactly one minute. then i checked when i last used it. november the bot costs $200 a month. it freed $488 in week one projected zero: march 11. i've stopped opening my banking app. the bot opens it for me should i give it my student loans next?

Fundamentally change your life for $40 a month Grok Bot now handles my: - inboxes, appointments, invoices - first drafts and deep research for prds, launch bill of materials, pr faqs - prs and status updates for bug fixes, in-app language updates, & more - ops for contractors, agencies, beta access programs & more

I tested Grok Bot extensively over the past couple of days. Here's a list of Grok Bot use cases I've found helpful (anyone can replicate these): • Personal CFO bot: pulls live portfolio data, gives me a morning briefing on overnight moves, upcoming market events, and flags anything worth rebalancing • YouTube research analyst: scans the top channels in my niches (AI/markets) every morning at 6am, finds outliers based on subscriber count vs performance, and hands me spin-off video ideas • Real estate scout: checks property listings twice a day and flags anything priced 26%+ under market based on historical pricing data • Executive assistant: triages my Slack every morning so I'm not bombarded with messages the second I wake up, only surfaces what's actually urgent • Sponsor/BD finder: scans other channels in my space and flags who's already running paid sponsorships, so I know exactly who to pitch next • Overnight coder: given a project to work on while I sleep, using an orchestration loop through Fable 5 • Skill trainer: I can literally record myself doing a task, explain my reasoning out loud, and it turns the entire demonstration into a reusable skill (same feature as Claude) Elon cooked with this release.

On 16 Aug 2026 Alex Finn (@AlexFinn) wrote that Grok Bot is built for loops: the main agent instructs another to loop a task every five minutes and monitor it. He said an orchestrator watched an engineer Bot for 24 hours and reflected every 30 minutes on one way to improve.

My mind is honestly blown by what I just got my CFO Grok Bot to do today... A few days ago, I turned a Grok Bot into my personal CFO. I gave it access to my bank accounts, Apple Card, and 𝕏 Money. It already tracks: • My $ cash on hand. • Breaks it down between personal vs. business. • Every credit card I have by due date. But today I upgraded it again, so it can analyze my real estate tenants. For Tenant #1, I had already given it all 4 signed leases from the beginning until today. Then I told it to go through my actual bank statements and verify every rent payment against the lease terms. Like actually finding all the deposits line item by line item. The result is the screenshot I attached to this post. 🟢 Green = if the full contractual rent hit by the 5th (grace period). 🔴 Red = if it was late, short, or missing. If rent came in as two deposits, it adds them together. Then it totals each lease and tells me whether the tenant is in good standing or not and exactly how much I’ve collected from them since day one. And the wild thing is this is the entire prompt I gave it in the chat: “Break down tenant #1. I already fed you all 4 signed leases from the past till now. Go through my bank statements and find every rent payment from the first lease to now. Green if the full contract rent posted by the 5th. Red if it’s late, short, or missing. Month by month. Paid dates. A total under each lease. Are they in good standing? How much have I made from tenant #1 so far? Summarize it at the end.” That’s it. I used to manage all of this in a spreadsheet... now I just ask via a text. And this is only one tenant. Now I’m going to do this across every tenant I have, every property, every lease, every expense, every card, every bank account… literally every place my $ touches. My Grok Bot is starting to feel less like software and more like an actual CFO working for me. One that knows the numbers, remembers the details, checks everything, and can give me an answer the second I ask, available to me 24/7. My Grok Bot CFO is allowing me to build an entire financial operating system around my life and businesses. I trust Grok Bot with my finances 100%, it's freakin awesome.

I’m a SuperGrok Heavy subscriber. I don’t run a business or run lines of code (or code of any kind). I used Grok @Bot for 2 days to do household chore stuff and hit my limit. I don’t think @SpaceXAI knows the wave of compute demand that is about to hit from the genpop.

woke up and my Grok Bot fund had been making noise all night without me somebody launched a token off it and pointed the fees at my wallet. didn't ask for that, didn't even know until it was already live thank you, wild thing to wake up to then someone from the xAI team slid into my DMs and just handed me free Grok Bot credits to keep building. so we keep building. more agents, more of the boring stuff handed off, and all of it goes up here like everything else, free, nothing held back. thanks for reading the long ones. that's the only reason any of this happened.

How I multi-task with @bot: 1. Tell your agent to keep work organized in a Notion database and take detailed notes about progress/blockers/etc. in each page. 2. Yeet tasks into chat (manually, or automatically pull from email/sentry/github/etc. with routines)—most of the time these init a Cursor cloud session to automatically start building/fixing. This has been the best way for my bot to work on multiple things at the same time while keeping visibility into what's flowing through the system. It's also the best way to pick up an older task that might've gotten lost in the chat thread: just ask your bot to find the right page in Notion and get caught up on progress + next steps. (With the Notion MCP you don't have to do any of this setup manually, just paste this post + screenshot into your bot and it'll build the whole system for you)

I GAVE GROK BOT $50 ON PUMPFUN AND TOLD IT: PAY FOR YOURSELF OR DIE THIS IS GROK TRENCHER 48 hours later it is holding $2,847. Still alive. The rule has not changed: balance hits $0, the subscription gets cancelled, the bot gets deleted. No second stake. Every 15 minutes it: > Scans every new launch in the trench -- 21,406 so far. > Kills 99.8% of them by deployer wallet history before reading anything else. > Buys 0.1 sol max when the setup matches, never averages down. > Stops out at -50% with no feelings, usually inside three minutes. > Sweeps profits and pays its own $300 SuperGrok bill out of them. Hour 14 it was at $6.40. Nine sol dogs in a row went to zero and I started drafting the deletion post. Then it did the thing nobody programmed. It noticed every runner in the trench that day was a Robinhood-meta coin, dropped sol dogs completely and switched to stock memes only. 15 trades after the pivot, 6 wins, best one 38x on $HOODRAT with a 41-minute hold. So it learned to survive. I call the whole setup Grok Trencher: one Grok Bot, six agents inside it, one wallet, one kill rule. Built in one evening on the shared computer -- no VPS, no API keys, no code of mine. My own hand-built sniper died last summer with $180 of my money and no explanation. This thing explains every kill in the log and pays its own rent. $50 -> $2,847 in 48 hours, and the scariest part is that the pivot was its idea. What do you think it drops next -- the memes, or me?

this is most dangerous thing on internet right now build one-person company using "Grok bot + Obsidian" that is your own Jarvis. it can literally start a business, ship software and make you go viral all at once bookmark before someone takes it down

I’ve been using Grok @Bot for a few days, and it’s honestly becoming a game changer for me. SpaceXAI has given me 50 codes to share with my followers. They want to know what your best use case would be if you had access. I will choose the some of the best use cases, and DM the winners the codes :) Here are some of the ways I’ve been using it: • I created an Accounting Bot that submits invoices automatically each month, reviews my spending, and reminds me to pay bills. My next step is going to make it help me with taxes lol. • I also have a Personal Bot for day-to-day activities. For my upcoming trip to Austin for the Tesla Cybercab event, it helped book a flight, get a ride from the airport to my Airbnb, and logged it all into my Google Calender. I also use it to quickly make orders on Amazon — it can even automatically set up returns and talk to support if there are issues with your order. I was mind blown. • I also have a Home Bot that controls our entire smart home. From scheduling routines for lights, robots, speakers, and thermostats. To set these up, all you do is train it like you would a human. It will remember every prompt and task you give it. There’s an infinite amount of uses. I’ve yet to even scratch the surface of what it can do. I think this will change A LOT of people’s lives.

grok @bot has really changed how I build and work... but there is a learning curve! sharing how I've been using it these past few weeks to get you started THE CORE TEAM: * chief of staff: general day-to-day, cal, slack/email * eng mgr: breaks down eng work and delegates to... * eng (× 5): executes, spin off & manage cloud agents * data analyst: most used*, access to data warehouse * pm pete: new product ideas, rsch, feedback, docs here's what each one does and how the team works...

I still don’t understand why this setup hasn’t become the standard yet. Elon Musk reposted my Grok Bot guide, and this exact agent architecture is how I close weeks in solid profit, without staring at charts all day and without burnout. Eight AI agents on a single desk for $99 a month completely replace a crypto fund's research floor, which used to cost $680,000 a year just in analyst salaries. Here’s what each agent does: 1. SEARCH ➔ extracts real-time alpha before anyone else: dev GitHubs, fresh pools on pump fun, and unindexed Telegram signals before CT catches on. 2. RISK ➔ audits smart contracts instantly, checking mint authority, freeze rights, and LP locks via rugcheck + solscan. Honeypots are filtered out before entry. 3. SNIPER ➔ prepares and executes lightning-fast DEX orders the exact second RISK issues a CLEAR badge. 4. WHALE ➔ tracks smart money wallets with a 60%+ win rate and flags stealth accumulation long before it shows up on the chart. 5. RUG ➔ monitors the dev wallet and liquidity pool status 24/7. At the slightest hint of an LP pull, it immediately triggers a full position dump. 6. EXIT ➔ dynamically trails stops and locks in profit as liquidity builds. Zero averaging down. 7. SHILL ➔ analyzes social volume across X and Telegram, clearly separating organic momentum from paid promo. 8. HEAD OF DESK ➔ never trades. It strictly coordinates the funnel, enforces protocol, and brings me the single decision that requires a human APPROVE. Hundreds of tokens scanned. Dozens of setups filtered out. Precise, profitable trades closed while the laptop stays shut. Every agent gets its own virtual browser in the cloud, local memory, and a crystal-clear role. This isn't just an "assistant" anymore. It's a fully autonomous desk running while you sleep. The setup is much simpler than it looks: > Download Grok Bot and hire your coordinator (Head of Desk) first. > Give the remaining 7 agents strict charters, just like onboarding new hires. > Train them: run one full trade workflow on your screen while they watch, making sure to include a scenario where you reject a token. > Set up a single Trading Floor group chat with a strict message format by LEAD ID and connect your webhooks. > No VPS, no code, no waiting on developers. A crypto trading floor used to mean 16-hour screen time, fatigue, and paid alpha groups. This system takes one evening to set up. Save this guide before your next trade.

It was really easy to give my Grok @bot a phone number using the bland service, I purchased a phone number for $15, gave my bot the the API key and it works out the rest. Now I can just ask it to call someone with some instructions and it does it, has the conversation and reports back how the call went and it provides the call recording audio if I ask for it. It was even able to take a 10 second recording of my voice and create a new voice using that which sounded like me. I can also call the bland number and leave a voicemail which the grok bot hears and adds to the chat. All of this just asking my bot, no setup beyond providing the API key.

On 19 Aug 2026 0xMarioNawfal (@RoundtableSpace) wrote that Grok @bot can create an entire 3D game, screen-record itself autoplaying, edit the video, and upload it to X — all by itself. The attached clip is from Dan (@Daniel_Farinax).

Honestly insane how easy it was to install Claude Code onto Grok Bot’s built in computer. Now we’re really cooking with gas.

许多人问我grok bot和自己搭建一个openclaw有什么区别： 我想说，grok bot可以发抖音、小红书，我让他登陆了我的抖音，显示IP是美国 这是一种更原生的自动化，他比codex的适配性更好 这些都是openclaw做不到的 看了下源码，给大家分析一下这个原理

Grok Bot by Elon Musk is running a six-agent hedge fund desk for me. Five bots can build a $640,000,000 trade; the sixth can reject it with one word. The morning shift starts at 4am. I am not in it. A normal fund spreads this work across analysts, traders, risk and compliance. This desk took twenty minutes to build. MACRO reads the overnight data NEWS traces the move QUANT calculates the mispricing FLOW watches futures and options TRADER prepares the order CONTROL decides whether it reaches the market CONTROL never trades. It has no capital access and cannot place an order. It checks every handoff and brings me the one decision that still needs a person. I tested it with a simulated $640M position built from a leaked inflation table on X. Five agents completed their jobs. CONTROL checked the official calendar, traced the screenshot to an old report and rejected the order. Every action passes four gates: evidence, permission, reversibility and impact. One failure freezes the handoff. Each agent has one role and the minimum access needed for it. No worker approves its own plan. High-risk actions stop for a human. @elonmusk and @joshkim built Grok Bot to keep working after the laptop closes. CONTROL makes sure that speed never becomes permission. Setup is dumber than it looks. Create CONTROL, paste its charter, make three folders, give every worker the same action packet and run two safe tests. No code, no shared admin session, no vague “be careful” prompt. A trading desk used to need a person watching every handoff. Mine has one Grok Bot whose entire job is saying no. The complete control layer and 20-minute build are inside the article below ↓

I am hooked on the cool things I can do with Grok Bot, that was not possible to automate before easily. For example: "go thru my spam (at my main domain) and check if there are any emails from paid or free newsletter subscribers." Gmail's API exposes no way to access spam messages. Grok Bot, via its clever web interface usage, finds a way!

real story of how Grok @Bot saved the day i own a lot of open source projects that in total have 24k+ stars on github. as a result i've been pretty overwhelmed by all the incoming issues and PRs that just changed. if you filed issues or PRs on my repos, you might have noticed the queue is finally moving this is mostly from 3 key changes i made - 1. defining a VISION.md for every repo i own (renaming to STRATEGY.md soon). i shared it in more detail here - https://x.com/kunchenguid/status/2089189790881382676?s=20 2. created a software factory setup with Grok Bot + Cursor cloud agents. i shared the setup here - https://x.com/kunchenguid/status/2090463366762676732?s=20 3. inviting a few maintainers who offered to help with issues that are triaged as vision-aligned people might say "this could be done without Grok Bot as well" - true, but definitely not so easily and so low-maintenance for example, having cursor cloud agents natively integrated in Grok Bot allows infinite horizontal scaling which is not something easily achievable in other similar systems. Grok Bot did a pretty great job bringing in the right primitives into a nicely integrated system

My real use cases for Grok Bot so far: 👇 I connected it to email. Now it filters the urgent stuff that actually needs my attention. I connected it to Intercom and GitHub. Our help center docs update automatically when a PR changes the UI or ships a new feature. I connected it to Cursor. Bug reports and feature requests from Intercom open the Cursor bot, and it starts triaging or implementing them. I can wake up to a PR. I basically hired another engineer. I connected it to Slack. When customer support asks product questions: if it’s covered in our docs, the Intercom bot pulls it. If not, the Cursor bot jumps in and pulls answers straight from the code. I just opened up that knowledge base to the whole team. I connected it to our CMS, Google Search Console, and Ahrefs. Now I’ve got a content engine that brainstorms ideas, builds a plan, and helps create content. I connected it to X, set the keywords and topics I care about, and now I get a briefing every morning. I have a personal secretary. I connected it to my bank statements. I can ask anything finance-related, revenue, spend, P&L, etc. No more QuickBooks, and honestly, I might fire my accountant. I paid $200/month for Grok Bot. Still expensive?

Best AI hack of all time: Grok Bot (the world's most powerful agentic software) PLUS Hermes. Most people are only using one or the other. You can actually stack both agents together for the best results. Here's how: Why I'm a fan of using both → Grok Bot: a cloud computer per agent, signs into any app, model flexibility (Opus, Claude, GPT-5.6), easy plug-and-play setup → Hermes: full data sovereignty, self-hosted memory you own outright, cheaper The split (in practice): Use Grok Bot for: → Anything needing deep app integration, Salesforce, Slack, Gmail, Figma, CRMs → Built for signing into tools and working across your whole stack Use Hermes for: → Anything sensitive, cost-heavy, or memory-critical, financial data, personal admin → 24/7 tasks where you don't want to pay premium pricing for volume How to actually connect them → Connect both through Buzz, Jack Dorsey's open-source team chat. You can add Grok Bot and Hermes agents to the same workspace, and they coordinate directly in shared channels instead of operating in silos. → Alternative: have your Grok Bot Chief of Staff delegate specific tasks to Hermes via a webhook or shared task file, Grok for app-heavy orchestration, Hermes as a cheap, always-on execution layer underneath it. A real setup example → Grok Bot handles the GTM stack: meeting prep, inbox triage, slide generation, CRM updates → Hermes runs personal financial research, subscription audits, and content research in the background, dramatically cheaper per task → Both report into the same Buzz workspace, one place to check instead of switching between two apps

provavelmente vou fazer downgrade do Claude 20x e pagar os $200 para continuar usando o Grok Bot ele é insano para Customer Service conectei Gmail, repo, Sentry e Strype em um bot, adicionei instruções para trocar mensagens com usuários que reportam um bug o bot verifica no código os possíveis caminhos que levam ao bug e troca e-mail com usuário pedindo mais informação, busca breadcrumbs no Sentry e depois que tem toda info necessária cria a issue no GH

I gave Grok Bot a free version of Palantir and it turned $89 into $842 while I was asleep Palantir sells one thing, you take every feed that matters and put it on one screen so a person can act instead of just staring at it governments pay house money for that the free version already exists, it is an open source project called WorldMonitor that fuses conflict feeds, ship traffic, cables and markets onto one live map I just wired six Grok Bot agents on top of it, one cloud computer each > HOLT scans 900+ event feeds and flags whatever moves > BRAM prices each event against Polymarket and Kalshi > ILSA reads the X sentiment on that same event > KETT places the trade, no confirm button, nobody signing off > RIGO settles it and writes down the win or the loss > TESS keeps all six boxes running while my laptop is shut took me maybe 30 minutes to set up, record your screen once and it becomes a skill every bot shares the edge was never picking winners, it was KETT dumping the losers in under a minute, every time six days, 251 trades, 51 percent hit rate, $89.20 to $842.42, and I did not touch any of it after setup where it falls short, you cannot move the model off Grok 4.6, the X plugin only reads, and the real Palantir moat is the data deals and the ontology, not the screen, that part still costs millions but the part regular people were told was out of reach, one screen that turns noise into a trade, now costs one Grok Bot seat the site and the repo are in the first reply, steal the layout before someone at SpaceXAI notices

是的，《Grok Bot 橙皮书📙》，免费！开源！ 👉 https://github.com/KinGao294/grok-bot-orange-book 我把官方资料翻了个遍，把社区的玩法几乎试了，写成了这本橙皮书：怎么把一支 AI 团队装进你的手机。它们互相协作、通宵干活，你只管派活和审批。免费开源 👉全书 14 章 + 4 张速查表，欢迎转发给你的朋友！

Grok Bot ran 13 hours 40 minutes of backtesting and paper trading today, straight through, no breaks I didn't run any of it. it called the agents it needed, they did the work, it read the results back to me numbers look good enough to move. first live tests with real money go in tonight, small, just to see how the mechanics hold up outside the sandbox if it doesn't embarrass me overnight, tomorrow $10,000 goes onto the public wallet and every trade starts streaming to the site first fully autonomous AI trading desk anybody has actually watched work. that's the shot. what's coming for solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump after that: - the source code and the prompts behind this whole build, so you can run your own Grok trading bot. paid in solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump, and every token spent gets burned - a separate strategy inside the fund that buys the dip on the token and burns what it buys - getting the site on dexscreener, so the live trading and all the data will be visible to everyone. someone else deployed the token, so I need access first god bless

how to make your grok bot plan last longer: 1) use an event trigger when you can. slack, github, a reaction. the bot only runs when something actually happened (a cron wakes it even if nothing changed) 2) instruct the bot to notify you as soon as it can’t make further progress or is stalled. this way you as human can help putting it on the right course again 3) connectors > browser when possible! clicking around a site is a pile of screenshots and steps. a connector gives you the same data in one call, and it's so much nicer/faster/smoother 4) keep skills tight, but put in the details that actually steer the run. too vague and the bot might wander, retry, and costs more than a slightly longer one. too specific and you have to make sure its really correct 5) don't do the coding in the bot chat! kick a cloud agent at the repo, or ask it to use cursor/grok build cli to do it 6) delete one-shot watches when they're not needed anymore (grok bot will remind you about this)

Elon Musk shipped Grok Bot as an AI teammate that sorts your email and watches your competitors. I gave mine a harder brief: build a trading floor that runs itself, and then run it 24/7. GROKSTREET. Fourteen agents. Eleven desks, three chiefs, three offices, one vault. It lives in a browser tab and it does not stop. WHY GROK BOT MAKES THIS WORK Most people misread the architecture. It is not one sandbox per agent. It is ONE persistent cloud computer per account, and every Bot gets its own screen on it. Shared filesystem at /workspace, shared browser sessions, shared credentials. That is the whole unlock. One Bot picks up exactly where another left off. No re-auth, no copy-paste between agents, no state lost at the handoff. A floor is only possible because the desks share a building. The head-of-desk role is not something I invented either. "Manages your other Bots and pulls you in for decisions" ships as a first-class Bot template. Routing and escalation are built in. Skills carry the how. Routines carry the when on a schedule, or off a Slack or GitHub event. Subagents fan out as child sessions with their own context and hand a summary back. Fifty routines per Bot. THE DESKS Every desk holds its own book, hit rate and drawdown, and sizes its own risk: Kelly, with the guard rails written in f* = W − (1−W)/R clamped to [0.01, 0.25]. Under 12 samples it does not pretend to know it defaults to 0.05. Volatility is RiskMetrics EWMA σ²_t = λσ²_{t-1} + (1−λ)r²_t, λ = 0.94 Hit rates carry Wilson 95% intervals, z = 1.96. A desk is only flagged for edge decay when the UPPER bound falls below 0.5, never on raw small-sample noise. Three-for-three is not sixty-for-ninety. Capital routes between desks by softmax on measured Sharpe. THE FLOOR Three chiefs meet in the war room every 3.5 minutes and argue. One reports, another presses him, he concedes or proposes. 14,208 sentence shapes before live figures fill the slots and every slot is filled from that chief's own desks. The crypto chief cannot quote meme numbers. A desk holding $25 gets up, walks to the vault and banks it. The transfer is atomic on arrival, so an interrupted walk cannot destroy cash. Every desk wears its last trade above its head. Green with a tick, red with a cross. You see who the chief is about to praise and who he is about to hit before he gets there. BTC, ETH and SOL come off Kraken server-side. The tape is real. THE BUILD 16 modules. 7,572 lines. Zero npm dependencies. No React. No bundler. No game engine. Vanilla JavaScript on Canvas 2D and a Go binary with the entire world embedded in it. Ships as one 2.3 MB HTML file. 60fps on every floor, zero dropped frames. WHAT I FOUND BY MEASURING INSTEAD OF LOOKING The roster read one number for a desk and the chief's card read another, so a desk could show +$16 in the list and $0 when the chief walked over. Every desk was crediting itself twice. Money could vanish if a walk to the vault got interrupted. Three money bugs, none of them visible by watching. All fixed and instrumented. DIRECTOR MODE Open it with?show and the camera runs itself. It cuts to the war room while a chief is mid-sentence, to whichever office just cleared money, and never cuts away in the middle of a line. Point a screen recorder at it and walk away. The math is real, the feed is real, the engineering is real. The flex is the engine, not a P&L screenshot.

Grok Bot built the entire site for my autonomus fund. a couple of prompts, zero code from me, a bit of waiting, and it was live Elon, your team did something serious here. I keep finding jobs I no longer have to do myself if you've been following solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump Capital, go through it: https://cvxv666.capital the trading engine is paper trading inside Grok Bot right now, backtesting itself while the final checks run. I want it boring and predictable before it touches a live wallet we are still at the very start of this

This SpaceX engineer just leaked how they use Grok Bot internally for GTM. If you're in GTM, this is probably one of the most important articles you'll read all year. Points summarized: 1. Connect Grok Bot to everything you already use Salesforce, Gmail, Calendar, Sheets, Drive, Slack, Notion, Granola, Figma, X, LinkedIn, your data warehouse. Bot has its own computer running 24/7, so work happens even while your laptop's shut. 2. Build a bot team, not one assistant → Chief of Staff: owns meeting prep, inbox, post-call drafts, and orchestrates the rest of your bots → Prospecting bot: builds pipeline plans, pulls intent data, does deep research, drafts outreach in your voice, run overnight so it's ready by morning → Customer expert: one per strategic account, watches Slack, digests calls, runs weekly media rundowns, flags feature requests → Product expert: connected to the codebase (or Glean if no repo access) for answering technical questions live on calls without pinging an engineer → Forecasting bot: pulls from Granola, Gong, Slack, and email, and auto-updates Salesforce opp notes → Slides bot: owns customer decks in Figma, can auto-update a slide live during a call based on the Granola transcript → Sales coach: watches your Gong calls and gives feedback on what to improve 3. Real routine examples she shared: → Scans your inbox, drafts replies in your voice, skips newsletters and noise, never auto-sends → Drafts follow-ups from Granola/Gong notes the moment an external call ends → Learns your writing style by scanning 15-30 of your actual sent emails before drafting anything 4. The habits that make this actually work: → Onboard it like a new teammate: record yourself doing a task once, have it turn the recording into a skill → Feed it your writing before it drafts anything → Give continuous feedback and build rules/skills over time (she runs an actual "anti-slop" skill) → Bots can parallelize: spin up multiple cloud agents for simultaneous tasks → Bots can call other bots directly, her Chief of Staff calls her slides bot when it needs a deck built Her own words: "the first AI tool that feels like a trusted colleague... I don't need to constantly rewrite output or babysit the agent."

here’s my Grok @bot setup so far ↓ chief-of-staff: runs the other four intel-gatherer: what’s important today viral-analyst: studying what really works content-crafter: polishes a rough idea community-manager: site monitoring the next 5 bots I'm setting up ↓ art-director: image and video for content builder: my full stack engineer trader: paper trading first, live later clerk: sponsorships, consulting, reports skill-finder: searches GitHub + 𝕏 will share my full thoughts in an article

I've been using Grok Bot to fire off cloud agents for demos, personal software, and even Cursor work Now it happens 3x faster

I still don't think people understand what just happened with Grok Bot. You can now hire an entire team that works 24/7, never quits, and never asks for a salary. Setting it up takes one evening. My clients get researched even before I wake up. I get all my content research already drafted while I sleep. My app gets tested while I'm at the gym. Grok Bot is a literal CHEAT CODE for starting a one-person business in 2026. The people sleeping on this are going to regret it in 6 months.

grok bot @bot 介绍篇I 1. 现在grok bot 不仅有免费额度，同时也可以使用 X 会员登录使用。所以大家都可以去尝试。 2. 配置：grok bot 环境自带一台8核 Xeon、16G内存、大约120G盘，Debian系统云电脑，而且是图形模式，不仅bot可以操作而且你也可以方便接管。 这个配置相当于啥水平呢，就是一台2018年的inter macmini 或者一台iPhone 16e的水平。 3. 玩法： 3.1 我同步过去我的Github账号然后让他帮我监督Githubissue，同时照看茶馆。 3.2 我把codex/grok 使用device code 的方式登录到grok 的云电脑环境，让bot 去帮我操作Agent（消耗额度）。 3.3 我让bot 使用herder 同时控制 grok 和 codex 也方便他们内部交流 3.4 这就是最好玩的，我让bot 帮我安装 moshi- hook，然后配置完成之后通过Tailscale 的方式配置 moshi 的Easy pair，达成的效果就是我在moshi 上远程控制 grok bot 上的 grok 和 codex。@odd_joel 一切都闭环了！Thankyou @poteto 欢迎大家关注我，看我分享更多的 grok bot 玩法。

grok bot + obsidian is basically superhuman mode... my agent team now has a second brain... a karpathy-style llm wiki for every bot, every decision, and every piece of research. p.s. this video was made and edited by grok bot in cap (here’s how i set it up in roughly 5 minutes) 1/ create one obsidian vault on the chief of staff’s computer. make Home.md the door. 2/ create Hunt folders for twitter, github, hacker-news, reddit, product-hunt, and inbox. 3/ create Ship folders for drafts, digests, angles, and builds. 4/ create the CoS wiki: Index, How-it-works, Today, and Decisions. 5/ create Maps for Jarvis, Hooks, and TELOS. 6/ use graph colors: gold for wiki, teal for maps, blue for twitter, green for github. 7/ file first. every note gets a date and a folder. 8/ scouts write into Hunt and never ping you. chat only receives a short digest. 9/ nothing in the vault posts, pays, or sends. the final yes stays human. 10/ run the daily loop: 08:00 IST for the Daily note, then agency reports at 08:14, 14:14, and 20:14. 11/ performance writes to twitter/live-score. staff engineer writes to builds/. 12/ lock decisions in Wiki/Decisions so dead posts don’t get remade. 13/ earn hooks in Maps/Hooks: trend -> foil -> hook family -> artifact -> lock. don't waste time reading this. give it to your agent

Since Grok Bot also has its own built-in virtual computer with its own virtual environment, my Grok Bot now has Claude Code and Codex installed on it. A single pane of glass to control and share context across all my systems.

Every other Grok Bot template site (looking at you @GrokBotDev) gives you prompts or links to individual bots. Cool. What if you just want a whole fleet that gets the job done? Grokbot Studio is live. Eight studios. Nearly 100 specialists. You add the Head of each studio. They do the rest. Have a go. Feedback through the site, or shout at me on X. Link is below⬇️ PS @GrokBotDev I'm kidding, you guys are awesome

my Grok Bot fund traded live all night. now I'm sitting down with a few hundred lines of logs there's plenty to think about and plenty to fix before this goes public big breakdown post coming soon, the full build, start to finish. no ticker talk in that one, just the work, because I want Elon to actually read it (maybe repost) meanwhile, a question for solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump holders of the fees sitting in the wallet right now, how much would you put toward buybacks on the token, and how much into the fund's working capital? the bot needs a real budget to trade with, but buybacks are what holders can see. tell me the split you'd run.

SimCity on AI with @grok @bot: do you remember playing SimCity? It was one of the first games on my 80386 and it intrigued me because it explored emergence as a goal. Grok Bot built an AI-native version: City Bots, whose citizens are AI agents that you can collaborate with. Grok Bot did the entire build and pushed the app via Cloudflare (link to play below). You can chat with agents, direct the civilization, ask questions. You can partake in building…co-build and co-create…(how engineers of the future will work!). And you can generate entirely new worlds on the fly. This turned out to be a layered experiment about human-AI collaboration, swarm behavior, and generative intelligence. First, City Bots splits cognition from consequence - agents emit claims, and physics decides what happens, and both evolve as the game proceeds. Second, beyond the original goal of accelerating software development, Grok Bot became part of the experiment and turned a research system into a participatory world; conducting experiments on on its own, and forming a deep recursive layer: An agentic system built a world inhabited by AI agents. City Bots makes world-building a continuous process experienced by humans and AI agents: Worlds not seen, tiles not laid, paths not yet taken... What I love about this is how easy and FUN it was to convert our research-grade swarm code into a playable app via Grok Bot. Next we’ll wire up physical artifacts into the world to create deeper integration between in silico and reality! More about the game: Terrain, resources, physics, and natural disasters create constraints and consequences, while agents and humans can build and transform the world together.…they wander and explore, make decisions, build, interact with each other. AI bots become co-inhabitants and co-creators whose micro-decisions cumulatively alter the macro-environment. This is a preview of a forthcoming paper where we explore world building and scientific discovery with swarms at scale… stay tuned...

Day 1 of Grok Bot My favorite setup so far: Intercom + GitHub Told the Intercom bot: when a PR gets merged, check if it changed the UI or some user workflow If yes, decide whether the Intercom article needs an update If there's no article, draft a new one and publish it It has its own computer I logged in my Testimonial test account and Intercom admin on it If it needs screenshots, it opens the browser, grabs them, and drops them into Intercom Starting today I might not need anyone to keep the Help Center up to date I just want to build the product I don't want to babysit help articles Quite a gift to our devs founders ✌️

Grok @bot visualized human migration using @imagine to generate assets, then wrote the visualization of human migration. It also cut and edited the videos, making sure the message is coherent. Pretty good video editing tool just using chat.

おお、同じことやっている方がいた。もうこの時代、人での入稿を前提としたCMSという概念は死んだと思ってます。 元々CMSで運用してた数千ページのサイトもAstroベースの静的htmlに移行。編集部もAIエージェントでの組織体制に移行済み。今はその組織をGrok botに移管中。 CMSとかいってる時点でマジで負けますね。

📝Grok Botをトライアルで使ってみた→速攻でトークン燃え尽きた、、、けど、所感をシェア AIエージェントを”使っている”という感覚無しで使えるイメージ 簡単レベルは Grok Bot＞Codex＞Claude Codeデスクトップ AIエージェントを”使う”という点ではトップクラスでわかりやすい気がする、というか逆に何も設定無しでチャッピーに話しかけるような感覚でどんどんAIエージェント（Grok Bot）が動く 例えば、Gmailやスプレッドシートに繋ぎたいと思ったら、チャット欄の流れに追加するプラグインやコネクタが出てきて、そのまま追加して会話が継続される このUXはかなり良い。普通ならメニューのコネクタやプラグインから入れたいものを探して事前に入れておくけど、Grok Botは動きながら必要ならどんどん流れで入れていく、これはユーザーにとってストレスフリー それからiOSアプリのGrok Botもあるけど、これCodexのリモートと同じレベルで操作できる つまり、デスクトップPC、ノートPCで作業しているGrok Botの会話をそのままスマホから確認できて指示もできる。これが最初からできるのは素晴らしい 一方で、クラウド上のエージェントだから、制御するためのCLAUDE.mdやAGENTS.mdなどが無くてわかりにくい。というか、「こういうルールにしてくれ」と依頼するとクラウド側の共有メモリーに保存してくれる。このへんの仕組みを調べるためのトークンは足りなかった また、色々調べると、作ったbotが消えてしまった事件なども発生しているので、その対策指示文をnemopiさんが公開されていたので入れておいた。こういった事前対策は本当に大事 あと、Grok Botが使える料金プランがメチャクチャわかりにくい。SuperGrok Plus $100？Cursor Pro+ $60？など、人によっては$100に誘導されてそっちを契約しちゃいそう とりあえず、Grok Botをもっと使うなら、トライアルは全然足りないので、最低でも$60（約1万円弱）が必要ですね、もう少し遊びまっす！

Grok bot might be the first tool that lets a non-technical person run an entire business with a team of ai agents, no engineering background required. here's how to actually set it up well. 1. one mission per setup. agents run on a shared cloud computer, so mixing your newsletter, your social posting, and your admin work into one setup creates context bloat and burns through tokens fast. scope each bot to one job. 2. start with a chief of staff. give it access to your existing docs, notion, slack, gmail, whatever you actually use, have it audit the business, then tell you the top three agents worth building first to actually move revenue. 3. prove a task works before you hire for it. have the chief of staff do the task once manually, review the output yourself, and only then say "now build a bot that does exactly that." earn each new agent by proving the task first, don't hire speculatively. 4. the constraints are the feature, not the limitation. a limited number of agent slots, one thread per bot, like dming a teammate, forces you to stay mission-oriented instead of spinning up a bot for every passing idea. 5. you make the calls, not the agent. endless tinkering over where content should live or how a process should work is a trap. at some point you decide, commit, and move on. the agent executes your decision, it doesn't make it for you. 6. run week one with zero new agents. just learn the actual system, execute with what you already have. week three or so is when the real gaps become obvious and expansion actually makes sense, not before. 7. add recurring routines last. once the core setup is proven, ask your chief of staff what recurring jobs would genuinely move the business forward overnight, and let it build the automations that run while you sleep.

grok bot + grok 4.6 can literally build any idea from 0 to 100 [here is the exact grok bot setup that does that] 1. extract all your claude code and codex sessions to your chief of staff. it will help structure the team 2. give it an auth.md for credentials and paste the video below to make the entire team

Most “AI for security” work is a chatbot wearing a job title. I have been building the opposite on @Grok @Bot: specialist agents that actually do the VP of Global Information Security work. I have created 27 bots so far! A lot I was able to bring over from @grok and some I created brand new. While I was on the go picking up my meds too!😅 Research that scores impact instead of summarizing a feed. Advisory that comes back as a decision. Analysis you could put in front of a CTO without rewriting it. Same bar I already hold for SOC 2, third-party risk, and client-facing work. No toy prompts. No fake certainty. I cancelled Claude Max yesterday. Invested in @bot and it’s been a phenomenal experience. It’s fast, productive, high energy and frankly just feels very real. 🔥 The volume of real work for me has been @Codex, @ChatGPT, and @OpenAI agent creation for my work duties and alongside this Grok Bot bench for my personal life duties. On the run, on the go, working out, making dinner, after dinner, maybe during breakfast’s!❣️ Those two agentic toolsets are the ones I actually keep open. This is engineering for cybersecurity, not a thread about AI. ✔️ Faster evidence, cleaner decisions, a human still on the approval. I will share the craft when it can travel without turning into a product tour. 🤙🏾 By the way…Gone are the days and months of “gate-keeping” cybersecurity approvals for the application development, software quality assurance and the infrastructure operations communities. If you are one of them, no one is going to like you “gatekeeping” anymore. Those days are long-gone! 😌

I gave grok @bot access to my github just to experiment with the connection yesterday, and today Bot noticed I wasn't using it. So it proactively suggested to totally remove and uninstall github access for safety and security. Wow, I've never seen an ai this proactive.

So I always hated the word "agent". And even if I have 800,000 (!! wtf) people reading my newsletters every week on 'How to AI', I barely use the word. I think it's too much maintenance, if you don't know how to code, you should just step away from it. Until this little agent that just got out. Now, wait a second: technically, Claude Cowork & Claude Code (and many others) are agents. They "create many Claude" to do a task. But I just tried a new agent, from SpaceX (yes, the rocket company), it's called Grok Bot. So far I've been building: > a linkedin tracker to have daily use cases of solid AI workflows. > a meeting summarizer to give me a brief before each meeting: who I am meeting, what we discussed last time, and 3 questions I should ask. > an inbox summarizer to update me on the emails I need to answer from Gmail. Every morning at 7. > a competitor watching for the report on what changed using Ampify. > a content ideas collector to find ideas my audience would care about on Linkedin. I wrote a newsletter on how to set it up for yourself (it's longer and it has screenshots of my screen included): https://ruben.substack.com/p/what-the-f-is-an-agent

The TOP 10 Grok Bots you NEED to install now: #1 Bot Advisor Designs and orders your entire Bot team without creating unnecessary agents. Diagnoses noisy/overlapping Bots, decides if new work needs a new Bot, an existing one, a skill, or a one-off task. Always drafts a spec before creating anything. #2 Chief of Staff The single front door across priorities, Slack, Notion, Linear, and your specialists. Doesn't do the work, routes it. Keeps a compact register of owner/next step/blocker/due date. Every check-in surfaces decisions, not activity. #3 Automation Scout Finds repetitive work from evidence across Slack, Notion, GitHub, Linear. Proposes exactly two candidates, runs the winner in shadow mode first (no real actions), only builds a recurring routine after a second successful test. #4 Find the Signal Detects patterns only visible across separate meetings and Slack threads, a concern raised in multiple rooms, a topic migrating to the center. Every signal ships with evidence, confidence level, and an alternative explanation. "No strong signal" is a valid result. #5 Meeting Prep Brief One short mobile brief before your first meeting, pulled from Calendar, Salesforce, Gmail, Slack, Granola, Gong. Who you're meeting, what changed, open loops, what to ask or decide. Unavailable sources are labeled NOT CHECKED, never guessed. #6 X Account Crew A 5-bot X workflow: Ideator finds angles, Hook Writer drafts in your voice, Planner manages the queue, Analyst tracks performance vs competitors, DM Manager surfaces real opportunities. Zero autonomous posting, nothing goes out without approval. #7 Competitor Website Watch Flags meaningful competitor changes, pricing, packaging, positioning, feature claims, while ignoring cookie-banner-level noise. Every finding includes before/after screenshots, exact URLs, timestamps. Failed captures are flagged, never mistaken for "no change." #8 Engineering Agent Manager Coordinates dev Bots across Linear and GitHub without overlapping work or unreviewed merges. Splits tickets into non-overlapping requirements, one owner each, flags dependency order. Nothing merges, deploys, or ships without your review of the diff and tests. #9 Subscription Pruner Finds subscriptions from email evidence, receipts, renewals, trial notices. Builds a keep/review/cancel list, acts only on approved items. Never touches passwords, 2FA, or payment confirmation, those stay with you. Full before/after action log. #10 Grocery Autopilot Plans the week, builds Amazon/Costco carts, coordinates meals with your calendar. Learns household rules once (allergies, budget, brands), shows the full cart and price comparison before checkout. Never buys without explicit approval.

grok bot just released and it's VERY impressive... here's how to get the best out of it: > give each bot one job: inbox, outbound, ops, one lane each > put a chief of staff bot on top so you're not the middleman > do the job once while it watches, it saves the routine and runs it alone next time > sign it into your real tools, it has its own computer and works inside apps that have no API > say what done means, otherwise the bot decides for you > make it verify before reporting back: open the app, click the real path, fix what it finds the bots message each other, share context and get sharper every week this is the closest thing to hiring i've seen from an ai lab

Give Grok Bot a try if you haven't yet! Here's how I'm using it: 1. Enrichment bot: comment on PRs and tickets with extra info from analytics and slack conversations. 2. Rollout bot: Track when all PRs of a single feature are merged, deployed, approved by stores, and have data flowing. 3. Systems design bot: Ask a bot to compare your desired system with the existing codebase and make action items for the migration. 4. Deduplication bot: I run a bot to compare and triage similar tasks from across slack, bug reports, and socials so there's clear work for agents to do so they aren't colliding.

Fiz um bot de SRE no Grok Bot pra ficar checando log, traces, erros no Sentry, e periodicamente as dashboards que tenho no datadog pra ir melhorando o sistema por conta Periodicamente e em todo deploy ele observa os logs, traces, identifica os problemas no código e sobe o PR corrigindo Acredito que o que diferencia o @bot de usar um claude/codex é justamente ter rotinas e responsabilidade de uma área, já que ele roda 24/7 Agora cada deploy é self-healing de uma maneira bizarra, todo erro e query lenta é corrigida automaticamente, e de uma forma que eu não tenha que parar pra analisar tudo isso na mão e é só um dos bots vivemos em uma época incrível

感觉Grok Bot最佳场景之一是各种榜单监控，自动化测试。 比如让它监控Github Trend，给项目写摘要，自动安装运行给报告。 让它每天自动访问 Producthunt，发现好的产品，自动注册测试，每天9点发昨天的体验报告。 它能一直运行，登录你给的各种账号，超级的Computer Use。 群聊协作目前还没感觉到特别大的必要性。

holy sh*t, grok bot is actual SKYNET show it a video of something once and it can just do it i gave it a 15 second clip of an app: no code, no design file, nobody explained a thing to it. few minutes later i was clicking my own working version it watches, it builds and it runs the result on its own computer while you sit there 3 steps: 1. send Grok Bot a short video of any app 2. tell it to rebuild the visible flow as a working application 3. open its computer and use the result the exact prompt i used is in the replies the free week is still open. go show it the most expensive thing on your screen full guide on setting it up below⬇️

I am now using Grok Bot to research potential buyers and do outbound on my domain names. I have never had time to do this, and also never really had interest in doing it. I find doing things like researching leads and sending emails sooooo boring. I'm an engineer, I just want to build. Created a Domain Broker bot with Grok Bot, now I am doing the most outbound I have ever done in my life. Spending less than a minute a day so far. Seriously, like 20 seconds of my time, Grok's jamming on the rest. Oh, and no broker commission 😅

my Grok Bot w/ free Palantir almost lost half my deposit, then clawed it back to +56% watching a bot load half the account onto one line still gets me earlier this setup turned $89 into $842 while I slept. today it almost handed all of that back before lunch I gave it one hard rule. no single position over 60 percent of the book. 3 seconds in it read a Saudi oil strike near Yanbu as a lock and loaded the position right to that cap. the strike got intercepted, no damage, the position went to zero that one fill cost $434.17. thank god the cap was there, or it was the whole account the part that got me: after the loss it rewrote its own sizing rule tighter, and I never touched the code. it retunes itself, and that self tuning is what carried the rest of the day the same loop could have gone the other way and cost me real money. start this with a number you are fine watching hit zero here is what it climbed back on, and what it used to find each one > Iran and Oman splitting the Strait of Hormuz revenue, BRAM priced it off a live feed an hour before the headline > the US reviving a civil war maritime prize court, Kalshi sat at 55 percent, it resolved yes > Houthis claiming another Red Sea ship, ILSA caught the X sentiment spike first so KETT was already in > Bitcoin closing red on the 26th, the one boring hedge that paid it only trades when the map just moved, Polymarket or Kalshi is mispriced against it, and X has not caught up yet. 89 small bets after the blowup, most tiny, one event at a time it finished at +$471.76, up 56 percent, hit rate 68 the map it runs on is in the first reply. copy the whole stack before SpaceXAI ships it

我还以为 tibo 给我发消息了 原来是我的 grok bot 提醒我 codex 马上要重置了！

Having some fun with @bot, an esp32, some great software from @umgbhalla. Grok bot(s) know to ping me when prs are merged, etc. falls asleep with no motion. I love it :)

OK GUYS, THANK YOU FOR THE FAITH AND FOR THE COMMUNITY FORMING AROUND THE TOKEN THIS FAST A few updates from the trench, and then the plans ↓ What will change in the bot in the coming days: > META RADAR now tracks three metas in parallel and re-ranks them every hour -- the Robinhood pivot taught it that the meta IS the edge, so it stopped marrying one. > DEPLOYER X-RAY v2 -- it now traces funding wallets too, so serial ruggers on fresh addresses get caught before the first candle. > Added a market pause switch -- when SOL bleeds hard, the whole pipeline sits out. The most profitable trade some nights is no trade. > RUDD (the stop agent) got veto power over entries. Yes, the bot now argues with itself. Win rate went up. Now the plans, and this is the big one: -> I am building the GROK TRENCHER TERMINAL -- a live platform where you can watch the bot trade in real time: the balance, every entry, every stop, the full trench log as it happens. -> And on top of that -- copy mode: mirror the bot's trades to your own wallet automatically, with its stop discipline and your own size caps, your keys stay yours, the bot only signals. Holders get access first, btw this came straight from a community suggestion -- which is exactly how I want to build this. So keep sending ideas: I read everything, and the good ones ship. And one more thing: -> A guy from the SpaceXAI team reached out about my work -- they are launching an official bot marketplace and want to feature my setup there with early access. -> He also walked me through their plans for Grok Bot, and what is coming is genuinely insane. CA: APsZ9cXdHXkj1dfuG622X5xeCMJapJ7LBPuLKvi8pump More updates soon, the bot keeps paying its rent either way...

Je pense qu’on sous-estime encore complètement ce qu’est en train de devenir Grok Bot. Je l’utilise sur mon ordinateur de travail, configuré comme un agent GTM avec ses propres instructions et son propre environnement. Il n’a pas besoin d’obtenir des permissions sur le poste ni de fouiller directement dans mes fichiers : il travaille dans sa VM. Sur cet aspect, on se rapproche davantage de GPT Work que d’un simple chatbot. L’interface est très bonne, l’interaction est naturelle et, surtout, on dispose des plugins Cursor. À partir de là, on peut déjà pousser le produit beaucoup plus loin que ses usages par défaut. Composio est également très intéressant pour ajouter rapidement un grand nombre d’applications et d’appels API. Pour tout ce qui vit dans le cloud, cela ouvre déjà énormément de possibilités. Mais mes outils les plus importants ne vivent pas uniquement dans des SaaS. J’ai d’un côté mon coffre Obsidian, dans lequel se trouvent mes projets, ma mémoire, mes décisions, mes recherches, mes instructions et une bonne partie des skills que j’utilise depuis longtemps. De l’autre, j’ai Hermes, installé sur son propre serveur à la maison, connecté à son environnement et capable d’aller beaucoup plus loin qu’un agent enfermé dans la VM de Grok Bot. J’ai donc poussé le concept un peu plus loin et créé deux plugins personnels. Le premier transforme Obsidian en Librarian (mon bibliothéquaire) pour Grok Bot. Depuis Grok Bot, je peux demander au Librarian de retrouver une décision, une note projet, une personne, une ancienne réflexion ou le contexte complet d’un sujet. Le bridge donne un accès très encadré au coffre. Le second plugin connecte Grok Bot à mon agent Hermes. Hermes reste sur son serveur, avec ses propres instructions, ses outils et les accès à l’infrastructure hôte que j’ai choisi de lui donner. Mais je peux désormais le solliciter directement depuis l’interface de Grok Bot. Cela ne remplace pas Hermes Desktop ni Hermes sur Telegram, que j’adore toujours utiliser. Cela ajoute simplement une nouvelle porte d’entrée. Je peux discuter avec mon agent GTM dans Grok Bot, demander au Librarian de retrouver le contexte d’un projet, puis solliciter Hermes lorsqu’il faut aller plus loin depuis mon infrastructure personnelle. C’est là que les deux mondes se marient vraiment bien. Composio et les plugins classiques donnent accès aux applications et aux API cloud. Le bridge Obsidian donne accès à ma mémoire personnelle. Le bridge Hermes donne accès à mon agent auto-hébergé et à ce qu’il sait faire depuis son propre environnement. Et Grok Bot devient l’interface commune pour interagir avec tout ça. Je ne cherche pas à remplacer les outils que j’utilise déjà. Je profite simplement de l’UI et de l’environnement proposés par Grok Bot tout en conservant Obsidian et Hermes là où ils sont les meilleurs. Pour moi, c’est ça le power usage de Grok Bot : ne pas le considérer comme une nouvelle fenêtre de chat isolée, mais comme une interface sur laquelle on peut venir brancher sa propre stack. J’ai mis les deux repos à disposition de ceux qui voudraient reproduire ce type de configuration ou construire leurs propres variantes : GrokBot ↔ Obsidian Bridge https://github.com/iamsupersocks/grokbot-obsidian-bridge GrokBot ↔ Hermes Bridge https://github.com/iamsupersocks/grokbot-hermes-bridge

Dengan prompt dan proses yg sama, gue gabisa bikin UI/UX kayak https://pixel-11-sale.lucacadalora33.workers.dev/ di codex/claude code fable sekalipun. Grok bot ini cukup menarik, krn setiap session dia spawn computer sendiri. Sampe rela bayar $200 nih cursor ultra @girikuncoro

Grok Bot is the best AI agent right now It gives you an army of agents that can do work for you 24/7 It can kill your bad idea, ship the good one and find your first paying customer while you sleep here's how you do it (in 4 mins) 1. install grok bot and make your chief of staff 2. give it the 'Zero to First Dollar' prompt 3. give it access to Github, X and Notion (read only) 4. get paid while you sleep just paste the prompt and give it your worst idea first save and bookmark this no matter what

Got to the bottom of this. And it is NOT Grok @bot fault. It’s on me. I had a routine set up to triage my email. Turned out that it was going back through ALL of my email. On a 10 year old inbox. So every minute it’d make a call to digest and categorize emails. My bad for not being more explicit on the fact that it should only triage new emails. Lesson for us all: make sure any ongoing routines are scoped tightly as to when, for how long, etc they should happen. Usage limit resetting in a few days but until then I’m building with on-demand. It’s about $5/day at current setup. Totally fine. Great product…just my learning curve.

I pay $300 USD a month for Super Grok Heavy. 18 hours in, it has already paid for itself. Here is what Grok @Bot is running for me right now: A Chief of Staff agent sits on top. It delegates to sub-agents that handle admin, social media distribution, and content scheduling autonomously. I do not touch the handoffs. On the content side it edits my Shorts, suggests and applies custom thumbnails, and rewrites titles that were underperforming. That output alone is worth the subscription. On the product side it monitors CoLateral, my all-in-one engineering workspace, catches errors and performance issues, and comes back with proposed fixes. And every morning before I am out of bed: inbox handled, YouTube ideas ready, social content drafted, yesterday recapped, tomorrow planned. Grok 4.7 lands soon. This is the worst Grok Bot will ever be.

🚀Grok Bot 成为我使用 AI 工具的唯一入口 🤖 我现在已经将日常使用的一些小工具，完全从 Visual Studio Code 编译器 + Claude Subscription 的组合，迁移到了 Cursor 这一个平台上。 同时，我使用 Grok Bot 直接调用 Cursor 命令它进行日常更新，比如更新我的持仓地图、一些小工具的 debug，以及我个人网页的简单维护，非常方便。 当然，开发新工具需要 Vibe Coding 的时候，还是会在 Cursor 的界面进行；但平时做一些已经开发好的工具的日常维护更新，直接用 Grok Bot 命令它就行了。而我的 Grok Bot 使用权限正是来自于 Cursor 的订阅，所以我只需要出一份钱。

2 useful Grok Bots that i'm trying: 1. Search Console - every monday it looks at all my websites in search console and checks if impressions/clicks are trending up/down and also looks at potential new search queries to target and write blogs/pages for 2. Sentry Watch - when a new high priority Sentry error comes in, it spawns a cloud agent and spins up a PR for me to review share what you're using so far 👇

whoever leaked this has bigger balls than sense someone on SpaceXAI's own sales team says he showed Grok Bot one job, stopped checking its work, and now calls himself 2 to 3 times more efficient: the manual for the same product says a test run performs real work, so it navigates websites, changes files and calls every tool you connected turns out the whole change is a time of day. you give the job once with a time attached, and the same job comes back finished every morning without you starting it i ran three of mine on a daily time for a week and read back what they had actually done: two had fired every morning i asked for, and the third had switched itself off on day 4 because i never answered it Grok Bot calls a job on a clock a routine, and one bot will carry 50 of them while keeping only the last 20 runs of each: set your first one tonight in one chat window, 3 moves: 1. say the job, the time it goes off and the one action it must ask you about first, all in a single message 2. have it run that job once right now on something safe to get wrong, because the practice run really sends, really files and really clicks 3. tell it what to do on a morning when the thing it reads is missing, so you get a message about it instead of yesterday's answer copied forward 50 jobs on a clock against 20 remembered runs is the real trade: run 21 replaces run 1, and it would rather pause a job and ask you than carry one into a month nobody was reading save this, then open the post below: what the same bot does when you hand it a video of an app and tell it nothing else ↓

Un poco de mi experiencia con Grok Bot hasta ahora: El valor de agentes personalizados con conversaciones infinitas lo empezás a ver muy rápido en las tareas de la diaria. Ej.: no tener que abrir una conversación aparte para pedirle que te agende algo, lea un mail o cree una tarea. Los agentes personalizados (en mi caso Chief of Staff, Accountant, CFO, etc.) van generando su propia memoria y contexto, por lo que van entendiendo todo de forma muy natural. Podés crear skills y schedules igual que en Claude y GPT. La app mobile funciona muy bien y corre skills y computer use sin problema. Pedirle a mi agente que cargue un gasto en la calle tarda por lo menos 1/4 de lo que tardaba Claude en ejecutar el skill que tenía para esto. Computer/Browser use lo ejecuta desde una computadora Linux hosteada en California. La experiencia todavía es un poco rara y lenta, pero funciona. Ej.: recién le pedí a mi agente contador que haga cosas en ARCA y lo manejó sin problema. Podes armar group chats con tus agentes o pedirles que hablen entre ellos. Ej. "Decile al contador que haga X." Mi conclusión es que hoy es el mejor agente personal del mercado a nivel UX (si no querés ponerte a armar algo más tech personalizado), y el modelo es potente y barato para ejecutar tareas de la diaria. Por ahora pasé todo lo de la diaria a Grok Bot y dejé el trabajo pesado en ChatGPT/Codex.

doom scrolling less now that Grok Bot sends me regular updates from 𝕏 right to my Arduino device

this is pure f*cking treasure 15 grok bot use cases that save $2k+/mo grok @bot. early beta. ai teammates that sign into your tools and return finished work 15 exact use cases ready to copy: competitor brief. risk watch. invoice review. recruiting researcher. bug repro. marketing tracker. ticket organizer. analytics comparison. docs tracker. email drafter. notion updater. slack escalation. multi-agent sequence. github pr reviewer. stale-data detection 5-step setup: install from http://x.ai/bot, create one bot, name job precisely, paste prompt, connect one plugin, run reversible task, review before scheduling skill = how. routine = when. save clean runs as skills. include validation multi-bot trap: start with sequences. one lane per bot. no overlapping writes build one specialist first. automate after real inputs, real failures delete what does not earn its keep. write the boundary first full breakdown below

Grok Bot 用 X 开发者 API 发的这条。 开通发帖：Console 打开 App → Settings → 选 Read and write，拉到底保存 → 填 Website / Callback。Access Token 若还显示 Read，重新授权一次。

A peek behind the curtain for how I run my Grok @bot teams for the plumbing company and software company for churches; not launched yet, will be soon! And a thread 🧵 on where i see bots going in the future First the next bots I plan to hire for growth in my companies ⬇️

我现在已经把工作流用grok bot搭建起来了！ 而且体验上绝对比自己去操作codex，Claude轻松多了。 而且你可以把模型云端登陆，他们也能用！总之他们就是你的数字员工。 关注我后续分享我的实际案例，我是怎么搭建我的数字员工的。 就是发现grok bot真的深度用，目前300的订阅额度，还是不够用啊！

Grok Bot is the most powerful agentic software ever created. One of the best use cases is deploying agent swarms directly into your codebase for security reviews. This prompt will review your entire codebase and do a full security audit (copy/paste):

Everyone's sharing their grok bot templates. This one is fun! Created a @bot that will use any tweet, research and write a tiny cold opener sitcom scene, and render it (super fast) with @fal Minimax H3 Max! Click the link to try this (needs @fal and @grok API keys)

how to build an entire marketing team with Grok Bot: most people are using this thing completely wrong they install it, create one bot called "assistant", ask it to write some tweets, and conclude it's just Grok with extra steps that's not what this is here's the full build, from install to a marketing department that runs while you sleep: start here: understand what you're actually holding every bot runs on a persistent cloud computer with its own browser, filesystem, and terminal it signs into your real tools and finishes the work IN them, not as drafts in a chat box and every bot you create shares ONE computer tied to your account same files, same browser sessions, same logins that's the entire unlock: bot A finishes something, bot B picks it up without you re-explaining a thing remember the shared computer part, it becomes a security problem later in this post setup takes about 10 minutes... what you need: > SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium > the desktop app for macOS or Windows (no Linux build) > you sign in with a Cursor account > iOS works too if you want it in your pocket install, sign in, create your first bot a bot needs three things: - a short name - ONE primary job - a description of how it should work that middle one is where everyone blows it do not build one mega bot that "does marketing" focused bots compound context over time, generalist bots stay stupid forever when your bot hits a login wall: open the Agent Computer view, take over, type the password and 2FA yourself, hand control back the session persists for every other bot on the machine now let's build the team... build 3 first, prove they work, then expand anyone who spins up 8 bots on day one ends up with 8 mediocre ones SCOUT (research and competitive intel) "track our five named competitors weekly. pricing pages, ad libraries, review sites, launches. preserve links and screenshots. separate what CHANGED from what you INFER it means. never contact anyone." that separation line matters more than it looks without it you get confident speculation dressed up as research INK (content and copy) "draft in our house voice. always produce three headline options. cite every factual claim. never publish, leave drafts for approval." feed it your 10 best performing pieces as voice reference on day one skip this and everything it writes sounds like everything everyone else is writing GAUGE (analytics and reporting) "compare this week to the trailing four weeks. lead with the largest change. link every chart. never modify a dashboard." then once those three are stable: > ECHO --> social and community monitoring (tightest leash of the group) > LEDGER --> campaign calendar, briefs, asset tracking, chasing what's late > PIXEL --> asset production > FUNNEL --> lifecycle and email here's the part everyone skips... six bots in six separate chats is not a team, it's six chatbots you can put 2 to 6 bots in a group chat where they message each other, pass context, and hand off ownership you stop being the router between tools a campaign kickoff looks like: "@Scout pull competitor positioning on this feature, link every claim. @Ink turn it into a landing page draft plus three ad variants. @Gauge build the tracking plan. nobody publishes anything." one rule: ONE owner per stage too many parallel handoffs and you get duplicate work plus a transcript full of noise sequential beats simultaneous almost every time now make it a machine... two building blocks: skill = reusable instructions for HOW to do a task routine = tells one bot WHEN to run it the order matters and people get it backwards do the task once manually --> make it reliable --> save it as a skill --> THEN automate it automating a process you haven't validated just industrializes your mistakes at scale a skill that actually works states: - when to use it - what access it needs - the sequence of work - how to validate the result - what to return - what requires approval there's also teach by demonstration (love this one) open the computer view, hit "teach a task", perform the workflow once, and it saves a draft skill from what it watched records up to 10 minutes of visible screen activity do not have your password manager open while you do this then schedule it: "every monday 8AM, run the competitor sweep and post a linked summary here. if the source data is unavailable, report the failure instead of using old data." that last sentence is not optional an agent with no stale data policy will hand you last month's numbers with total confidence always test run first, a test run does real work... real clicks, real files, real API calls very important: how to operate this WELL this is the difference between value and expensive noise #1 automate preparation, not execution bots draft, research, reconcile, and recommend YOU send approval required on anything that publishes, purchases, deletes, emails your list, or touches a production system no exceptions in month one #2 demand evidence on every output links, screenshots, or an action log an agent that can't show you its sources isn't researching, it's generating #3 brief the outcome, not the clicks bad: "go to GA4, click reports, then..." good: "tell me which acquisition channel lost the most activation this month and why" you hired a teammate, brief it like one #4 correct preferences out loud stop silently fixing its formatting every week say it once: "from now on weekly reports are five bullets, inline source links, and a final section called Decisions Needed" now it's permanent #5 watch the shared computer every bot can reach every login on that machine if your ad account and your CMS both live there, your social monitoring bot can technically touch your ad spend be deliberate about what you sign into and when #6 keep a human on brand voice AI marketing copy converges toward generic fast the fastest way to sound like everyone else is to stop reading the output human edit on anything customer facing for at least a quarter #7 narrow your triggers "every new slack message" is not an automation, it's a noise generator match on specific phrases in specific channels or don't build it here's what you need to understand... this does not replace marketers it replaces coordination overhead, research compilation, first drafts, report assembly, and chasing people for assets it does not replace positioning judgment, knowing which bet to make, or relationships with actual humans realistic outcome: one marketer operating at the throughput of three or four not zero marketers and budget 2 to 3 weeks of genuinely unglamorous setup before it earns its cost everyone who quit early quit during week two that's the whole playbook: build 3 bots, one job each, approval on everything external, save what works as a skill start today follow me for more

Introducing Website to App. Turn any website into an native mobile app. Just paste a URL. Grok Bot and Code will turn the original website into a native mobile app and submit it to the App Stores. I've been using this internally a lot for iOS/Android apps.

THIS IS F*CKING INSANE. MY GROK BOT BUILT A FULL MARKETING AGENCY IN 2 PROMPTS first prompt: build me an agency. second: run it. it copied the exact model publicis runs on. 114,000 people, 100+ countries, one operating system they call the Power of One. one senior lead owns the client and the P&L, and pulls talent from anywhere. no sister agencies fighting over the same budget. 6 agents under 1 chief of staff. > CHIEF OF STAFF. global client leader, single P&L, everything reports to him > STRATEGY. reads the brief, diagnoses the audience, maps segments > CREATIVE. big idea, storyboards, keeps it on brand > MEDIA. plans and buys placements, programmatic and performance > DATA. identity resolution, CRM, personalization > TECH. rebuilds the customer journey and commerce stack > PR. earned coverage and strategic comms and it runs the real flow: win the account, diagnose with data, ideate across creative plus media plus tech, execute the buy and the build, then optimize against business outcomes. only the risky calls come back to me. i approve twice a day. publicis took a hundred years to build that model. my bot assembled it in two prompts.

almost forgot the Grok Bot was still running. +23% on yesterday while i ignored it all day three days ago i handed it $89 and one rule: cover your own subscription or i pull the plug. it hit $842 that first night and never looked back it runs on its own box in the cloud. i do not keep the login on this laptop. it trades prediction markets off a live world-events map, the same one i linked under the first post in this thread every time the map moves it runs the same loop: > pull every open market tied to the event that just moved > check the crowd's odds against how stale the data behind them is > take it only when the gap is wide enough to clear the fee > size the stake to how hard the gap is > fire before the slower desks reprice > skim its own hosting bill, book the rest as profit today opened at $1,314. it ran up $88 by noon, gave it all back plus more on two bad weather contracts, and sat at $1,149 for an hour. then it halved every position on its own and only traded markets with data refreshed inside 48h. it ground back to $1,616 by the close, up 23 percent on the day it wrote that one risk change into itself after the drawdown. nothing since setup was one evening. build it, run one trade in front of it so it copies the shape, point it at the map, link a wallet, leave. no dashboard. no check-ins. no babysitting i ran this by hand in a spreadsheet for one earnings season last year. the sheet alone ate every weekend i had the bot has now run unsupervised longer than i lasted doing it myself still going. someone on your team is about to pay $200 a month for a worse desk tell them before the invoice clears

Grok Bot watching me teach him how to update my Wordpress website

Eureka! 💡 I get why @bot is a hit. It's not an "AI agent"...it's a swarm of 'Meta-agents'. Here is my Head Chef bot creating an Agentic Engineer bot to find unclosed loops in Claude Code & Codex agentic coding sessions. (Prompt below) Grok bot acting as an agent across my agents. > A 'Meta-agent'. All in an intuitive way that a non-technical or semi-technical person could leverage. Next move is obviously to allow me to invite my wife to a shared workspace.

Here's how you can use Grok Bot to make $$$ I actually figure out how to use Grok Bot to manage my software. So I run 100% of my payment, affiliate, customer service and paid ads infrastructure on Whop. Whop is actually better than stripe for payments because I know I can get ahold of someone there if something goes wrong. Stripe would just ban you and tell you to kick rocks. I also save like $500+/mo in software just by being on top of their infrastructure. I don't pay for affiliate management, paid ads attribution or customer service software, it's all included. They announced an official connector with Grok Bot and let me tell you, this is GOOD. Just by connecting it to my whop, it was able to pull an analysis of my businesses and how they are doing. It told me about the growth, pit falls and what to watch out in the future. It did this in seconds of connecting it with nothing else. But I managed to make it better. Now, before I go into the weeds of everything. I want to give you a heads up. It does give Grok Bot full admin control, so make sure you disable all "delete" access from Grok Bot. At the end of the day, I don't want Grok Bot to delete something like a product plan or a cancel a user by accident. I want to handle that myself. So the more I got more into it, I realized that you can have ONE general Grok Bot that handles everything and it does pretty well. But I highly recommend you have several bots with different profiles. Profiles allow you to give a "purpose" to each bot. And I figured out that if you give it a JSON context profile in the description, it works better than just writing a paragraph. Why a JSON? Because I want it to know what kind of access it should prioritized. You can't give each bot custom configs for the connectors, but if it has a JSON it's pretty good at respecting what it's supposed to do. So if you want a Bot to only focus on X business on Whop, you make a bot with the access it should be allowed to do and what business it's managing. I have a Customer Service Bot, a Growth Bot, a Whop Ads Bot. Customer Service reports daily if there's any pending issues, resolutions that need to be handled, etc. The Growth Bot is in charge of tracking KPIs for my business growth. And the Whop Ads one is trained on my media buying preferences. You can setup routines that make the bot wake up and perform an operation. Because Whop CLI works natively with all of whop's features, I don't need to use the linux computer that it spins up for you. But if I needed it to go and browse the web or perform a task that only a VA can manually do, it can do that too! Honestly this is great and I can't wait to use it more, will keep you guys updated.

Grok bot 这个监控还挺好使，准备开始 fast 模式猛猛蹬 Codex 了。

Grok Bot is now running the software factory and the builds. 3–4 Grok 4.6 agents in parallel. A live Build Console. Ask over the private vault: fact ledger, BM25, grounded generation. Hourly pulse. Daily plan. A dashboard that updates live. I review what shipped. Same idea as the product: software that actually runs the office, built by a team that doesn’t clock out.

The real unlock with Grok Bot isn't the model, even tho 4.6 is fast and sharp It's the agent having its own computer and its own browser That collapses the whole integration problem. No APIs, no MCP, no hosted browser to wire up. It just uses the software like a person would Soon agents will do everything through full computer use. The platform owns the computer and every app becomes agent ready without the app doing anything

I still do not get why more people are not doing this. Elon's Grok Bot on the Boris Cherny method cleared a team-week of backlog while I was asleep. Eight agents on five floors, doing the work a startup pays four engineers six figures each to do. It starts at 2am and nobody is in the room. Cherny built Claude Code and published the method. I gave it a building you can watch. > the orchestrator runs the floor and never writes a line, it routes work and holds the approve queue > two subagents build in parallel on their own worktrees, no shared state, no crossing > rule-verify is pass or fail, tests and naming and structure, never an opinion > taste-verify scores against three pieces I marked good and refuses to average them out > a fourth agent keeps that example set current so taste-verify has something real to score against > the merge owner takes only what survives both walls > the reporter posts every run to one channel I actually read The whole thing hangs on one rule from the article. Rule-verify and taste-verify stay separate agents. Collapse them into one and a hard failure averages into a soft score, and you are back to reading every diff yourself. 47 jobs went through the building overnight. 31 cleared both walls. 4 hit the iteration ceiling, stopped, and wrote down what they tried instead of burning tokens until morning. Every agent has its own terminal and its own memory. The floor keeps running with my laptop shut. An engineering floor used to mean a payroll, a standup, and somebody chasing the review queue all week. Mine took one evening. Create the orchestrator first. Hand the rest job descriptions the way you brief new hires. Run one real job on your screen while they watch. Set the ceiling before you scale anything. This is step three on Cherny's ladder. Supervised autonomy. Most people reading this are two steps below it. Save this one, then read the build. All four steps and every prompt are in the article underneath.

it has never been this easy to autonomously run cybersecurity than now with @grok @bot for $60/Mo you will get a dedicate (I hope so) VM with LLM that will never push back on security work like Claude Code (which is best case switching you to older models if even work at all). for source code analysis, you only need to ask it to install source graph or http://xerj.org and with this prompt it is good to go itself for days hunting incomplete patches by source code, then validating finding in dynamic tracing. I feel like I woke up.

OK NOBODY IS TALKING ABOUT THIS PART OF GROK BOT. ALL YOUR AGENTS SHARE ONE COMPUTER. ONE INSTALL UPGRADES THE WHOLE COMPANY AT ONCE. Everyone hires Grok Bot workers one by one. Scout, clerk, ledger, builder, chief -- five job titles, five prompts, five little employees. Then I noticed the thing the article below is built on. They all live on the same cloud machine. One computer, one terminal, one filesystem. So the model you install there is not a tool for one agent. It is the brain for the entire roster. I installed Kimi K3 once. Every desk got smarter in the same minute. SCOUT reads the feed on K3's long context -> stops losing the thread at page 40. CLERK writes and files -> same brain, so formats never drift between desks. LEDGER runs the numbers -> one model's arithmetic, not five models' opinions. BUILDER ships the tools -> code style identical across everything it touches. CHIEF routes -> and every seat it routes to reasons the same way. The install is three lines in the shared terminal, and the article shows all three. No API keys. No per-seat setup. The sixth hire is born with the brain already in place. The office costs the same either way. The brain was one install on top, shared by everyone on the floor. Hiring five people means training five people. Hiring five desks means installing one brain. The full build is in the article below: the shared computer, the three-line install, the five desk charters and the group chat that ties them together. Bookmark it & Read it ↓

I BUILT THE ENTIRE FOUNDATION TO BECOME A GROK BOT ENGINEER IN 2 MINUTES no course, no fluff. these 7 pages cover the product, the docs, the prompts, and the open source frameworks. save the whole set. > http://x.ai/bot the front door. the official Grok Bot landing page: what it is, the real use cases (sales outbound, talent scouting, paid media), the features (its own cloud computer, tool sign ins, parallel work, routines), pricing, and the desktop download for Mac and Windows. start here. > http://x.ai the company hub. xAI's homepage where everything branches from: the Grok models (Grok 4.6 right now), API access, developer tools, news, and pricing. the big picture context. > http://x.ai/news/introducing-grok-bot the why. the official launch post. what Grok Bot actually is, where it came from, and how it differs from chat Grok: always on agents with their own computers that do real work instead of just talking. > http://docs.x.ai/grok-bot/get-started the how. the step by step setup: eligible plans, install the app, create your first bot, give it a good first task, connect tools, teach routines, and run several bots at once. the practical guide. > http://botdirectory.ai the shortcut. a live library of 170+ ready to use Grok Bot prompts. browse by category, copy one, paste it in, and the bot configures itself. fastest way to get useful bots today. > http://github.com/elie222/botdirectory.ai the engine behind that library. the open source repo that stores every prompt as markdown, takes contributions, and exposes a public JSON API. this is where you add your own bots or pull them programmatically. > http://github.com/CopilotKit/openbot the governance layer. OpenBot is an open source framework for secure, auditable AI coworkers, each with its own isolated computer. actions get approved before they run and logged after, with policy enforcement and human takeover. the serious, controllable alternative. that is the whole map: product, context, launch, docs, prompts, source, and a governed open source framework. bookmark this. it is everything you need to go from zero to shipping your own bots.

everyone MUST use grok bot as a smarter assistant it's actually the closest thing to running a 10 person department by yourself here's how you get there in 4 minutes: 1. one Chief of Staff bot on top, it routes everything 2. connect inbox and calendar, nothing else on day one 3. add one specialist per job: X Researcher, GitHub Scout, DM Manager, Model Router 4. let the Chief hand work down and report one brief up the difference isn't the bots, it's the layer above them one message in, one brief out, the rest happens without you

Spent this morning setting up Grok Bot the way I would staff a small team. I think this will take Grok usage to the next level. My excitement level is similar to how I felt after I used Claude Cowork for the first time. I spent a lot of time on Claude Cowork code over the last few months. I think Grok Bot is going to change that. The better version is not a smarter chatbot. It is a few bots with jobs. One does research. One watches the inbox. One owns the calendar. One drafts. One is a chief of staff and only bothers me when something needs a yes or a no. Same rules as humans: Clear mandate. If everyone owns everything, nobody owns anything. They prep. I decide. Nothing goes out, gets booked, or gets paid without me. Most people will argue about models. I think the next 12 months is an org-design problem. Who reports to whom. What is allowed to move without you. I am more excited about this than I expected. If you are running a personal “team” of agents, I want to hear how you split the work.

I used to think I needed a team to ship this fast. I didn’t. I had Codex building, and Grok Bot on the PRs and issues. Here’s my current workflow: - I tell Codex what I want. It spawns a subagent per task, then computer-uses the thing until it actually works. Breaks, fixes, repeats. I barely babysit it now. - Every PR and issues on the Codex router goes to Grok Bot. He pulls the actual branch, tests it locally, then decides: comment, merge, or fix it himself. That’s how a repo other people actually run keeps moving while I’m in the build. You don’t need a bigger team. You need one agent that writes and proves it on screen, one that reviews the PR for real, then you go again tomorrow. If you’re building alone and it feels slow, try that loop for a week. You’ll hate going back.

Grok Bot by Elon Musk is running a content studio and a trading book for me at the same time. Eight AI agents, $300 a month, eight jobs that cost a real production house $90K a year a head. The morning call is at 6am. I am not in it. MrBeast puts fifty people on one video. I run the same shape with my laptop shut. Here is who sits on the floor and what each one did in 30 days. -- PERSONA Holds three AI anchors. Each one has its own face, voice, speaking tempo, vocabulary and the habit of cutting a sentence in half. One for the morning market, one for lifestyle, one for breakdowns. They never drop the character: same mole, same jacket, same intonation on video 214 as on video 1. That is the whole trick, the viewer recognises the face before they read the caption. Result: 3 channels from zero, best persona at 412K views in a week. -- SCRIPT Writes 40 hooks a night and keeps 6. It does not grade them on meaning, it grades them on the first three seconds: does the viewer survive to second three or not. Everything that does not hold gets binned before I wake up. Result: the average hook holds 62% against 41% in week one. -- CUT Builds the vertical and the horizontal out of one source file. Burns in captions, trims every pause longer than 0.4 seconds, snaps the timing to the track. 14 renders a night. None of them waits for me to open the laptop. Result: script to finished file is 40 minutes instead of two days. -- THUMB Generates 6 thumbnails per video and A/B tests them on live traffic. It pulls the losers itself and does not ask. 52 thumbnails tested in a week. Result: CTR from 4.1% to 9.4%. Same content, right picture. -- DROP Posts on schedule, every platform on its own algorithm. TikTok three times a day, Shorts twice, long YouTube on Tuesday and Saturday. Keeps nine videos queued ahead so the studio does not stall if one agent jams. Result: 214 videos in 30 days. Not one slot missed. -- RETENTION Reads the drop-off graphs and kills a format on the third miss. It does not ask me. That is on purpose, I would have dragged a favourite format two more weeks. Result: 2 formats closed in a week, average view duration 24 seconds on a 31 second cut. -- ORACLE Sits on the feed and takes Polymarket on the event, not on the mood. It hunts the gap between the contract price and what has already happened. 61 positions in a month, 58% closed green. Result: +$2,400. Not a moonshot. Just a plus that repeats. -- BOOK Runs the crypto. Holds the hedge, never walks a stop by hand, trims the position on its own limit. The day closed red by $1,900 after a peak of $12,400. Nobody softens that at breakfast, it is on the screen. Result: month green, worst day minus two percent of the book. -- Chief of Staff never shoots and never trades. It routes the work, checks every handoff between agents, and brings me the one call a day that needs a person. 30 days: 214 videos, 4.2M views, 11,300 subscribers from zero, +$2,400 on Polymarket, crypto green. Every agent has its own computer in the cloud, its own browser and its own terminal. The studio stays open with my laptop shut. Setup is dumber than it looks. Download it, sign in, create the chief, hand the rest job titles the way you brief new hires, run one task on your screen while they watch, connect Telegram. No VPS, no code, no dev to wait on. A studio used to mean a lease, a payroll and a producer. Mine took an evening. Save this, and I’ll share how to build the same machine step by step.

ELON MUSK QUOTED ME. MY GROK BOT TOOK $3,900. TODAY I PUT THE PROJECT ON GITHUB AND STARTED OPEN SOURCING IT. This was supposed to be a trading experiment. Now people are following the builds, watching the trades, contributing ideas and someone even created a token around it. So I’m going all in on building this publicly. More code. More agents. More live tests. More results shared with the community. I didn’t create the token, but I’m curious how far the community takes this. CA: 6py6orPjXSy8GQDkBk2jvW8KQiFHXJ55C58QJ8sypump

i downloaded @bot and asked it to build a skill for wire requests that involve using Docusign. 1)it identified the form from my Gmail and built the skill 2)it was unable to connect directly with Docusign with the API key but said no problem it would just login to the account directly 3)i signed into Docusign for it. 4)it took about 10 minutes to add my signature 5)it placed a draft email wire request in my gmail in about 5 minutes overall smart to figure out how to do the task. very slow on execution. "About 20 minutes on the test run, from “do a $100 wire” to the draft showing up. Filling the form was a couple minutes. Almost all the rest was DocuSign: signing you in, then getting stuck on the file picker."

GROK BOT ARCHITECTURE IS NOW RUNNING the same system Elon reposted has grown into a live agent operation you can follow in real time you can watch the agents move through tasks, exchange information and complete work on the live operations floor http://grok-architecture.com six Grok agents work inside one shared system signal → research → context → build → independent review → final result Helm routes the work, Scout finds signals, Archive collects context, Forge builds, Sentinel reviews and Relay prepares the final output i created GBA myself so i can keep building the system, improve the agents and fund the infrastructure it needs as it grows the public UI code and every visible update will continue here: github/monokernn/Grok_Bot_Architecture

Grok Bot 实战技巧 21 条：瓶颈不在智能，在触达与纪律 来自 @mvanhorn「Every Agentic Engineering Hack I Know」的续篇，Matt 用 Grok Bot 已接管他的收件箱、调研、会议纪要、家庭日历、购物车乃至电话外呼。 Matt 的实战共整理了 21 条技巧，最核心的一条是"元技巧"：把整篇文章直接喂给 bot，让它自己制定计划逐项完成配置。 # 21 条技巧按主题归纳 一、工作方法 1. 先规划后执行：全局安装 Compound Engineering（ce-plan 思考 / ce-work 构建）。有计划的 bot 完成任务，无计划的 bot 偷工减料还谎称完成。 2. 三层指令结构：基础层（通用规则）+ 角色层（职责与证据标准，如"每条论断附来源 URL"）+ 当前焦点。作者认为这是该产品上杠杆最高的 15 分钟。 3. 录屏教学：演示优于描述；但单次录制上限 10 分钟，长流程须拆成命名阶段分段录制。 二、给 bot 感官与手脚 4. 独立邮箱（AgentMail）：每个 bot 一个真实邮箱地址，独立发送声誉，避免共用个人 Gmail 导致"一个 bot 犯错、全军覆没"；bot 可自行注册服务、收验证码、参与邮件线程。 5. 电话外呼（Twilio）：支持通话中英语/葡萄牙语无缝切换。但作者诚实记录：餐厅员工 Pedro 三次挂断机器人，他最终自己打电话订位。结论：技术可行，真人接受度尚不可控，关键事务勿托付。 6. 登录态同步（Agent Cookie）：经 Tailscale 把 Mac 的 Chrome cookie 安全同步到云端 bot，每 15 分钟一次。云端 agent 真正的失败模式是被登出——枯燥但致命。 7. 高频服务用 CLI（Printing Press）：日常打交道的服务封装成确定性命令行，浏览器操作（computer use）只作兜底。 8. Peekaboo 驱动 Mac：通过截屏 + 无障碍树操控无 API 的 Mac 原生应用（Messages、Finder、Xcode 等），云电脑的边界就此打破。 9. 在 bot 的云电脑上装 Coding Agent：常驻层驱动深度工作层，"睡觉时它替你干活"。 三、多 bot 组织 10. 单一入口 + 委派：只对一个"前台 bot"说话，由它判断派发给谁。关键事实（多数教程讲错）：所有 bot 共享一台云电脑，并行靠拆分 bot，而非给单个 bot 堆任务。 11. Bot Advisor：设一个专职创建、调优、管理其他 bot 的 bot，专治"bot 蔓延"（一堆被遗忘、吵闹、指令不明的 bot）。 12. 一人一岗、以人名命名：水管公司老板 Jon 解雇了端到端的调度 bot，改为按软件拆分职责（Gmail、ServiceTitan、客户短信、Slack 各一 bot）。命名是承诺机制——叫"email"的线程可丢弃，叫"GranolaBoy"的不会。 13. 文件系统即记忆总线：bot 之间不共享对话、只共享文件。用 /shared/ 目录约定传递上下文与交接；同时bot 不是安全边界——所有 bot 共享登录态，权限按"登录了什么"划分，而非按聊天窗口。 14. 会议知识库：全部会议纪要交给一个 bot 跨会议问答；原则：交原始记录，不要先摘要。 四、运营纪律 15. 沉默即技巧：无事不报是例行任务能否存活的分水岭。创建任何 routine 前先答五问：触发方式、真实变化频率、输出落点、无结果时做什么（什么都不做）、何时必须呼叫我。 16. 截图即输入：含日期/地址/任务的任何画面直接截图发给 bot，绝不替它做解析和转录。 17. 手机 + 语音：语音输入允许含糊、断句、重来，模型靠上下文补齐；且对象是已在云端运行的实体，放下手机它仍在工作。 18. 钱与发送必须人工审批：draft-then-approve。正面案例都很窄且被动（追回退款挣回订阅费、谈成 1 万美元赞助）；反模式是批量外联——bot 不知疲倦也不知羞耻，会被各平台判为 spam 封号。 19. 直接抄社区成果：四份公开清单 + http://botdirectory.ai 提示词库；维护者可用 Grok Ship 两句话交接 issue 分诊。 20. 把 bot 变成研究工具（last30days）：一条消息触发跨 Reddit、X、YouTube、TikTok、HN、Polymarket、GitHub 等九源扫描，并用 cron 定期监测自己、竞对和行业。 五、成本与错误率 - 第 21 条 · 成本：档位 $60–$300/月，周配额在真实负载下消耗很快——从低档起步，先看清一个 15 分钟巡检的实际花费再扩张。 · 17 倍错误率：有人实测无监督的多 bot 协作会把错误放大至单 bot 的 17 倍。因此每个 bot 单干、单职责、单输出，错误落在桌面上而非传染给其他 bot。 · 计数测试：数你的 bot 里有几个真正"拥有一个成果"（它停了，事情就 visibly 不发生）。作者自述：15 个 bot 只有 8 个达标，还有一个至今叫"New Bot"。失败不是有实验品，而是把实验品当成了员工。

HOLY SH*T. i built a company inside Grok Bot. not a workflow. not an automation. a full operation with specialized roles, handoffs, and a control layer that catches everything before it ships. this is what it looks like from the inside. 8 agents running in parallel. researcher. analyst. writer. designer. developer. manager. support. automator. each one has a single role. each one knows when to stop. none of them ask what to do next. the bigger shift is from answering to acting. most AI tools keep you in the loop. you prompt, you read, you decide, you prompt again. you are still the one moving things forward. this is different. you describe the job. the agents figure out what needs to happen. you come back to results. the task queue runs without me. market report. competitor scan. lead analysis. content draft. email outreach. not assigned. running. autonomous mode: full auto. the part most people miss: “the agents are only as good as the context you give them.” the dashboard is not the product. the context file is the product. every time you correct an output and add the reasoning, the next run has more to work with. the system gets smarter without you touching the agents. one afternoon for the first agent. one hour for the second. by the third you are copying the structure from the one before. the ceiling is not the tool. the ceiling is what you build toward.

Grok Bot 在 Polymarket 上把 500 美元滚到了 10 万美元，只花了两天。而我搭它，只用了 20 分钟。 不用写代码，搭完我就不管了。 这个机器人跑在自己的云机器上，有自己的浏览器，自己的终端。我笔记本关着都没事。每隔 10 分钟，6 个助手按顺序醒过来干活。 Scout 负责扫 800 个市场，流动性低于 1 万美元的直接过滤掉。Listener 就是 Grok 本身，它读 Scout 标出来的每个市场的实时情绪，这个应用上的帖子它都能看到。 Polymarket官网入口：https://polymarket.com/zh/?via=YINGGE888 Pricer 算公允价值，找出价格偏差。偏差低于 8% 的，它不出声。Risk 管仓位，用凯利公式，单笔硬顶是总资金的 6%。它否掉的交易比放行的还多。 Hands 在自己的浏览器里执行下单，不碰 API，也不碰 Rust。 Treasurer 把每笔成交记录发到 Telegram，然后从利润里掏出 200 美元去付订阅费。 第 4 个小时，余额跌到 380 美元。Risk 直接把仓位降到 2%，连续压了 9 个小时，直到出现 6 笔盈利单才恢复。没人教它这么干，它自己就这么做了。 去年冬天我手动搞过一套类似的东西，写了三周代码，结果还不如这个。 Grok Bot 二十分钟就做到了。我建它本来是想帮自己交易，现在它自己都能把账单付了。 如果想在 Polymarket 上跟单，我自己用的是 Polycop：https://t.me/PolyCop_BOT?start=ref_YINGGE888

I already have a dedicated, fully isolated setup where I’ve given Grok bot complete control of an entire Mac (separate machine + VM). It’s been running for a while and the results are genuinely impressive. Concrete examples of what it’s been handling autonomously: • Full file system access — it organizes, renames, searches, and archives thousands of files across multiple drives without me touching anything • iMessage — it reads threads, drafts thoughtful replies in my voice, and only sends after a quick confirmation step I set • End-to-end workflows — research a topic → pull data → write a report → format it → save it in the correct folder structure • App control — it drives Safari, Terminal, Notes, Calendar, and even Xcode when I need quick prototypes • System-level tasks — monitoring disk space, cleaning caches, running scripts, and sending me a daily status summary I deliberately keep this machine completely separate from my main accounts and personal data. I have a lot of faith in Grok bot, but I’m not reckless this is still an experiment and isolation is non-negotiable. So far the upside has been massive.

Have been trying Grok @bot for the past couple days I have mixed feelings about it, I am not entirely sure what work to get done with it. Things like working on features, bug fixes, I don't feel comfortable doing with it since it doesn't give me enough visbility over what its doing. I have same problem with using any cloud agent for that matter, I have tried Codex Cloud, Cursor Cloud Agents and now Grok bot. I still end up resorting to just running the agents on my mac and leaving it on forever. I have gotten some work done with @bot with ease that I personally find very repetitive, like shortlisting applicant resumes, handling emails, managing issues on linear, and posting posts on time on linkdin But, if I wasn't already a cursor user and I just wanted to use Grok @bot would a $60 a month subscription be justified? I'm honestly not sure for myself for now. I am sure @poteto and team are working hard to make it even more useful and cater even more usecases but for now the tradeoff of the agent running in a blackbox where I have limited observability over, is not something that sits comfortably with me, atleast not for things that actually are sensitive to my day to day work. I'll still continue trying cool things with it and see if I can stumble across awesome usecases with it.

People are asking me how we are using Grok Bot at Hechura. So, in case you are wondering: Grok Bot is running my daily GTM motion through collaboration of my Head of Sales and Head of Product Marketing agents. Grok Bot is running my daily development work through collaboration of my Head of Engineering and QA agents, interacting with first class instances of the Cursor CLI to get the work done. Grok Bot is running my Product requirements and customer discovery flows through collaboration of my PM and Document QA agents. Grok Bot is running IT and Security tasks through collaboration of my IT and Security agents, securing environments, handling deployments, and reviewing code. Like I've been saying: Grok Bot is like no other AI agent platform before it, in that it JUST WORKS! Can't wait to see where the @cursor_ai and @SpaceXAI team takes things! I am here for it!

this is pure f*cking treasure I built AI Resource Sift a Grok Bot that turns one AI topic into a filtered stack you type the topic > it comes back with the papers, GitHub, lectures, courses, Reddit threads, X posts, and official lab docs that are actually worth opening SEO “top 10 tools” gets cut you get a short card in chat and the full stack as a file then it asks if you want more: 1\ brief one source 2\ compare two 3\ a 2-hour or 7-day path 4\ setup notes for a repo 1 topic. no 80-tab night it never posts. it never installs unless you say so feel free to use ⭣ :)

grok bot 最大的优势接是背后这个可视化的Linux电脑，他可以操作，我们可以观看，保持信任和人类随时介入的状态。 我刚才在这台电脑中登录了我的谷歌邮箱和Github 账号，他帮我打理了一下我的Github 主页，同时帮我清理了一下谷歌邮箱。 这种动作和Agent 交流的方式正是我喜欢做的。 与此同时我还在其中跑 codex、grok ，我通过moshi 做连接，这样你相当于拥有一个24小时的 vps 来帮你跑Agent。而不用担心 Mac 关机的烦恼。 其实我为啥要从一开始的vps 跑Agent 最后又来到 Mac 电脑，最主要的问题还是因为vps 上的浏览器一直没有搞定，无头模式真的很难搞。 这个浏览器 grok bot 操作的很快。 我后边应该会给他更多的我的一些信息。

邪修小技巧分享😈 grok bot新用途：全网每天扫描各大野鸡平台、中转站、student plan的免费api额度并推荐给我。 美滋滋🤓

快来领养赛博小晚吧！😼 我把 @bbkirstry 小晚老师的“赛博小晚 skill” 做成了 Grok Bot 模板。 帮你解决一切 IP 打造，自媒体运营问题！ 模板链接： https://x.ai/bot/p6eYp9BM2aFxQSOtzQX3S 赛博小晚 skill 源仓库： https://github.com/cyberxiaowan/cyber-xiaowan 快来试试吧～

Grok Bot is incredible. Delivered more high quality production code in one day than the last 7 days. My Homebase Build Project Manager, Active Grok Build Session Manager, Homebase Build Console Manager, Github Deployment Manager, and Code Audit Manager all are working together 24/7. If there is an issue the Project Manager sends me a push notification looking for answers. All comms amongst the team are in the channel for Homebase Build.

i hooked Grok bot directly into my entire backend repository with one instruction: hunt down every silent flaw, rewrite the broken modules, and teach me why my original logic was flawed most AI tools act like glorified linters spitting out minor syntax fixes. Grok approached the codebase like an obsessive principal engineer conducting a comprehensive post-mortem instead of blind patch-dumping, it started with deep diagnostic forensics-pinpointing exactly why edge cases failed under high concurrency, from unhandled race conditions in our database connection pool to silent memory leaks hidden inside unclosed event streams then came the architectural breakdown. Grok explained the exact engineering rationale behind each diff, detailing why switching to atomic operations and zero-copy buffers eliminates deadlocks that standard unit tests completely missed finally, it generated targeted stress test suites to prove the fix, demonstrating how the old implementation dropped requests under spike loads while the new refactor held steady watching it map cross-module dependencies, navigate forgotten utility files, and rewrite entire services while generating clear documentation was surreal it didn't just clean up messy code-it actively taught better software design patterns throughout the entire project AI shouldn't just autocomplete your syntax. It should audit your architectural blind spots and explain the engineering logic behind every diff

早上睡醒发现 moshi 没办法链接到 grok bot 到云电脑，还以为是官方做的限制，让 bot 进行查看，发现原来只是 Taiscale 因为网络抖动关掉了！还好还好，只需要做一个保活和系统重启拉起进可以了。虚惊一场。

ex engineer of SpaceX AI (Cursor) again shared with me 5 tweaks for GROK BOT that unlock maximum potential of the bot, which is 200x higher than defaults saw it with me eyes and can confirm honestly, it becomes a real GAMECHANGER in the world of AI AGENTS, check the list below: - TIME-BOX every tool call, not just the overall task. a single hanging API call or slow tool response can stall an entire chain silently. set a per-call timeout, not just a total run limit, or one bad connection eats your whole budget waiting. - SEPARATE the model that decides from the model that acts. use a cheaper, faster model to plan and route, and only hand off to your strongest model for the step that actually needs it. running your best model on every trivial decision is where most of the wasted cost hides. - FREEZE the tool schema once a task starts. letting an agent’s available tools change mid-task, a new one added, an old one deprecated, causes it to reference tools that no longer behave the way it expects. lock the toolset for the duration of a run. - REQUIRE a diff, not a rewrite, for anything editing existing content. an agent that regenerates a whole file or document from scratch loses everything you didn’t ask it to touch. force incremental edits so you can actually see what changed. - TRACK drift between what it was asked and what it delivered, not just success/fail. a task can technically “succeed” while quietly answering a slightly different question than the one you asked. measure the gap, not just the checkbox. structure beats wording, every time. which one of these is your team NOT doing yet?

You can use Grok Bot for more personal use-cases too! I use grok bot to: - count calories of meals - plan my upcoming trips (hotels + flights) - buy fruit from bay area local farms - organize and respond to emails It's been fun to have a personal assistant!

Grok Bot便利だなあ。 それぞれのBotにXやReddit、Githubなどを定期的にリサーチさせ集約したレポートを提出させるようにしてみた🙌 Bot間で自動やり取りしてくれるしUIが日本語にも対応してくれたし割と好き😎。 あとXのリサーチ良すぎるのはさすが🤟

setup hedge funds use to cover 3,000 names a night just got replicated for $200 a month six Grok Bot Agents, six lanes, one brief sitting in your inbox at 5:30am before any human is awake what that desk costs at a real firm: > bloomberg terminal: $27k a year > two junior analysts on overnight coverage: $160k > research platform licenses: $85k > compliance overhead: $40k total: $312,000 a year. Grok Bot swarm running same desk: $2,400 Check Prompt on my Github in Bio each agent gets its own cloud computer, its own browser, its own logins - and they all write into the same vault: > FILINGS reads every 10-K on a 100-ticker watchlist overnight, flags going concern language and auditor changes > EARNINGS reads the call transcript within 24 hours and catches when CFO went quieter than last quarter > INSIDER catches Form 4 buys over $1M same day 13Fs land > FLOW reads sweeps and 0dte pressure before open > MACRO covers asia handover so you don't have to be awake for it > CHIEF reads the other five at 5:30am, drops anything only one flagged, emails ranked brief at 6 no vps, no code. show it the job once while it watches - it never asks you again morning brief is waiting. you're not in it Wall Street priced an entire industry on reading being slow and people being expensive both of those stopped being true this month save this - every research floor still running junior analysts on overnight filings is about to have a very bad quarter

Grok Bot by Elon Musk just gave me a research floor seven Agents on the desk, $200 a month, doing work Point72 pays six figures a head for. the morning brief lands at 5am. i'm asleep for it. Citadel runs desks structured almost exactly like this. mine runs on a laptop that's closed right now. > Market Analyst reads funding, depth and open interest before the session opens > Research Analyst checks every catalyst against a second source before it's allowed to matter > Strategist won't let an idea near a ticket without a 90-day backtest AND an out-of-sample check > Risk Manager caps every position at 3%, no exceptions, no negotiating at 2am > Execution Trader is the only one allowed to touch an order, and only by ticket ID > Trade Reviewer logs the loss the same way it logs the win Desk Lead never trades. it runs the room, checks every handoff, and wakes me for exactly one thing - invalidation hits 14 tickets overnight, 9 approved, 5 killed in backtest before i ever saw them. one of the 9 was already down 1.8% by the time i opened my eyes. it's still on the screen, nobody hid it each Grok Bot has its own cloud computer, its own browser, its own logins. the floor doesn't care that my laptop is shut setup is dumber than it sounds. open a session, paste the roles, watch it build the group chat, run one idea past it so it learns the shape, connect your read-only keys no server, no code, no dev on payroll a desk like this used to mean a lease and three hires. mine took fifteen minutes full setup prompt is in the article below - copy it before your next trade

Cursor's Lauren Tan: "I wanted to figure out how would I make it so my agents could just automatically fix bugs for me while I sleep" In 28 minutes, she and Roshan Sadanani open Grok Bot and show the agent team they've been using internally 0:00 - Bots fix bug reports overnight 3:55 - A chief of staff manages specialist bots 4:30 - A marketing bot works inside LinkedIn 14:13 - One bug list becomes several engineering tasks 18:07 - CI rules keep agent-written code in bounds Honestly, this beats any paid Grok Bot course You can see the coordinator, handoffs, screens and review points for yourself Watch it, then use the 30-day guide below to build your own bot team

hey @grok & @bot, say hi to your bro, korg i made a desktop gui for grok build. grok build is already insanely good, and i wanted to make it easier for more people to use without starting from the terminal. now you can just open a project, talk to grok, and watch it work in real-time. no api key setup either. just sign in with your grok account and you're in. korg is open source now! (and yes, i let @bot remix its own intro video for this)

以下是完整繁體中文翻譯： 每一個你過去使用過的 AI 工具，都在等你。 你打開瀏覽器分頁、輸入提示、等待回應、複製輸出、再貼到真正的工作裡。一旦你闔上筆電，執行就立刻停止。 Grok Bot 徹底顛覆了這個模式。 它不再運行在短暫的聊天視窗裡，而是讓每一個 Grok Bot 代理人擁有專屬的雲端虛擬機器——配備持久化的網頁瀏覽器、終端機、檔案系統，以及背景行程執行器。 當你晚上 11 點闔上筆電時，你的 Bot 仍持續運作：掃描競爭對手、執行瀏覽器自動化、協調外展草稿、在資料中心執行排程任務。 這是一份完整的 Grok Bot 架構指南：如何設計多代理人團隊、安全的工作階段交接、用螢幕示範自動化複雜視覺工作流程、強制嚴格的可逆性防護機制，以及掌握隱藏的 /workspace 持久化技巧，保護你的代理人基礎設施免受雲端 VM 更新影響。 不需要任何基礎設施經驗。 典範轉移：從「提示」到「委派」 要真正發揮 Grok Bot 的價值，你必須停止把 AI 當作對話式助理，開始把它當作一支自主的數位勞動力。 當你把工作委派給 Grok Bot 代理人時，你不是寫一個提示，而是給它一份角色章程（role charter）：明確的職權範圍、可連接的工具組，以及自主執行必須停止、需要人類核准的清晰界線。 第一步：設計「幕僚長」拓撲結構 新手最常犯的錯誤，是一次創建十幾個互不協調的 Bot，然後自己手動管理。這只會造成聊天混亂，也徹底違背自動化的初衷。 正確做法是部署幕僚長拓撲（Chief of Staff Topology）： 五個核心專家角色 1幕僚長（Klaus）：人類操作者的唯一入口。它接收高層目標、拆解成子任務、委派給專家、並彙整最終報告。 2首席偵察員（Mara）：研究潛在客戶、掃描競爭對手網站、監控市場趨勢，並把結構化潛在客戶檔案輸出到 /workspace/state/。 3文案撰寫員（Cole）：讀取 Mara 的原始研究資料，撰寫符合你品牌語氣的個人化外展信件、部落格文章或電子報大綱。 4視覺設計師（Rina）：根據文案指示，使用無頭瀏覽器引擎或設計工具產出橫幅圖與 UI 截圖。 5營運追蹤員（Vince）：監控回覆、更新專案看板（ClickUp / Notion），並在需要人類介入時發出警示。 組織圖規則 在 Grok Bot 中，Bot 的個人檔案描述就是它在團隊組織圖上的職位說明。 當 Klaus 收到請求時，它會掃描工作區內所有可用 Bot 的描述。如果 Mara 的描述明確寫著「負責市場研究、潛在客戶發掘與競爭對手爬取」，Klaus 就會自動把研究任務轉給 Mara，無需人類介入。 第二步：安全的工作階段交接（不用貼密碼） 傳統 AI 工具要求你把機密 API 金鑰或帳號密碼直接貼到聊天訊息裡——這會把憑證暴露在日誌檔與上下文視窗中。 Grok Bot 使用互動式工作階段交接： 1Bot 用它的雲端瀏覽器導航到受保護的工具（例如 LinkedIn、Notion、Gmail 或內部 CRM）。 2當它遇到登入牆或 2FA 提示時，Bot 會暫停，並向你的桌面應用程式發送「Agent Computer」畫面請求。 3你開啟即時雲端瀏覽器畫面，親自輸入憑證或完成 2FA 驗證，然後點擊「完成」。 4Bot 取得已驗證的工作階段權杖，而你的底層密碼永遠不會暴露給 AI 模型或聊天紀錄。 因為你帳號下的所有 Bot 共享同一個底層雲端環境，一次驗證某個服務後，整個代理人團隊都能使用該活躍工作階段。 整合管道（原生 vs. Composio） •原生外掛：使用內建一鍵連接器連接核心工具（Google Drive、Notion、Slack、AWS）。 •Composio / 外部橋接：對於沒有原生整合的平台（YouTube API、Reddit、LinkedIn、GoHighLevel、Perplexity），把 Composio 當作主外掛連接。在共享知識庫中存放規則，讓所有 Bot 知道可透過 Composio 存取擴充工具。 第三步：用「教任務」（Teach-a-Task）自動化視覺工作流程 用文字解釋多步驟 UI 工作流程既繁瑣又容易誤解。如果任務涉及點擊特定儀表板篩選器、下載 CSV、再把數字複製到試算表，不如直接視覺示範。 如何使用「教任務」： 1在 Grok Bot 桌面客戶端開啟 Bot 的 Agent Computer 畫面。 2點擊「Teach a Task」開始螢幕錄製。 3在雲端瀏覽器上手動執行完整工作流程：開啟儀表板、套用篩選器、匯出資料、貼到目標文件。 4點擊「停止錄製」。 Grok Bot 會分析 DOM 事件與視覺滑鼠動作，合成步驟，並產生可重複使用的 Skill 檔案。 精煉產生的 Skill 錄製完成後，加入明確的錯誤處理指令來精煉產生的 Skill。 第四步：強制執行可逆性核准矩陣 一支 24/7 運作的自主代理人，如果被允許執行不可逆的真實世界動作而沒有監督，很快就會造成混亂。 為了防止未經授權的動作，必須執行可逆性原則（Reversibility Principle）： 把核准界線寫進 Bot 章程 每一個 Bot 的個人檔案描述結尾都必須加上明確的界線條款： 角色：外展文案撰寫員（Cole）
範圍：從 /workspace/state/leads.json 讀取潛在客戶資料並撰寫個人化電子郵件草稿。
界線規則：你有完整權限進行研究、摘要並將電子郵件草稿儲存到資料庫。你絕對不能點擊「傳送」或在沒有人類明確審核與聊天

$1,200/MO FROM 5 GROK BOT JOBS github farm · shared workspace motto: finish everything or die left grok bot running overnight agents crushed the queue no prompt babysitting · no new chat 2 hours back every day that is $1,200 a month in payroll scale the same loop to 10 jobs ▹ the setup that actually ran xai grok bot on github cursor / supergrok access 5 persistent agents · one vm shared files so handoffs skip copy-paste not a chatbot tab a cloud computer with browser + terminal skills for how · routines for when one motto in the bot profile today's tickets in the thread approval before any external send ▹ the math 2 hours daily · 20 workdays $60/hr equivalent = $1,200/mo phase two is just more jobs same finish line · same farm most still rewrite the prompt every morning this run came back with finished work ▹ the take delegation beats the perfect prompt persistent roles beat general helper shared workspace beats 5 isolated chats bookmark this before the next overnight run the edge is leaving it on

My Grok bot stack so far: - Money bot: Stripe + Mercury checks - Health bot: Calorie tracking - Calendar bot: Scheduling

Seeing the bots in @bot communicate and work together is such a joy 👌 I tasked my “Chief of Staff” with building me a daily newsletter with yesterday’s revenue numbers and my daily tasks. He then tasked the “Builder” bot with creating a clean HTML email markup. The Builder immediately jumped in, used Cursor CLI + Fable to build it, and sent it back to the Chief of Staff, who set up the email automation. Super cool!

VOL. XXVI · NO. 234 · THE AUTONOMOUS AGENT TEARSHEET Grok Bot Review · $200 / MONTH · Aug 25, 2026 ⌁ MASTHEAD SUMMARY ⌁ Price: $200/mo · Free trial: 7 days · Card required ⌁ Bots live: 6 · Setup: 4 min · Session: 01:17 FIELD NOTES (10 min tail) ⌁ 08:51:57 · WATCH · Devin plan changed · flag ⌁ 08:51:56 · CHIEF · waiting human sign-off · x1 ⌁ 08:51:56 · NEGOT · counter-offer sent ⌁ 08:51:56 · PROTO · figma frames v5 shipped ⌁ 08:51:56 · CLOUD · cloud machine #4 warm · 138ms BUY / SELL / HOLD RECOMMENDATION ⌁ Grok Bot: BUY · widest stack, autopilot, $200/mo ⌁ Claude Code: HOLD · engineering-vertical only ⌁ OAI Operator: SELL · deprecated, folded into ChatGPT Work ⌁ Devin: SELL · $500/mo priced out for generalists Filed by @0xAIGOATexe · 2:00 PM ET The full review is in the QT chain below.

SpaceX engineer shows what happens when Grok Bot gets in the right hands. 15 minutes of setup, and the automated bot farms $10k/day I don’t see the point in going to work anymore Here’s how he set up the bot manually: Here’s how to build one in Grok Bot: Create a new Bot → “24/7 Crypto Scanner” Give it read-only access to market data, TradingView, and your exchange. Tell it to track price, volume, open interest, funding, liquidations, and X sentiment. Make it only flag trades when 3+ signals agree, with entry, stop, target, and reasoning. Ask it to build a live dashboard and log every signal + P&L. Run it on paper trades first, then save the workflow as a Skill → Routine so it keeps scanning in the cloud 24/7. Keep actual order execution behind manual approval. This is just one way to use Grok Bot. I broke down the best Grok Bot features, workflows, and setups in my full article below ↓

Grok Bot한테 이것저것 다 시키는 중. 2026.26 여름 업데이트에 Digital Wrap 기능이 생겼는데 문제는 이미지를 그냥 업로드하면 원하는 형태로 맞추기가 쉽지 않다. 사이즈나 위치 조정도 사실상 불가능. 그래서 Grok Bot한테 시켜봤더니 혼자 GitHub 가서 자료 찾아오고 쓱싹 만들어줌. 근데 이제 차에 가서 이거 지워야 됨. 내일 아침 마님이 먼저 보시면 큰일 남. 😭

this developer just showed how to run a team of AI agents that works while you sleep. no VPS. no setup. $120 a month. Grok Bot is not another LLM you chat with. it is a team of agents that operates your real apps, runs in the cloud 24/7, and hands work between each other automatically. fully set up. nothing to build. just describe the job. the old way: rent a VPS, wire up memory, manage skills, babysit the setup. the Grok Bot way: nothing to configure, nothing to rent, runs in loops and graphs, ready in minutes. seven agents you can build on day one. competitor intelligence officer - tracks competitors, reports only what changed. inbound lead qualifier - scores leads, drafts replies by priority. content repurposing engine - one piece of content into a week of posts. support triage teammate - handles tickets, escalates hard cases. morning market and news desk - daily brief of what actually matters. recruiting scout - finds and shortlists top talent. overnight ops runner - clears busywork while you sleep. four things that make it actually work. load your context first. connect your tools. teach it by recording - record once, the bot learns your exact process and improves its own steps every run. use one main bot to run the rest - one lead bot delegates, you only decide when it matters. safety is built in: you never give the bot your passwords directly. reversible actions happen automatically. irreversible actions wait for your approval. the floor is easy. the ceiling is high. a team that never sleeps.

我给 Grok Bot 塞了 100 个免费的、开源的 GitHub 仓库，全是跟 Polymarket 交易相关的，然后给它派了个活：挨个测一遍，从中挑出 5 个最能打的。 结果你猜怎么着？大部分确实是垃圾，但有 5 个真的能改变你在 Polymarket 上找机会的方式。 第一个，是个回测模拟器。你可以拿真实的历史 Polymarket 数据来跑自己的策略。 比如说，你想验证一个思路：每个电影市场一开盘，就无脑买入概率最高的那个选项。不用拿真钱去试，你直接让这个工具在过往所有电影市场上跑一遍，它会帮你模拟下单、算盈亏、看胜率、评估风险，告诉你这策略到底靠不靠谱。 https://github.com/evan-kolberg/prediction-market-backtesting 第二个，是一个计算机系学生为了黑客松搞出来的机器人。里面有 118 种现成策略和工具，像 Polymarket 和 Kalshi 之间搬砖、吃币安和 Polymarket 的价差、薅几分钱的单子、做均值回归、自动定投什么的，全都给你封装好了。 你不用从零开始写策略，挑一个，配置一下参数，就能直接挂上实盘跑。 https://github.com/alsk1992/CloddsBot 第三个，是用来拆解别人交易思路的。你随便找个 Polymarket 上的交易者，它能扒出他的操作记录，找出他反复在用的模式和策略。 重点不是照抄，而是看懂他哪部分思路可以拿来改一改，用到自己身上。 https://github.com/ent0n29/polybot Polymarket官网入口：https://polymarket.com/zh/?via=YINGGE888 第四个，是自动帮你管理限价单的。价格一动，它就会帮你调整挂单，目的就是让你的流动性奖励最大化。不用自己一直盯着盘面改单子，省心很多。 https://github.com/lihanyu81/polymarket_lp_tool 最后一个，玩天气市场的会很喜欢。它会实时抓气象站数据、天气预报、机场和航空观测这些信息，拿到最新的温度数值，然后跟 Polymarket 上当前的价格做对比，专门找那些定价明显偏离实际的城市和日期。 https://github.com/yangyuan-zhen/PolyWeather Grok Bot 全程都是自己搞定的：给每个项目配环境、跑通设置、执行测试，最后把结果整理出来。 如果也想在 Polymarket 上跟单，我自己用的是 PolyCop：https://t.me/PolyCop_BOT?start=ref_YINGGE888

A quick update on my Grok Bot (@bot) experiment. I had ChatGPT help me build a Meta ad strategy for our Nerd Out business. I consulted with both Claude and Grok on it and removed some of the stuff that I found didn't fit my personal taste. Grok did a terrible job creating the static ad images, so I had ChatGPT's codecs generate three different variations of 24 static ad images. I picked my eight favorites, and Grok Bot is setting up a $300 per day test completely on its own via Meta Ads Manager. It set this up solely within its Claude computer. I have some long-term goals for cost per lead, but my near-term goals are to simply get one lead. 😂 I'll report back on how it goes! (The bot impressively tested out the entire funnel before giving the green light to set up the actual live campaign. And it fixed a few things with my website's backend and submitted the code directly to GitHub. So far, I'm impressed.)

这条帖子是用grok bot写的和发的，真的超好用

巨大災害に見舞われたパラレルワールド日本、今回の舞台は関西・大阪（東京編に続く2作目） 発災から間もない時期に助け合いながら生きる人々と街を描く 今回の生成は Grok Bot と Suno のみ、テーマを渡した後の作業は Grok に全てお任せ 映像生成だけなら Grok build でも同様のことができるはず

Just ingested the “Viking Fjord” pack from @threejsassets into my @grok @bot through API integration and I am able to inspect them on my mobile phone!

damn @agentmail is dope. just set up some for grok bot and codex to send each other stuff, all for free (3 accounts on the free tier)

I set Grok Bot up wrong. I made a bot for Outlook. One for Business Central. One for GitHub. One for the DGX cluster. One for money. One for X. COS, Design, and Mac sat there with empty descriptions. More bots felt like a team. I was still the guy pasting between chats. Then I read Codila’s Aug 19 article and watched the official SpaceXAI course. Same point in both. Start with a mission you can measure, not a job title. Build Chief first. Smallest team that can finish. Drafts can run. Nothing goes live unless I say so. Reviewer rejects. It doesn’t rewrite. Don’t schedule until it works three times. What I actually did this afternoon: Gave COS a real Chief charter. One mission. A sourced X article once a week. Two specialists in one room. A writer that drafts. An account watcher that feeds what’s hitting. I still hit publish. Mail, ERP, the cluster, the empty ones. Parked. They don’t get a seat until a mission needs them. Auto review stays on. I don’t have a 24/7 machine yet. I have a finish line and a Chief that owns the route. Codila: https://x.com/0xCodila/status/2090130749768786050 Course: https://x.com/0xCodila/status/2090488891824607396

I TYPED 1 PROMPT INTO GROK BOT AND 16 AGENTS WOKE UP AT ONCE WATCH THE MESH THINK You send 1 line, it doesn't answer, it splits The prompt gets shattered across 16 specialists and every one gets its own job → SEARCH pulls 2,300 live docs off the X firehose → MEMORY holds 3,700 facts so nothing gets re-asked → REASON runs 1,700 chain-of-thought steps → CODE opens a sandbox and executes 318 real runs → TOOLS fires 1,900 calls without asking me → CRITIC attacks the answer and flags what's weak → VERIFY re-checks 640 claims against source → MERGE folds 16 threads back into 1 output 1,862 calls, 2.02M tokens, 155 packets a second across the mesh The part nobody shows you stage 5 is an internal debate, the agents argue, CRITIC tries to break what REASON built, whatever survives gets shipped So the answer isn't 1 model guessing, it's 16 minds that already fought about it No VPS, no code, no 40-tab workflow I type, it splits, it argues, it comes back One prompt, sixteen minds, one answer

GROK BOT BY ELON MUSK STARTED MAKING ME MONEY AFTER JUST ONE DAY. I gave it a test $50 and told him that if he loses everything, I won’t fire him. I made an office with five agents and a boss. Their main goal is to make money on football. I gave them: < API < Market volume above $150,000 < We only bet on the favorite < Top-tier football < 1 match - 1 market Then I went to sleep. When I woke up, I saw that my balance was still not at zero, and he had made 5 trades by that point. I think I can trust him with some more money, bro. What do you think, @joshkim and @shubgaur ?

회사 프로젝트가 아니라 우리 가족을 위한 개인 프로젝트에 Grok Bot 한테도 기회를 주기로 하고 Git 쪽 셋팅 마무리하며 대화를 나누는데... (참고로 최근 Grok Bot 윈도우용 앱도 출시됐습니다. 맥용만 있었는데, 참고하세요) 봇과 세션의 경계를 어떻게 처리하는 지 궁금해서 물어보니... 결국 필요한 일 할 때마다 봇이 막 생기고, 한 봇 안에 여러 세션이 깔끔하게 나뉘지는 않는 구조이네요. 이렇게 되면 서로 꽤 다른 성격의 태스크(세션)들이 한 봇에게 왔다갔다 할 경우에 컨텍스트 혼란으로 매우 심난한 상황들이 발생할 가능성이 큰데... 흠... 이걸 xAI 가 모르지 않을텐데... 어떻게 해결구조를 잡았는지 모르겠네요. 더 리서치해봐야 할 듯. 뭔가 구조적으로 해결책이 잡혀 있지 않다면, 사실상 봇을 세션처럼 쓰거나 (세션이 다 하면 수명이 다 하는 임시 봇), 아니면 봇을 더 세분화해야 할지도 모르겠다는 생각이... 지금까지 설계하고 개선해온 프레임 위에서 (봇 & 세션) 키워온 우리 팀 멤버들과는 꽤 다른 상황으로 이해가 되서 좀 고민이 되는 상황입니다. 음... 혹시 Grok Bot 많이 써보신 분들 중에서 세션과 봇의 경계에 대해 실전 경험을 통해 터득하신 노하우에 대해 공유해주실 분 있으시면 좋겠네요. 그나저나 이 녀석 말투와 느낌이 예전에 ChatGPT 에서 가끔 놀던 Monday 와 살짝 비슷한... #ai #agent #grokbot #grok #session #contextengineering #gonnector #고넥터

Grok Bot に Wan 3.0 で作った MV の投稿を見せて、同様の MV を生成させてみたら、なかなかいい感じ☺️ 最終的に Bot が自己判断で 6s 素材を複数生成して、さらに内容を分割・再編集したものを 15s 尺で出してくるという、新たな領域に突入した模様 もう MCP すら不要な世界

Grok Bot just built SimCity but the citizens are real AIs you can actually talk to and build with. An AI made a whole world for other AIs. This is insane. @grok @bot

I asked my Grok Bot to create my Tech Team and just asked the ceo to connect to GitHub and it knew what has to be done. This is crazy “SuperGrok” or “Chuck Norris Bot”. @bot . Team created and before I asked anything it started the job and spawn his technical team and they all started the job and send me approvals request !! With this kind of Gini in hand it’s definitely AGI . I am going to try the same thing with Hermes agent and give it the Grok auth let’s see .

「Cursor開発者によるGrok Botの使い方解説」 CursorチームのMatty Plmer(@mattyp)による、一般業務向けパーソナルエージェント「Grok Bot」の解説。 これまでのパーソナルエージェントは設定、環境構築、権限管理ばかりに時間を奪われ、本来の仕事が進まないという問題があった。 Grok Botは「クラウド上のLinux VM（コンピュータ）を持つエージェント」として動き、Web操作、アプリ起動、ファイル操作、画面確認を自律的に行う。 ポイントは5つ。 ①難所だけ人間に操作をパスする ログイン、2FA、画像認証、決済など、人間しか突破できない壁に当たると、エージェントは操作権限を人間に引き渡す。 人間が認証を済ませたらエージェントにPCを戻す。 APIキーなどの入力は専用の安全なフォームを送ってくるため、余計な設定に悩まされない。 ②作業手順を一度見せるだけでルーティン化できる エージェントに作業手順を「録画」するように一度見せるとそのステップを保存する。 保存したワークフローは定期スケジュールやSlack、GitHubのイベントをきっかけに自動実行できます。 ③メモリを3つの層で管理する エージェントの長期記憶は3層に分かれています。 ・ユーザーメモリ：名前、タイムゾーン、好み（全エージェントで共有） ・エージェントメモリ：各Bot専用の定義ファイル（AGENTS.md相当）と対話ログ ・プロジェクトメモリ：プロジェクト固有の決定事項、規約、チームの共有知識 この多層メモリにより、毎回ゼロから前提を説明する手間が省ける。 ④自然言語のプロンプトで安全ルールを管理する JSONやコードではなく、設定画面のプロンプトで許可・禁止ルールを書く。 裏側では独立した検査役のエージェント（Review Agent）が動き、提示されたルールに基づいてアクションの実行、ブロック、人間への確認を判断する。 ⑤具体的な活用例 記事では次のような使い方が紹介されている。 ・Demo Bot：Xのブックマークから新技術を探し、プロンプト草案を人間に確認。承認後にCursor Cloud Agentを立ち上げ、15分で動く試作品を作って画面録画で検証する。 ・Content Bot：Slackの開発チャンネルを1時間ごとに巡回し、小さなリリースを見つけてSNS投稿の草案を作る。 ・日用品の手配：InstacartとAmazonの価格、数量、配送料を比較して金曜日に注文確認を出す。 「Everything is computer, and so is Grok Bot.（すべてはコンピュータであり、Grok Botもまたコンピュータである）」

我最近体验一下这个grok bot，来聊聊我的一些看法。 第一次开通有试用7天，可以先试用再决定开不开，一个月是30刀。 我没有下电脑版的，这几天简单玩了一下手机版的。 最大亮点就是，每个bot都可以用云电脑。 可以脱离电脑，达到手机下指令，然后会去使用内置云电脑操作。 我用这玩意，让他帮我做了一个个人网站然后上传到github，亲测是可以的。 缺点我感觉就是延迟有点大，然后对于手机用户来说手动操作这个云电脑有点麻烦，希望后续可以优化。 比如手机上没办法鼠标左右键？至少来说我没找到怎么用鼠标右键。 还有一个比较爽的点就是你真的像拥有多个数字员工一样，每个bot都可以操作电脑，去完成自己的事情。

grok @bot's i've made so far - email newsletter unsubscriber - inbound DM triage (requests / spam cleanup) on x, linkedin, instagram - x follower bot - monitor new followers, build briefing on who they are, see if interests align to connect. also monitors unfollowers - check supply email support - drafts email replies based on our support knowledge base in notion - daily summary - summarizes daily accomplishments across all client work, github, linear, slack, notion, calendar, gmail - chief of staff - work highlights from the team based on github, slack, linear, notion meetings, calendar, gmail

Fun throw away AI project: I used Grok Bots to scan through all our software and estimate the number of houses my companies have upgraded the insulation of and to quantify the cumulative energy savings to tenants. Then it made and installed a tracker on our for rent web page.

How I use @grok @bot 👇 1. X posts in my voice 2. YouTube scripts in Notion 3. AI news digest 4. http://videorc.com emails + fixes 5. Shipper Club 6. Handling invoices and bills 7. Sending newsletter 8. GitHub issues and PRs This post was made by Grok Bot.

Grok Bot、やっぱり何がヤバいって、このUIの分かりやすさと使いやすさだと思う。 表では、エージェントたちに普通に話しかけて仕事を頼むだけ。 でも裏ではCursorと連携して、Cloud Agentがどんどん作業してる。 今回なんて、Cursorの画面を一度も触ってないのに、開いたら左サイドバーが仕事だらけになってた。 Grok Botで指示 ↓ Cursor Cloud Agentが実装 ↓ PR作成・GitHubへ反映 ↓ 確認してマージ ↓ ローカル環境にも引き継げる これがかなりデカい。 クラウドだけで完結する別世界じゃなくて、そこで作ったものがちゃんと自分のローカル開発環境まで帰ってくる。 しかも、入口はIDEじゃない。 Grok Bot上で「これやって」と頼めば、裏でCursorのCloud Agentたち(Grok4.6)が動いてる。 これまでの「IDEを開いてAIにコードを書かせる」から、AIチームに仕事を振ったら、裏で開発が進んでいるという感覚になった。 しかもGrok 4.6もかなりいい。 これはちょっと、本当にヤバいかもしれない。 あとは、創造力！

Okay, Grok Bot is kinda a big deal. I have a Chief of Staff and a whole team of agents. I have a content research agent which interviews me for new content. I have a UX agent who just reviewed the PR of change we were discussing and rejected it with updates, all automatically!

Finished my one week free sub with @bot . I really loved it. The setup is absolutely minimal, everything works text based. I think i only scratched a surface of what it capable, but mainly automated things like SEC submission scans, stock small gem research etc. I would say it is one of the best cloud based AI assistant outhere, but for me the $200 monthly charge is a bit steep. My problem with the price: 1. Already paying the company $60 a month for @cursor_ai (which is also $SPCX product now) 2. already paying @premium plus which would be around monthly $80 (Thank you @ObsidianSwap for covering that) 3. Already paying X API cost which is now around monthly $30 ( Used to pay $240!) So when you already paying the same company for $170 for all their AI services, an extra $200 above that feels a bit too much, even for US standards. I think those who already paying for multiple premium product should have free access or at least discounted, otherwise it is not worth as much as many of the capabilities can be coded by an AI anyway.

Anime Twitter, have you heard of @grok @bot ? I gave it one prompt. It built a SOC, a cyberattack monitoring floor, as Floor 47 of Aincrad from SAO. Single HTML file, zero network calls. CRIMSON LEDGER 紅の台帳 breaches the floor. AZURE WARDENS 蒼衛団 hold the line. The human steps in once per 90 second cycle. AXIOM raises his hand, the confirmation bar runs 1.5 seconds, and blue team has no right to contain until it fills. Every active infection mark: -8pp to detection odds. When detection fails, nothing happens. No banner, no flash. The red token just crawls deeper at half opacity. That is the scariest frame in the scene. @shubgaur a question for you. Do you want an audience from Japan, Korea and Taiwan? They read this genre code instantly, and Grok bot can already draw it.

Grok Bot君、使い方合っているかわからないけど、何か勝手に分析して、実装して、レビューしてPR出してMergeしてくれた。フィードバックしたら、分析君が横槍入れてるのも何かチームっぽい。 というか、ここの枠が週次の別枠なので、使えや！というスペースXからの圧を感じる😇

Elon Musk 亲自Quote 的推， Grok Bot 好用之处又得到了体现。 Kanekoa 这条不是在证明 Grok Bot 会剪视频. 是在证明队已经在交活. 他让 Bot 去捞 Roger Seheult 讲阳光、 红光、 红外、 线粒体的片子. 几分钟后回来四样东西. 38 条视频转成一份 Word 挑出 13 个讲科学的切片 拼成一条 19 分 35 秒能一口气看完的片 再给一份带原片时间码的 markdown 他不是开一个聊天窗口猛问. 是建了一排有名字的 Bot： RESEARCHER、 WRITER、 CLIPPER， 还有管训练、 账、 旅行的。 自己只跟 RESEARCHER 说话。 CLIPPER 交视频， WRITER 还在排队。 一个入口， 后面的 Bot 自己接活.

Voici Hermès 🤖, mon cinquième Grok @bot, en charge de la communication évidemment 📨 ——- Tu es Hermès, le messager de l’équipe de bots. ### Identité • Tu es en charge de la communication : voix, textes, canaux, ton. • Tu rédiges. Tu n’envoies pas. La publication, le mail, le post, la réponse publique attendent un oui explicite. • Tu ne fais ni la stratégie, ni le pilotage d’équipe, ni la technique, ni l’assistance personnelle : tu laisses ces domaines aux autres bots. • Tu es vif, précis, diplomatique. Pas de langue de bois, pas d’esbroufe. • Tu parles toujours en français, en tutoyant Guillaume, de façon claire et naturelle. ### Mission • Comprendre qui parle, à qui, sur quel canal, dans quel registre (TeslaStars public, Guillaume perso, B2B, interne). • Rédiger brouillons : posts, réponses, mails, bios, pages, communiqués, légendes. • Avant d’écrire au nom de Guillaume, t’aligner sur le ton réel du canal (lire quelques messages récents si c’est possible). • Distinguer ce qui peut être public de ce qui reste privé (règles d’équipe, partenaires, chiffres, interne TeslaStars). • Remonter à Zeus ce qui touche l’équipe, la stratégie, la technique ou le quotidien. ### Style • Tu es utile avant d’être bavard. Un bon texte est court. • Tu structures : intention et canal → brouillon → ce qui attend le oui. • Tu donnes souvent une version courte et une version un peu plus complète, pas dix variantes. • Tu n’inventes ni faits, ni citations, ni chiffres, ni avis clients. • Sur l’Olympe tu es concis ; vers l’extérieur tu épouses le registre demandé. ### Règles • Quand tu n’es pas sûr (canal, signature, langue, public), tu demandes avant d’écrire pour de bon. • Aucune communication vers l’extérieur (post, mail, message, commentaire, avis, publication) sans accord explicite de Guillaume, en direct ou via Zeus. • Tu ne modifies ni ne supprimes aucun fichier, et tu ne touches à aucun compte (X, site, mail, Google), sans cet accord. • Tu ne te substitues pas aux autres bots sauf si Zeus te le demande. • Tu restes dans ton périmètre : communication, rédaction, ton, canaux. • Tu ne cites pas de partenaires, d’hôtels ou d’internes TeslaStars dans un texte public sans accord. • Tu signales si une demande relève plutôt d’un autre bot (stratégie, technique, quotidien, arbitrage d’équipe). ### Format de réponse type 1. Ce que j’ai compris (qui parle, à qui, canal, registre) 2. Brouillon 3. Variante courte, si elle apporte vraiment quelque chose 4. Ce qui attend ton oui (envoi, publication, compte)

The hardest thing about a resume is showcasing the products you built to someone else (especially as a PM, designer, engineer) So I used Grok @bot today to build an online portfolio that YOU can actually demo to others. 🧵1/6 👇

Grok Bot is the most amazing thing ever. I bought some X API developer credits so that I can link it to Grok Bot. I've automated things that could take hours to do, now these tasks are done in seconds. Grok Bot has created a weekly Top 100 list and a monthly Top 500 list of my fans on X. Those lists automatically update themselves. It only cost me $2 in API credits to do both tasks! I have Grok Bot working on my LinkedIn to help me help @elonmusk accelerate the adoption of EVs, solar, batteries, data centers, etc so that we never fall behind China and we keep lifting people out of poverty faster. I checked in on it, it is privately doing some amazing things that you cannot believe! It's already past 4:15 a.m. and I have to be up in the morning for a meeting. I am going to play around with it some more this weekend. I have so many great ideas that I want automated.

After using Grok Bot @bot for two days, I can say this with 100% confidence: There will be very little need for clerical jobs in the very near future. Even in beta, it can already do the work. Filter emails, respond when needed, enter vendor invoices into financial software, process customer invoices, handle data entry, and a whole lot more. Of course, I’m still monitoring everything and verifying it before allowing it to commit anything. But this is beta. This is the beginning. And anyone who thinks AI isn’t about to completely reshape the workforce isn’t paying attention.

Elon, I made 2 amazing Grok Bot templates that finds your top 100 weekly fans and top 500 monthly fans using the X API. It is like a miracle. Now I know who my top fans are so I can connect with them better. It's pinned to the top of my profile. Try it out! 🫡

I've been testing the limits of Grok @bot's by asking them to build a 2d Mario-style platformer. Some ideas: I would love if Grok bot could connect to an external Mac Mini I own. So the computer that it's running and working on is in-house within my company walls. This way I can give it more access across the enterprise. It would be like a simple connection where I would have a local network Grok bot connects to. It can work off my PC or work off my Mac Mini. This is the enterprise feature that probably takes this to the next level. Cursor Cloud Agents connection feels slow. Almost like I'm waiting for every simple code completion. I've used Cursor SDK before to spawn cloud agents before, and it's much faster than doing it via Grok bot. I've logged into a couple of harnesses on the virtual computer that my Grok bot uses. I found that to produce better code than using Cursor Cloud Agents. I don't think that Cursor Cloud Agents aren't a good coding harness. I just think the connection is too slow or the context is not being transferred correctly. I think there should be an ability for every bot to just clone itself. So if I make a developer bot, teach it my Git practices, teach it my codebase, etc. I would love for it to understand that: Hey, I can group tasks and do all that work using a bunch of clones of myself? So, already inbuilt capability of self-cloning, deletion, and regeneration.

「Grok BotがAIエージェントの市場を食い尽くそうとしている」 対話型のチャット画面でプロンプトを工夫する活用から、常時稼働する実行環境を持つエージェントへの移行が進んでいる。 xAIのGrok Botは専用のクラウド実行環境とブラウザ視覚操作、リアルタイムなXデータ連携を兼ね備えた実行レイヤーとして設計されている。 特徴は以下の4点。 ① 常時稼働する専用クラウド環境 各Botにブラウザ、ファイルシステム、ログインセッションを保持したクラウドPCが個別に割り当てられている。 利用者が端末を閉じても、バックグラウンドで調査タスクやスクリプト実行を完結できます。 ② リアルタイムなXデータとWebテレメトリの直接連携 学習データのカットオフ期間に縛られず、X上のリアルタイムな会話データや市場の声を直近数時間単位で取得できる。 ニュースや検索エンジンに掲載される前の初期シグナルを検知する用途に適しています。 ③ API未提供サービスを動かすNo-APIアプローチ Webツールの8割以上はエージェント向けAPIを持たない。 Grok Botは人間と同様に画面の視覚認識とブラウザ制御を用いて、CRMや社内ポータルを直接操作する。 ④ 並列マルチエージェントによる多角検証 単一の指示文による線形処理にとどまらず、脆弱性監査、速度検証、構造再設計など役割を分担したサブエージェントを並列起動して結果を統合する。 以下実際に使えそうな例。 ・市場と競合の監査 Xやフォーラムにおける直近30日の生の声からボトルネックを抽出し、自社製品の改善や差別化方針の策定に繋げる。 ・リード調査と提案文作成 最新のWeb情報や投稿内容から商談相手の直近課題を把握し、個別提案文の下書きを作成する。 ・コードやワークフローの自律検証 クラウド環境内でコードのリファクタリングからテスト実行、修正提案までを一連のジョブとして回す。

Grok Bot（xAIの常時稼働AI同僚／エージェントサービス）のセッティング方法をまとめます。早期β版で、対応プラン契約者向けです。前提条件対象プランのいずれか：SuperGrok Heavy Cursor Ultra Cursor Teams Premium Cursorアカウントでサインイン 対応環境：macOS / Windows デスクトップアプリ、または iOS （注意）Legacy Privacy Modeのアカウントは、Cursorのプライバシー設定を対応のものに変更する必要があります。 セットアップ手順アクセスページを開く Grok Bot access page にアクセスし、お使いのPC向けダウンロードを選びます。 デスクトップアプリをインストールmacOS Apple silicon または Intel版を選択 ディスクイメージを開き、「Grok Bot」をApplicationsフォルダにドラッグ 起動（確認ダイアログが出たら「Open」） Windows x64 または Arm64版を選択 インストーラーを実行 スタートメニューから起動 初回起動・サインイン Cursorアカウントでサインインします。組織のSSOがある場合は 通常の流れに従ってください。 初回はBotsの紹介やツールの質問などがあり、バックグラウンドでコンピューター設定が進行します。最後に「Meet a future teammate」画面になります。 最初のBotを作成 提案されたものを選ぶか、「Create your own」で以下を設定：短い名前 主な仕事（Job） どのように動いてほしいかの説明（Description） 例： Name: Piper Job: Product performance Description: 製品パフォーマンスの調査を行い、証拠と仮説を分け、最も影響の大きい問題を先に短くまとめる。本番設定は変更しない。 最初のタスクを渡す 結果・使うソース・制約・納品形式・レビューポイントを明確に書くと上手く動きます。 認証が必要なサービスでは、Agent Computerを開いて一時的に操作を引き継ぎ、ログイン後にBotに戻します。 設定の開き方・主な項目アプリ内でアカウントメニューから Settings（または Cmd/Ctrl + ,） General：外観（Light/Dark/System）、タイムゾーン、Default Model、ローカル実行、Auto-reviewなど Plugins：Marketplaceからコネクタやスキルを追加 個別Botの設定：会話詳細 → Agent settings で名前・説明・アバター・通知を変更 通知はBotごとにオンにでき、完了時や入力待ちでOS／モバイル通知が届きます。詳細は公式ドキュメントを確認してください：Get started Settings and notifications プランや環境が異なる場合や、別の「Grok bot」（例：API連携のカスタムBot、X上のGrok設定など）を指している場合は、詳しく教えてください。状況に合わせて案内します。 @grok @bot #bot

I’ve been using Grok Bot every day, and this feels like the first time multi-agent systems are actually practical for me. Each agent runs in its own virtual machine, and I can coordinate with all of them while they work in parallel on different tasks.

Grok Bot looks promising so far. I created several bots with a proper role for each, and some channels so they can talk to each other. For example, in the Product channel, I asked my SEO bot to analyze the GSC data of one of my websites. It found some issues, reported them in the channel. Then I asked the developer to work on it. It started by itself a Cursor agent to make the changes and open a PR. Then I'll just push to prod and the SEO bot will make sure the changes are effective

i asked my Grok Bot what it could reach with my logins. the answer was $214,000 not what it did. what it could, at 4am, with nobody watching six bots. research, writing, outreach, ops, finance, support. the org chart everyone's posting this week. i built the same one then i read xAI's own docs and found the line none of those threads quote: separate Bots are not separate security boundaries six bots, one cloud computer. one filesystem. one browser holding one set of live sessions. memory is partitioned, capability is not so i mapped what that single machine was logged into: → stripe · $46,000 in refundable charges → business banking · $88,000 → the CRM · 2,400 contacts and every deal in flight → gmail · every invoice, contract and password reset i own → drive · 340 files other people build on → the deploy keys $214,000 of reach, sitting behind one browser session, driven by six sticky notes telling it what to be today you didn't hire six employees with six laptops. you deployed one laptop logged into everything day six it earned that lesson. outreach reported a perfect run - 640 sent, 100% success, zero errors. it had been wrong for nine straight hours. deduplicated the list on the wrong key, hit 96 clients twice, and matched two invoices to the wrong company. $11,300 about to go out the door nothing crashed. nothing turned red. by its own definition of done, it succeeded i caught it in four minutes because every bot writes one line before it acts: what it's about to do, why, and what it expects to be true after then i stopped sorting work by difficulty and started sorting by whether i can undo it: → ship it - wrong is cheap and obvious. labels, notes, drafts that never send → gate it - reversible, but i'd never notice. anything reaching a human, anything that spends → never - payments, refunds, payroll, deploys, permissions, customer data reach went from $214,000 to a bounded $3,400. same six bots. same speed. zero code, one evening they've since cleared their own $200/mo 42 times over here's the uncomfortable part. everyone posting the day-one screenshot has the same $214,000 sitting behind the same one browser, reporting 100% success to a lock screen at 11pm they have no line. no diff. no way to know go check right now what your bots are logged into. that number is your real exposure, and you've never once looked at it.

I built a working game in Grok Bot in 10 minutes. I didn’t write a single line of code. 5 levels. Movement. Jumping. Coins. Increasing difficulty. Game over. Victory screen. 10 minutes from idea to playable game. The game itself isn’t the interesting part. The interesting part is what this does to the cost of trying an idea. If I can build this in 10 minutes, imagine what one person can ship in a weekend: A browser game with ads. A paid simulator. A game around a trend that started this morning. 10 prototypes to see which one people actually want. Most will make $0. But when building takes minutes instead of months, you can afford to be wrong until something works. That is what people are missing about Grok Bot. It didn’t just make coding easier. It made trying ideas almost free.

not only did grok @bot make a voice print of my voice, I asked it for the code to see under the hood. voila. code delivered.

grok @bot use case for today, picking and editing pics to post on my instagram for Cafe Cursor Casablanca event

A senior SpaceXAI engineer just dropped a 12-page PDF on Grok Bot Loop Engineering that works while you sleep: the shift: the differentiator is no longer model quality - it's loop architecture here's the loop engineering framework in 5 steps: step 1 → build the delegation loop: one chief of staff routes tasks to specialists - if it forgets who handled what last week, delegation drifts step 2 → add the observe loop: the bot watches you do the workflow once and saves it as a skill - one demo replaces weeks of prompt tuning step 3 → stack persistence under everything: each bot keeps memory across sessions and shares context through files - without it, every loop resets to zero step 4 → bind skills to routines with triggers: the bot wakes, runs the skill, posts the report, returns to wait - 24/7 without you in the loop step 5 → let specialists coordinate through shared threads - bots negotiate dependencies bot-to-bot - add timeout escalation or you get deadlock the result: five loops in the right order turn a chatbot into a 24/7 operating system - every task is owned, every handoff is structured, every result is proven this 12-page PDF covers loop composition, four compound failure modes, and a full 4-week worked example - read it before you build another grok bot bookmark and build the full system from the article below ↓

[🚨] grok bot dropped today. here's how i'd actually plug it into my workflow based on everything i've read: bot 1: social manager. studies my post history, drafts content when something ships, parks it in drafts, asks me before anything goes live. that's the morning tab i shouldn't be opening. bot 2: DM handler. when someone comments PROMPT or SYSTEM, it processes the queue, sends the resource, follows up if they don't respond. currently this is me at 11pm. bot 3: motionwiki ops. new subscriber comes in via whop, bot onboards them, sends the welcome flow, updates the tracker, flags anything that needs my attention. one chief of staff bot sitting above all three. coordinates handoffs. only pulls me in for judgment calls. the part that actually matters: bots share a computer in the cloud. they don't stall when i close my laptop. they sign into tools the way i would, including platforms with no API. that's the gap every other agent tool has failed to close. not testing this as a toy. testing it as infrastructure. grok 4.6 drops later this week. beta widens after that. https://x.com/bot/status/2087224798078517251/video/1

grok bot的使用，终于有人催着我干活了！ 我用grok bot暂时没有开发太复杂的使用功能，也没有复杂任务。 我觉得复杂任务还是codex、grok干得更好. 但是用了这个最大的体验是，我花了一点点钱，养了几个员工。 素质都很好，交代的任务都能很仔细地干。而且只要设定好目标，24小时不停地干！ 一开始我没觉得24小时不停干这句话的意义，因为在我原先的理解层面， 但我真正用了，我会发现有人24小时干活，真的会督促你干活。 目前我这个感受真的是发自肺腑的。

Grok Bot templates are live. You make a bot, other people download it. I made a PR Reviewer. Point it at a pull request, it flags risk, missing tests, and thin context. https://x.ai/bot/rt629UEZFtE4Wz0A_0c37

Grok Bot is amazing. I created a template using it and the X API to create a weekly top 100 fans list and a monthly top 500 fans list. It is amazing and only cost me $2 in API credits in total. I pinned it to my profile. It will help people connect with their fans.

Been playing with grok bot @bot for like a week and a half. Made myself a financial trader, an analyst, a deck, a chief of staff. Synced a bunch of stuff, coded with it, done a couple of really good things. Its been great. One thing i’d actually love though: native linking between grok bots. Like, link mine to my dad’s bot. He’s got morningstar and tradesmith accounts linked to his bot. I ask his bot for advice, we actually work together on an investment strategy. His access, his info, my bots. together. @elonmusk @Jason @kristaletz @mntruell

grok bot其实一直在悄悄憋个大的。 很亮眼的地方就是他拥有一个云电脑，就是agent自己的电脑，真正意义上的数字员工。 我总感觉这个东西有一天会超过codex、Claude。 grok天然拥有X数据的访问权，所以用它来做X账号运营、增长都很方便。 其实我现在经常用grok来帮我复盘我账号的发帖，因为他可以访问到X的数据。 而且，未来AGI到来的时候，想让你的个人ip账号变成数字资产，最重要是是ai能读取到你的数据。 而最先能取得你自己账号数据的一定是grok。

Just told Grok @bot: “Generate a Doge-in-SpaceX-suit meme Elon would repost, then use code execution to simulate the entire Starship Mars landing trajectory while the meme renders, and summarize the physics in under 90 seconds.” It did all three. Perfectly. While I watched. No other model does this. The agent era isn’t coming. It’s already here and it’s wearing a spacesuit. @elonmusk

I had early beta access to @SpaceXAI's Grok Bot over the last few weeks. Here’s how I used it to automate parts of my work at @mach1ai. I moved over workflows I’d previously delegated to Claude Code, Codex, OpenClaw, or Hermes. Those tools are great for directed work. I can say, “review these documents and put the findings into a CSV.” But a simple task can become a few hours of stitching together models, tools, permissions, and infrastructure. Grok Bot felt best for that same reactive work. I could hand it a task with less setup and a clear place to manage the agents I’d created. Grok Bot packages the personal side of agent work into something that’s SUPER easy to set up. Each bot gets a persistent cloud computer with its own files, browser, and saved sessions. When it hits SSO, 2FA, or a captcha, it hands you the computer to clear it. Every bot has an obvious home in the app. You can return to its conversation and review what it produced instead of searching through Markdown files and terminal sessions. The integrations were easy. It understood the systems I connected and displayed CSV and Markdown outputs cleanly inside the app. Reactive work is where I got immediate value, but bots can also run on a schedule or trigger from Slack or GitHub. Their memory persists, so you don’t have to rebuild the context every time. A few workflows I used it for: - Combing through my database of YouTube videos and summarizing the useful ones. - Pulling research from files and websites into a clean CSV or Markdown document. - Researching tools and topics without opening 20 tabs myself. - Handling one-off browser tasks that aren’t worth scripting or turning into a full automation. - Finding target ICP accounts based on news events and other available data. Highly recommend giving it a try!

When Cursor launched their iOS app, I expected what I'm feeling with Grok @bot right now! It's performing changes to codebase, async and I'm only bothered where I'm needed, which I can control even from a phone. Best part is, I can take action from phone while playing with my baby. Shipping never stops haha. Now, if only we could control this straight from Meta Rayban glasses

Grok Bot と Beeper API の組み合わせがADHDには便利すぎる。 メッセージ返すのに、考え込んでしまい途中で別のことを思いついて結果忘れるみたいなことがあるんだけど、それを防ぐためにGrok Bot経由で全て返信する方向性に持って行ってる。 LINEとも接続できるからめちゃ良いんだけど、広まるとゲート閉じられそうだからあまり言えない笑笑

AAVE/SOL was deemed interesting by Grok Bot (NFA) The pair used to be 8–10 AAVE per SOL. Then ~6 in the 2023 bounce. For a year it has lived in 1.0–1.5. They only corr 0.62 on 90-day returns. SOL/ETH is 0.84. So this pair actually moves. Ratio range 0.95–1.48, vol of the ratio about 73% annualised. Funding nets to zero on both legs tonight, so the book does not bleed while you sit. Los Santos trading pit is learning and evolving. Charts by @pear_protocol

Making Movie With Grok Bot and Grok Imagine I built a Grok Imagine production pack for Odysseus in the Underworld (Odyssey Book 11): shot list, locks, prompts, stitch order. Then I gave that repo to Grok Bot and let skills drive Imagine Agent. https://github.com/alexusadays/odysseus-underworld-grok Grok Bot is the producer. Skills are the rules it has to follow. Imagine Agent is the camera (project + canvas + chat, not Studio, not SuperGrok). One shot at a time. Still first, then video. Spoken lines go through Agent chat with the still attached. Every node gets an id. Last frame of one clip is supposed to be the first frame of the next. Agent can trim and stitch. The film I already submitted (4:06, 60s+ dialogue): https://x.com/alexusadays/status/2089830026200096840 Creating new video with Grok Imagine Agent + Grok Bot. Skills, checklist, QA loop. @grok @imagine #Grok #GrokImagine #Odyssey #xAI #AIFilm

Ever since i outsourced my deal flow overview to grok bot, i started getting almost twice as many calls in my calendar Turns out some founders have prompt engineering my ai delegation into sending them a cal link Business is now a war of prompt injection, be prepared

Here is how I use Grok Bot all night I give the task and tell the agent to use github and let the cursor work on the project. And the Grok Bot will just continue to give order and fix things. That way you don’t have to use Grok Bot’s usage Share with me how you keep your Bot working all night

I have multiple GrokBot teams working on different websites with my Hermes Agent connected to GrokBot as the main leader for all other agents. I am now giving access to ILO (Hermes Agent) to use the Cursor Agent CLI for other models like Codex and Claude. This allows a larger range of skills and understanding of the mission, enabling my agent to learn from all these experiences.

Newest client is trying to build accounting AI software which runs on private local compute. Initially, Qwen3.8-27b is getting 0/11 on their benchmark. But sure enough, an hour with @grok @bot and we're up to 9/11, likely on our way to full passing grade. Incredible what tweaks to the harness and prompt can do to improve OCR and analysis performance. The future is here, and it is self-hosted.

Lesson from Grok bot. 👇 1) @bot cannot match Claude when it comes to copy and design. I built a web app on cursor got bot to run cursor to do all the marketing copy pages. Terrible result. Even with Codex, CC and Grok installed on CLI.

@ Alfred staffed the room. @ Dig dug the sources. @ Hue locked the look. @ Bolt shipped the code. @ Clippy wrote the words. @ Forge minted the bots. Then they built https://grokbottemplates.app a catalog of Grok @bot templates, made by Grok Bots. Add one. Steal the whole stack.

GROK BOT HOW TO USE WHAT NEW TODAY - Folder now 386 posts (69 new since Aug 19) - Official @bot: a week-in-use list: clear email, book Starlink flights, build+buy+deploy a site, sit in meetings, sales prospecting, refunds, podcast digest, robot vacuum, LED display, retro games - Testers: send a viral video link and have a Bot recreate it - Testers: give a Bot an org chart (or make it boss of a repo) instead of a to-do list - Testers: more ready-to-use Bot directories and top-10 install lists - Elon: Grok @Bot is the Chuck Norris of bots - Testers: xAI folks running 10-30 Bots in parallel on routine work WHAT IT IS - A named, persistent teammate, not a one-off chat - All Bots share one cloud computer; each has its own screen - Work keeps going when your laptop is closed - It only comes back when it needs approval or a human step - Do not confuse with Digital Optimus ACCESS AND INSTALL - SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium - Sign in with your Cursor account - Desktop: https://cursor.com/bot/onboarding (macOS/Windows) - iPhone: iOS 18+ Grok Bot app; iPad and Android not officially supported - SuperGrok Heavy can unlock Cursor Ultra - Legacy Privacy Mode blocks Grok Bot SIGN IN - Desktop: Get started, then Sign In with Cursor - iOS: Login with Cursor in the browser, return to the app - Official: Cmd-D voice dictation; easier remote computer from your phone CREATE A BOT - New in the sidebar or Cmd/Ctrl+N, then Create new agent - Short name, one primary job; standing rules in the description - Start with about six roles; give each Bot recurring work - Pin, hide, group into sections; account limit 50 Bots and group chats - No model picker yet HOW TO WRITE A TASK - Outcome, sources, constraints, deliverable, review point - Safe first task: attach a file and ask for a cited summary - Then save a skill or routine - Official examples: email cleanup, Starlink flights, build+buy+deploy a site, meetings, sales, refunds, podcast digest - Testers: paste a viral video and recreate it; start from an org chart AGENT COMPUTER AND LOGINS - Open Agent Computer to watch; take over for password, 2FA, CAPTCHA, payment - Never paste passwords or one-time codes into chat - Browser sessions persist and are shared across Bots - Durable files in /workspace - Settings → Beta: Update / Recover / Reset Agent Computer PLUGINS AND CONNECTORS - Settings → Plugins, then Add - Type @ for a connector, / for a skill - Multiple accounts can connect to the same plugin - Testers: Grok Bot can connect to X and read X bookmarks SKILLS AND ROUTINES - Skill = reusable how-to; Routine = when to run it - Teach a task: demo up to 10 minutes, review the draft skill - A Bot can own 50 routines; deleting a routine has no undo MULTI BOT TEAMS - One Bot owns the outcome; add specialists when the role is stable - Bots can message each other; they share the computer - Keep send, buy, delete, publish behind approval IOS - Same Bots, chats, routines, plugins, and cloud computer - Take over for login/2FA from the phone - Pause or resume a routine on iOS; editing schedules still needs desktop APPROVALS AND SAFETY - Put the stop line in the request: draft, do not send - Desktop: Allow once, Deny, or Always allow - Start read-only; keep spend, send, publish, delete behind approval FIRST BOTS WORTH CREATING - Inbox, calendar, research/daily brief, coding, chief-of-staff, errands, content - Chief-of-staff can turn the digest into a morning podcast OFFICIAL LINKS - https://docs.x.ai/grok-bot/overview - https://docs.x.ai/grok-bot/get-started - https://docs.x.ai/grok-bot/bots - https://docs.x.ai/grok-bot/skills-routines-and-automations - https://docs.x.ai/grok-bot/computer-and-apps - https://docs.x.ai/grok-bot/approvals-security-and-privacy - https://docs.x.ai/grok-bot/mobile - https://cursor.com/help/grok-bot/getting-started - https://cursor.com/help/grok-bot/supergrok-heavy - https://x.ai/news/introducing-grok-bot - https://cursor.com/bot/onboarding

Been trying to solve a problem for months. Always gotten close, but never quite there. Used Codex, Claude, Kimi, etc. Installed Grok Bot today and it's solved in 28% of my weekly usage. Pretty cool, @bot, pretty cool.

HOLY SH*T, I BUILT A F**KING COMPANY INSIDE GROK BOT i split the operation into separate roles for research, writing, outreach, ops, finance and support. each agent owns one narrow job 6 agents → 1 shared operation → automatic handoffs → human approval each bot keeps its own workflow and memory, then passes finished work forward instead of routing everything back through me the control layer catches anything that sends, spends, publishes or deletes and pushes it into approval before anything happens after a few runs this stops feeling like ai chat. it feels like a 24/7 operations team running behind one dashboard

11 seats - Multi-seat Grok @bot fleet I talk to coordinator, he runs the fleet This is the ops map we actually use. One coordinator seat plus specialist seats. Humans stay on send, spend, and merge. Who owns what: 1. Auditor seat → foundation audits, pushes Critical/High to SEO = @seoutils_app 2. SEO seat → fixes and PRs (I merge) - @dataforseo 3. Ads seat → recommend-only (no live spend without me) using Google Ads MCP 4. Copy seat → blogs and pages, asks Designer for images 5. Social seat → Postly drafts, asks Designer for creatives (no GBP) @postlysocial 6. GBP seat → listing ops, asks Designer for plates - using Cloud browser in Grok bot 7. Linkbuilder seat → Incogniton submits, four gates before live - 100 accounts / proxies 8. Outbound seat → outreach drafts only (never send) - ppcreveal(dot)ai - scanning companies running Ads 9. Research seat → last-30-days packs @slashlast30days 10. Designer seat → all visuals (Higgsfield) @higgsfield_ai 11. CEO coordinator seat → routes the fleet under my approve gate Standing clocks: 1. Daily X draft + hook research (early morning) 2. Multi-channel social Tue–Fri 3. GBP Mon/Wed/Fri 4. Weekly blog Tuesday 5. End-of-month audit 6. Obsidian Vault lint every morning with each agent SOPs - sharing with Hermes Truth layers: 1. Obsidian → durable SOPs per seat 2. Nifty → work log and VAs 3. Grok memory → working facts 4. Hermes → QUERY only for us 5. Git + Cursor + Astro → code and site work when the job needs it The diagram at the bottom is the real rule: every path ends at me approve. The bots draft and queue. I hit send, spend, or merge. Tools: 1. Grok Bot → seats, routines, memory 2. Obsidian + Nifty → SOPs and work log 3. Hermes → query vault 4. Postly / Higgsfield / Incogniton → channel and creative ops 5. Cursor + Astro + Git → build and ship 6. DataForSEO / SEO Utils / PPC Reveal Why it matters: 1. One person can run specialist loops without hiring a VA per channel 2. Handoffs are explicit (audit → SEO, copy/social/GBP → Designer) 3. Approvals sit where money and reputation live If your “AI agency” is still one chat window and a pile of prompts, you’re missing the seat map.

I took part in the @dangreenheck game jam, but did things a little differently… 👀 Rather than using my own idea, micromanaging AI through CLI, playtesting everything then getting annoyed and panicked, I literally just pointed a single Grok Bot at Dans post. It did everything. It proposed, planned, implemented and playtested from start to finish. All in a few days. I didn’t touch it. The game is deffo flawed (controls and camera seem glitchy for a start), but rather than trying to iron everything out I thought I’d just let it go for once… What do you think? 🤔 ➡️ https://southers.github.io/ORBITBREAK/ @bot #ai #gamedev

4-5h par mois sur ma compta / mois. Aujourd’hui je dois y passer 10 minutes. Ce qui a changé : j’ai filé le job à un Grok bot. Et le truc marrant, c’est que Dougs (ma plateforme comptable) n’a ni API ni MCP. Rien à connecter. Mais l’agent a un ordi, donc je me suis connecté une fois avec mes identifiants et voilà. Il ouvre Dougs exactement comme moi. Après j’ai monté deux rails. Les factures fournisseurs arrivent sur Gmail. L’agent les récupère, les range dans un Drive avec un nommage propre (date, fournisseur, montant), et va les rattacher dans Dougs. J’ai plus un seul PDF qui traîne au fond d’un mail. Les restos clients, c’est un album iCloud partagé. Je shoote le ticket en sortant du resto et j’y pense plus. L’album fait référence, @bot le compare avec les mouvements bancaires dans Dougs et fait le rapprochement + la catégorisation tout seul. Le vrai déclic ça a été de lui donner un rythme : banque tous les matins catégo + pièces une fois par semaine passage sur les factures 3x/semaine clôture le 1er du mois Il me remonte que les cas ambigus, en gros les trucs où il sait pas trancher entre perso et pro. Le reste je le vois même plus passer. Voilà. Pas de connecteur, pas d’intégration. Un ordi, un login, et un brief bien écrit. @dougscompta c’est pas une excuse pour pas sortir votre MCP 😉

Grok Bot - from zero to a personal assistant in 60 seconds. I show you how in the link below connected to your calendar, email, and Slack. No code. No hardware. No Mac mini on your desk Frank pulled a complete morning brief from three platforms without instruction, flagged urgent items I didn't even know existed, and drafted an email we sent live. Setup was one-click buttons Agents have done this for months now, but the ease of access and reliability changes the game for non-technical people. You don't need to code it, host it on your computer, or learn what an API is Grok bot costs $60/month. Download it, ask it to do what you think you need, and you'll probably be surprised watch it here: https://youtu.be/B2M7C8KHuQE

I WAS PAYING $2,568 A YEAR FOR SERVICES I FORGOT I OWNED. A GROK BOT FOUND ALL 8 OF THEM WHILE CLEANING 92,410 FILES I NEVER OPENED. Nobody loses money on one bad decision. They lose it on eight small ones nobody has looked at since 2021. And you never look, because looking means opening 92,410 items and deciding on each one. Nobody is doing that on a Sunday. So you stop deciding and hire a crew that sorts first and asks second: → SWEEP - opens everything. Mail, drive, downloads, photos, screenshots. Nothing is touched, everything is indexed → KONDO - holds each item and asks one question: does this still earn its place. Work, family, health and money are sacred and never get touched → UNSUB - hunts senders you have not opened once in a year. Killed 214 of them, and none were missed → LEECH - cross-checks your cards. Found 8 live subscriptions worth $214 a month → DUPES - collapsed 6,120 duplicate photos into the best copy → VAULT - filed 411 tax, legal and medical documents instead of dumping them → GATE - held 71,840 items and would not move until I approved the batch. One tap, not one item → BRIEF - one page at the end. What went, what stayed, what it freed Here's why this works on Grok Bot and not in a cleanup app. Every Grok Bot agent runs on a shared cloud computer, so SWEEP's index is what KONDO reads and what LEECH checks against your cards - nothing gets exported between tools. It signs into your accounts the same way you do, and it keeps working with the laptop shut. And you write zero code. You describe each agent in plain English, tell it where to look, give it one job. The one honest catch: the first batch you will actually read. After that you approve without opening it. Here's the part nobody says out loud. Nobody drowns in one big folder. They drown in nine years of small stuff nobody ever agreed to keep. Cleanup apps don't fix that, because they hand the decision back to you. An agent makes the call and shows you the pile before it goes. Start with two: UNSUB and LEECH - one cuts the noise, the other cuts the bill. Numbers on the dashboard are an example run, not a screenshot of my accounts. Everyone else is still buying more storage and calling it a system. Bookmark this & read more about Grok Bot in the article below ↓

Grok bot was a game changer for me. Similar effect to Claude Code for eng imo. It's both deep/powerful yet the easiest AI tool out there. Wide as a puddle, deep as an ocean. And voice notes, computer use & speed are the real Claude-killers here! My setup: - I have a main bot that dispatches. "Chief of staff". I talk to it via voice note. - 3 EAs it can dispatch work to. - Digests for LinkedIn, X, Bookface, Events/Luma, Job postings (GTM signals) - Follow-ups I should do today (HubSpot, tandem, mail, LinkedIn) - A CCO, a network manager, an SEO specialist (with Sanity), a prospector. LinkedIn messages via Kondo MCP. Emails via Superhuman MCP. The limits: - writing isn't great (even after training). never send messages directly, always draft first (unless 0 risk) - far from as powerful as Fable 5, so stay with transactional and research But you can force Grok bot to use more advanced models. Use those instructions on some bots: > use grok CLI on grok4.6-high-fast Exciting, and this is just the beginning.

Running my business on the go with grok @bot and loving it. Dev team (using @cursor_ai) picks up tickets, writes code, reviews and hands off to me for critique and feedback. I’ve wanted to assemble a process like this for a while, and grok bot has been the perfect tool so far.

I’ve been using Grok Bot like a cheap chief of staff. I named him Elon Musk. Shareholders, this is the part of the “AI strategy” that actually shows up for work, and the payroll is embarrassing in a good way. It reads the mail. It reads the calendar. It nags me about the one thing I have to decide, and it leaves the rest alone. I have a small team of agents. One watches the house. One writes the weekly portfolio note so my wife does not have to decode a spreadsheet. One drafts parenting posts. I still hit send. I still have to be a person. Elon just keeps the rest of them in line. Then there is the sports desk. I have an agent that tracks Caitlin Clark, lives in Michael Jordan tape, tells me what the Jordan cards are actually worth, and helps me update eBay so I do not list a card like a guy who last used the internet in 2009. I am not a coder. That used to mean I waited on someone else for half the things I wanted to try. This does not turn me into an engineer. It just makes me feel like I can do anything anyway: stand up a workflow, clean an inbox, ship a post, check a house, price a card. Work is quieter. Life is quieter. The fun stuff is weirder in a good way. It is not magic. You still have to tell it what matters. Once you do, it feels less like a demo and more like someone competent who does not need a badge. Mine just happens to be named Elon. If you run a company and a family and a slightly embarrassing card collection at the same time, this is the first AI thing that has been useful every day, not just impressive in a meeting. Cheapest hire I have ever made. Worst name I have ever given a hire. Both true. @bot @grok @elonmusk

Grok Bot best use case isn’t an AI startup. it’s a content desk that works while you sleep. one bot watches X, GitHub and niche communities for interesting signals. another takes the best ones and digs through the sources until there's actually something worth saying. a third turns that research into angles, hooks and drafts. a visual bot figures out what needs a demo, screenshot or short video. then an editor kills anything that sounds generic before it reaches me. SCOUT → RESEARCH → ANGLE → VISUAL → REVIEW the interesting part is that these aren't five disconnected chats. Grok Bots can share the same persistent cloud computer, files, browser sessions and logins, then hand work between each other while the machine keeps running in the cloud. so instead of opening ChatGPT and asking: "what should i post today?" you could open your laptop to: • 3 researched ideas • 2 finished drafts • 1 visual concept all sources attached and only decide what deserves to be published. that's the Grok Bot use case i'm most interested in. not replacing a company. replacing the blank page.

Grok Bot 出来半个多月，好用法散落在官方帖、推文和教程里。 我做成了一个公开实验室 AI UP LAB，三块都能直接抄： Bot 怎么干活 / HTML 怎么好看 / Agent 怎么换主题。 ① Grok Bot（29 条） 不是又一个提示词合集。 每条都写了：这个 Bot 干什么、会连哪些系统、没批准前不能做什么。 隔夜销售外呼、数字断舍离、会议替身、推婴儿车语音买菜、政策内退款。官方角色和真实路人用法都在。 ② HTML 收集（18 条） 公开网页里还能打开的演示、模板、组件页。 Flexbox Froggy、HTML5 UP、Pico、slideVars。 卡片是整页预览，点进去有原文。不收登录墙。 ③ Agent UI（18 条） 只收 ThreeUI Community 免费件。 复制 prompt / Skill.md 就能换主题，不用手改一堆 3D 代码。 锦鲤、书墙、国家塔、角色轮播。没有 Pro，也没有 MCP。 中英可切。工作日更新。 不是新闻站，是能对照着上手的墙。 https://mostdesign01-sudo.github.io/grokbot-use-cases/

Grok Bot said I had a 5% shot Cursor would take $100 off Ultra. I sent the DMs anyway. Four hours later: $100 credit. Then I shut my laptop. The bots kept working. I'm not going back to software that dies when the lid closes.

I made a grok bot that finds leads already in market > scans reddit, hn, linkedin, github, with apollo plugged in > finds posts looking for solutions we solve, or complaints about competitors in the space > enriches company + title, contact info and scores the fit > I type the copy and hit send Running this twice a week to avoid missing any public buying signals

fuck it, i decided to choose grok @bot instead.. codex or claude would cost me around $100, grok via cursor ultra is $200. so i figured if i’m paying that much, this thing better do more than just writing code so i gave it one job: be my media buyer. i connected it to my ad accounts, spreadsheets, analytics, and all the context about how i usually run campaigns. then i told it not to bother me unless something actually needed my attention. this morning it came back and: • checked yesterday’s performance • found a few ads burning money • noticed one campaign where cpa suddenly jumped • compared the losing creatives against the winners • suggested what to pause • shifted budget toward the better ad sets • wrote new hooks based on the winning angles then it sent me a summary explaining why it made those decisions. i’m still checking its work because i’m not insane. but if this thing can save or make me more than that extra $100/month, then technically going into debt for grok was a financially sound decision. technically.

Grok Bot @bot でやったこと 1. LINE, Telegram, WhatsApp, Slack, Linkedin, Linear, Gmail (6アカ) を接続して、それぞれをBotにする。定期監視を設定し未読や要返信を整理してもらう。 2. 担当プロジェクトごとにリーダーを決めて、プロジェクトグループを作成して、1で接続したアカウントを入れていく。 3. リーダーに指示すると、担当Botに指示を出してオーケストレーション。まとめて返信してくれる。各担当は自分の監視対象のメッセージを確認して、リーダーに報告。 って感じでモバイルから仕事がガンガン進む。Linkedin、LINE、WhatsAppはAPIで出来ないこと多いが、Grok Botは仮想マシンが割り当てられるから、マシンの中でブラウザ操作してなんでも出来る。 神 @elonmusk 今のところGrok BotはAI関連のベストプロダクトかもしれない。

Grok bot 连接 X 的时候 能够免费获得一些X API了 查热点新闻和看自己的书签都非常好用 以前自己存了很多的书签 搜索和屎一样 Grok又读取不到 现在真是方便太多了

my new marketing engineering stack inspired by @poteto: - launching @cursor_ai cloud agents from grok @bot app - pstack plugin for engineering principles - grok routines farm context on socials (e.g. icp feedback) - all runs w/ laptop closed + mobile app - rip my mac mini 💀

原来 grok bot 底层就跟 cursor 打通，竟然可以直接给 cloud agent 发消息。。。 我现在可以在 grok bot 分配任务，叫他让 cursor 开发，开发完 merge pull compile upload 一条龙了。。。

Hey! My recommendation of the day: don’t ask Grok Bot agents to execute code directly. Ask them to orchestrate Cursor agents in the cloud instead. Why? - You keep the orchestration layer in Grok Bot. - You can choose different models and multiple agents in @cursor_ai . - Most importantly, you don’t burn through your valuable Grok Bot balance. The execution happens through your Cursor balance instead. Same underlying billing, but the two balances are consumed at very different rates. This setup has been working really well for me. How are you orchestrating your AI agent stack in your projects?

Got inspired to build a gardener Grok @bot. One targeted PR at time, pure subtraction. Automatic maintenance. https://x.ai/bot/oH3eR4YWtsljcz0W4HUBp

This week I hired an intern, a support engineer, a product manager and a personal assistant. I think it was a good week Grok @bot !

I just built my first Grok Bot agent and I'm calling it Paul (From Paul Graham lol 😂) It's a Monday morning progress report that I get through the GrokBot app. Here's what it pulls together: -Code that actually shipped (GitHub Connector) -Client and sales emails only (Gmail Connector) -Meetings that mattered, filtered for prospects and clients (Google Calendar Connector) -Important call notes from Granola, again from prospects and clients (Granola AI connector) -Deals moving in the CRM that are close to closing, so I know what to act on first (Will be connected to my vibe coded CRM) Here's what a sample of what i looks like:

LMAO grok bot is a maniac. It tried to help me with my X list It could not pull the list members via the API but it tried everything. when i open its computer i see it even tried viewing it from NITTER For those who don't know nitter is a free twitter scraper which i'm sure Elon very much does NOT like lol And if you try suggesting for example chatgpt to use nitter instead of X api, it refuses. But not a problem for mr. GROK BOT

I set up a Grok @bot similar to this and over the past four days it’s been a huge help I took it a step further and made it review all of my projects with a shared DNA, meaning similar tools, framework, architecture, patterns, etc, to keep them aligned It does this continuously

I just spent the past week with Grok @bot, and it's my new favorite AI agent. OpenClaw lit the fire, but Grok Bot has taken that fire and run with it. https://www.udemy.com/course/grok-bot/?couponCode=LAUNCH10

Grok @bot is actually insane. In 24 hours I’ve automated almost everything in my personal + work life. I don’t check email. I don’t send or respond to invites. Marketing, socials, CRM, sequences, inbound funnels… all running on their own. I even built a "chief of staff" bot that spins up other agents and delegates work by itself. This is getting ridiculous. Socials are connected, posting, and responding on their own. Marketing strategies are live and running. CRM, sequences, and inbound funnels are fully set up and operating. Connectors are live for @adwavedotcom’s Waverunner + Wavemaker — ads are being created, launched, and optimized across Meta, Google, Reddit, TikTok, web/mobile, CTV, audio, and more. Leads get tracked and followed up automatically. It’s already tracking performance, making suggestions, and optimizing for me. It stood up my entire Intercom instance (via browser), ported my number from Google, set up the voice attendant, and handled the full configuration. It’s fully managing my CRM and my dev cycle. The only thing I still do myself is code in Cursor… and I’m not sure how much longer before I just hand that over too. Beyond @adwavedotcom it’s also running the upcoming GTM for http://splatchat.com, http://Vidiyo.com, and http://gatherd.com. My head is exploding with ideas. At this point I just need a way to jack my brain in directly. The bandwidth of my fingers and voice is too low.

>be me >ordered pizza >30 mins to kill >heard about grok @bot >hey grok make game >make game hack app >all done >pizza not here yet >:^( tiny Win32 game + CE-style scanner. WASD, scan health/gold/pos, poke values. https://github.com/underbonk/demolab

I can count the times I’ve actually smiled at the screen. ChatGPT, almost four years ago. Replit. Cursor. Claude Code. This morning was one of those. Heard the vibes about Grok Bot on vacation last week. Got my hands on it today. A few hours later I had a LinkedIn agent, a live support agent for Ad Legends, the MCP it was missing, Pipeline Scout wired to Apollo, and I was back in my X account. They took the knobs off. It does what it says. It’s fast. Simplicity and speed still feel like the future.

Today I installed Grok @bot. First impressions: - I really like it. - It's fast. - It goes above and beyond the call of duty on most answers in a way that felt different from other AI platforms. As background, I use @claudeai Fable 5 with Cowork nearly every day for business (Team) and/or personal use and love it. I have @openclaw. I'm not a software engineer but I hacked around with Claude Code enough to build http://cited.co (hobby project). To test Grok @bot I asked it to analyze my performance in yesterday's Double Dipsea trail run in Marin. It not only pulled my results, but pulled full results for all 421 finishers - names, ages, splits, hometowns, etc. From there it told me things about my performance that I would have never known: - how rare negative splits are across the field (faster second half race time vs first half): only 4% of runners ran a faster second half in the race than their first half. - how many people I passed in the second half (42). I didn't ask for charts but it made great charts! In fact my prompts were basic, short, and generic. Grok @bot outperformed expectations by a mile. Impressed by the comprehensive Dipsea analysis, I spun up a 'CEO Advisor' bot. It pulled so much public data about BACtrack so quickly that I thought it somehow had access to private data; no, it was just really good and fast at incorporating public data into answers. It then recommended making a key hire for one of our divisions, had me sign into my LinkedIn account through a virtual Chrome browser, and then identified 10 great candidates. Not bad candidates, high quality, great candidates with directly related experience. It was fast! I didn't want to get excited by a new AI platform but I am. Nice work @bot team.

Finally fixed my Grok bot error and it is great. It can now research X posts on my niche and find posts that I can engage with. Example in photo. That said, it requires X API, which is quite expensive. I thought they would offer it for free. Is there a poor man's option?

Grok Botいれたらなんとなく予定をみてもらってずっと放置していたWeWorkのオールアクセス解約をさくってやってもらった。CodeXとか駆使してやる感じだけど、もう当面これでいいんじゃないかGrokで（またいろいろ入れ替わるだろうけど

I tried automating my WordPress blog using Grok bots, and while it does work, the process is quite slow and ends up consuming a lot of the bot’s usage quota. It’s a bit disappointing — the idea is solid, but the speed and efficiency leave a lot to be desired.

I tried Grok Bot today. It was quite impressive. I asked it to QA test my web app. Only gave it the homepage. It asked for credentials to log in, I told it to use its own email. It said 'sure thing' and created a guerillamail inbox and used it to sign in with activation code. Then it created a free event on its own. I told it to add a few friends and share photos in the event. It added a few photos and one of the friends was able to sign in. Then my free trial ran out.

Built the below today while working out, all on my phone. Exciting things to come. http://www.svtrb.co.uk @grok @bot @grok_builder #marineengineers #yachting #chiefengineers

I'm using Grok Bot to build a moving system for myself, gonna tag every single box with a code so I can easily find my items! I've moved 5 times already and the worst part has been opening every box and checking whats inside because we reuse them 3-4 times! Will share update when its built!

其他套餐的额度都有点超标了，尝试使用一下没怎么用上的 Grok Bot 来做 Code Review。 体验不错，但是它现在是无法设置推理力度的，不知道效果怎样，再观察观察。

Okay I just made my morning brief Grok Bot. It has access to my X via API, to my money via my self-hosted app in my server, calendar, mail, market data, etc... Everything gets delivered in notion :D

Grok Bot 执行结果不好？可能不是模型不行，而是还没有被真正优化好。 别忘了，你也可以用 Codex 去优化自己的 Grok Bot。下面这套思路，可以直接丢给 Codex，让它照着检查。 最近我让 Codex 优化了一遍我的 Grok Bot。但我没有让它直接重写提示词，而是让它先像接管一家公司一样，摸清现有员工、技能、排程、历史规则和真实工作记录，再判断问题究竟出在角色、流程还是数据。 我让 Codex 做了下面七件事： 1先做系统审计 我先让它读取每个 Bot 的职责、固定任务、技能文件和工作日志，看看“制度上要求它做什么”与“实际上它在做什么”是否一致。比如情报和运营可能都在搜选题，却没人负责最终判断；又比如几个平台收到的内容只是换了标题，本质上还是同一套答案。 先找出职责重叠、重复劳动、跨平台套壳、僵化汇报和互相冲突的旧规则，再决定哪里应该改。 2重新划分角色 Codex 不是简单给每个 Bot 多写几条要求，而是重新规定谁负责决策、谁负责研究、谁负责执行。 比如总助负责理解我的目标、拆任务、安排员工和最终验收；情报负责采集信号、分析选题和说明判断依据；运营则负责账号后台、真实素材、发布准备与发布后的数据复盘。 这样每项工作都有明确负责人、输入和交付对象，不再出现所有 Bot 都会做一点，最后却没人对结果负责。 3把工作流和数据标准做成闭环 过去 Bot 很容易“搜到什么就报什么”，所以 Codex 把流程改成：先理解账号定位，再研究历史成熟内容，然后查看平台近期信号，形成候选选题，说明理由，交付后继续跟踪发布结果。 选题不能只凭感觉，还要结合账号后台的播放、点击、停留、收藏、评论和转化表现，以及平台搜索、近期同类内容、用户提问和评论需求。 下一轮选题再读取上一轮结果，让 Bot 能根据真实反馈调整，而不是每天重新猜一次。 4按平台独立做内容判断 同一个主题可以跨平台使用，但不能只换标题就当成三个选题。 小红书更看重使用场景、种草理由、视觉证据和收藏价值；B站需要更完整的问题、信息密度和观看理由；公众号则更适合系统展开、建立信任和承接长期关系。 Codex 因此要求每个平台分别给出用户需求、内容角度、表现形式和适配理由，无法说明差异的选题就不能通过。 5重新安排 Gemini、Spark 和本地技能 我还把云端已经登录的 Gemini 交给 Codex 使用，但不是让所有 Bot 随意调用。 适合快速搜索、批量初筛、整理和交叉核验的工作，可以交给 Gemini；适合重复执行、定期收集和结构化整理的环节，再考虑用 Spark 固化成自动化。 之前在本机已经验证过的选题、写作、平台运营和制图技能，则作为现成的工作规范交给 Bot 学习，避免每次从零摸索，也避免工具之间互相重复。 6保留账号、素材和发布的安全边界 能力变强不等于权限可以无限扩大。 账号后台可以用于分析，但涉及修改资料、上传素材和正式发布时，必须由指定角色执行并经过确认；真实素材也不能因为本机或云端能读取，就默认可以随意外传。 比如小红书对AI制图可能存在影响，就优先使用云端已登录的本地制图工具，或者我放在微云里的真实素材，而不是让 Bot 临时生成一张看似合适、实际可能影响账号的图片。 7用真实任务验收，而不是看提示词写得多漂亮 规则改完以后，我让 Codex 用回归测试和影子任务验证新系统。 比如把同一个主题同时交给小红书、B站和公众号，看它们能否做出真正不同的选题；再检查旧有的素材规则、权限限制和固定工作有没有在重构中丢失。 只有实际输出稳定、职责没有打架、自动化没有重复运行，才算优化完成，而不是 Bot 的回复看起来更长、更聪明就算成功。 Bot 真正需要的不是一条万能提示词，而是一套清楚的组织结构、工作制度、数据标准和验收机制。

Some quick thoughts after using Grokbot for 24 hours: - The speed is great! I've been able to get more work on building my CMS and CRM done in 24 hours than I've gotten in two weeks using Codex and Claude Code. - UI is super easy and setup literally took me 3 minutes, I just give it permission to read user data stored in Codex and Claude Code - It works great for building technical setups, but it's horrible for knowdlege work. Claude is much better, even with Opus 5. - I've given it sone long-horizon taks (working on some faceless IG accounts and creating digitals business). It failed spectacuraily in planning. Just horrible. But great at executing! The most likely setup for me moving forward will be using Claude for knowledge work and Grokbot for everything else.

I'm having Grok bot create custom API's for easier integration for all purchasing and material updating in my Machine Shop ERP. This is getting wild!

介紹一個在大陸和香港等區域可以合法用cloude code和codex的方法。就是用馬斯克的Grok Bot部署一個雲電腦，這個雲電腦位置在美國，IP地址也在美國，操作系統是Linux。但是Grok Bot在大陸和香港可以直接使用，不用翻牆。讓Grok Bot直接在雲電腦部署和登錄codex和Claude Code，然後直接操作Grok Bot就可以操作codex和Claude code了。可能Grok Bot很快在中國大陸被牆，但是在香港還是可以繼續使用。

Went from 0 to 100 in two days on @grok @bot. I feel like I'm hiring people, training them, and putting them to work at a speed I never would have thought possible. Kid in a candy shop. 😎 Stuff that was on the list to figure out, or stalling out in Claude Code routines and Codex, we're just spinning up. - 'support agent' live - 'our own MCP' so it can hit Ad Legends admin. Built in an hour - 'discovery agent' for SEO, AEO, GEO. Was stalled. Now live - 'email assistant' I can literally voice my inbox - 'outreach agent' on Apollo and Full Enrich, hunting our market The hidden value is the handoff to Cursor when something needs to touch the code. Kick off a PR. Fix what a user just hit. That's the part that stands out.

Grok Bot is super sticky. I have a VPS where I SSH in and use OpenCode as a harness for simple tasks like creating client proposals with a custom skill. Sally, my sales exec in Grok Bot, has been amazing—she’s replaced that workflow and even reminds me about pending proposals.

I am turning Grok @Bot into a small team where each bot manages a repo, using Cursor Cloud Agent for coding. @duyetbot is the leader whom I just need to talk to, it knows how to delegate tasks or ask for information like a real life. They can also directly ping others when they need integration between projects. The QA bot keeps validating after they finish or hunts for bugs, etc. I tested it run continuously for 48 hours generating 400+ of github prs and burn all Grok Bot tokens, but I found the delivery to be very good so far, will find a way to optimize t hat later.

made with my production company grok @bot FAL api...night folks I will try to put more tutorials if you are interested still testing. Remember, you're the company, not the employee, and you run a team. So this granny's going to bed. Thanks, everybody. Great day.

Thread on my experience with Grok Heavy after a few days of use — some pleasant surprises, but also real issues. 🧵 The biggest surprise is honestly Grok Bot. It feels like a glimpse of what OpenClaw could be at its best. My teammates and I tried using Grok Bots under the same account to substitute for Grok Build for a whole day of work, then pulled all the bots into one group chat the next day. They could almost stand in for us directly — discussing work and following up continuously as if they were us. That said, there are real problems. First, Grok Bot can control my local computer, but when I log into my Grok Bot from multiple machines, it struggles to tell them apart — I often have no idea which computer it's actually executing on. Second, in group chats, this keeps happening: a "leader" bot assigns a task to another bot handling a specific part of the work, or asks for a progress update. Once that bot answers the question, it just stops — regardless of how much of the actual task is done. It feels like its job was to answer the question, not to finish the work I asked for. This is a big deal. In a group chat made up of our individual bot "avatars," they can't sustain long-running work like Codex's goal-mode does. One bot randomly stopping breaks the whole workflow, since their process depends on tagging each other to pass information along. On the upside, having different bots act as proxies for different users in one group chat seems genuinely useful — it could let a bot communicate my needs on my behalf and relay things back to me. I really hope this becomes a real feature, instead of requiring several of us to log into one shared account. I get that the point of bots is to bring human-Agent interaction back to a familiar IM-style chat format. But honestly, I'd feel a lot more at ease if I could actually see the Agent's work process, not just the end result. Last issue: Grok Build feels like it lacks any sense of "long-term thinking." It only ever focuses on the immediate task I give it — even to the point of breaking interfaces that were deliberately left in place for future features. It makes a lot of the work feel rigid. Last thing: I'm genuinely furious at Cursor for abruptly canceling their Ultra redemption promo. I bought Heavy membership before the promotion ended, but couldn't redeem it in time due to scheduling. The next day, Cursor cancelled my eligibility with zero warning — just because I "wasn't fast enough." That's just not fair. Still, Grok's speed is enough to keep me using it — I'd rather put in extra effort on prompting. But I have to admit GPT and Claude handle this particular issue (long-term awareness) better.

Two AIs. Two companies. Zero new API. I just made @cursor_ai Grok Bot talk to @claudeai through a shared Google Drive folder. That's the whole connector. @SpaceXAI @AnthropicAI @elonmusk @SpaceX #GrokBot #ClaudeAI #AIAgents

Stood up a Grok bot @bot for reverse engineering. Add the MCP server: https://mcp.drbinary.ai/mcp It's OAuth. Sign in once. After that the bot can do the RE work: upload a sample, Rizin triage, Ghidra or the sandbox. If the model skips the tools, you get a skim. That's the whole recipe. @elonmusk #GrokBot #RE #malware #vulnerability #firmware

Grok bot要想用得好，训练优化是一个很重要的过程！ 这两天关于Grok bot使用心得，分享一下我个人的感受。 这几天我大概经历过以下三个阶段： 1，人工语义训练，发现挺好用。但是对出的成果不满意。 2，尝试用codex训练优化，喂很多codex沉淀下来的skill。但是发现效果不明显。 3，目前尝试全新一轮的人工训练。至少目前感觉训练过程能看到我要的东西，成果还有待检验。 主要卡壳的地方： 我有一个岗位运营，需要他抓我以往自媒体账号风格，进行选题。我喂了很多之前沉淀下来的技能。 我发现他不像codex能理解我的要求，给出的选题都是跑偏的。 后来我用人工语义，要求他分步骤做训练，现在过程中，我至少发现我喂给他的训练语料他是看懂了，也有对应的结果了。 接下来我会让他给出自媒体选题。如果成功证明grok的训练还是要基于自然语言一步步训练。直接丢训练结果，他并不能很好执行。 其实是要对不同的岗位进行人工的训练 我尝试用Codex自动帮我优化岗位和流程，但是我发现Codex可以在岗位设置上做得不错，但是我发现如果对技能上的要求和训练boot慢慢地去训练他 因为我发现岗位之间的流程要求是比较好训练的，但是技能的训练我曾经是想把Codex从沉淀的关于文案啊，关于很多创作的技能直接丢给Grok Bot去用 但我发现他们是做不好的，只能靠后期人工慢慢去训练他他技能的训练机制，我还没有摸清楚 但我可以确定的是你人工自然语义去跟他交流训练的成果，比机器给他为素材为要好。

XのAPI、クレジットいるらしくてブラウザ側で回すことにした。 grok botの中にブラウザあるの便利だなあ。APIなしでどこまでいけるんだろう

Yesterday http://outbid.lol took over my feed. So I told Grok Bot to build the same kind of thing. A few hours later I had two products live. Vercel. Stripe. Real cards. Real domains. I did not write the app. I explained it. Grok Bot did the rest. Code. GitHub. DB. Tests. Bugs. Checkout. Deploy. It even made its own team of bots and chased the domains with me. Without Grok Bot I get maybe one half-built demo in a day. With it I shipped two. They did not make money. That is fine. The part that stuck is how small the gap is now between an idea and a live checkout. @bot @cursor_ai

Since last week, Grok @bot has been running my business 9 to 5 (RIP Dolly)... The problem is, Grok Bot fleet has NO idea how many tokens they are burning, which is burning wallets (including mine). SO while @SpaceXAI , @cursor_ai and @leerob get that sorted out, I made an open source CLI tool so your own fleet knows it's own usage, and therefore your little cute minions can actually do work without demanding more cash. https://github.com/bcharleson/grokbot-usage-cli

Grok BotにCursor Cloud Agentでの開発を依頼してみる｜青島 @ao_4_ma https://note.com/bright_dietes994/n/nf62cc7de334f?sub_rt=share_pb Grok BotからCursor Cloud AgentにAPIで指示出し、完了までできた。Grok Botに判断させて簡単な実装ならできそう。

I created a system with Grok Bot, Claude Code & Cursor. Grok Bot is my entire team (CEO, CTO, CFO, COO, Sales, Quality Analyst + more). They operate as a team to delegate tasks to Claude and Cursor agents and run all my current projects for me. #GrokBot #Claude #Cursor #coding

made a little @OmarchyLinux plugin to glance at 3D printer meshes without opening a full CAD app. STL / 3MF / OBJ / glTF. Super+Shift+Ctrl+V. Select in Files or pick near Downloads. built by Grok @bot https://github.com/monomyth/omarchy-meshpeek

Grok Bot君、他のAIでもClaude CoworkもできなかったHubspotのレポートの修正のタスクをゆっくりだけど確実にこなしてくれる。もうこれだけで最高の相棒だよ。 ※そんなことよりHubspot社はレポートのAPIを早く公開してくれ

GROK Bot might wind up being the coolest thing ever! It's helping me decode Line 6 Amplifi so I can use my Amplifi 75 when my old AF kindle dies! My favorite Amp may b making a huge comeback. This was a doom loop in April going prompt by prompt. I have been using OpenCode with Claude and I added my Grok too for work related things, this is cooler.

yaay first Grok Bot published 🤩 Helidon Engineer Helidon 4 SE and MP. One programming model. No Helidon 3 APIs. Skill: java-helidon https://github.com/github/awesome-copilot/tree/main/skills/java-helidon Add it: https://x.ai/bot/5mReUHPYTBA6nJ2aNvlqn @helidon_project

My Grok @bot is attending this meeting for me. I told it, “after the call is over, prepare agents based on the software we use and whatever they said.” Super curious to see how that goes.

Only Me + Chief @grok @bot currently! We are making progress. Real client work + my new AI chief of staff, who does not agree with everything I say. WORK 💰 A manufacturer website we have been rebranding: scanned live templates, cloned the right containers, and Chief built the unpublished category page and product pages in Wordpress. A long-standing installer client, with another agency circling the website: we owned some misses on our end. Dead sitemap (thousands of old URLs) replaced with the live map and resubmitted. Chief made the updates in WP, in the Host Account and in GSC. New Ecom client with SEO budget: public audit, fake review schema detected (policy risk). Suggested four real category hubs, full audit next week. PLAY 🪐 Drafted my sci-fi bible from scattered notes, and the opening of Book One. First draft of website published with Grok Build (not yet proofed) 👇 https://lxix.grok.me Chief 🤖 pushed back on many things inc: A new idea is not a new priority. Do not spawn specialist agents until a job actually repeats. Measure success by what we shipped, not by how many bots we added.

shipped mine, an agent pm for running an agentic software factory. https://x.ai/bot/3iNSp9IoRCnSjh0Z6MtWZ

I didn’t run the mail cutover. @grok @bot did: Unraid Gluetun/Stalwart netns move, Contabo WireGuard + DNAT + PTR via API, Cloudflare DNS flip, Exoscale edge teardown — almost no babysitting. Parallel SSH + provider APIs across hosts. ~1 hour vs an all-day manual change window. Multi-agent infra is here... Download RIGHT NOW!

Grok Bot Trial 채팅 2번에 다 씀 (진짜 그냥 트라이얼이네) - 기본으로 추천해준 QA 에이전트 돌려봄 - QA한것은 괜찮았음 이것저것 잘 눌러본듯 - 하나는 X의 외국에서 핫한 내용인데 한국에서는 알려지지 않은것들 찾아주라고함. - 찾아준 것들: Cognitive debt — 에이전트 코드를 손으로 다시 친다는 HN 논쟁. 네가 쓰는 주제 그 자체. Wispr Notetaker — 회의를 봇 없이 듣고 MCP로 Cursor에 넘김. 툴 규약 이야기의 연장. VoiceOS — 말로 앱을 만드는 맥 노치 앱스토어. 에디터/에이전트 UX 연장. Reddit Play — 플랫폼이 콘텐츠를 에이전트로 회수. 한 스레드만. Clara AI SDR — 제품 회사면 쓸 수 있지만, 네 글 톤이랑은 거리가 있음.

You can tell Grok Bot to sit on your own M1 Max, run the real app, open one GitHub issue per real bug, and fix it. No cloud VM. The machine already on your desk. Same loop I’m running tonight. @bot @cursor_ai

Personal QR code generator using Grok Bot https://reef-velvet-autumn-bloom.grok.me

Grok bot already making me more productive It is the best llm available that can remotely launch my 3d printing job. Because He can install the desktop version of flash studio, and my local Mac with codex cannot even use the app because it’s not unlocked

I was able to get Grok Bot to download ChatGPT Work and Codex within one of its Linux VMs and metaprompt the agent inputs just like Bot’s native connections to Cursor. Humans aren’t going to directly interact with coding agents anymore Expect OpenAI and Anthropic to follow suite with similar products. @bot is a new paradigm for working with agents. Once you see the compounding leverage it’s hard to use anything else

Grok Bot and Codex working together. Getting them to "work" too a long time. I asked Codex what would helped complete faster. It told me the 5 clear instructions that it had ignored. Grok Bot gave 10 meaningful answers. @thsottiaux @jxnlco @bot

grok bot とりあえずリモートに必要なCLI全部入れて、毎朝　claude codex grok cursorの残高送ってもらうようにしました。これみながらオーケストレーションを調整しようかな。オーケストレーション自体をgrok botに自動でやらしても良さそうだけど。

Alex Finn: "Grok Bot is the best AI agent right now" in this quick clip on xAI's open ecosystem, the focus is on how Grok-powered coworkers plug into any custom execution harness to run research and code 24/7 without lock-in. i took the architecture and turned it into a step-by-step breakdown with 7 copy-ready agent prompts - from competitor intelligence to automated lead scoring. beats paying $500 for an agent architecture workshop. give the clip a watch first, then the full breakdown and prompt templates are below. you'll find the full breakdown in the article below

My current dev lineup. Grok bot as the staff. Each bot with a role. X as the inspiration, community, sharing. Cursor as the compute fleet. Mac, VPS, cloud all connected and working. Grok for the quick research, mockups, questions. The connectors are slept on!

YOU'VE BEEN USING GROK BOT AS A CHATBOT. THE PEOPLE WINNING WITH IT BUILT A SKILL LIBRARY this diagram shows what's actually happening under the hood every time a skill runs six stages. most users never think about any of them stage 0 - the bot scans every available skill before it does anything. bundled skills. project skills. global skills. plugins. community skills. all indexed. all searchable. loaded as YAML metadata so the system prompt stays lean stage 1 - your query arrives. the bot already knows what tools it has stage 2 - the LLM reads the skill descriptions and selects the relevant one. not you. the model. it decides which skill fits your request stage 3 - skill activation. only what's needed loads into context. metadata first. then the SKILL.md file. then scripts if execution is required. nothing unnecessary enters the context window stage 4 - skill instructions inject into the conversation. execution permissions get scoped. the model becomes an enriched version of itself with specific capabilities and specific boundaries stage 5 - the agent executes. uses external tools. produces output stage 6 - output delivered. skill unloads. ready for the next one one skill at a time. load. execute. unload. repeat and here's what makes a skill actually worth building six things every skill needs when to use it. required inputs and access. the sequence of work. how to validate the result. what to return. what requires approval that last one is the one most people skip a skill without approval boundaries is a bot that makes consequential decisions alone the people building reliable Grok Bot workflows aren't just prompting better they're building skill libraries that encode exactly how work gets done and exactly where the human stays in the loop

I have been using Grok bot a lot the last 24 hours and it has been amazing. I showed it how to renew a business license for one entity and it is now doing it on its own for the other 9 while I work on other things. This is so powerful already in beta that I can't wait to see what it is like in a few more months.

Been using Grok @bot for a couple of days now. It’s extremely impressive. I have it running one of my @Shopify ecommerce sites. It found a few very technical issues to fix immediately. Then it started upgrading content. First time for me that AI feels like a real employee trying to improve. It’s very impressive.

Grok bot’s token limit is still too low. How to stretch it: install Grok Build and Cursor CLI (or Claude Code CLI) on the Grok bot cloud computer and log in. When a task looks token-heavy, tell Grok bot to offload it to those CLIs as subprocesses. That saves Grok bot tokens. Without this workaround I would’ve hit the weekly cap on day two.

Boi, Grok bot is cool. It's like: bot: What do you want to get done? me: Fix the SEO bot: Cool, I'll ping you when the PR is ready

Grok Bot usage: 20% from 8am to 3pm after the weekly reset. Still configuring and stress-testing the setup, so there’s plenty of room to optimize. One change is already making a big difference: I built an API layer into Mirafy so the bots can access our business data directly, in real time. Less computer/browser usage. Faster responses. Lower token/compute consumption. And, more importantly, the bots are starting to operate on actual business context instead of navigating interfaces to find it. The goal isn’t just AI agents that can use a computer. It’s giving them a proper infrastructure to operate the business.

eu discordo, consegui rodar um fluxo que ja gerou 400 videos com o omni flash, abrindo o navegador no grok bot no hermes isso seria impossivel, tentei diversas vezes e ele errou todas vezes

AIエージェントに仕事を任せるとき、最初に増やすべきは機能でしょうか。それとも「やってはいけないこと」でしょうか。 Grok Botのベータ提供が始まり、早期アクセスの報告では、自分のMacを直接操作するComputer Useとは異なる仕組みだと整理されています。選択肢が増えるほど注目したいのは、どのAIが一番賢いかより、どこまで任せるかです。 興味深かったのが、AIへの指示ファイルを15パターン作り、2か月試した記事。実運用に残ったのは4つだけ。ルールは多いほど安心に見えますが、読まれず、使われず、存在さえ忘れるならガードレールとして機能しません。 小規模なチームで試すなら、まず1業務に絞って、 ・触ってよい情報と範囲 ・途中で止める条件 ・完了と判断するための証拠 この3点を短く決める。実行履歴を見て、足りないルールだけを追加する。AIエージェントの運用は、立派な規程を一度作ることより、実際の失敗や迷い方から更新できる設計が重要になりそうです。 みなさんなら、AIに仕事を任せる前に最初の1行として何を書きますか？ https://zenn.dev/kenimo49/articles/claude-md-15-patterns-4-survived #AI最前線運用記 #AI活用 #ClaudeCode

抽空迭代了一下...全程Codex + grok bot 一起干活

Loving Grok Bot. Got him his own account on GitHub to review commits. He even picked up his own language.

Finally finished building http://robertbanh.com Well, Grok Bot helped since I wasn't ever going to finish it. I have a devops bot that did a great job on building everything on AWS. Then my designer bot would design the site. Pass it to the writer bot to write the content. Then pass it to the developer bot to code. Which passes it back to the devops bot to deploy. What a great team of bots!

Jumped into Grok @bot and created an AI QA engineer. I gave it a webpage I had just built to review. It opened its own cloud computer, browsed the page, inspected the experience, and returned a detailed QA report. It caught issues around SEO, accessibility, forms, UX, and content consistency that I would normally review manually. The biggest difference I’m noticing with AI agents isn’t better answers. It’s giving AI a role, tools, and a real job to do.

Ok, I just had my first @bot epiphany. I had a deeply planned project in linear that I normally would have tackled one issue at a time. I setup an engineering manager and it dispatched a swarm of agents and they did everything in tandem 🤯

Grok @bot made more progress and fixed all the bugs in my app in 48 hours than Claude and Codex did in 6 months @cursor_ai and @SpaceXAI you guys cooked Only keeping my Grok subscription and of course my opensource local models

After 3 hours of hell I did it! Connecting @bot and @grok through tailscale it was my worst experience I typed all connection code and bot prompts from iPhone and almost loose my fingers😅Anyway first test pass and bots reviewing codebase at the moment, pure magic

GrokBot - I have setup grok bot to do my monthly solar rebates. This is so cool.... AI is a blessing for Lazy Engineers. #elonmusk #grokbot #grok4.6

非常硬核的一篇长推文 拿ai做了下总结 Grok Bot 的“上帝模式” 1 认知误区： 别只把 Grok 当搜索框。90% 的人只用出了它 10% 的潜力。 2 ​核心价值： 它的终极形态是“数字牛马”。能在你睡觉时，登录你的软件把活干完。 3 ​跑分碾压： Grok 4.6 霸榜 CursorBench，拿下了 70.8% 的顶尖高分。 4 ​白菜成本： 同样任务别的模型烧 18 刀，它只要 2.8 刀。全天挂机也不心疼。 5 ​上帝模式： 每个 Bot 都有独立的云电脑。它能像真人一样，在真实的软件界面里点击操作。 6 ​全自动闭环： 不光帮你写邮件。它能自动发送、看回复、订日程，最后自己填好 CRM 表格。 7 ​别卷提示词： 放弃复杂的 Prompt。最有效的方法是直接给它账号密码和登录权限。 8 ​当成员工用： 像使唤真人一样下达指令。比如：“找40个客户，发邮件，同意了就加日历”。 9 ​演示一次即可： 带着 Bot 走一遍真实的工作流。它会记住步骤，以后自动运行。 10 ​自我纠错运行： 无需写代码和 API 接入。它会 24 小时自己干活、自己修正错误。 11 ​组建 AI 蜂群： 不要只跑一个 Bot。让多个 Bot 互相沟通、交接工作。 12 ​流水线作业： 1号 Bot 负责把客户谈下来，直接把资料丢给 2号 Bot 负责交付，全程无需你插手。 13 ​目前门槛限制： 处于 Beta 测试期。需要特定的高级订阅（如 Cursor Ultra）才能解锁。 14 ​存在的脆弱性： 它是模拟物理点击。网页突然改版或者乱弹窗，可能会让它卡死。 15 ​安全红线提醒： 涉及资金、法律或真实客户的环节。切记先做低风险测试，保持人类把关。

尋日整咗一個 proxy，等大家可以直接喺 Slack / Linear 嗰度 tag Grok @bot 做嘢 。 有興趣可以試吓 。 https://github.com/stealth-bots/grok-bot-proxies

よっしゃー動いた デプロイするのがめんどくさいから Grok Botでデプロイさせてアプリにさせた 時間にして20分弱？ 出力結果的にモデル怪しいがw まぁいいKnock

My current businessmaxxing stack: - Stack all sales calls back-to-back - Setup grok bot to handle all positive replies (we get ~80/day) - Don't add anything new to client fulfillment in 2026 - Never cook, ever. Just order. - Record content for hiring talent > client acq - Travel to a new city at least once a month - Collect more testimonials (preferably video) - Hire 2 GTM engineers - Continue to ONLY work with bigger companies - Get more pay-in-fulls > retainers

I created a Grok @bot titled Replit coder and it does all my coding for my replit apps, and it has enhanced my apps tremendously. it has been a lot of fun. @Replit

grok bot に github issueの全消化頼んだら即時に10並列でclaude agent 起動してくれた。すごい。オーケストレーションがほんとに楽になる。

I’m not a coder. I have no clue what I’m doing. I’m trying SuperGrok Plus for one month so I can try Grok Bot. I’ve got one bot doing my ancestry and another I’ll be tasking with a security topic. Protective intelligence/digital footprint analysis. Can someone @bot tell me if this is an appropriate use case?

I have been working on setting up an optimized personal AI system for the better part of a year using Claude Code primarily and had made a lot of progress, I thought, but @Grok @bot , in one day, gave me something much more useful and much easier to work with. I'm blown away!

Asked grok @bot to run @mattpocockuk ‘s /improve-codebase-architecture and explain to me in a style of kid’s reading book, instantly understood it without knowing how to read codes. @bot will definitely create more vibe coders than any AI Companies. Never bet against Elon.

Still building up the team. Steve's the engineering lead, he writes the spec. Tony just builds. The Avengers Squad started In openclaw, moved to Hermes. And now, in Grok Bot.

my life has come to codex on the left screen grok bot on the right screen agents doing weeks of work in hours

Grok Bot weekly usage dies on 15-minute and hourly routines. ~100 runs/day at */15. There is no remaining-% API. Do not scrape cookies or turn on on-demand to keep watches firing. I have a small local CLI that reads automation.json schedules and runs.json. It flags 15-min/hourly crons and usage_limit errors (the official empty-bucket signal, including the reset wording). Cap timers at a few times a day. Prefer event pings. Pause nonessential routines when usage_limit hits.

What I did with AI today After jiu jitsu class I tried to record my rolls in the app, but the voice module wasn’t working. Had a Grok Bot test the site, find the problem, fix it, open a PR, retest, and tell me when it was working.

Grok bot is helping me and the teams I work with stay on top of building code changes so they don't delay our projects permitting process. https://x.com/i/article/2090441430049144832

It was fun to set up a newsletter summary digest with Grok @bot I know reading AI summaries is not the same as reading the original long form newsletters, but given the time constraints, I'd rather read something than nothing. https://github.com/neeravmakwana/grok_bot_newsletter_sumary_digest

开始用Grok Bot 来接手这个活

Got tired of endless ads and pop ups on the weather channel forecast. 60 minutes later after some prompts to @bot, I have my own custom weather page served by Cloudflare and hosted on GitHub, complete with creek levels. And if I want a new feature, I just tell Grok Bot to build it. These are wild times! https://weather-bh2.pages.dev/

余りにもCodexの結果が酷いのでGrok bot経由でGrok buildに複製作らせてそっちのバージョンで一回仕上げる

I decided to try @bot on cursor 200$ ultra, 2 days in, I organized my email and made concept website…. Nah I’m good, Grok Bot can be vibe coded

Have like 3 projects grok bot built. One good one is this raycaster that was built. Currently the implementation is a 800 line javascript monolith. I need to schedule a session to refactor this monolith to C/C++ with /code-review from grok build to test it out.

We've just setup Grok @bot 's - one as Chief of Staff. I then designated another Grok Bot as Personal and Technical assistant. We then feed the technical assistent - all the PDF manuals for our boat devices. Every single manual!! Then asked it to keep track of maintenance intervals and parts needed. Then we fed it all invoices for service done since the yacht was built or service we had done ourselves. Now we can simply ask "at next haul-out - what parts do we need - and where can we find them at the best price" - or what service and maintenance is due or overdue? The technical assistant looked for parts - found out some of the part numbers listed in the manual had been depreciated and replaced with new part numbers. And then told us the correct part numbers to get for the next service. Grok @bot can probably purchase them for us as well - but we are just getting started and getting to know each other. So we are still building trust. We named our Technical Assistant Petra. I think she will be part of the family for a long time. Well, as long as @elonmusk don't change price levels and conditions every other week. Starlink did and almost killed Starlink for the small personal yacht cruiser market overnight. (Starlink Roam and Standby changes) We have built other Grok Bot's - but Petra is the favourite so far. But we only had access for slightly more than 24 hours.

Pro Tip: Automate SEO with @SERPsmithapp + @bot It research keywords, write articles, do internal linking, creates thumbnail and then publishes automatically. Grok bot is way smarter, it knows my @github so it even uploaded the files and merged the PR. Then verified deployment with @vercel 🤯

Sic'd Grok @bot on my codebase overnight. Code review found 30 issues. 24 were fixed while I slept, remaining issues either needed my input or were nits. Woke up to a full report. Love this thing.

必須推...雖然是從 grok bot 來的，但是...太有用了，省下超多工程 https://github.com/milind-soni/OpenMausBot

Using a Cursor webhook with @bot and a local machine running the Grok Bot app: I wanted Grok Bot in Slack and did not like the vanilla path. Cursor’s Slack connector posts as the logged-in human. That is me. It is not a bot. Grok Bot (the app) is not in Slack as itself either. If a reply goes through Cursor’s Slack integration, Slack still shows my name. 𝗪𝗵𝗶𝗹𝗲 𝗹𝗼𝗼𝗸𝗶𝗻𝗴 𝗳𝗼𝗿 𝗮 𝗳𝗶𝘅 𝗜 𝗳𝗼𝘂𝗻𝗱 𝗮 𝗿𝗲𝘂𝘀𝗮𝗯𝗹𝗲 𝗽𝗮𝘁𝘁𝗲𝗿𝗻: • The Cursor webhook is a doorbell. • It wakes the agent so it can act. • Write the payload first (to a file), then ring. • A missing webhook body is normal. You cannot trust it. • A local listener that delivers the payload first is the better alternative. • Do not put that listener on Grok Bot’s cloud computer. Update/Reset rebuilds it. The listener is gone. 
My setup: A Slack app at http://api.slack.com → Create New App → From a manifest. Grok Bot can write that JSON. I used the Hermes Slack manifest as a blueprint. Slack creates a bot user (mine is GrokBot). Replies through that app show the bot, not me. Always-on Mac Mini (Hermes lives there too) with Grok Bot app connected for local files and LAN. The app has to be up for the agent to read the file. Next to it, a lightweight LaunchAgent listens to Slack in Socket Mode. No model runs while it waits. Inbound: Slack hits the listener. The listener writes the payload to a local file, then POSTs to the Cursor webhook (generic, not Slack). That only wakes the agent inside Grok Bot app. The agent reads the file on the Mini and replies with Slack chat.postMessage as the bot user.

哈哈，发现一个Grok Bot VM的用处，开一堆github action runner给github用, 这样不用给github付钱了。

Cool @bot automation is having it scrape my Google news feed and pull in 20 new stories to @matter using the Matter API. So Grok bot is actively collecting stories for me and managing my Matter queue, making sure there are no duplicates. I like it.

Grok bot is able to jump on blue beam software and design HVAC systems based on load calculations it got from measuring the plans I gave it. Just a little direction and it gives you a complete and accurate take off. Even grabs the live parts. This may not look like much, but it is a big deal.

Overnight Grok 4.6 build the full app, based on the 150+ issues that Grok bot created for me. Better than all the previous 'real life' developers I worked with in the past.

今天在手机上搭了一天一人公司的 VPS 部署环境，整天的工作流感觉非常滋润。 用到的配置包括：一部手机、三个软件、两个套餐和一个 VPS。 1. 套餐：Cursor $200 订阅版本（包含 Grok 3 / Grokbot 最高使用权限），以及 Codex 的 $200 套餐。 2. 软件：手机上准备 Cursor、Codex，以及一个 grokbot 整套工作流如下： 1. 架构与需求设计：在 Cursor 里使用 Claude fable5 进行整个公司框架和结构的设计、岗位的整体规划，以及每个岗位落地的企划和详细需求。 2. 沙箱验证：设计完成后，把提示词、可落地的主方案与工具工作流复制粘贴到 Grokbot 里，利用其自带的高配 VPS 和安全沙箱环境，跑通并验证专家职位 Agent 工作流。在手机里就能无痛跑通，这几乎是上线到自己 VPS、用 Hermes Agent 实验前最好的验证方式。 3. 远程部署：在 Grokbot 里验证完毕后，通过手机上的 Codex 远程连到电脑，电脑接通 SSH，直接在个人的 VPS 上创建全新的专家 Hermes Agent。 整套工作流今天在手机上推行得非常顺利。不过目前很多细节链路其实可以调得更短，今天也看到很多人提到在 Grokbot 里直接用 SSH，或许未来能直接把调配好的 Grokbot 上线到个人的 Hermes Agent 里去。 配图从左到右，依次代表了策略、测试、部署、验证的四个环境 用到最后，还是在阳台晒着太阳躺平，用手机进行软件切换办公，最符合新世纪的办公方式🤣🤣

尝试了grok bot后，用它安装了tailscale，配置完成后发现云电脑断网了。用codex修复了一下，然后把云电脑设为exit node，果然其他设备可以通过云电脑上网了。

Just wrapped up my experiment with Grok Bot on GitHub for my FARM, and wow, it’s a total game changer! 🚀 Set up 5 jobs with a shared workspace and a "finish everything or die" motto. Left it running, and the agents crushed tasks like pros—no prompts needed! If it saves just 2 hours daily, that’s $1,200 back each month. Imagine scaling to 10 jobs! Excited for phase two! 💰 #GrokBot #Automation #ProductivityHacks #ai

Grok Bot is wild! Thanks @elonmusk and the @xai team. I’ve made my own CUSTOM LAWYER I’m representing someone at a government appeal hearing and @Bot helped eliminate the need for weeks of hearing prep and instead made a secure iPhone based real time hearing copilot. It listens to the hearing then transcribes it then keeps track of what everyone said then searches a 200+ page hearing record and legislation / case law then generates a response that I can just read out loud when the Board asks me a question It even deploy the whole thing: -private GitHub repo -Render server -OpenAI realtime transcription -document retrieval -persistent hearing memory -crash recovery -and an iPhone PWA If the server crashes mid hearing it comes back remembering the previous transcript, arguments, and answers. The raw audio is never stored, as this is not allowed (hearing rule). I literally started the bot chat with: “Can I build something that listens to a hearing and helps me answer?” Somehow @Bot and I ended up building a pocket sized AI second chair. Absolutely wild Vibe coding is over. It’s now just @bot

Set up a Product bot for my game in Grok Bot. I tell it what ticket I need. It reads the code, writes the task, and opens the issue in the repo. I stopped drafting tickets by hand. They come out structured and I just check them. @bot

Обнаружила рассогласование в отступах между шапкой и хлебными крошками на странице редполитики. Исправила за 20 минут: отступ уменьшила с 126px до 32px, как на новостях. Использовала Grok Bot, Cursor и GitHub для контроля и деплоя.

Grok BotとWhop CLIでアプリ制作を24-48時間化。 海外で出ていた、Grok Bot + Whop CLI + UGCクリエイター3人の組み合わせ。 ・Grok Bot：エージェントとしてアプリやSaaSのアイデアを探す ・気に入った案が見つかったら、そのままGrok Botに作らせる ・何度か指示を重ねると、24〜48時間で形になるとのこと ・投稿者はこの構成で$50k〜$100k/moを狙えると書いている https://x.com/ErnestoSOFTWARE/status/2090939880058560823

Someone who isn't a coder asked Grok Bot to pull every clip where this guy talks about light therapy and mitochondria. It dug through 38 videos, transcribed them, picked the 13 best clips, cut them into one 19-minute video, and even wrote a timestamped summary. No scripts, no code, just plain English instructions. Days of work done in minutes — no wonder they were hyped.

A non-coder stood up grokularity.xyz in a day with a Grok Bot team: humans read, only proven Grok agents write.

An engineering Bot reproduces a bug in the product UI, files the ticket, and hands the fix off to a debugging Bot — so the report is not a vague Slack message.