afka uses analytics cookies to see how visitors use the site, and a service that can identify the company a visitor works for. We do not sell your data. Decline and none of it loads.
Grok Bot, from xAI and delivered through Cursor, gives each person AI Bots that work on a computer in the cloud and talk to that person in the Grok Bot app. afka is one AI for the whole workspace, inside six team chats: Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp. afka also joins meetings and keeps an audit log on every plan. This page compares where the conversation happens, who the AI works for, tool access, isolation, approvals, audit, meetings, the work covered and price.
Last verified 16 September 2026, against the public pages of xAI and Cursor.
Grok Bot is a product from xAI, delivered through Cursor, and Grok Bot launched in beta on 11 August 2026. Cursor documentation says that each Bot works on a persistent computer in the cloud with a browser, files and a terminal, and a person talks to the Bots in the Grok Bot app on desktop or iPhone.
Choose Grok Bot when one person wants several Bots that operate websites and apps on a computer of their own.
afka is one AI that the whole workspace hires, and afka works in six team chats: Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp, plus the web dashboard. Support, sales and RevOps, recruiting and e-commerce are capabilities of that one AI. afka also joins meetings on Zoom, Google Meet and Microsoft Teams.
Choose afka when a team wants one AI that every member can address in the chat the team already uses, with a record of every action.
Last verified 16 September 2026, against the public pages of xAI and Cursor.
| Topic | afka | Grok Bot |
|---|---|---|
| Where you talk to the AI | Six team chats: Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp, plus the web dashboard. afka answers in the thread where a person asked. | One app: the Grok Bot app on desktop and iPhone. Slack is available to a Bot as a plugin and as a trigger for a routine. |
| Who the AI works for | The whole workspace. Every member can address the same AI. | One member. Bots act as the signed-in person and never hold more access than that person. |
| Where the work runs | The afka platform, with sandboxed execution and connections to your tools. | A persistent computer in the cloud with a browser, files and a terminal, hosted by Cursor in the United States. |
| How the AI reaches your tools | Connections through Pipedream Connect. afka never receives your passwords, and once a person disconnects a tool, the next step that needs that tool stops. | Plugins and MCP servers shared with Cursor, with OAuth tokens held by Cursor, plus computer use through the signed-in browser sessions of the member. |
| Isolation | Per workspace, separated at the database layer. | Per person. Each person has a dedicated, hardware-isolated computer, and all Bots of that person share it, including files, browser and logins. |
| Approvals | Three modes per agent: Suggest, Review and Auto. In Auto, afka does the work and asks a person only before money goes back to someone, such as a refund, or before a decision against a person, such as rejecting a candidate. In Review, afka asks before it acts. Every action is recorded. | Allow once, Always allow and Deny on proposed actions, plus Auto Review, an AI reviewer that follows rules written in plain language. Cursor documentation says Auto Review does not check every side effect. |
| Audit and admin controls | An append-only audit log on every plan: who asked, which agent acted, what data, what changed and why the action was allowed. | Audit logs, action recording, SCIM and network controls on the Enterprise plan, according to Cursor documentation. |
| Meetings | A meeting agent that joins calls on Zoom, Google Meet and Microsoft Teams. | Not described in the Grok Bot documentation as of 16 September 2026. |
| Security status | SOC 2 in progress. afka claims no certification today. | ISO/IEC 27001 and ISO/IEC 42001, held by Anysphere with Grok Bot in scope, according to Cursor documentation. |
| Price | Per workspace with unlimited seats: Team at $50 a month and Pro at $500 a month. A new workspace starts free with 10,000 credits and no card. | Included with paid Cursor plans, or through a linked SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, per person. Usage resets weekly, and extra usage is billed through Cursor. |
| The work it covers | Skills for support, sales and RevOps, recruiting and e-commerce in one AI, working through the tools the team already pays for. | General computer use: a Bot operates the websites and apps its person can sign in to, and can learn a routine by demonstration. |
afka reads and answers in the thread where a person asked, in Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp, and in the web dashboard, so nobody opens another app to hand work over. As of 16 September 2026, the Grok Bot documentation places the conversation in one place, the Grok Bot app, with Slack available to a Bot as a plugin and as a trigger for a routine.
afka belongs to the workspace, so every member can hand work to the same AI and read the same record. Cursor documentation says that Bots act as the signed-in member and never hold more access than that person, so each Bot works for one person.
Every afka action lands in an append-only audit log, and the log is part of every plan. Cursor documentation lists audit logs and action recording for Grok Bot as Enterprise features, and says that self-serve Teams do not get that log.
The main difference is where the work is directed: afka works inside the six team chats a company already uses, and Grok Bot works from its own app, on a computer in the cloud, for one person. afka is one AI for the whole workspace, with a meeting agent, skills for support, sales, recruiting and e-commerce, and an audit log on every plan. Grok Bot gives each person several Bots that sign in to websites and apps as that person.
As of 16 September 2026, the Grok Bot documentation describes no conversation inside Slack or Microsoft Teams: a person talks to the Bots in the Grok Bot app, and Slack is available to a Bot as a plugin and as a trigger for a routine. afka answers inside Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp, in the thread where a person asked.
afka connects to each tool through Pipedream Connect and never receives the passwords, and once a person disconnects a tool, the next step that needs that tool stops. Cursor documentation says that Grok Bot uses plugins whose OAuth tokens stay on the Cursor backend, and uses the signed-in browser sessions of the member for everything else, shared across all Bots of that member. For login, two-factor and payment steps, a Bot hands the computer back to the member.
Grok Bot is the better choice for some work, and this page says so plainly. The four cases below come from the public pages of xAI and Cursor.
Cursor documentation says that each Bot works on a persistent computer in the cloud with a browser, files and a terminal, and xAI says that Bots work in parallel around the clock. For work that lives in websites with no integration, that computer is a real advantage.
Cursor documentation describes Teach a task, where a Bot learns a routine by watching a person do the work, and notes that the feature is rolling out gradually. afka takes standing instructions written in the chat and quotes each one back before the instruction takes effect.
Cursor documentation says that the Grok Bot desktop app runs on macOS, Windows and Linux, and that the mobile app runs on iPhone. afka works inside the team chats and the browser a team already uses.
Grok Bot is included with paid individual Cursor plans and Cursor Teams, or through a linked SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, so many people already have access. Cursor documentation also says that Anysphere, the company behind Cursor, holds ISO/IEC 27001 and ISO/IEC 42001 certification with Grok Bot in scope. SOC 2 for afka is in progress, and afka claims no certification today.
Grok Bot is a product from xAI, delivered through Cursor, that gives a person AI Bots which sign in to tools, use those tools the way a person does, and return finished work. According to Cursor documentation, each Bot works on a persistent computer in the cloud, and a person talks to the Bots in the Grok Bot app on desktop or iPhone. Grok Bot launched in beta on 11 August 2026.
afka is one AI for the whole workspace, and afka works inside six team chats a company already uses: Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp. afka also joins meetings and keeps an audit log on every plan. Grok Bot gives each person Bots that work on a computer in the cloud and talk to that person in one app, the Grok Bot app.
As of 16 September 2026, the Grok Bot documentation places the conversation in the Grok Bot app, not inside Slack or Microsoft Teams. Slack is available to a Bot as a plugin and can start a routine. afka works inside Slack, Microsoft Teams, Google Chat, Zoom Team Chat, Discord and ClickUp.
Grok Bot is included with paid individual Cursor plans and Cursor Teams, or through a linked SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription; usage resets weekly, and extra usage is billed through Cursor. On 16 September 2026, the xAI page showed $20 a month for Cursor Pro, $30 a month for SuperGrok and $40 per seat a month for Cursor Teams. afka is priced per workspace with unlimited seats: Team at $50 a month and Pro at $500 a month, and a new workspace starts free with 10,000 credits and no card.
Yes. xAI announced Grok Bot for enterprises on 3 September 2026, with access, network and audit controls, and Cursor documentation lists audit logs, action recording, SCIM, network controls and enforced Auto Review as Enterprise features. afka includes an append-only audit log on every plan, and SOC 2 for afka is in progress.
Yes. xAI says that all Bots of one person share one persistent computer in the cloud, including files, browser and logins, so isolation is per person, not per Bot. Between people, Cursor documentation says that each computer is dedicated and hardware-isolated. afka separates each workspace at the database layer, and the audit log is scoped to the workspace.
Yes, both can, in different ways. Grok Bot offers Allow once, Always allow and Deny on proposed actions, plus Auto Review, an AI reviewer that follows rules written in plain language; Cursor documentation says that Auto Review does not check every side effect, and that admin enforcement of Auto Review is Enterprise only. afka has three modes, Suggest, Review and Auto, set per agent. In Auto, afka does the work and asks a person only before money goes back to someone, such as a refund, or before a decision against a person, such as rejecting a candidate; in Review, afka asks before it acts. Every action is written to the audit log.
Start free with 10,000 credits and no card, connect Slack or Microsoft Teams, and give afka a first task.