Skip to content
View original post on X: SCOTTY BEAM· 40/100AI score40/100

Grok Bot adds email, coordination, and cheaper plans from $20/month

AISummary

X's Scotty Beam says Grok Bot, in public beta since August 11, 2026, now gets its own email address, a main bot that coordinates other bots, and expanded access to subscription plans starting at $20 per month.

The post says the bot can organize inboxes, research topics, build software, and keep working after users close their laptops. The post also claims the entry price dropped 90%, but does not give the prior price.

Post on XView on X
@ScottyBeamIO

Grok Bot just got a MASSIVE upgrade – starting at $20/month.

It's own email. Smarter agents. Better coding tools. Tasks straight from X.

Set it up once. Give it a goal. Let it keep working while you sleep. https://x.com/i/article/2108171813201080320

Grok Bot just got a MASSIVE update. And the entry price dropped 90%.

Grok Bot launched in public beta on August 11, 2026. By October 8, it had been publicly available for just 58 days.

In a little over eight weeks, it has already become a seriously useful tool for everyday work.

It can help organize an inbox, research a topic, prepare documents, coordinate projects, and build software. It works across the apps people already use, keeps context between tasks, and can continue working after they close their laptops.

That makes it useful across very different working days. A founder can delegate research. A freelancer can prepare client replies. A developer can hand off a feature. An operations team can reduce repetitive work across several systems.

And Grok Bot keeps getting better.

The latest updates add more ways to give it work, coordinate several bots, and review what they produce. Meanwhile, access has expanded to much cheaper subscription plans.

Here are the five major changes, what happened to pricing, and two prompts that can help you get more value from the whole system.

Before you read: this guide breaks down Grok Bot’s biggest updates, its lower entry price, and two daily prompts you can use to put it to work.

I share practical AI workflows and the updates worth your attention → Follow @ScottyBeamIO

LIKE + BOOKMARK this article – keep it open while you set up your main bot and try the prompts.

Here’s what changed – and how to use it.

1. YOUR BOT GETS ITS OWN EMAIL ADDRESS

Email is where a lot of work begins.

A client sends a request. A colleague shares a document. Someone suggests a meeting. A service sends an account verification message.

Giving your bot its own email address creates a direct route from those messages into its workflow.

Start by asking:

“Can you claim an email address for yourself?”

The bot can check access and guide you through setup. Once the address is ready, you have another way to send it work without moving every conversation into a chat manually.

Forward a message and give it a clear job

You could forward a long email thread and ask:

“Summarize this conversation. List the decisions, deadlines, and open questions. Draft a reply for me to review.”

The email provides the context. Your instruction tells the bot what to produce.

This is especially useful when you want help with a particular conversation without connecting your entire personal inbox.

Meeting coordination is another example. With the necessary calendar access, you could include the bot in an email conversation and ask it to find suitable times.

It can use the discussion to understand what people need and the calendar to check availability.

Use a separate address for tool accounts

A dedicated address can also simplify setting up accounts for services you want the bot to use.

For example:

“Use your own email address to prepare an account for this service. Tell me if setup requires payment, identity verification, or my approval.”

The bot can handle more of the preparation, while you complete any steps that require you.

Over time, this gives the assistant a more practical role in your workflow: work can arrive directly at its address, and it can help move that work forward.

2. MAIN BOT GIVES YOU ONE PLACE TO COORDINATE EVERYTHING

Having several agents sounds useful until you have to manage every conversation yourself.

One bot has the research. Another has the project notes. A third is working on a feature.

You become responsible for moving information between them.

Main Bot helps solve that problem.

The primary bot is marked with a star and acts as your main point of contact. It can help coordinate work across your other bots and spot tasks it could take off your plate.

You bring it a goal, and it helps organize the next steps.

A more proactive assistant

A useful assistant can notice unfinished work in the information it is allowed to access.

That might mean identifying:

- A meeting that still needs a confirmed time.

- An email waiting for a reply.

- A deadline approaching without the required document.

- A project blocked by a missing decision.

This is where connected context becomes valuable.

Your calendar explains what is coming up. Your email contains requests and commitments. Your project tools show what is unfinished.

The main bot can bring that information together and suggest useful action.

Select your main bot when prompted, or ask your preferred bot to help you set it as the primary bot. Then explain what you want it to coordinate:

