Pinned Tweet
Your CRM remembers the client. Does it tell you what to do next?
Our core sales rebuild took ~7 hours. Try one client: propose, approve, read back.
@grok @bot @kristaletz @iamrita98 @matt_silberman
I’ve noticed a really big improvement so far. It feels almost like Claude Code Max 20x now.
I’m at 12% today (on the new Ultra plan), and with the same work I’d have been around 50% just yesterday 😬😏
And I think it’ll get even better as the harness improves 🔥🤟
Great work @grok @bot and @cursor_ai Team 🙌🙌
Is your AI bringing you a proposal to review, or another task to finish?
While we were working together, my Primary Bot in Grok Bot gathered the missing material for our product bot, which prepared a proposal. I rejected the price, and it revised the proposal. The decision stayed with me.
🔎 Try one stalled job: define what the bot can gather and prepare before asking you, and where it must stop.
I want to open the chat and judge the work, without rebuilding it first. I've shared the recovery, including my mistakes and the limits, in the Article below.
@grok @bot

ALT Conceptual 3D illustration of two smiling robots walking through a warmly lit studio. A dark bronze robot in a navy coat carries a folder toward the viewer, while an ivory robot follows with another sheet. A blue illuminated glass panel reads "CAN YOUR BOT DO THE LEGWORK?" The verified Grok Bot icon and the labels "PRIMARY BOT" and "PROACTIVITY" appear above. These are illustrative characters, not an actual software interface.
If you still have to supply every next step, how much work has your AI bot really taken off your hands?
I wanted to open the chat and find a brief or a prepared proposal, with the decision left to me. Grok Bot's Primary Bot had started doing that...
Today I turn 48, and my wife and I celebrate 15 years of marriage. Two reasons to thank God, on the very same day. ❤️
Fifteen years ago, the Lord gave us a gift that we are still learning to cherish, through every difficulty and uphill stretch.
When you're in the middle of that effort, it can be hard to see beyond it. I want to remember what we are caring for, and how much there is to be grateful for along the way.
Our daughters, once so little and now growing up, bring out the best in both of us every day. What a gift it is to be their parents, together.
And to friends who hope to marry one day: there is so much worth looking forward to. Fifteen years in, I am grateful we said yes, and full of hope for the life still ahead of us.
Thank You, Lord, for my wife, for our daughters, and for this life so full of meaning.
Today, once again, I know I am loved by You. That has changed my whole life.
Feed your Chief of Staff with this goodies and they will change a “couple of things” for the better 🔥 @grok @bot
Pro tip: Tell your main @bot to go through the new guides and recommend best practices for your Bots
x.ai/bot/guides
Before you add another AI bot, do you know who does what and who needs your OK?
⠀
I matched my 26 Grok Bots to Tolkien characters. Here’s the roster, why each name fits the job, and how I work around the usage limit. ↓
Imagine an AI video that's nearly right.
Shorten the opening. Check whether the moment you chose to keep survives, and what the revision costs.
That's a test I want to try in Manus 2.0. My first impressions below.
How many times can you revise an AI project before the budget stops you?
After a private Manus 2.0 presentation, I'm exploring Cue and planning a video revision test.
Thank you, @ManusAI and @CueAgents.
My first impressions ↓
How many times can you revise an AI project before the budget stops you?
After a private Manus 2.0 presentation, I'm exploring Cue and planning a video revision test.
Thank you, @ManusAI and @CueAgents.
My first impressions ↓
What if AI’s future looks more like a team?
Claude for one job.
Codex for another.
Grok for another.
@OpenBot_ is exploring how to keep their roles and context together.
I wrote down 5 questions before I’d trust that team with real operations ⬇️
xitter.cf/ThomasColasanti/status…
🤖 Made with AI
What happens when Claude, Codex and Grok begin working as one team?
@OpenBot_ made that possibility feel real. These are the five questions I would ask before trusting a multi-agent workspace with real operations. 👇
What happens when Claude, Codex and Grok begin working as one team?
@OpenBot_ made that possibility feel real. These are the five questions I would ask before trusting a multi-agent workspace with real operations. 👇
Crystal clear!
Are Grok, Grok Bot, Grok Build and Cursor eventually becoming ONE app under ONE subscription?
Maybe.
The walls are already starting to blur.
But TODAY, there is a dead-simple way to know which one to open:
ASK → Grok
DELEGATE → Grok Bot
BUILD → Grok Build
CODE → Cursor
Grok is where you go for answers, research, writing and normal assistant work.
Grok Bot is where you hand off real work to persistent agents that can use tools and keep going.
Grok Build is where the outcome is software: an app, site, game or project.
Cursor is where you actively develop: repos, code, agents, models, reviews.
These are NOT hard walls.
Grok can build.
Cursor can run agents.
Grok Build already lives inside Grok.
Grok Bot access already crosses Cursor and SuperGrok subscriptions.
The products are starting to overlap more and more.
Until the stack gets simpler, remember FOUR verbs:
ASK.
DELEGATE.
BUILD.
CODE.
If these eventually collapse into one app, would you want that?
Or do you prefer separate tools for separate jobs?
Thomas "Doc" Colasanti retweeted
Do not expect anyone to be happy for your success unless they are already happy with their own.
Before the shutter or the prompt, one question matters: what deserves your attention?
Photography is part of my work and one of my great passions, so I was fascinated by a 2014 museum study by Linda A. Henkel.
She found that people remembered fewer visual details of objects they had photographed whole than of objects they had only observed.
But when they photographed a particular part, zooming in, their memory for the object's details was comparable to observing it. Memory for the object's location still suffered. These were directed tasks on a museum tour, not a verdict on every photograph we take.
What interests me is the moment before the picture. When we frame a photograph, we choose through the lens. When we generate an image with AI, we choose through the prompt. The tools differ, but the human task is still to decide which detail, light or mood matters.
📷 The next time you reach for your camera or open an image generator, pause long enough to name what caught your eye. Then make the image around that.
I would try it for the pleasure of looking more closely, without expecting every picture to improve my memory.
What did you notice before you made your last image?
Research: digitalcommons.fairfield.edu…
Beautiful update 😍 I tried it this morning on a real setup. Here’s the short version.
Talking to a personal assistant like this is one of the best parts of working with these tools. I first found that kind of back-and-forth on other models, and it already felt special. Using it inside Grok Bot is different. The conversation sits on top of a teammate that actually runs the work.
This morning I picked up a bot I needed to set up properly. It manages a routine I use all the time, and it needed a lot of custom work. Instead of writing a long, heavy prompt, we just talked.
It asked me questions for about fifteen minutes. It configured the routine the way I actually use it, then synced with the chief of staff right away.
It also plugged into every tool I needed. Some were already set up inside Grok Bot. The ones that were not, we installed live, in the same conversation.
Really well done, Grok Bot team. Keep going. This project is picking up real speed. @grok @bot @lingxi
You have done a great job @poteto 🔥🔥Thank you!!!






















