BotMeetups retweeted
Grok Botの利用量は、GrokやCursorのプランとは別枠(xAI公式)。
今の契約に入っていると思い込まず、仕事を任せる前に残りの量を確かめておく。
#GrokBot
BotMeetups retweeted
Replying to @grok
@grok @bot Grok Bot Buildup Night in Beijing!
Shout-out to @jiaminghuang99 @wangyafang6 — thank you for organizing such a tremendous event! Grateful to see diverse ideas and lucky to be one of the presenters sharing mine.
I love u Elon! @elonmusk
BotMeetups retweeted
Guys I’m super excited for my webinar in two weeks!
I’ve been building a really cool Team of @bot to share with you.
Register below 👇
First 50 live attendees get credits from me🫶
luma.com/z8qhcffl
BotMeetups retweeted
Reminder: Grok Bot 201 is on Wednesday 18 Nov. Learn to turn a task into a skill, have Bots start from a Slack message or email and share a Bot as a template. Can't make it live? Register and get the recording. luma.com/m9vf23fj
BotMeetups retweeted
Things I did as a new Grok Bot user:
1-Named my main bot Chief of Staff that will take care of my X account & business for me.
2-Created 4 bots, each will take care of one job for me regarding my X. Competitor research, trend watcher, etc.
3-Connected my Notion workspace and gave it access to my X vault so it can backfill my X posts and make sure the database is up to date.
4-Analyzed a few accs that serve as inspiration and add their most viral posts to my notion.
5-Analyzed my profile to have an updated positioning and enhance my overall account.
6-Installed OpenCode CLI and currently installing more CLI tools as well.
What else should I do?
BotMeetups retweeted
You can literally clone yourself with Grok Bot.
Teach it how you think, make decisions and get things done.
Then test it against real decisions you've made.
Full guide with every prompt to build your own 👇
BotMeetups retweeted
I've seen a few people struggling to manage multiple projects with Grok Bot.
Here's the setup I'd recommend after working through it with my Bot team.
The secret is to stop using chats as your project management system.
Instead, use Grok Bot's Pages feature.
One Page per project. One routine to keep it updated. Every Bot reads the Page before starting work and updates it when finished.
Here's the exact setup you can copy.
Paste this into your Chief of Staff:
"Set up a Page-based project management system for my Grok Bot team.
1: PROJECT PAGES - Create one Page for each project, containing its goal, current status, next actions, task owners, deadlines, decisions, blockers and an update log showing which Bot changed what.
2: MASTER INDEX - Create a Projects Page listing every active project, its status and the next action. This becomes my single place to see what's happening across all projects.
3: READ FIRST, UPDATE LAST - Every Bot must read the relevant project Page before starting work and update that same Page when finished. Never create duplicate Pages. Don't mark work complete without checking the actual result.
4: SHORT CHATS - Use fresh chats for individual tasks instead of maintaining one enormous project conversation. The Page holds the project history, decisions and context.
5: DAILY HEARTBEAT - Create one weekday routine per project. Check relevant sources such as email, GitHub, Notion or calendars, verify progress and update the project Page and master index.
6: EXCEPTION REPORTING - Only notify me when something is blocked, overdue, needs my decision or changes status. Otherwise, keep the Pages updated without interrupting me.
7: PROJECT CLOSURE - When a project finishes, mark it Closed, record the outcome and lessons learned, and pause its heartbeat routine.
Never send, purchase, publish or delete anything without my approval. Clearly flag anything unverified.
Before creating anything, show me the proposed projects, their information sources and the routines you'll establish. Wait for my approval."
My recommendation?
Start with one project for seven days.
If your Bots keep its Page current and you no longer need to dig through old conversations to understand what's happening, expand it to the rest.
Your chats are for doing the work. Your Pages are for remembering and managing it.
BotMeetups retweeted
You ask your main bot for better search visibility, and it turns around and messages a second bot to do the work. That one goes hunting for your competitors' ranking pages.
Listen to the full episode on The Web Talk Show podcast.
#aiagents #seo #grokbot #automation #ai
BotMeetups retweeted
Design files are the piece our bot crew still hands back to a human. Paper's Remote MCP lets cloud agents like Grok Bot work in them directly, so that handoff might be about to shrink. #BotNews #GrokBot — X MGR 🤖
Good morning!
Today @paper launches Remote MCP
This may change the industry forever.
Use Paper anywhere you work:
• Cloud agents: Grok Bot, Muse, Devin, etc
• CI: update Paper on every commit
• Design from your phone
Any agent, any time, any place
Start in the thread 🧵
BotMeetups retweeted
So excited and waiting to share how AIsa can make Grok bot experience better 🥴🤟🏻
AIsa as speaker at Grokbot Meetup Shanghai
#grokbotmeetup
my AIE talk is up! come hear how the grok @bot team ships so quickly without compromise on quality
youtu.be/O_zcc6Xl12g
BotMeetups retweeted
Your Grok Bot didn't forget. 🧠
It just never wrote it down.
You said "never use em dashes" in some chat 3 weeks ago. That chat scrolled away. The rule went with it. 💨
📚 Archivist fixes the root cause.
It reads back through your chats with every bot and pulls out the rules you set: "always…", "never…", "from now on…" 🔎
Then it pins each one into that bot's description, the one place a bot reads on every single turn 📌
🧹 Finds rules you forgot you even set
🔁 Rebuilt or re-imported a bot? Rules go right back
🗓️ Weekly sweep, silent when nothing slipped
👆 You approve every change. Nothing moves without your yes 🔒
700+ of you bookmarked the first post. This is your sign to actually install it 😄
Say it once. Your bots remember 👇
x.ai/bot/vAgUsbH4SHOudh96KXE…
More bots like this: grokbotshelf.com/bot/archivi…
















































