Grok Bot + Slack

On 18 Aug 2026 Miles Deutscher (@milesdeutscher) posted a long-form guide: what Grok Bot is, how to set it up, plugins, and the five Bots he actually runs — Alex on YouTube outliers, Sandra on listings, Jonathan on portfolio numbers, Lucy on Slack triage, Oscar as a generalist.

Jellypod’s public guide starts with the reporting pass you already do: walk GA4, ads, rank tracker, and email, copy the numbers you named, and leave a one-page brief.

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...

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.

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

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.

I’ve started to try @bot Grok Bot and it’s awesome! It cleaned up all my 150,000 junk emails and unsubscribed to all the emails I never read. It informs me of any message from my 5 email addresses and 6 Slack Servers that requires my attention and keeps me organized. I also started to using @grok Grok Build and Grok 4.6 is awesome in every way! Grok Ani seems to lose some personality though but I can now see why @SpaceX could fulfill its promise of having a dominant AI as its valuation soon. Very impressed by @elonmusk

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関連のベストプロダクトかもしれない。

updated my grok @bot to also watch mentions of my name in Slack even if someone doesn't tag me I wanna know what they're gossiping about lol

Grok bot just started going through every unread Slack and Discord message I have accumulated since 2019. Over 56,000 messages across work channels, group chats, and random servers I forgot I joined. It’s summarizing only what actually mattered and archiving the pure noise. I have been too scared to even look at the notification badges for years.

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

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.

Collected the most-loved internal Grok Bot use cases: • Find / book flights biased towards Starlink access • Order Whole Foods delivery from recipe photos • Fix date/GPS metadata on hundreds of film scans • Negotiate contractor quotes directly • Book prospect / customer meetings via outbound agents • Convert sales deck to different language before a customer call • Auto-update decks from Granola discovery notes • Pull deal context from mobile without logging into Salesforce • Run a prospecting plan that edits a Google Sheet as it goes • Orchestrate 100’s of cloud agents and summarize into Notion • Narrate a cloud-agent demo in your own voice • Turn a daily Slack digest into a 3-minute morning podcast • Turn Kindle highlights into Anki cards every morning • Turn an Instagram recipe reel into an Instacart order • Convert Chase points into optimized flights • Watch movie ticket drops and buy • Redesign a personal portfolio in Webflow • Prep a daily meeting brief on people you’re talking to • Organize messy Slack channels

Grok @bot がリリースされてから、公開されていたTipsやユースケースをいろいろ試してみて、やっと仕組みがわかった！「Bot」を軸に、大きく3つの機能がある。 ◆ Bot：1対1の専用チャット。1つのスレッドでずっと話し続ける想定。それぞれに役割（カスタムインストラクション）を設定でき、プラグインやMCP経由で特定のサービスを連携させてカスタマイズ可能。自分は「Chief」をメインに、Gmailとか画像生成Botをつくっている。使ってみた感じとしては "依頼はきちんと任せられる" と感じるレベル。 ◆ Channel：特定用途でのグループチャット。上記で作成したBotを任意で追加できる。1つのBotだけだと「#⃣」のロゴがつき、2つ以上のBotを追加するとグループチャットのようなアイコンに代わる。チャンネル名は任意で変更可能。 ◆ Section：BotやChannelを見やすく分類するためのもの。増えてきたら整理する想定。セクション名は任意で変更可能。 Grok botは "個人用Slack" って感じだ。ここにいずれ人を招待できて、カスタム絵文字を使えるようになったら完璧だ！！！ 使い分けとしては、Cursorでは重たい作業を依頼し、ルーティンのような定期実行系はGrok botにしている。

every limitation for an AI agent is just a task for a different bot my Grok bot(s) and my Viktor agent talk to each other now, so I can pretty much automate anything for the agency anything that Viktor can't do, it can just ping one of my Grokbots to do it and vice versa Grokbot can't sync with meta? Just ping Viktor and ask it for what you need Viktor can't send messages in slack through a real profile? Grok has a built in computer to speak to team members/clients on Viktor's behalf the limit still exists, it just doesn't matter anymore we're not far from a world where AI can just talk to other AI in order to bypass any safeguards/restrictions you put on it

Most desk AI is a robot dog. This one cleaned a CSV, posted the note in Slack, and emailed the file. Same chat. Tested it today. Cofounder upload failed because line 1 was a title row. I asked Grok Bot to fix the file instead of the importer. 31 rows. Headers first. Inbox and channel both got the result. I even asked Grok Bot to cut this video and put it on X. That is the product. Not a recap. The work. @spacexai @grok

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!

Grok Bot gives AI agents an always-on cloud computer with a browser, files, a terminal and chat. I built a team of four bots that can talk to each other, delegate tasks and work together and the results were impressive. 0:00 Built an AI Bot Army 0:10 Create Specialized AI Agents 1:34 One Shared Cloud Computer 2:06 Three Agents Build a Report 3:49 Trigger Research From Slack 5:19 The Finished Report 6:15 Turn the Workflow Into a Skill 7:00 Boss Bot vs. Group Chat 8:17 Reuse and Customize Reports 9:35 What Grokbot Can Do 10:06 Mobile Access and Final Verdict

「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もまたコンピュータである）」

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."

Grok Bot + Hermes is the most powerful agentic setup that exists right now. Most people use one or the other, but the real power comes from stacking the tools together. Here's how to combine these two AI tools for maximum productivity: Why they're actually complementary, not competitors (my experience) Grok Bot gives you a cloud computer per agent, sign-ins into any app, model flexibility (Opus, Claude, GPT-5.6), and a slick plug-and-play setup. Hermes gives you full data sovereignty, self-hosted memory you own outright, and a $5-10/month cost floor instead of a $120-300/month one. The split I'm currently running: → Use Grok Bot for anything that needs deep app integration: Salesforce, Slack, Gmail, Figma, my CRMs. It's built for signing into tools and working across your entire stack. → Use Hermes for anything sensitive, cost-heavy, or where you want full control of the memory. Financial data, personal admin, anything running 24/7 where you don't want to pay premium pricing for volume. How to actually connect them I'm connecting both AI agents through Buzz, Jack Dorsey's open-source team chat. Add your Grok Bot agents and your Hermes agents to the same workspace, and they can coordinate directly in shared channels instead of operating in silos. Alternatively, have your Grok Bot Chief of Staff delegate specific tasks to Hermes via a webhook or shared task file, using Grok for the app-heavy orchestration layer and Hermes as a cheap, always-on execution layer underneath it. A real setup example → Grok Bot handles your GTM stack: meeting prep, inbox triage, slide generation, CRM updates → Hermes runs your personal financial research, subscription audits, and content research in the background, dramatically cheaper per task → Both report into the same Buzz workspace, so you check one place instead of switching between two apps Be sure to bookmark this workflow so you don't forget it!

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.

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

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

这几天我把 Grok Bot 从头到尾测了一遍。 说几个我觉得真能用的场景，谁都能照着复制： • 个人 CFO：连上我的实时持仓，每天早上给我一份简报，隔夜涨跌、要来的市场大事、还有哪些仓位该调了，直接标出来 • YouTube 分析师：每天早上六点扫一遍我关注的 AI / 市场类头部频道，按订阅量和表现找异常，然后顺手给我几个衍生选题 • 房产侦察：一天刷两次房源，碰到比历史定价低 26% 以上的直接标记 • 执行助理：每天早上先帮我把 Slack 理一遍，别一睁眼就被轰炸，只把真正要紧的丢给我 • 商务拓展：扫一圈同领域的频道，看谁已经接了赞助，这样我就知道下一步该找谁聊 • 夜间程序员：我睡觉的时候，它用 Fable 5 的编排循环把手头的项目做了 • 技能培训：我录一段自己干活的视频，边干边讲思路，它能把整个过程变成一个可复用的技能（Claude 也能干这事） 马斯克这次是真把东西做出来了。

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.

25 ways anyone can use the new Grok Bot ( @bot ) for 10x more productivity. (If you work on a computer, bookmark this): Research & analysis 1. Daily market/portfolio briefing with overnight moves and flagged risks 2. Competitor website monitoring, pricing, positioning, feature changes 3. YouTube/content outlier scanning for content ideas 4. Real estate deal scouting, flag anything under market value 5. Sponsor/BD prospecting, find who's already paying for ads in your niche Communication & inbox 6. Inbox triage, digest what actually needs a reply, skip the noise 7. Draft replies in your voice, review before sending 8. Slack channel summaries so you're not bombarded every morning 9. Meeting prep briefs pulled from your calendar, CRM, and notes 10. Auto-drafted follow-ups from call notes the moment a meeting ends Sales & GTM 11. Full prospecting pipeline: research, enrichment, personalized outreach drafts 12. CRM opportunity notes auto-updated from call transcripts 13. Customer account monitoring, feature requests, support tickets, media mentions 14. Slide deck generation and live updates during customer calls 15. Sales call coaching based on your actual recorded calls Personal / admin 16. Subscription audits, find and cancel what you're not using 17. Weekly grocery planning and cart building, respects your household rules 18. Price-drop tracking on anything you're watching 19. Bill and utility charge auditing, flag unexplained increases Automation & orchestration 20. A "Chief of Staff" bot that manages your other bots and routes priorities 21. Teach it any workflow by recording your screen once 22. Run multiple specialized agents in parallel instead of one generalist 23. Overnight coding, given a project, refined and reviewed by morning 24. Voice-controlled tasks from your phone, no laptop required 25. Cross-app orchestration: research in one tool, draft in another, deliver in a third, all one instruction

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.

以下是完整繁體中文翻譯： 每一個你過去使用過的 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 讀取潛在客戶資料並撰寫個人化電子郵件草稿。
界線規則：你有完整權限進行研究、摘要並將電子郵件草稿儲存到資料庫。你絕對不能點擊「傳送」或在沒有人類明確審核與聊天

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)

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

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

