Grok Bot Sign In: Which Account Should You Use?

Last Updated: November 2026

Grok Bot sign-in uses the account that actually holds the plan including the agent, and there is no separate credential for it. That sounds obvious, and it is where almost every failed sign-in goes wrong. Four arrangements grant access, each with its own correct account, and picking the wrong one produces a working session with no agent in it.

AiBuildrs builds custom AI systems for mid-market businesses. The team has completed over 200 successful AI implementations, producing $4.7M in documented client cost savings.

On The X Subscription, use that same account. On a legacy Cursor plan or a Teams seat, use that Cursor account. A SuperGrok link is created on whichever Cursor account you are signed into. A self-serve Grok Business seat needs Sign in with Grok on the account holding the seat.

Key Takeaways

1. Match the account to the entitlement: Sign in with whichever account holds the plan that includes the agent.
2. Legacy and X Subscription both use their own account: No separate Grok Bot credential exists.
3. Grok Business seats are different: Those use Sign in with Grok on the account holding the assigned seat.
4. Check the account before linking: A link binds permanently to whichever Cursor account is open at the time.
5. Metering stays on Cursor: Usage reports there regardless of which route granted access.
6. Multiple accounts are the usual culprit: Personal and work Cursor accounts are the most common cause of a missing agent.

Those six points cover the four arrangements and the one permanent trap. Each situation is taken in turn below, ending with what to try when the agent still does not appear.

Which account do you use on The X Subscription?

Use the account that holds the subscription. Grok Bot is included on Premium, Super and Ultra, and the entitlement follows the tier.

According to xAI's documentation (2026), this applies to individual accounts and to team seats alike. There is no separate agent credential to obtain.

If the agent does not appear after signing in, the usual cause is the tier rather than the sign-in. Free and Plus do not include Grok Bot at all.

The second most common cause is signing in with a different account from the one carrying the subscription. That produces a working session with no agent in it.

Which account on a legacy Cursor plan or Teams seat?

Use that Cursor account. Every paid individual legacy plan includes Grok Bot, which means Pro, Pro+ and Ultra, and Cursor Teams includes it for team seats.

Cursor's help pages (2026) set out the legacy sign-in paths. All the paid tiers sign in the same way, through the Cursor account itself.

A Teams seat behaves like the individual plans for sign-in purposes. Your access comes from the team arrangement rather than from a personal subscription, but the account you use is still your Cursor account.

Where access was provisioned for you by somebody else, the entitlement may sit on an account you do not normally use. That is worth checking before assuming anything is broken. AiBuildrs starts there on any access ticket.

Cursor Enterprise is arranged through an account executive rather than self-serve, so an enterprise setup may not match these screens at all.

When do you use Sign in with Grok?

Only for a self-serve Grok Business seat. This is the one arrangement that does not sign in through Cursor credentials.

The flow is to sign out of your current session. Then sign back in choosing Sign in with Grok, using the account that holds your assigned seat.

The seat must actually be assigned to you. Belonging to an organisation with a Grok Business plan grants nothing on its own, so an unassigned member sees no agent.

Seats are frequently provisioned by someone other than whoever manages Cursor billing. If you are not sure whether you hold one, your administrator will answer faster than any screen available to you.

What if you have more than one Cursor account?

This is the most common cause of a missing agent, and it is entirely mundane. Entitlements attach to accounts, not to people.

Holding a personal Cursor account alongside a work one is normal. The agent appears on whichever one carries the qualifying plan, and signing in to the other produces a perfectly functional session with nothing in it.

Check the signed-in email rather than assuming. The expected account is not always the active one, particularly on a machine used for both personal and client work.

AiBuildrs checks this first on any access problem, because it resolves more cases than every other cause combined.

What should you do before linking anything?

Confirm which Cursor account is open. This is the single most important step in the whole area, and it takes seconds.

Official help describes a link as permanent and says it cannot be moved to another Cursor account. The account signed in when you create the link is the account it binds to, for good.

So the order matters. Sign in deliberately, verify the email on screen, and only then open the Grok Bot plan screen to link a subscription.

Linking a work subscription to a personal account is the mistake this prevents. It is cheap to avoid beforehand and awkward to resolve afterwards.

Worth knowing before you go further: linking does not add to your Cursor plan. The agent uses whichever grant is higher, so the exercise is only worth doing when the outside subscription is the larger one.

What if the agent still does not appear?

Work through the entitlement before the sign-in. Confirm the plan actually includes Grok Bot, because several tiers do not.

Then confirm the account. Free and Plus on The X Subscription include no agent, and neither does any free Cursor arrangement. The tier is as likely a cause as the credential.

Then confirm the product. Grok Bot and the Grok chatbot are different things, and access to one says nothing about access to the other.

If all three check out and the agent is still absent, that is a support matter rather than a configuration you can fix. Nothing documented requires an additional activation step.

AiBuildrs raises those with the vendor rather than building workarounds, since an undocumented behaviour is not something to design a team's week around.

Frequently Asked Questions

