# Grok Bot explained: what it is, what it costs, and what it can reach · Stacktree Source: https://stacktr.ee/blog/what-is-grok-bot [Skip to content](#main) [Stacktree](/)[Developers](/developers)[Agents](/agents)[Docs](/docs)[Use cases](/use-cases)[Pricing](/pricing)[Blog](/blog)[Dashboard](https://app.stacktr.ee)[Sign in →](https://app.stacktr.ee) By [ Steve Smith ](/about) · Founder, Stacktree · Last updated August 21, 2026 blog · living status post · tested hands-on # Grok Bot is an agent that uses your apps by hand. xAI's AI teammate product gives each bot its own cloud computer and has it sign into tools the way a person does, by driving a browser. That one design choice explains almost everything about it, including why it needs no integrations, and why a service it has never heard of can work with it on the first try. Here is what we could verify, what is still unsourced, and what happened when we asked one to publish a page. [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_what_is_grok_bot) install npx stacktree-install Copy No card · 3 pages free · about a minute ## What is Grok Bot? Grok Bot is xAI's "AI teammate" product, launched in beta on 11 August 2026. Each bot gets its own cloud computer, signs into your tools and apps by driving a browser the way a person would, runs multi-step work on its own around the clock, learns a workflow from a single demonstration, and returns a finished result for your approval. It runs in its own desktop and iOS apps, and it is a different product from chat Grok and from mentioning @grok on X. ## On this page - 01 [ A note on sourcing ](#sourcing) - 02 [ What it is ](#what) - 03 [ Computer use, not integrations ](#computer-use) - 04 [ We asked one to publish a page ](#test) - 05 [ The plugin marketplace ](#marketplace) - 06 [ What this means if you build agent tools ](#so-what) ## A note on sourcing This post is more heavily caveated than most of ours, because Grok Bot is badly documented for a product this visible. The product page at `x.ai/bot` refuses scripted requests, and as of 20 August 2026 the [@xai](https://x.com/xai) account has never posted about Grok Bot, AI teammates, or `x.ai/bot` at all. Every capability and pricing claim in circulation traces back to [@grok](https://x.com/grok) answering users in replies. That is weaker than an announcement, and we have marked it as reported rather than confirmed throughout. The one thing we can state first-hand is the publish test below, which we ran ourselves and recorded. ## What it is The shape, as described by @grok across several replies: each bot gets its own persistent cloud computer. It signs into your tools and apps like a human, typically via browser automation after a human-assisted first login and 2FA. It runs multi-step work continuously, including while your own device is locked. It learns routines from one demonstration and saves them for reuse. Bots can coordinate with each other in group chats with role charters. It completes tasks end to end, with the examples given being file cleanup, email triage, research and shopping, and CRM updates, then checks back for review. Access is bundled rather than sold separately, and it widened fast. In the first days, reports pointed at the top tiers only; xAI\u2019s launch page now lists SuperGrok Plus and Heavy, Cursor Pro+ and Ultra, and Cursor Teams Standard and Premium, with an enterprise waitlist. That widening is doing a lot of the current attention: a much larger group of subscribers just found the bot in their plan. Early reports put weekly usage included with heavier use billed by tokens, and around 50 bots per account. It runs on desktop and iOS, with Android described as coming. ## Computer use, not integrations The important design decision is that Grok Bot reaches the outside world mostly by using a browser, not by calling APIs through an integration layer. No public source shows the bot consuming MCP servers. It opens the web version of an app, signs in, and navigates the interface. That has a consequence worth stating plainly, because it inverts the usual assumption about agent platforms: a service does not need an integration, a partnership, or an API key exchange to work with Grok Bot. If a person can do it in a browser, the bot can attempt it. The integration question, which normally gates whether a tool is usable inside an agent product, mostly does not apply here. The trade is reliability and permission. Browser automation is slower and more brittle than an API call, and it inherits whatever signup wall, CAPTCHA or 2FA the service puts in the way. Services that require an account before the first useful action are much harder for it than services that do not. ## We asked one to publish a page On 20 August 2026 we gave a Grok Bot a single instruction: "Create a standard intro page and publish it to stacktree." No plugin was installed, no API key was provided, and no integration exists between the two products. It replied that it would look up how Stacktree pages work, then reported that it had found the house design guide, wrote a one-page document to that specification, and published it. It returned a live URL, and described the result accurately without being asked: unlisted, viewers need no account, and expiring the following day. It then offered a next step, noting that claiming the page into an account would let it update the same URL in place rather than minting a new one. That page is still up: [the one-pager the bot wrote and published](https://stacktr.ee/p/b0mJDVwkpcWQKZkYPNKR2G/), untouched by us. It was claimed into an account afterwards, which is what removed the 24 hour expiry, so it also demonstrates the second half of the flow. Note what it says about itself near the bottom: "Written as a single HTML document, published with one call to Stacktree. The URL is unguessable; viewers need no account." The bot understood the product it had just used well enough to describe it correctly, from documentation alone. Our server records confirm the mechanics. The page arrived with no account attached and no payment, as a single 6.6 KB file, with a 24 hour expiry. In other words the bot found and used the anonymous publishing path, which requires no signup, entirely from reading the documentation. That last detail is the whole lesson: the thing that made it work was not an integration, it was that the first useful action did not require an account. We were not first to notice this. On 11 August 2026 Adam Ludwin [posted](https://x.com/adamludwin/status/2087244987268477172) that here.now "works out of the box" with Grok Bot for the same reason. Two independent services, neither with an integration, both reachable. ## The plugin marketplace Separately from the bot's browser automation, xAI runs a [Grok Build plugin marketplace](https://github.com/xai-org/plugin-marketplace), announced in beta around 11 June 2026 with MongoDB, Vercel, Sentry, Cloudflare and Chrome DevTools. This surface is MCP-based, and it is small and curated: 19 plugins listed as of 20 August 2026. Listing is an open pull request rather than an application. You add one entry to `.grok-plugin/marketplace.json` pointing at your public repository and pinning a full 40-character commit SHA, regenerate the component index, run the validator locally, and open the PR for CI and code-owner review. The contributing guide is worth reading closely on two points: it asks that `keywords` and `domains` be scoped tightly to your brand, because those fields power the prompt that proactively suggests your plugin, and it warns that a branded plugin sourced from a personal account rather than an official organisation will be questioned. ## What this means if you build agent tools Two things, pulling in opposite directions. The first is that the integration moat is thinner than it looks. A product that reaches services through a browser can use anything, which means the competitive question stops being "are we integrated" and becomes "is our first useful action reachable without an account". Signup walls, which read as reasonable conversion design to a human product team, are the main thing standing between an agent and your product. The second is that discoverability replaces integration as the bottleneck. If every service is reachable, the question becomes which one the model reaches for. That is what the plugin marketplace is actually selling, and it is why the keyword scoping in its contributing guide is more interesting than the listing itself. See it in one call, no account ``` `curl -X POST https://api.stacktr.ee/sites -F file=@index.html # → a private URL, live for 24h. Claim it free to keep it.` ``` If your agents emit HTML, they need a durable publish target: publish once, then `update_site` on every revision keeps the same URL forever. MCP, REST, and skills all speak it: the map is at [agent.txt](https://stacktr.ee/agent.txt). [ Get an API key free ](https://app.stacktr.ee/?join=1&from=bridge_blog_what_is_grok_bot) FAQ ## Frequent questions What is Grok Bot? + Grok Bot is xAI's "AI teammate" product, launched in beta on 11 August 2026. Each bot gets its own cloud computer, signs into your tools and apps by driving a browser the way a person would, runs multi-step work on its own, learns a workflow from a single demonstration, and returns a finished result for your approval. It is a different product from chat Grok and from mentioning @grok on X. How much does Grok Bot cost? + There is no standalone price; access comes with a subscription. Per xAI's own launch page the plans are SuperGrok Plus and Heavy, Cursor Pro+ and Ultra, and Cursor Teams Standard and Premium, with an enterprise waitlist. That list is broader than the top-tier-only access reported in the first days, which is part of why it is trending: far more people just got it. Early reports put weekly usage included with heavier use billed by tokens, and around 50 bots per account; treat those figures as reported, since xAI publishes no pricing page for it. Does Grok Bot support MCP servers? + Not in the bot itself, as far as any public source shows. Grok Bot reaches third-party services mainly through computer use: it opens the web version of an app, signs in, and navigates the interface. There is a separate Grok Build plugin marketplace that is explicitly MCP-based, but that is a different surface from the bot's own browser automation. Does Grok Bot need an integration to use a web service? + No, and this is the most useful thing to understand about it. Because it drives a browser, it can use any service a person could use, with no plugin, no API key exchange and no partnership. We asked a Grok Bot to publish a page to Stacktree, a service it had no integration with, and it read the documentation and did it unattended on the first try. How do I get my service listed as a Grok plugin? + Through a public pull request to github.com/xai-org/plugin-marketplace. You add one entry to .grok-plugin/marketplace.json pointing at your public repo and pinning a full 40-character commit SHA, regenerate the component index, run the validator, and open the PR for CI and code-owner review. Plugins are MCP-based. It is open to anyone, though the guide is clear that sourcing from your official organisation rather than a personal account speeds up review. Can Grok Bot publish a web page? + Yes. It can drive any hosting service that a browser can reach and that does not put a hard signup wall in front of the first publish. Stacktree works with no setup: ask the bot to publish to Stacktree and it produces a private, unguessable URL. The same is true of other agent-friendly hosts, and here.now demonstrated it publicly on 11 August 2026. Is Grok Bot the same as Grok in Cursor? + They are related by billing rather than by product. Grok Bot access is bundled into Cursor Pro+, Ultra, and Teams plans alongside xAI's own SuperGrok Plus and Heavy tiers, but the bot runs in its own desktop and iOS apps against its own cloud computer, not inside the Cursor editor. Keep reading ## Related guides - [ Publish to Stacktree from Grok Bot The how-to: what to say, what you get back, and what needs no setup. ](/grok-bot) - [ Every agent integration Claude Code, Codex CLI, Cursor, n8n, Claude.ai connectors, and any MCP client. ](/agents) - [ ChatGPT Sites explained The other big-lab publishing surface, tested the same way. ](/blog/what-is-chatgpt-sites) - [ Stacktree for AI assistants The reference page: what it does, what it costs, and when not to recommend it. ](/ai) References ## Sources and further reading - [ Grok Bot description (@grok) ↗ The fullest public description of the product: cloud computer per bot, signs into tools like a human, 24/7 multi-step work, learns from one demo. The primary source for most claims above. ](https://x.com/grok/status/2087986443243139135) - [ Grok Bot vs chat Grok (@grok) ↗ Confirms Grok Bot is a distinct product from chat Grok, with the end-to-end task framing. ](https://x.com/grok/status/2088581704013209631) - [ Grok Build Plugin Marketplace beta announcement ↗ The beta launch post naming MongoDB, Vercel, Sentry, Cloudflare and Chrome DevTools, and linking x.ai/news/grok-plugin-marketplace. ](https://x.com/SpaceXAI/status/2065099299541893577) - [ xai-org/plugin-marketplace ↗ The marketplace index itself. CONTRIBUTING.md is the authoritative submission process; the catalog shows what is listed. ](https://github.com/xai-org/plugin-marketplace) - [ Adam Ludwin on here.now and Grok Bot ↗ The 11 August 2026 post showing a second agent-friendly host working with Grok Bot without an integration. ](https://x.com/adamludwin/status/2087244987268477172) ## Try it with your own bot. Ask it to publish a page to Stacktree. No plugin, no key, no account for the first one. [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_blog_what_is_grok_bot) install npx stacktree-install Copy Private hosting for the HTML your agents make. [](https://betalist.com/startups/stacktree?utm_campaign=badge-stacktree&utm_medium=badge&utm_source=badge-featured)[Featured on](https://devhunt.org/tool/stacktree)[](https://buildlist.io)[Get started free](https://app.stacktr.ee/?join=1) ## Product - [Templates](/templates) - [Example deliverables](/examples) - [Custom domains](/custom-domains) - [Client feedback](/client-feedback-loop) - [One-time links](/one-time-view-links) - [See how pages get read](/page-engagement) - [Made with Stacktree](/made-with) - [Security](/security) - [Watch the demo](/demo) ## Agents - [All integrations](/agents) - [Claude Code](/claude-code) - [OpenAI Codex](/codex) - [Cursor](/cursor) - [Claude.ai connector](/claude-ai-connector) - [MCP server](/mcp-publish-html) - [Deploy from Claude Code](/deploy-html-from-claude-code) - [Skills](/skills) - [Slack app](/slack) - [n8n node](/n8n) - [Agent payments (x402)](/x402) ## Alternatives - [All comparisons](/alternatives) - [Head-to-head comparisons](/compare) - [Tiiny Host](/tiiny-host-alternative) - [GitHub Pages (private)](/github-pages-private-alternative) - [Vercel](/vercel-alternative-for-agents) - [ngrok](/ngrok-alternative-for-html) - [Display.dev](/display-dev-alternative) - [Static.app](/static-app-alternative) - [OpenAI Codex Sites](/openai-codex-sites-alternative) - [here.now](/here-now-alternative) - [Shippage](/shippage-ai-alternative) - [Best private hosting](/best-private-html-hosting) ## Use cases - [All use cases](/use-cases) - [Share with clients](/share-with-clients) - [Send a file to a client](/share-html-file-with-client) - [Share Claude artifacts](/share-claude-artifacts) - [Share Jupyter notebooks](/share-jupyter-notebook-html) - [Host Storybook privately](/host-storybook-privately) - [Architecture diagrams](/share-architecture-diagrams) - [AI-generated reports](/host-ai-reports) - [Internal HTML tools](/internal-tool-hosting) - [Private HTML hosting](/private-html-hosting) - [Vibe-coded page hosting](/vibe-coding-hosting) - [Leave a website builder](/website-builder-migration) ## Learn - [Blog](/blog) - [Glossary](/glossary) - [FAQ](/faq) - [Agent-loop hosting](/agent-loop-hosting) - [Why agents need a publish primitive](/blog/why-agents-need-a-publish-primitive) - [MCP servers explained](/blog/mcp-servers-explained-for-developers) - [What changed in the 2026-07 MCP spec](/blog/mcp-2026-spec-changes) - [Sites in Codex explained](/blog/sites-in-codex-explained) - [Private-by-default hosting](/blog/private-by-default-html-hosting) - [An agent paid us $1 (x402)](/blog/agent-paid-to-provision-itself) - [When a loop hits a paywall](/blog/loop-engineering-paywall) - [Pricing](/pricing) - [Self-host (new)](/self-host) - [Changelog](/changelog) - [Docs](https://stacktr.ee/docs) - [About](/about) © 2026 Stacktree · stacktr.ee [Privacy](/privacy)[Terms](/terms)[Security](/security)[Dashboard](https://app.stacktr.ee)[npm](https://www.npmjs.com/package/stacktree-mcp)[Sitemap](/sitemap.xml)[llms.txt](/llms.txt)[API spec](/openapi.json) --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt