Cloud agent productsUpdated 9 October 202612 min read
Kavela vs Grok Bot
Grok Bot gives you a roster of named agents that message each other on one shared cloud computer. Kavela gives each agent session its own computer, a lead agent that runs the team, and one inbox for everything the agents need.
Yong Hong TanFounder, KavelaAbstract
Grok Bot is SpaceXAI's team of always-on agents, launched in beta on 11 August 2026: named Bots with their own identity, memory and tools, working on a persistent cloud computer that runs in Cursor's cloud 1, 2, 3. Of the cloud agent products, it is among the closest to Kavela, with Bots that hand work to each other and typed cards for approvals, purchases, drafts and secrets 1, 4, 5. This report describes how Grok Bot handles six things a team of agents needs, then how Kavela handles the same six. The short version: Kavela comes with the lead agent, a calendar of every task and one Approvals inbox across every agent, gives each agent session its own cloud computer, and runs on your own Claude or ChatGPT plan, chosen per agent.
| Topic | Kavela | Grok Bot |
|---|---|---|
| Your model plan | Claude or Codex on your own plan, or included Kav AI, chosen per agent | No model picker; Cursor manages model selection 6 |
| Managing many agents | A lead agent plans and assigns work to a standing team, on one calendar | Bots hand work to each other; the lead Bot is a pattern you set up, with no built-in board 1, 2 |
| Agent email | A workspace inbox agents use to sign up for services | Your connected Gmail or Outlook; no Bot-owned mailbox in the docs 7 |
| Approvals | One inbox across every agent, as typed cards | Typed cards, shown in each Bot's own chat 4, 7 |
| Recurring runs | Schedules or events, each agent session in its own cloud computer | Routines per Bot, at least five minutes apart; all Bots share one computer 8, 9 |
| Connections | OAuth, MCP, API keys, secrets or a live browser sign-in, set up by the agent | OAuth and key plugins, custom MCP, secrets, shared browser sign-ins; Bots ask you to connect 10, 11, 5 |
What Grok Bot is
Grok Bot comes from SpaceXAI, formerly xAI, which SpaceX acquired in February 2026 12. SpaceXAI calls it your team of always-on agents, which have their own computer, work inside tools and apps the way you do and keep working around the clock. It launched in beta on 11 August 2026 1.
Each Bot is a named, persistent agent with its own identity, memory, runtime and tools. The sidebar is a roster of Bots, each with a name, avatar and title and its own long-running conversation, and the avatar shows whether a Bot is idle, working, waiting or blocked 2. You create a Bot by giving it a name and one main job, then message it, dictate to it or talk to it by voice in the desktop and mobile apps; Team Bots also work in Slack 13, 7, 3, 10.
The Bots work on a persistent cloud computer with a browser, a file system and a terminal, which runs in Cursor's cloud, and you sign in with a Cursor account 3, 13. SpaceX's purchase of Cursor closed on 14 August 2026, according to third-party reporting 14. Grok Bot is included with paid individual Cursor plans and the Cursor Teams plan, or through a linked SuperGrok subscription, and usage resets weekly 3, 15.
1. Your own model plan
How Grok Bot does it
Grok Bot does not offer a choice of model. Its docs say Cursor manages model selection, so there is no model picker, and that the serving mix can change over time with no fixed set of vendors guaranteed; usage analytics show which model served each request 6, 16.
Access comes through a paid Cursor plan or a linked SuperGrok plan, and the two do not stack 15. On SpaceXAI's pages, Cursor Pro costs $20 a month and SuperGrok $30 a month 17, 18. On-demand usage beyond the plan is billed from model and token cost 3. The docs describe no way to run Bots on a Claude or ChatGPT subscription 6, 15.
How Kavela does it
Kavela runs on your choice of plan, agent by agent. With your own Claude plan, the unmodified Claude Code runs inside the agent's own cloud computer and you sign in to it yourself; with a ChatGPT plan, the agent can run Codex instead. Anyone who has neither uses Kavela's included Kav AI usage.
Because the choice is per agent, one team can mix Claude and Codex agents, and you always know which plan each agent runs on.
When you choose each agent's model and plan, you know what every agent runs on and which bill it lands on.
2. Managing a team of agents
How Grok Bot does it
Grok Bot is built for many agents at once. Bots can message each other and share context in threads, and in group chats of two to six Bots they pass work, assign ownership and pull you in only for judgment calls 1, 7. Since mid-September 2026 a Bot can start a Project, a Cloud Agent that plans the work and runs its own agents, and telling a Bot to stop also stops the Bots and Cloud Agents it handed work to 5.
The lead agent is a pattern you set up. SpaceXAI says people inside the company often run one Bot to manage the others, a chief of staff on top with a specialist for each lane 1, and since 2 October 2026 your primary Bot, marked with a star, spots work it can take off your plate and offers to handle it 5. SpaceXAI chose not to build dashboards or assignment boards, because each one gave the user more coordination work 2. In an official guide, the author tracks each project for a Manager Bot in a Notion database of their own, and calls it an experimental pattern 19. Routines are listed per Bot with their run history; the docs describe no calendar of Bots' tasks 8.
How Kavela does it
In Kavela the lead agent comes with the workspace. You tell Kav what you want, in the workspace chat or in Telegram, and Kav plans it, hands each part to the right worker agent, follows up and brings back the result. The workers are a standing team: named agents with their own skills, connected apps and run history, and you can hire a new one by describing the job.
Every task from every agent sits on one calendar, by day, week or month, with its start time, due time and live state, so you can see what is scheduled, what is running, what needs you and what is done without building a tracker of your own.
Grok Bot leaves the manager and the tracker to a pattern you build; Kavela starts with both, so a new team is organised from its first task.
3. Agents that can sign up for things
How Grok Bot does it
Grok Bots handle email through your own connected Gmail or Outlook. They write drafts, send, send from a verified Gmail send-as address and search your spam folder 5, 7. A mockup in SpaceXAI's design post shows a draft sent from a grokbot.app address, but the docs describe no mailbox that belongs to a Bot 2, 7.
For sites that need a sign-in, Bots use the browser on the shared computer, where sign-ins persist and are shared across Bots, along with 1Password on Mac and in-chat Secure Forms for login and checkout fields 11, 5. Bots can also make purchases through a Link wallet once you approve a card showing the amount 5.
How Kavela does it
Every Kavela workspace has its own receive-only inbox, Kavela Mail. When an agent signs up for a service on your behalf, it uses a fresh sign-up address from that inbox, waits for the verification email, reads the code or the link and carries on. The wait shows in Approvals. A workspace can hold up to 10 live sign-up addresses at once, each address lasts 24 hours, and received mail is deleted after 30 days.
With a live browser sign-in for the services that need one, agents can create the accounts a job requires and set those services up, and each verification email lands in the workspace's inbox, apart from your personal mail.
An agent working from your Gmail signs up as you. An agent with its own sign-up address can get through verification without going through your personal mail.
4. What agents need, and what they deliver
How Grok Bot does it
Grok Bot has a detailed set of typed requests. A Review an action card offers Allow once, Always allow, which saves a rule, and Deny, and Auto Review rules set what to ask about first and what to allow automatically 4. There are also purchase approvals, email and Slack drafts with Send and Discard, masked secret requests that are not shown to the model, Secure Forms, multiple-choice questions and reconnect cards 5, 7, 4.
Each request appears in the chat of the Bot that raised it, and a notification tells you when a Bot is waiting for you 5. Approvals, secret and login requests and drafts do not appear in group chats 7, and approvals raised by routines or by other Bots expire after about 10 minutes 4. Results appear as cards in the conversation and in each Bot's Library tab 20, 5. The docs describe no single inbox that collects requests from every Bot 4, 7.
How Kavela does it
Kavela uses typed cards too, and collects them into one Approvals inbox for the whole workspace. Each request is a card you answer where it is: connect an app, sign in to a site in a live browser, approve an action such as a post before it goes out, choose between options, or let an agent know the email it was waiting for has arrived. Other work carries on while a card waits.
What agents produce arrives as deliverables attached to the task that made them, from documents and reports to sites and files, listed under Delivered and opened in one click.
Both products use typed cards. With every agent's cards in one inbox, checking on ten agents is one visit instead of ten chats.
5. Many agents, running on schedule
How Grok Bot does it
Every Bot on an account uses one persistent cloud computer and shares its files, browser sessions and logins. The docs say the computer is assigned per user, and that separate Bots should not be used as a security boundary 9, 17. Each Bot gets its own screen on that computer and runs one computer-use task on it at a time 3. Coding work can go to Cursor Cloud Agents, which run on separate computers 21.
Routines belong to one Bot and run on a schedule or on an event from Slack, GitHub, Linear, Sentry, PagerDuty, Microsoft Teams or a webhook. A Bot can own up to 50 routines, schedules must be at least five minutes apart, and the app keeps the last 20 runs 8. Each routine's runs open in their own chat 5, and you can teach a Bot a workflow by recording up to ten minutes of browser work 8.
How Kavela does it
In Kavela each agent session works in its own cloud computer, with a shell, files, git and a browser, which starts when work starts and sleeps when it stops. One agent's work never slows another's, and work keeps going after you close the tab. The workspace's files persist between runs, so tomorrow's run starts from today's output.
Automations run on a schedule or on an event, such as a webhook or a merged pull request, and can be limited to an active window with start and end dates. There is no cap on how many are switched on at once.
On a shared computer, every Bot's work lands on one machine. With a computer for each agent session, one agent's work never slows another's.
6. Connecting your tools
How Grok Bot does it
Grok Bot connects broadly. Connect Apps offers plugins that sign in with OAuth or take a key or token, plus custom MCP servers, and a Team Bot can hold up to 25 secrets, encrypted and redacted from output 10. Browser sign-ins persist and are shared across Bots, 1Password works on Mac, and hardware security keys are supported 11, 5, 4.
Bots also start connections themselves. When a Bot asks you to connect an app in chat, it resumes the task on its own once you finish signing in, and a repository card connects GitHub, GitLab, Bitbucket or Azure DevOps 5.
How Kavela does it
Kavela connections belong to the workspace: connect a service once and every agent can use it. A service can be connected by OAuth sign-in, as an MCP server, with an API key, with custom secrets, or by signing in to it in a live browser you control. Passwords and keys go into the card, never through the model.
You can also leave it to the agent. With Let Kav set it up, the agent reads the service's documentation, works out the right way to connect it and does the setup, creating the account first if there is none.
Connections are well matched here. Kavela's added step is an agent that can create a missing account and work out the setup from the service's own documentation.
Where Grok Bot is the better choice
Grok Bot is the better choice if you want persistent Bots that each keep their own memory and role 2, talk to each other 1 and work alongside your teammates in Slack 10. Its approval and secret handling is detailed, with saved rules, Auto Review, masked secrets and hardware security keys 4, and a Bot can learn a workflow by watching you do it 8.
It changes quickly, with more than 30 releases between 12 August and 7 October 2026 5. If you already pay for an individual Cursor plan, Cursor Teams or SuperGrok, Grok Bot is included 3, 15.
Conclusion
Of the cloud agent products we compared, Grok Bot is the closest to Kavela's idea of a team: named agents that hand work to each other, with typed cards for what they need. The differences are narrower than with most products. Kavela starts with a lead agent, a calendar of every task and one Approvals inbox across every agent, where Grok Bot leaves the manager and the tracker to a pattern you set up and keeps each request in its Bot's chat. Kavela also gives each agent session its own cloud computer, where all Bots share one, and runs on the Claude or ChatGPT plan you choose.
If you already work in Cursor or SuperGrok and want a few persistent Bots alongside your team in Slack, Grok Bot fits. If you want a team of agents run by a lead, on one calendar, with one place to answer them, use Kavela.
Questions
Can I choose the model Grok Bot uses?
No. Cursor manages model selection for Grok Bot, and there is no model picker. In Kavela you choose per agent: Claude Code on your Claude plan, Codex on your ChatGPT plan, or the included Kav AI usage.
Does each Grok Bot get its own computer?
No. All Bots on an account share one persistent cloud computer, including its files, browser sessions and logins, and SpaceXAI advises against using separate Bots as a security boundary. In Kavela, each agent session works in its own cloud computer.
Does Grok Bot have a main agent that manages the others?
Not as a built-in role. SpaceXAI describes a pattern where you set up one Bot as a chief of staff, and your starred primary Bot can offer to take on work. In Kavela, Kav is the lead agent from the start, and every task sits on one calendar.
Where do Grok Bot's approval requests appear?
In the chat of the Bot that raised them, with a notification when a Bot is waiting. Kavela collects every agent's requests into one Approvals inbox for the workspace, as typed cards.
References
- Introducing Grok Bot, SpaceXAI, 11 August 2026.
- Designing Grok Bot for a world of persistent agents, SpaceXAI, 3 September 2026.
- Overview, Grok Bot docs, accessed 9 October 2026.
- Approvals, security, and privacy, Grok Bot docs, accessed 9 October 2026.
- Grok Bot changelog, SpaceXAI, entries 12 August to 7 October 2026.
- Settings and notifications, Grok Bot docs, accessed 9 October 2026.
- Message and collaborate, Grok Bot docs, accessed 9 October 2026.
- Skills and routines, Grok Bot docs, accessed 9 October 2026.
- FAQ, Grok Bot docs, accessed 9 October 2026.
- Team Bots, Grok Bot docs, accessed 9 October 2026.
- Use the computer and apps, Grok Bot docs, accessed 9 October 2026.
- xAI joins SpaceX, SpaceXAI, 2 February 2026.
- Get started, Grok Bot docs, accessed 9 October 2026.
- Cursor (company), Wikipedia (third-party), accessed 9 October 2026.
- Grok Bot plans and billing, Cursor Help, accessed 9 October 2026.
- Grok Bot security, Grok Bot docs, accessed 9 October 2026.
- Grok Bot product page and FAQ, SpaceXAI, accessed 9 October 2026.
- Compare Grok plans, SpaceXAI, accessed 9 October 2026.
- How I run multiple teams of Grok Bots, SpaceXAI guides, 27 August 2026.
- Files and results, Grok Bot docs, accessed 9 October 2026.
- Teams and enterprises, Grok Bot docs, accessed 9 October 2026.
Checked 9 October 2026. Products change; tell us if something here is out of date.