Can I use a different email for Grok Bot than for Cursor?

Not for the agent itself, because Grok Bot has no separate credential and signs in through the account holding the plan. The exception is a self-serve Grok Business seat, which uses Sign in with Grok on the account holding the assigned seat. In every other case, the account carrying the entitlement is the one that works. A different email simply produces a session without the agent in it.

How do I use a Grok Business seat?

Sign out of your current session, then sign back in choosing Sign in with Grok, using the account that holds your assigned seat. The seat has to be assigned to you specifically, since membership of an organisation on a Grok Business plan grants nothing by itself. If you are unsure whether a seat exists for you, ask whoever administers the plan rather than working through sign-in screens.

What if I signed in with the wrong account?

Sign out and sign back in with the account carrying the plan. Nothing is damaged by signing in to the wrong one, and no state persists from the attempt. The exception is linking, which is permanent and binds to whichever Cursor account was open when you created the link. That is the one action worth confirming your account for beforehand rather than afterwards.

Do macOS and iPhone share the same sign-in?

Yes, the entitlement is the same across both and you sign in with the same account. One usage detail is worth knowing while you work across devices: macOS and iOS draw from a single shared usage bucket rather than separate allowances. Work done on one therefore reduces what is left on the other, which is expected behaviour rather than a reporting fault on either device.

Is there a separate Grok Bot login?

No. The agent has no credential of its own and is reached through the account holding the qualifying plan. That is either The X Subscription account at Premium, Super or Ultra, or a Cursor account on a paid legacy plan or Teams seat. Anything presenting itself as a dedicated Grok Bot login is not an official route. Treat it with the caution you would apply to any unexpected sign-in prompt.

Does signing in to Grok give me the agent?

No, and this trips people up regularly. Grok is the conversational chatbot on X, while Grok Bot is an agent that runs inside the Cursor environment. They are separate products with separate entitlements. Signing in to the Grok apps tells you nothing about whether you hold agent access. Some tiers include the chatbot without including the agent at all, which is why the two are worth checking separately.

Why does the agent appear on one machine but not another?

Almost always because different accounts are signed in on each. Entitlements attach to accounts rather than to devices or to people. A machine signed in to a personal Cursor account will show no agent, even when your work account holds a qualifying plan. Check the signed-in email on both machines, which resolves this faster than any other diagnostic step available to you.

Do I need to sign in again after switching plans?

Not usually, since the entitlement follows the account rather than the session. After moving to The X Subscription your access comes from the subscription tier instead of a legacy plan, but the account stays the same. If a screen still shows an old allowance after a completed switch, treat that as a support issue. Signing in again will not resolve it.

Can two people share one Grok Bot sign-in?

That is not how the product is arranged, and sharing credentials is a poor idea regardless of the product. For more than one person, Cursor Teams includes the agent as part of the team plan, and a self-serve Grok Business plan assigns individual seats. Those are the designed routes for teams, rather than one person's sign-in being passed around an office.

Where do I see usage once I am signed in?

In your Cursor account, which is where Grok Bot usage meters regardless of which route granted your access. Your Grok account and your X account do not display the figure, which sends people looking in the wrong place. The same Cursor account also holds your prepaid credit balance or your on-demand billing setting, depending on which plan family you are actually in.

Executive Summary

There are four arrangements, and each has its own correct sign-in. Getting the wrong one usually looks like the agent being missing rather than an error message.

The X Subscription and legacy Cursor plans both sign in through the account holding the plan. A Grok Business seat is the exception and uses Sign in with Grok instead.

Before linking anything, confirm which Cursor account is open. Official help describes a link as permanent and unable to move, so the account signed in at that moment is the account it binds to.

Grok Bot usage meters on the Cursor account in every case. That does not change with the sign-in route, so check it once you are in.

What Should You Do Next?

Check the signed-in email before anything else. Most sign-in problems here are account problems wearing a disguise.

If access across the team is inconsistent and nobody can say why, talk to AiBuildrs about mapping who holds what before buying more seats.

People Also Read

1. Which Plans Include Grok Bot, and Which Ones Do Not
2. How to Link SuperGrok Grok Bot Access on a Legacy Plan

About the Author

Jerry Jariwalla is the founder of AiBuildrs and creator of the Growth Signal Intelligence framework. With over 22 years in digital marketing and multiple successful business exits, Jerry has spent the past decade leading AI implementation programs for mid-market businesses across professional services, recruitment, membership organizations, and traditional industries. AiBuildrs has completed over 200 successful AI implementations using a workflow-first methodology and is trusted by leaders at YPO, Vistage, Tiger 21, and C12 executive peer organizations.

Expertise: AI Strategy, AI Implementation, Workflow Automation, Custom AI Development, Voice AI, Offshore Engineering, B2B Sales Intelligence, Mid-Market AI Adoption

Connect: LinkedIn

Disclaimer: This content is for informational purposes only and does not constitute professional business or technology advice. ROI outcomes vary based on industry, existing systems, and implementation commitment. Contact AiBuildrs for a consultation regarding your specific situation.