“Help me manage my active projects. Review the relevant connected tools, identify unfinished tasks, and suggest the highest-priority actions. Tell me which ones need my approval.”

That gives the bot a defined responsibility.

You now have one conversation to return to when you want an overview, a decision list, or help moving a project forward.

3. GROK BOT IS MOVING TOWARD A WIDER CHOICE OF AI MODELS

Different AI models have different strengths.

A model that handles everyday questions quickly may struggle with a complex coding task. A visual project needs different capabilities from a research report. Music generation requires another kind of tool.

The planned expansion beyond Grok brings that idea into the agent itself, with Claude, Midjourney, and Suno among the tools and model families named.

The aim is to let Grok Bot draw on the capabilities that fit the task.

Why this matters for your workflow

Moving between AI tools often means repeating the same setup.

You explain the project again, paste the relevant information, upload files, and move the result back to wherever the work started.

A broader model system could reduce those repeated handoffs.

You would describe the outcome:

“Build a working prototype from this brief. Use the available tools that fit the task, explain any additional cost, and show me how you checked the result.”

The bot would handle more of the decisions about how to complete it.

The practical value comes from better finished work: fewer corrections, stronger results, and less time spent transferring context between applications.

This also changes how you should judge an agent.

Its usefulness depends on the combination of models, tools, context, and execution. The model name is only one part of that experience.

4. DEEPER CURSOR INTEGRATION MAKES CODING WORK EASIER TO FOLLOW

Delegating a coding task raises an immediate question: how do you know the change actually works?

A message saying “done” gives you very little to inspect.

Deeper integration with Cursor Cloud Agents makes the work more visible. You can follow the coding task through a live link and review outputs such as screenshots and recordings.

For changes to a website or app, that makes a real difference.

A screenshot can show a new layout. A recording can show a menu opening, a button responding, or an animation playing.

Give the agent something it can demonstrate

Suppose you want to improve a landing page.

A useful request would be:

“Use a Cursor Cloud Agent to improve the mobile layout of this page. Keep the existing content. Check the navigation and main button, then send screenshots and a short recording of the updated page.”

This defines the scope and asks for evidence tied to the change.

You could use the same approach for a dashboard, signup form, or small internal tool.

Visual evidence helps you review the experience. Tests and other checks establish whether the underlying behavior works, including cases that a short recording cannot show.

Make review part of the task

Ask the bot to explain:

- What changed.

- What it checked.

- Where you can inspect the result.

- What remains unfinished.

This makes delegation easier to manage.

You can look at the result, understand the changes, and give specific feedback without reconstructing the entire development process.

5. X POSTS CAN BECOME THE STARTING POINT FOR REAL TASKS

X is full of useful material: product announcements, technical explanations, workflow ideas, and examples worth exploring.

The difficult part is doing something with them after you scroll past.

The mention-to-task feature creates a shorter path. Mentioning the bot in a post or reply gives you a way to send a request into Grok Bot for follow-up.

An interesting post can become a research brief, an implementation plan, or a small experiment.

Turn an interesting idea into a useful output

For example:

“Evaluate the workflow in this post. Explain what it requires and suggest one small test relevant to my current project.”

Or:

“Compare this product announcement with the tool we currently use. Focus on the capabilities that matter for our workflow and include source links.”

Or:

“Turn this idea into a short implementation plan. Identify the first step and anything that needs my input.”

These prompts connect the post to something you can act on.

A saved post is easy to forget. A task with a defined output is much easier to follow through.

Keep public instructions general and add private project details inside your bot conversation.

6. GROK BOT HAS BECOME MUCH CHEAPER TO ACCESS

The pricing changes deserve as much attention as the new features.

At launch, individual access was tied to expensive plans: Cursor Ultra at $200 per month or SuperGrok Heavy at $300 per month. Team access was available through Cursor Premium Teams at $120 per seat per month.

On August 26, access expanded to include the base SuperGrok plan, Cursor Pro, and all Cursor Teams plans.

Here is how the entry points changed:

These are monthly subscription prices in USD.

The minimum individual entry cost fell from $200 to $20 per month – a 90% reduction.

On the Grok subscription side, the entry point also fell by 90%, from $300 to $30 per month.

That makes trying the product a very different decision.

A $200 or $300 monthly commitment requires a strong reason to buy. Access through a $20 or $30 plan is easier to justify for everyday research, documents, email, and occasional delegated tasks.

You may already have access

