I built Grok Army, a learning board for Grok Bot. Pick a workflow, move it from To Do to Doing to Done, and mark it Useful, Needs Work or Not For Me. Progress stays in your browser.
grok-army.grok.me
Feedback welcome. Not affiliated with or endorsed by xAI.
small updates in pstack v0.15.46
• lots of pruning, skills are now much shorter
• gemini 4 neon is added as a panel reviewer
it's autoupdated for grok bot / cursor users! if you want to change any of the model routing, just run /setup-pstack again
x.ai/bot/plugin/9717366
Matthew Sutherland retweeted
Make phone calls, right in @bot
0:16 How it works
0:58 Limits
1:40 Calling a business
2:49 Phone calls as a tool
3:17 Handing a call off to you
3:42 Confirming who it calls
5:18 Live transcript
5:46 What I'd use it for
Phone Calls in Grok Bot
Phone Calls in Grok Bot
I think a lot of people aren't using Grok Bot to its full potential, because knowing how to automate things is actually quite a difficult skill to learn. I wrote this post to break down how I approach automating anything with Grok Bot!
I built this with Grok — try it out: grok-bot-life-memory-ledger.…
Grok Bot Memory Ledger Strategy, Feedback welcome!
1
1
21
Matthew Sutherland retweeted
I was on ABC News yesterday morning to talk about the bank outages, after Fox & Friends on Friday. A busy week of national TV.
JPMorgan Chase hit a software bug that left some customers unable to deposit checks, see their balances, use an ATM, or send an online payment. That rippled out to Wells Fargo, U.S. Bank, and Bank of America.
The line I wanted to land: it has a ripple effect across the other banks, because a lot of other banks do transactions with Chase.
Large providers will have bad days. The question for any business is how you keep operating when one of them does.
If you run a company, it's worth asking your team how you'd reach staff and customers if your bank or your main software went down tomorrow.
humanology.ai
Replying to @parkersmith
I run a team of Grok Bots for my business. An orchestrator hands work to specialists for my inbox, calendar, social drafts, a class desk for students, LinkedIn, and a red team bot that QCs drafts. Nothing goes out without my yes.
I also teach it in my AI for Life community.
1
23
Matthew Sutherland retweeted
What's new in Grok Bot 1.0 🚀
00:45 Team Bot improvements
01:47 Bots join your meetings
03:26 Bots take initiative
04:10 Bots learn and improve
05:19 Bots are smarter and faster
Lots of easter eggs in this one for y'all!
Grok Bot 1.0 - What's new in Grok Bot - Nov 16, 2026
Grok Bot 1.0 - What's new in Grok Bot - Nov 16, 2026
Matthew Sutherland retweeted
At @spacexai, Lauren Tan (@poteto) and Roman Ugarte (@romanugarte_) are on the core team that took Grok Bot from first line of code to launch in seven weeks.
It lets you spin up AI teammates with their own identities and logins, and they just keep working in the background. Their marketing team gave a bot its own ad budget. Lauren built an entire feature with her bot in one Slack thread without ever opening Cursor.
They joined us on the @LightconePod to talk about what it’s actually like working next to bots every day, and how the hard part is shifting from doing the work to figuring out what to do and why.
03:36 — Giving Bots Real Jobs
06:49 — One Bot or a Team of Specialists
10:39 — Sharing Bots Across the Company
14:46 — Identity and Permissions for AI Coworkers
18:37 — Bot-to-Bot Collaboration and Trust
22:35 — The Workflow Behind 4,000 PRs a Month
26:00 — Teaching Agents to Write Code You Trust
29:01 — Building a Personal Software Factory
33:44 — The Future of AI Coworkers
36:47 — Rethinking the AI-Native Company
40:13 — Teaching Agents to Check Their Own Work
43:56 — How Much Code Review Is Enough?
47:33 — Codebase Guardrails That Save Tokens
52:20 — When Product Judgment Becomes the Bottleneck
56:29 — From Finance to AI Engineering
Matthew Sutherland retweeted
I was on Fox & Friends this morning to talk about the Microsoft outage.
The point I wanted to land: a lot of companies found out their Plan B was also Microsoft.
Email went down, so people turned to Teams. If you run on Microsoft, Teams went down too. Then they called IT, and IT couldn't connect either.
Microsoft says there's no sign of an attack. That should worry leaders more. Nobody had to break in for a normal workday to stop.
Every big provider has outages, and this is Microsoft's third this year. What decides the damage is whether you have a backup that runs somewhere else, and whether your people know what to do next.
Two questions worth answering today:
How do we reach our staff and our top customers if our main provider is down?
Who makes the call to switch?
If nobody can answer in ten seconds, that's the gap. And ad-hoc AI roll-outs will make this more complex.
Full segment: youtube.com/watch?v=HDA0zrU9…





