Skip to content

feat: grok bot docs - #2957

Open
Jakub-Vacek wants to merge 5 commits into
apify:masterfrom
Jakub-Vacek:feat/grok-bot-docs
Open

Jakub-Vacek wants to merge 5 commits into
apify:masterfrom
Jakub-Vacek:feat/grok-bot-docs

Conversation

@Jakub-Vacek

Copy link
Copy Markdown
Collaborator

This PR adds Grok Bot plugin (already released, reuses Cursor plugin and marketplace) docs.

@Jakub-Vacek
Jakub-Vacek marked this pull request as ready for review September 8, 2026 10:50

@marcel-rbro marcel-rbro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some adjustments are needed for this to be perfect 👌


[Grok Bot](https://docs.x.ai/grok-bot) is an AI teammate that works from a persistent cloud computer. It reads and edits files, runs commands, uses a browser, and completes multi-step development tasks.

The [Apify plugin for Grok Bot](https://github.com/apify/apify-cursor-plugin) connects Grok Bot to Apify's library of [Actors](https://apify.com/store) and bundles:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is not a single mention about Grok in the Cursor plugin readme. At that point, is there even any value in mentioning this? The user doesn't even know that it actually reuses the Cursor plugin. While installing, they don't really care what exact plugin is installed, only that it works when done.


1. Open **Settings** > **Plugins**. The **Marketplace** opens with the **Plugins** tab selected.

![Grok Bot Marketplace with the Plugins tab selected, showing featured connectors and Add buttons](images/grok-bot/plugins-settings.webp)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The screenshot could at least show the Apify tile more prominently. Could show the state when you search for term "Apify" for example.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the official logo? Looks kinda off.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

This one has black BG still present.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Snímek obrazovky 2026-09-21 v 16 53 46 Snímek obrazovky 2026-09-21 v 16 54 02

Fixed :)


1. Choose **Add**.

Installed connectors are account-wide. Their availability is not isolated to one Bot.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is in 3 separate locations on this page. Pick 1 (or 2 at most) or rephrase.

- Skills that edit files in your project (Actor development, actorization, SDK integration) make changes on the Grok Bot cloud computer - review them before deploying or committing.
- Installed connectors are account-wide. Their availability is not isolated to one Bot.
- All Bots on your account share the same cloud computer. Files and credentials you place there are visible to every Bot.
- Prefer the Apify connector over browsing Apify's website in the Grok Bot browser. A connector is often more reliable than clicking through a site.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be somewhere in the "Run your first prompt" section.

…grok-bot-docs

# Conflicts:
#	sources/platform/integrations/ai/index.mdx
#	sources/platform/integrations/index.mdx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants