Definition:
Grokbot is an application in the Cursor ecosystem that allows users to create persistent artificial intelligence agents to carry out tasks with files, applications and websites. Its official name is Grok Bot. The agents work on a cloud computer and receive instructions through conversations.
Each bot can have a name, a role and a working context that it retains between tasks. The application combines tools, memory and reusable procedures to carry out work that requires several steps, beyond generating a text response.
Table of contents
Relationship with Cursor
Grok Bot uses a Cursor account and forms part of its tool ecosystem. However, its interface and purpose are not limited to the code editor.
While the editor organizes work around files and software projects, Grok Bot provides agents with ongoing roles. They can research information, prepare documents, work with spreadsheets or use connected services.
The product should not be confused with Grok as a model or conversational assistant either. Grok Bot refers to an application that organizes agents, tools and execution environments, not just the model that generates its responses.
How its agents work
A bot receives a task along with the available instructions and materials. It can consult sources, open applications, modify files and use the results of each operation to decide the next step.
Its cloud computer has a browser, filesystem and terminal. This allows it to perform operations in real applications and retain files between tasks. Work can continue even when the application is closed or the user’s personal computer is no longer connected.
The conversation displays messages, tool activity, generated files and approval requests. The user can provide further instructions while work is in progress.
For example, a bot can consult a list of issues, gather information from different services and prepare a document covering outstanding cases. The result comes from a sequence of queries and operations, not just a response based on the initial message.
Each bot retains its conversation and learned context, such as preferences, relevant facts and summaries of previous work. This continuity allows it to maintain a role without repeating every instruction in each request.
However, bots belonging to the same account share the cloud computer. Files, browser sessions and active sign-ins in that environment may be available to several bots.
Separate conversations therefore do not amount to complete resource isolation. An individual screen for each agent allows parallel work, but does not by itself establish an access boundary for files or accounts.
Retaining information is also different from retraining a model. Memory provides context for subsequent tasks; it does not imply changes to the language model’s parameters.
Collaboration, skills and routines
Grok Bot supports group conversations and handoffs between agents. One bot can gather information and pass it to another responsible for preparing a document or reviewing the result.
Skills contain reusable instructions: steps, decision criteria, required inputs and output format. They can be created from written instructions or from a procedure carried out previously.
The teaching-by-demonstration feature allows a workflow through an application to be shown and converted into a draft skill. Availability is being rolled out gradually; a demonstration does not amount to automatic validation of the procedure.
Routines determine when work runs. They can be triggered by a schedule or by certain supported events. A skill describes how to perform a task; a routine establishes when it should start and which bot is responsible for it.
Installation and application connections
Grok Bot has an application for macOS, Windows and Linux, as well as access from iPhone. The installed application is used to communicate with bots and observe their activity; the computer where they normally perform their work remains in the cloud.
The getting-started guide distinguishes several stages:
- Install the application and sign in with the Cursor account.
- Create a bot, assigning it a name, role and instructions.
- Provide a task and its materials, such as documents, links or files.
- Connect the required services through plugins or browser sessions.
- Review the result and retain reusable instructions as a procedure.
Plugins provide structured tools for working with compatible services. When an application does not have such a connection, the bot can use its interface through the browser, subject to the site’s capabilities and restrictions.
Permissions and action review
Grok Bot includes approval requests and a layer called Auto Review, which uses a review model to evaluate certain actions before they run. It can allow an operation, request approval or block it.
These controls are distinct from the permissions of connected applications and from network restrictions. Blocking a plugin does not necessarily block access to the same service’s website.
Execution on the local computer also has a policy separate from operations performed in the cloud. Access to the remote environment does not imply automatic authorization to run commands on the user’s computer.
Approvals apply to specific operations. Stopping a bot interrupts pending work, but does not automatically reverse changes it has already made.