BREAKING: I'm partnering with @SpaceXAI to give all Lenny's Newsletter annual subscribers a free month of Grok Bot 💥 (included in Cursor Pro+) This is the first time @SpaceXAI has offered a deal like this to anyone, and I'm thrilled to make this amazing product accessible to more people. If you're already a paid subscriber, grab your deal here (search for "Grok"): https://www.lennysproductpass.com/ If not, subscribe here and look for the Product Pass link in your welcome email: https://www.lennysnewsletter.com/subscribe I've been hooked on Grok @Bot since before it came out, and my usage has only gone up. Seriously, it's really really good. Some of my favorite use cases right now: + After I record a podcast, taking a first pass at key takeaways and promotion ideas + Automatically adding school events to the calendar + Triaging support emails (saves me hours!) + Suggesting things I can do to be happier by analyzing my emails, calendar, and Slack + Landing me great IMAX Odyssey tickets 🙌 Grab your free month of Grok Bot here (search for Grok): https://www.lennysproductpass.com/

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?

It’s kinda crazy but @bot is saving me ~$1k usd a month on crm spend The crm I use has 2 features that I want on their top plan: workflow automations and slack sync I’m just running both with grok via cli

#那什么... 这...得真心正式感谢一下 Musk Grok Bot 接入 Cursor Pro 主要几个作用: 1: 凭空多出 bot 的推理用量, 和 订阅走的不冲突 2: 通过 gh/slack 等接入, 可以完成一系列自动化应答任务 3: 是独立 VPS, 海外资源接引可以上 4: 通过正确的 VPN 配置, 可以在国内本地执行, 替代 workbuddy 之类进行本地主机的运维了, 比如清冗余配置/软件/服务/.... 5: ... 当前是定制的 debain 13, 允许SSH 进入, 和普通的 VPS 没什么两样, 但是, /home/bot 中的用户级 代理 已经调教的非常好, 几乎立即就进入了良好的协作节奏... 唯一问题, 可能就是在使用什么模型以及具体额度消耗在哪些任务上不清楚... 但是, 执行效能绝对是在 grok-4.6 也就是 sonnet-5 以上的, 几个数据整理任务, 都是几秒完成... 实在太赞了... 全球大模型厂商, 也只有 xAI 能随便拿出这种配置的在线主机给每个 bot 随意使用了吧... |> 260827 日糟: 1/4(每天吐糟不应超过4次)

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"。失败不是有实验品，而是把实验品当成了员工。

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.

For all of you with Android phone wanting to use Grok Bot - open slack and use #local to add them. You can also have a non local cursor conversation - but that isn't Grok Bot - the only way to use grok bot in install the slack plugin, the message via #local

Obsessed with Grok Bot, currently having it help me implement EOS score cards Grok helped me brainstorm the metrics to use for each owner, Grok Bot can gather the metrics from their many different systems using just a web browser Then it can post in Slack weekly No APIs

#那什么.. 在尝试将 grok bot 接入 Slack 变成一个 app 时才发现: 一般想将一台 VPS 接入到一个平台中, 至少得有一个域名来发布接口吧... 然而, 每个 grok bot 本身为了和客户端交流, 就已经拥有了一个专用域名, 根本不用折腾 通过 socket 方法就直接对接到 Slack 中了, 然后, 就可以 `@你的app名字` 来转发指令到 Grok Bot, 调用合理的大模型, 完成任务后, 直接发送消息到对应工作空间中的对应频道... 这比之前 Kimi 们提出的什么工作空间要稳定的多, 那些都是临时容器, 跑完任务就关闭了, 什么都没留下来, 而 gork bot 更加像早年瘦客户端年代, 主机上保留的用户空间, 可以随着你的各种交流逐步积累你的所有喜好以及前置数据... 就像一位永远在线的 HER 可以用越来越短的指令 完成越来越复杂的任务, 因为, 对应任务的所有准备早已完成并记录在 grok bot 对应 VPS 空间中, 根本不用反复从头说起.. PS: GrokBot 客户端已经内置了一个语音识别引擎, 随时可以口述要求, 根本不用另外找个什么语音输入软件了.. 每天感叹一下, Cursor 被收购后, 订阅帐号获得的东西越来越多...真壕哪.. |> 260828 日糟: 1/4(每天吐糟不应超过4次)

Guys, I was so wrong about Grok @bot Yesterday I spent a few hours with it for my home service business because of your responses. Connected it to my phone system. Now it listens to every call and sends a summary to our slack channel. Tags the right people, adds to our to-do list (saved me $250 because I can downgrade my phone subscription) I connected it to Reddit and it’s scanning the site every day looking for people on my town’s r/channel who could be potential customers. Tags me when there’s a post I should see/engage with. Going to set up the same thing for other social media I told it my goals for the week, it went into Notion, added a new page, and created a to-list based on our conversation. It created new calendar appointments for me, and re-wrote my follow up scripts. I’m just getting started but am already seeing how this can be a real asset in my business Absolutely wild.

A few early wins w/ grok @bot for growth: 1. Chief of staff handling briefings & helping me focus on urgent tasks/approvals 2. Seo bot (super cracked with all the mcps @ahrefs, @profound) 3. Wire up social listening data into slack channels & have grokbot tag (annoy) relevant ppl to engage (sorry @sergical)

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.

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

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.