If you already subscribe to an eligible Cursor or SuperGrok plan, Grok Bot is included. You do not need a separate Grok Bot subscription to use the included allowance.

X Premium+ subscribers can also access Grok Bot by linking the appropriate account.

For existing subscribers, the first step is simply to check the access they already have.

Choose a plan around your workload

The cheaper entry plans include smaller weekly usage allowances. Higher plans provide more room for larger or more frequent tasks.

For individual subscribers, Grok Bot has its own usage allowance, separate from ordinary Grok and Cursor usage. Additional work beyond the included allowance can be billed through optional on-demand usage.

That means $20 is a starting subscription price, while your actual needs depend on how much work you delegate.

Begin with a few representative tasks. Check how much usage they consume and whether the results save enough time. Then decide whether you need a larger allowance.

The expanded access makes that experiment much more affordable.

7. TWO PROMPTS THAT MAKE THE WHOLE SYSTEM MORE USEFUL

More capabilities do not automatically create a better working day.

You still need a simple way to identify useful work and hand it over clearly.

Two habits can help: a morning review and an evening handoff.

The morning prompt: find what needs your decision

Start with:

“What approvals do you need from me right now?”

That is a useful opening. Adding scope makes it more actionable:

“Review my connected calendar, relevant email, and active projects. List the highest-priority tasks you can move forward today. For each one, explain the next action, what you need from me, and whether approval is required.”

This encourages the bot to look beyond the last message you sent.

It may find an unfinished reply, a missing document, or a decision blocking another task.

Ask it to separate actions awaiting approval from suggestions for new work. Then review the actions you want it to take.

The value comes from making the necessary decisions together, so several tasks can move forward with fewer interruptions.

The evening prompt: prepare a useful handoff

Before finishing for the day, try:

“I’m going offline. Based on our current goals, what useful work could you complete before tomorrow?”

Then make the handoff concrete:

“Suggest up to three tasks. For each, define the finished output and any access or decisions you need. Wait for me to choose before starting.”

Good candidates include a sourced research brief, a draft document, a comparison of tools, or a prototype in a test environment.

Once you choose, give the bot a clear completion point:

“Prepare the comparison document using these criteria. Include source links and unresolved questions. Leave it ready for my review tomorrow.”

A defined output gives the bot something useful to work toward while you are away.

It also makes the next morning easier: you have a result to review and a clear place to continue.

8. CHOOSE YOUR AI AGENT AROUND THE WORK YOU ACTUALLY DO

It is easy to become attached to one AI tool.

A better approach is to start with the work you need completed.

For everyday knowledge work, evaluate context, connected apps, research quality, and document output. Grok Bot is especially relevant when a task crosses several tools and needs follow-up.

For building software, evaluate coding quality, project access, testing, and how easily you can review changes. Cursor integration helps connect the request to a visible development workflow.

For personal assistance, evaluate how well the tool handles your calendar, preferences, communication, and approvals. Consistency matters when the task affects your actual plans.

You may find one agent works well across all three areas. You may prefer a small combination of tools.

Give the agents you are considering the same representative task and compare the experience:

- How much context did you need to provide?

- How often did you have to intervene?

- Was the result accurate and usable?

- How easy was it to verify?

- What did the task cost?

Those answers tell you far more than a general claim that one agent is “the best.”

FINAL TAKEAWAY: MORE CAPABILITY, A LOWER ENTRY PRICE, AND LESS WORK TO COORDINATE

Grok Bot has covered a lot of ground in its first eight weeks of public availability.

Its email capabilities create another way to receive tasks. Main Bot gives you a central place to coordinate work. A wider model strategy could expand what it handles. Cursor integration makes coding results easier to inspect. X integration connects useful ideas to action.

And access through $20 and $30 subscription plans puts it within reach of many more people.

The best place to start is one task you already repeat.

Prepare for meetings. Turn requests into draft replies. Research a decision. Improve a small part of a product.

Give the bot the necessary context, define the output, and check the result. Refine the workflow until it becomes something you can use again.

Then use the morning prompt to clear decisions and the evening prompt to hand off useful work.

The real payoff is getting more of your day’s work finished with less effort spent coordinating every step.

If this was useful – LIKE & BOOKMARK it. You'll want to come back to it.

For more breakdowns like this follow @ScottyBeamIO

No fluff, just what actually works.

Source: SCOTTY BEAM · x.comPublished · added here