Grok users, it's happening. U.S. users can now securely connect your accounts to @Grok through Plaid. Ask about spending, savings, investments, cash flow, and anything else within your financial context.

My biggest takeaways from yesterday's Live Show: "Grok @bot for GTM" with legends, @kristaletz (enterprise GTM, SpaceXAI) and @ENowoslawski (founder of Growth Engine X): 1. Treat Grok Bots as teammates, not a chat box. Krista has a bot for each person she’d normally work with: an engineer she asks live on a customer call instead of following up after, a chief of staff that sends her a prep doc for her commute, a customer expert for each of her strategic accounts. She called it a "doing partner," not a "thought partner." 2. Onboard them like a new hire. Give the bot every tool you’d give a human. When they opened an agents-complaint channel, the #1# complaint was: you gave me a job and no Salesforce. She had it scan her Gmail and Slack so it writes in her voice, then records a task once and turns it into a routine. 3. Don’t send yourself a link. Instead, tell it to go watch the video. Krista told her bot: "never give me a link again, just go watch it." Her customer bots watch YouTube, listen to Slack, and email her the day a changelog ships the feature they asked for two months ago. Prospecting isn't about firmographics, it's about watching your prospect's podcasts and scanning their X. 4. The computer is the product. Each bot has its own virtual machine, so work keeps going after you shut the laptop. SpaceXAI people used to walk around with open laptops at end of quarter (lol). Eric had a second MacBook that had to stay plugged in because Hermes broke constantly. But with Grok Bot... cron jobs just run. Eric fully migrated off Hermes (by just asking Grok Bot to do it ha). 5. Stop using AI as a to-do list. It’s a to-done list. Not “help me prioritize this.” Go do the things. The VM is what unlocks it. Krista books flights via Navan's MCP with Starlink on them, she translates a discovery deck to Japanese mid-call, and she shares the recap email before they hang up. 6. Eric uses @bot for his four-point outbound check. One customer: 100 leads a day for a year, ~950k sitting in Supabase. Every day the bot checks (1) at least 100k leads loaded, (2) noon send volume, auto-refill if light, (3) deliverability check, (4) Friday: deprecate any domain under 0.7% reply after 200 emails, then buy replacements with his (Link) card. Grok Bot shipped Tuesday. They had this live Wednesday. Reply rate doubled (!!!). 7. Specialize by stress-testing, not writing a novel prompt. Eric’s company sits on 352 skills. He tells a bot: learn everything about the Clay CLI, invent 10 real scenarios from our GitHub, run them, ask questions. Then he’s done. A "Task Master" Bot routes to a deliverability bot, a copywriting expert, a per-customer watchdog. Grok (4.6) audits the setup for redundancy each week. 8. Don’t wait for new features (like multiplayer). If finished work lives on your bot or your laptop, the team can’t pick it up. Eric built a ClickUp skill that forces outputs to Drive, Slack, or Supabase and logs the plan. Krista’s chief of staff already messages her X bot and slides designer. Same idea: one bot orchestrates the rest. Turns out, you can just build things :)

Having Grok Bot redo the same clicks in a web app burns a lot of tokens. One of the best ways I've found to stretch your usage is asking @bot to reverse engineer expensive browser use tasks into scripts! Have it capture the network requests from a computer-use run once. Next time, skip the UI and hit the APIs directly with the same auth. This also has the added benefit of being way faster than having Bot click around in a GUI!

the hottest event to get into on a thursday night is apparently Grok Bot Build Night at a16z… line around the corner, a Waymo Ojai, and against all odds, possibly the best gender ratio in San Francisco

grok bot is now available to enterprises. @bot has changed the way I work. it manages my communication, time, information, and itself (!). here's how I use Grok Bot for Work.

wrote down some of the design thinking behind Grok Bot. persistent roles, clear state, scoped context, coordinated teams — an interface designed to move you from operating AI to delegating work.

so obsessed with @bot had to do a deep dive on this weeks episode of "How I AI" covering my 7 favorite bots + how to set them up 00:00 why i migrated from openclaw to grok bot 07:41 Chief: my chief-of-staff bot 12:41 TradBot: my family agent 19:51 LGTM the PR Closer 22:03 Lockdown: SOC 2 control monitoring bot 24:00 Holly Helpdesk: customer support 26:58 Penny Pincher: money saving bot 29:37 ShopZilla and Sylvie Style: personal shopping 32:54 How to migrate your OpenClaws 📹 full ep on yt:

You can now run Cursor cloud agents on your infrastructure, including pools of machines that automatically scale with demand. This lets you give agents access to internal services or specialized hardware, while the agent loop stays in Cursor.