Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124

This is Cursor Grok Bot, the desktop teammates with their own computer. It is not the Grok chatbot on X, not a Tesla feature, and not a Discord bot. If you searched how to use grok bot or grokbot and landed here, you want the always on agents you install from Grok Bot download, not a chat window.
How to use grok bot is a roster problem, not a prompt problem. One catch all bot that holds your whole life gets noisy. A short name, one job, and a stop rule will beat a mega intern. Steal a setup people already shipped. Inspect the share before you import it. You type the password.
xAI launched it as early beta on August 11, 2026. Bots have a cloud computer, sign into tools you already use, keep working after you close the laptop, and come back when they need approval. That is the Grok Bot intro.
Bookmark the stack and stay on this page for the first hour: Grok Bot docs, Grok Bot download, Grok Bot guides, grokbot.dev, and botdirectory.ai.
Grok Bot is a team of always on agents. Each one has its own computer in the cloud. You message it like a colleague. It works inside apps and websites, including tools with no clean API. It remembers how you like the work done.
What is grok bot, in one line from xAI: AI teammates you can give real work to. They finish jobs and only pull you in for judgment.
Grokbot as a word also shows up on grokbot.dev, an independent community of shareable setups. It is not affiliated with xAI. A share link copies instructions, memories, and workflow into YOUR bot. It does not share their computer, files, or logins.
Do not mix this with Grok the chatbot. That product lives on X and grok.com. This article is the desktop Grok Bot getting started path.
You use it by hiring seats, not by dumping every task into one chat.
Give each bot a job a human could hold: inbox, prospecting, board hygiene, a site audit. Put specialists in a group chat so they call each other. Pin a chief of staff if you want one place that only wakes you for decisions.
The official Grok Bot guides show the pattern that scales. One project gets one channel, a roster, and a board. Reuse bots you already have. Cap a channel around six. Create a new specialist only after you say yes. When a bot is stuck, it marks Blocked and pings you. That is the multi team guide.
The GTM bot guide is the same idea for sales: pin a chief of staff, run prospecting overnight, teach a workflow by recording it once, and scan sent mail before it drafts in your voice.
The PM bot guide argues against one omniscient agent. A chief of staff for calendar, Slack, and inbox. An eng manager who does not code. IC eng bots. A data analyst who owns the dash. One prompt they actually use: read past Slack messages and write a Slack style guide.
Two more official guides sit on the same index. Mobile app development is a six seat studio with overnight tasks and a hard rule that spend needs a human yes. Designing Grok Bot with Grok Bot is a design crew, not a blank chat.
You stay the manager. Money, send, delete, and production settings stay with you.
Install from the Grok Bot download page. Desktop is macOS or Windows. iOS works. Linux desktop does not. That limit is in the Grok Bot docs, not a rumor.
Who can use it, per those docs: SuperGrok Plus or Heavy, Cursor Pro+ or Ultra, Cursor Teams Standard or Premium. Sign in with Cursor. The August 11 launch post listed a slightly wider set, including SuperGrok and Cursor Pro. If you are checking a plan, use the docs page.
Accounts on Legacy Privacy Mode have to move to a supported Cursor data setting before Grok Bot can start. The docs say it needs cloud data storage.
Create the first bot with a short name, one primary job, and how it should work. Focused beats catch all. Their example is Piper, product performance, never change production settings.
On first use the app asks which tools you use. Those answers shape teammate suggestions. They do not connect the tools by themselves.
The docs formula is five parts.
Outcome: what should be finished.
Sources: which apps, files, or sites matter.
Constraints: what it must avoid or ask before doing.
Deliverable: what it should return.
Review point: when it should stop for you.
A no login starter from that page: attach a document. Summarize it in five bullets. List every date, decision, and open question. Cite the page. Do not change the source file.
Then try one real tool. Open a dashboard, compare this week with the last four, name the largest step change, draft a plan with chart links. Do not change the dashboard. Ask you to sign in if needed.
When it hits a login, you take over the computer for the password, passkey, two factor code, or CAPTCHA. The session sticks on the shared machine so other bots can reuse it. Connectors live under Settings, then Plugins.
When the process is stable, ask it to save a skill or a routine. Show it the job once if you can. That is how the launch post says a bot learns a workflow.
A good first week is boring on purpose. One bot. One tool. One review format you will reuse. Then add a specialist when the work actually splits, using New, then Create new agent. Do not staff a twelve bot company on night one.
Do not write the first roster from scratch.
grokbot.dev is the recipe box. Independent community, not xAI. When we checked, it listed 218 shareable bots and 39 plugins. One link installs instructions, memories, and workflow into your bot.
Start with onboarding, not with a random famous name.
Spark Onboarding is a five minute onboarding bot that spawns the starter bots you need.
Box Inspector inspects a share link before you let it into your account.
Onboarding Coach (@tpgoebel) and Brief (@anandVragav) are listed on grokbot.dev as a guided first hour and a first brief coach. We are not inventing extra share URLs for them. If the page does not show an official x.ai/bot link, do not paste a guess.
Verified shares only, from pages we opened:
Grok Bot Coach audits the bots you already have.
X Brief learns your beat from your own posts.
Site Audit is a one pass site audit.
Need a prompt by job, not a full install? Use botdirectory.ai. When we checked it listed 473 ready to copy prompts, with 146 tagged Grok. Sort Most copied or Newly added. There is a Chief of Staff collection.
Most copied on the homepage when the lock was taken: Bot Advisor 542 at Bot Advisor, Bot Team Chief of Staff 239, Email Purger 200, X Account Crew 136, SEO Team 109. Counts move. Confirm on the sort.
A listing is not proof the integration is live in your account. Confirm tools before anything can send, spend, or subscribe. Do not invent an x.ai/bot share URL.
Plugin catalog with no key: MCP catalog. Never auto install a template.
Do not import a share you have not inspected. Random grok share URLs are how you copy someone else’s mess, their routines, and their stop rules.
Run Box Inspector first. Read the job. If it can send mail, spend money, delete files, or post, you keep the approval.
Do not import five crews on day one. Reuse before you hire. Cap the first channel around six.
Do not import a Tesla, Discord, or trading setup because the title said grok. This page is Grok Bot the desktop teammate.
Do not treat grokbot.dev as official xAI. It is a community index. The official install and plan list stay on the docs.
Do not let a directory prompt fire a connector you did not authenticate. Paste it into a named bot. Confirm Plugins. Then run a dry task that cannot send.
Always on desktop agents with a cloud computer. Not the Grok chatbot on X.
Usually the community site grokbot.dev, or shorthand for Grok Bot. Check which one the link is.
Install, one job, first task with a review point, then steal a roster and inspect it.
iOS works. Linux desktop does not. The docs still want a Cursor sign in and an eligible plan.
No. A share copies instructions, memories, and workflow into your bot. It does not share their computer, files, or logins.
You can. It will get noisy. The guides and the docs both push focused bots.
Skip it, or copy the prompt text only after you read it. Do not invent an x.ai/bot URL.
Install, plan check, one named bot, a five part first task, then Spark or Box Inspector, then a directory prompt only if you still need a job recipe.
If you want the first hour in order: download from Grok Bot download, skim the Grok Bot docs, pick a pattern from Grok Bot guides, run Spark then Box Inspector, cap the channel, and only then paste a prompt from botdirectory.ai. Money, send, and delete stay with you.