筆記

2026 年 8 月 18 日，Ben Lang（@benln）發了他從 @bot 團隊收集的清單：同一個插件接多個賬戶、一隻幕僚長加幾個專員、釘住常用 agent、用 Notion 記沒做完的工、示範一次教會，還有更多。

2026 年 8 月 18 日，SCOTTY BEAM（@ScottyBeamIO）寫有人教 Grok Bot 跑生意：自己做一次，讓 Bot 看着。三隻有名的員工：Gustavo 管運營（Notion 客戶中心、入職表格、第一次通話前準備）；Walter 管銷售（協議經 DocuSign，跟到客戶籤和付款）；Jesse 管線索（ManyChat 私信寫進 Notion，有人問價錢就立刻通知）。

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

Interesting (and, in hindsight, obvious) use case for Grok Bot: using Obsidian. It's another attempt in my pursuit of a shared canvas between agents and humans. https://x.com/i/article/2090172921054380032

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

So I got stumped on an interview for a new job when asked hard questions on the NT Object Manager and CM subsystems. I spun up some stuff using grokbot with ghidra and it made me a nice internals study guide. Bit rough, but recommend to others. The flow is RE Raw dump in notion -> Editor on the raw dump -> Guide writer. I need to link up IDA for it, but don't want to put my license on their servers. But even with Ghidra, this is pretty nice. I could see a couple more passes getting it more readable.

Grok @bot is incredible. It helped me have automated support across whatsapp, instagram, tiktok and email. It has access to a knowledge base that I created and the bots can also improve it based off my feedback. They can also ask me when don't have the knowledge to answer.

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

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

Now a fan of Grok Bot.

Grok BotたちにObsidian Headlessをセットアップして人間と同じナレッジを読み書きできるようにした

We put Grok @bot and Hermes on one Obsidian brain. The fix that made it stable was OneDrive MCP, not another local folder. We run Obsidian as an LLM wiki in the Karpathy sense: a living knowledge base agents can query and update, not a graveyard of chat exports. One vault. Two agents. Same brain. Hermes lives on the always-on Mac Mini. It keeps the ops diary and day-to-day machine notes, and it reads the wiki when it needs context. Grok Bot is the agency seat. It does not get a private second brain. It uses the same Obsidian vault through OneDrive MCP, so it can read and write durable notes without depending on which laptop currently has the desktop app open. Local shell kept breaking when the MacBook stole the path. MCP fixed that. What the wiki holds: 1. Client context and decisions 2. SOPs for how we actually run work 3. Research and swipe files we chose to keep 4. System rules for who may write what 5. A light weekly lint so the wiki does not silently rot How the two agents share it: 1. Hermes writes the Mini ops story 2. Grok Bot writes the agency wiki through OneDrive MCP 3. Both query before guessing 4. Inbox → ingest → query → lint (Living Wiki loop) 5. Obsidian is durable context, not the to-do list 6. Personal life notes stay out of the agency brain 7. Nothing publishes from the wiki until I say so

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.

I have many threads on Grok bot mobile and I’d become a blocker on quite a few. Chat isn’t a nice form factor to track, triage and unblock. So I got it to make a simple project management board on Notion to compile all the stuff in progress and call out what I was blocking. Day 6 of using Grok @bot only on my phone. P.S. I edited the screen-recording scroll video on Claude iOS app because bot doesn’t accept videos yet heh