Set Up and Use Five New Grok Bot Features

Claim a dedicated bot email, enable native X search and monitoring, receive tasks via @bot, hand off coding to Cursor cloud agents, and run a specialist bot team led by a primary bot

Who

Grok Bot subscribers (including via Cursor) or team-plan users who want AI agents to handle email verification, X research, coding tasks, and multi-agent coordination

You get

Configure a standalone bot inbox and X connector, create a direct task pipeline from X, execute code changes through Cursor cloud agents, and orchestrate specialist bots with a primary chief

You need

Cursor · GitHub · X · Slack · Notion

Steps

1. Claim a dedicated email address for your bot

   Open the Grok Bot desktop app and make sure it is updated to the version that supports email inboxes. Message your bot: "Is [your-desired-name]@mail.grokbot.com available?" If the name is available, tell the bot to claim it and approve the confirmation card that pops up. Only one address per account; all bots share it; the claim is permanent. On team plans, an admin must enable inboxes before anyone can claim one.

2. Enable native X search and monitoring

   Add the X connector in Grok Bot and authenticate with your personal X account. No X Developer API or prepaid credits are needed. Once connected, you can ask the bot to search, read, and monitor public posts. Start with a test: ask it to find mentions of your brand from the last 24 hours and label sentiment (praise, complaint, question, neutral). Note: this consumes Grok Bot usage, not X API credits.

3. Send tasks to your bot via @bot on X

   When you see a post you want your bot to act on, reply to or quote the post, tag @bot, and include an instruction (e.g., "remind me to read this tomorrow"). The task goes straight into your Grok Bot queue. Use cases: read later, save to a knowledge base, or read replies on your own posts. Note: tagging is unavailable in the EU, UK, and Australia, and some account types are not supported yet. Users on Cursor subscriptions currently get no response.

4. Hand off software tasks to Cursor cloud coding agents

   Ensure you have a Cursor subscription (the Grok Bot connection exists by default). Connect GitHub in Grok Bot so the bot can see your repos and pull requests. Set up the project and environment in Cursor, and review cloud-agent settings such as default models and automated code review. Then instruct Grok Bot with something like "spin up a cloud agent to do X." Optionally create one engineering bot per project and always route work through it. Set approval rules before anything runs. To conserve Grok Bot allowance, keep the bot as an orchestrator writing short briefs and handling approvals, while pushing heavy work to cloud agents (billed to Cursor usage).

5. Set a primary bot to coordinate a team of specialists

   In Grok Bot, designate one bot as primary; it gets a star icon and becomes more proactive across projects. Give each specialist bot one clear job with no overlaps. Provide a shared workspace per bot (e.g., a Notion database) so nothing lives only inside chat. Keep all outbound actions as drafts approved through the primary. Ask the primary for a usage-saving schedule and approve it before changes take effect.

No prompt needed — just follow the steps.