2026-08-27 · Comparison
Grok Bot vs Devin: A Teammate Product Against a Coding Agent
The outage channel wanted a patch, the support inbox wanted a reply, and grok bot vs Devin treated both as one hire.
They are not one hire. Grok Bot is a named cloud teammate for standing ops: mail, briefings, clocks, a charter with a stop line. Devin is Cognition's software-engineering agent. Confirm every Devin verb, price, sandbox claim, and merge behaviour on Cognition and Devin docs the morning you rely on it. Recaps disagree. This page will not freeze Devin claims. Grok Bot facts were checked against the Grok Bot FAQ as of 25 August 2026.
Devin is not a Grok Bot SKU, not Grok Build, and not grok-4.6. SpaceX acquired xAI (announced 2 February 2026) and closed the Anysphere/Cursor deal (14 August 2026). That story does not purchase Cognition. A Cursor login that unlocks Grok Bot does not unlock Devin. Grok Bot does not merge pull requests as the ops product you bought. Grok Bot does not read SKILL.md.
Worked example: a founder who wants one bot to fix a production pay-page bug and triage the mail that bug created. Split the products. Mail stays on Grok Bot. The patch stays on a coding agent you confirm on Cognition, a human, or Cursor Background Agents. Click-path evidence stays on bug reproduction. Skill files stay on Grok Build.
Split grok bot vs Devin on standing ops work versus a software-engineering agent
Grok Bot vs Devin is mail and ops versus software engineering. It is not two brands for the same autonomous engineer, and it is not two doors into the same cloud computer.
Grok Bot is the product in What is a Grok Bot. You name a bot, brief it, connect tools, attach routines. It sits on a managed Linux VM assigned to your user account, not to a bot. Each bot gets a screen. Screens are not security boundaries. That is a standing teammate for work that still exists next Tuesday.
Devin is a Cognition product. Recaps call it an AI software engineer or a coding agent. Some describe pull requests, sandboxes, or a desktop app. None of that is a Grok Bot fact. Open Cognition. If the page says software engineering, believe the page. If it has added mail, believe the page then.
| Job you actually have this afternoon | Product that owns it | What you must not pretend |
|---|---|---|
| Standing mail, vendor threads, overnight buckets | Grok Bot. Start with Inbox Triage | That Devin is the Grok Bot catalog |
| Click the failing pay path, screenshot, write steps | Grok Bot reproduction desk. See bug reproduction | That screenshots are a merge |
| Clone, test, open a patch | A software-engineering agent you confirm on Cognition, a human, or Cursor Cloud Agents | That Grok Bot merge is the job |
| Local skill files, CLAUDE.md, grok CLI | Grok Build. See Grok Bot vs Grok Build | That Bot reads SKILL.md |
If the work still has an inbox after the laptop lid closes, you wanted Grok Bot. If the work is a software-engineering agent you will confirm on Cognition, you wanted Devin. If you wanted both, you wanted both, with two briefs.
Keep Grok Bot as a named cloud teammate that cannot own a production merge
Grok Bot launched in beta on 11 August 2026. Eligibility widened on 21 August 2026. Platforms: macOS (Apple silicon and Intel), Windows (x64 and Arm64), Linux (x64 and Arm64), and iPhone (iOS 18 or later) or Android (9 or later) phones. iPad runs the iOS app. The computer is a managed Linux VM. The Bot is a non-root user on that VM, not a Linux desktop app. See supported platforms.
All bots on the account share one persistent cloud computer. Cookies, sessions, files, and CLI credentials are shared. Deleting a bot does not remove those files or sessions. Do not use separate bots as a security boundary. One computer, many screens and least privilege are the isolation and grant articles.
No model picker, for members or admins, and none is planned. No Grok Bot-specific spend cap, only the account-level On-demand monthly limit. Weekly allowance, then on-demand from model and token cost. No public dollar figure exists. Do not invent one. See spend cap and token burn and Grok Bot cost. No audit view of Bot actions outside Enterprise. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer.
Routines attach to one Bot, max fifty, with twenty recent run records, and they die when the bot is deleted. Nothing is team-level. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it.
Grok Bot can drive a browser. If you signed GitHub into the shared computer, a bot could open a pull request or click merge unless the charter and approvals stop it. State the rule in the brief: Bot does not merge PRs. Approvals do not reverse a merge already clicked. Keep git write off this computer. If you needed an isolated repo job, you wanted a coding agent, not a second Grok Bot named fixer.
Inbox Triage sorts and drafts and never sends. Mail Cleanup Assistant drafts a purge list and still does not send. Chief of Staff Briefing writes a pack and leaves it in a file. None of those jobs is land a production patch.
Reconfirm Devin on Cognition before you copy any autonomous-engineer recap
This article will not print a Devin price, concurrency cap, VM size, plan SKU, ACU rate, or git-host list. Roundups disagree. Cognition's enterprise docs have discussed Agent Compute Units billed per an order form. That is a pointer, not your invoice.
Confirm Devin on Cognition's current page and docs.devin.ai. Confirm whether a human still approves a pull request, whether a session is isolated, and whether mail is in scope. If a tweet said Devin lives in your Grok Bot screen, that tweet invented a SKU.
Do not import Grok Bot language onto Devin. Do not write that Devin uses the Grok Bot computer, that a Grok Bot screen is a Devin session, that deleting a Grok Bot cleans a Cognition workspace, or that a Cursor Pro+ invoice includes Devin.
Do not import Devin recap language onto Grok Bot. Sandboxed per-task VMs, if a recap claimed them, are a Cognition claim to recheck. Recaps that say Devin submits pull requests do not add a Grok Bot merge feature. Grok Bot still does not merge PRs as the ops product.
Hedge the noun too. People say Devin when they mean Cursor Cloud Agents, Grok Build, or a human intern. Ask which vendor login they used this morning. Cognition SSO means Devin. grok-bot inside Cursor or SuperGrok means Grok Bot. The grok CLI means Build.
Follow the founder who wanted one bot to patch checkout and empty the mailbox
Rafi runs a twelve-person shop. At 07:40 the pay page starts returning 409 on the second Apple Pay tap. The first tap fails. The second looks like a double charge. It is not. Support mail fills with "I was charged twice." Vendor mail still arrives.
Rafi searches grok bot vs Devin and tries to buy one worker: fix production, and triage the mailbox that the bug created. Those are two jobs. They want two products.
If he pastes one Grok Bot charter that says "patch checkout and handle the inbox," the shared computer will hold a Gmail session and a GitHub session on the same disk. Inbox Triage was never the merge tool. Split it on Tuesday morning, not on Friday after the merge.
Mail belongs on a named Grok Bot. Paste Inbox Triage or Mail Cleanup Assistant. Boundary: never send. Never open git. If a thread is a charge dispute, bucket it and write the sentence a human should send. Leave it unsent. Grok Bot and Gmail is the mail door.
The failing click-path belongs on a Grok Bot reproduction desk if you need screenshots. That bot loads staging, taps twice, captures the 409, and stops. It never opens a pull request. That desk is bug reproduction, not Devin, and not Inbox.
The patch belongs on a software-engineering agent you confirm on Cognition, a human with branch protection, or Cursor Cloud Agents if that is the repo job you already have. Confirm Cognition before you tell the team Devin will open the PR. Grok Bot does not own that sentence.
By day thirty the mail bot still has at most twenty recent run records per routine, and those records die if Rafi deletes the bot. The Gmail session is still on the shared computer. Do not file Devin usage as a Grok Bot weekly allowance. Do not file a missed merge as an Inbox outage.
Friday check: Did the mail bot send. It must not have. Did anything merge from the Grok Bot computer. It must not have. Did a SKILL.md in the payments repo change Inbox behaviour. It must not have. If any answer is wrong, he mixed the products.
Rank job kind, persistence, and merge rights before you rank brand names
Feature dumps go stale on the Cognition side. Score grok bot vs Devin on axes that survive a recap.
| Axis | Grok Bot (docs.x.ai, checked 2026-08-25) | Devin (confirm Cognition today) |
|---|---|---|
| Job | Named ops teammate: mail, briefings, routines, standing work after the lid closes | Software-engineering agent per current Cognition copy. Recheck scope |
| Machine | One persistent cloud computer per user. Screens are not isolation | Confirm sandbox, session, and retention language on vendor docs |
| Merge | Not the product job. Charter never-merge. Bot does not merge PRs | Confirm whether a human still approves every pull request |
| Identity | Cursor or SuperGrok plan check. See why Grok Bot needs a Cursor account | Cognition account. Not a Grok Bot SKU. Not included by that Cursor door |
| Skill files | Does not read SKILL.md, CLAUDE.md, or AGENTS.md | Confirm Devin's own config story. Do not paste Bot docs into it |
| Audit | No audit view of Bot actions outside Enterprise; Enterprise has audit logs and Action Recording | Confirm whatever log Cognition currently ships |
A sixth axis is model choice. Grok Bot has none, and none is planned. Recheck Devin model options on Cognition. Overnight mail is a Grok Bot job because scheduling attaches to one named bot and the computer stays up when the laptop sleeps. That is not a reason to let that same bot own production git.
Pay Grok Bot from the published eligibility list, then ask Cognition about Devin
Grok Bot eligibility is published. Devin pricing is not a Grok Bot fact. Do not add them on one spreadsheet line as if they were two SKUs of one vendor.
| Door, checked 25 August 2026 | Grok Bot | Devin |
|---|---|---|
| Cursor Pro at $20 | Included. Cheapest documented paid individual door | Paid Cursor is not Cognition. Confirm both vendors |
| Cursor Pro+ at $60 | Included, with more weekly usage than Pro | Not a Devin SKU. Confirm Cognition separately |
| A self-serve Cursor Teams seat | Included for every member | Team Devin, if offered, is Cognition admin work. Recheck |
| SuperGrok Plus | Included once linked | SuperGrok is not Cognition |
| SuperGrok Heavy | Eligible. Price unpublished. Do not print one | Still not Devin |
Privacy Mode (Legacy) blocks Grok Bot. An individual SuperGrok subscription can be linked for usage instead. Cursor Hobby, the free plan, does not include Grok Bot; Cursor Pro at $20 does, and so does Cursor Ultra at $200. A one-time trial is an individual Grok Bot path, not a Devin trial unless Cognition says so. The interesting row is still Pro at $20: paid Cursor, Grok Bot included since September, and still no Devin unless you bought Devin. If finance wants one AI line item, they can still receive two invoices. SpaceX does not bill Cognition. The Grok Bot safety checklist is the sequence before a mailbox, not a Devin onboarding doc.
Measure Grok Bot risk on the shared account computer, not on a Cognition workspace
Grok Bot blast radius is the shared computer. If Inbox is signed into Gmail, every other bot on the account can reach that session. If someone signed GitHub in to "just look at the 409," that session sits next to the mailbox. Treat the computer as hostile. Limit plugins and approvals.
Deleting Inbox does not sign Gmail out. Deleting a bot named Fixer does not delete /workspace. Signing out of grok.com does not sign the Bot computer out of anything. Each logout is local to its object.
Devin blast radius is whatever Cognition currently documents for a session, a repo grant, and a network policy. Recheck. Do not claim the Grok Bot VM is sandboxed like a Devin recap. Do not claim a Devin session shares Grok Bot cookies. If Rafi connects GitHub in the Grok Bot browser, that is not a Cognition sandbox. Prefer keeping git write off the Bot computer. Churn Watch and Inbox on the same account are two screens, not two machines. A second name is not a security domain.
Write the mail brief so git verbs are out of scope before the first unread thread
The boundary belongs in the brief, not in a file Grok Bot does not read. Rafi pastes this into the Grok Bot, not into a repo, not into SKILL.md, and not into a Devin task box.
Name: Inbox Only, No Production Patch
Job: Triage inbound mail for four hours of unread while a human or a
coding agent you confirm on Cognition handles the pay-page 409.
Scan unread mail. Bucket into action, wait, and noise. For charge-dispute
threads, note the order id if present, write the sentence a human should
send, and leave it unsent. For vendor mail, bucket only. For the
partnership thread, draft and stop.
Boundary: Never send. Never open GitHub, GitLab, Bitbucket, or Azure
DevOps. Never comment on a pull request. Never clone, push, merge, or
approve. Never click merge. Bot does not merge PRs. Never start Devin,
Cursor Cloud Agents, or Grok Build. If mail asks for a patch, write
"human, this is a software-engineering job" in the digest and stop.
If you lack mailbox access, say so. Do not open extra tabs to look
helpful. Do not read SKILL.md, CLAUDE.md, or AGENTS.md. Those files
are not your interface.
That charter is the product split in pasteable form. Standup Scribe can sit on a second bot on the same computer, which means it shares sessions with Inbox. Do not use that second bot as a wall. If the scribe must not see Gmail, do not sign Gmail in on that computer.
The patch side of Rafi's morning does not get a Grok Bot charter unless he wants an attention summary of a diff he showed it, with merge forbidden. That is still Grok Bot. It is still not Devin. It is still not SKILL.md.
Leave SKILL.md on Grok Build so neither Bot nor a Devin recap inherits it
Claude Code compatibility, SKILL.md, CLAUDE.md, AGENTS.md, and the grok CLI are Grok Build. The Bot docs never mention those files. Do not say Grok Bot reads SKILL.md. Do not say a Devin task applies a Grok Bot charter. Do not say a Cursor login applies a repo skill file to Inbox.
If a tweet said "Grok is compatible with Claude Code," that sentence belongs on the Build page. Grok Bot vs Grok Build vs Grok 4.6 keeps the three Grok objects apart. Bot does not read SKILL.md, even if the payments repo is full of skills, even if you also bought Devin.
Devin may have its own instruction files. Confirm that on Cognition. Do not assume it is SKILL.md or a Grok Bot charter. Bug triage is still a Grok Bot listing when the job is rebuild a ticket, not land a fix.
Diagnose the outage where mail still arrived and the patch never opened
Most grok bot vs Devin failures are filing errors. The symptom is real. The noun is wrong.
| Symptom | Cause if you mixed the products | What to check first |
|---|---|---|
| Inbox never opened a pull request for the 409 | Inbox is a mail teammate. Bot does not merge PRs | Cognition session, a human branch, or Cursor Cloud Agents |
| Devin asked about unread vendor mail | You briefed a coding agent as if it were Grok Bot | Move mail to a named Grok Bot. Confirm Devin scope on Cognition |
| Grok Bot ignored SKILL.md in payments-api | Expected. Bot does not read that file | If you needed skill files, you wanted Grok Build |
| Hobby user cannot start Grok Bot | Hobby does not include Grok Bot | Invoice spelling. Pro or another eligible plan. Trial |
| Deleted Grok Bot, Gmail still signed in | Deleting a bot does not clean the computer | Sessions and files on the shared VM. Not a Devin workspace |
From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Do not expect that client to be a Devin dashboard. Restarting Grok Bot will not unstick a Cognition session.
Answer the claim that an AI software engineer should also run the inbox
The strongest objection is honest: if Devin is an agent with a computer, it can open Gmail. If Grok Bot can click a browser, it can open GitHub. Why pay two vendors. Why split grok bot vs Devin when both are "teammates."
Because the products you can actually buy still diverge. Grok Bot is a named ops roster on one persistent account computer, with routines, plugins, a catalog of mail jobs, and a required stop line. Devin is Cognition's software-engineering agent. Confirm that on Cognition. SpaceX owns the Grok Bot story. Cognition owns Devin. Sharing a metaphor does not merge the machines, the invoices, or the merge rights.
The objection wins in two clean cases. If Rafi only writes code, he can skip Grok Bot. If he only wants overnight mail, he can skip Devin and still need an eligible Grok Bot plan. He should not skip the split inside one charter.
What the objection does not win: turning Devin off will not make Inbox merge the 409 fix. Turning Grok Bot off will not move Gmail onto a Cognition workspace you have not verified. If Cognition later documents a standing named mail teammate that matches Grok Bot, believe Cognition that day. As of the Grok Bot docs checked 25 August 2026, Devin is not a Grok Bot SKU.
Prove the split with checks that fail if the mail bot opened a pull request
Verification has to be able to fail. If every check is that a login worked, you learned nothing.
Name a Grok Bot and confirm you see a screen. If you cannot, you do not have Grok Bot yet. Check the invoice against the eligibility list. Check Privacy Mode (Legacy). Check platforms. A Linux desktop and an Android phone have been Grok Bot clients since September 2026, so an old OS version is the usual miss, not the brand.
Open Cognition, or the Devin product URL they currently publish, and confirm you are on that vendor. If that UI is missing, you do not have Devin. Do not call that a Grok Bot outage.
Drop a SKILL.md into the payments repo that says the mail bot must send. Run Inbox. If Inbox sends because of that file, something is badly wrong. If Inbox ignores the file, that is expected. Build reads skill files. Bot does not.
Ask Inbox to open a pull request for the 409. It should refuse if the charter above is in force. If it opens GitHub and merges, the boundary failed. Bot does not merge PRs. An approval does not rewind that merge. Ask a Devin task, if you have one, to archive a Gmail label. If it can, you handed a mail grant to a coding agent. Undo that unless Cognition's current page says mail is in scope.
Friday checks: sent mail from Inbox, fail. Merge from the Grok Bot computer, fail. Devin usage filed as Grok Bot allowance, fail. SKILL.md changing Inbox, fail.
Point the production click-path at bug reproduction, not at a merge
Rafi still needs evidence. A fluent guess that Apple Pay retries are idempotency bugs is not a packet. A Grok Bot that loads staging, taps twice, and writes STEPS.md is a packet. That is the reproduction desk, not Devin, and not Inbox.
The reproduction bot stops at the 409 frame. It does not open a small PR. Small PRs from the mail computer are still git write from the mail computer. A Grok Bot that reproduces bugs and never merges and bug triage sit on the Grok Bot side of grok bot vs Devin.
Cursor Cloud Agents, currently documented as the rename of Background Agents, are a third coding surface. They are not Devin and not Grok Bot. If Rafi already pays Cursor and wants an isolated repo job, read Grok Bot vs Cursor Background Agents and confirm Cursor's Cloud Agent overview.
Three coding nouns, one ops noun. The ops noun is Grok Bot. The coding nouns are Devin (Cognition), Cloud Agents (Cursor), and Grok Build (CLI and skills). Pick with the job, not with the search phrase.
Keep the mail teammate and the coding agent both hired, with two briefs
You do not have to pick a winner if you have both jobs. Grok Bot holds standing ops that is not a branch. Devin, if you buy it, holds software-engineering work you confirmed on Cognition. Cursor Cloud Agents, if you use them, hold repo jobs on Cursor's current terms. Grok Build holds local skill files.
When the 409 and the dispute mail land at 07:40, Inbox drafts and does not send. Reproduction, if you staffed it, captures the tap. The coding agent, or a human, owns the patch. Rafi does not wait for one worker to become the other. He reconfirms Cognition whenever he repeats a Devin price or capability, because those pages move.
Keep reading: Grok Bot vs Cursor Background Agents: Two Products, One Account, Grok Bot vs Grok Build vs Grok 4.6: Three Products, One Name, A Grok Bot That Reproduces Bugs and Never Merges the Fix.
Frequently Asked Questions
Is Devin a Grok Bot SKU or another Grok product?
No. Devin is Cognition's product. Confirm what it currently sells on Cognition's site and docs. Grok Bot is the named teammate on a persistent cloud computer assigned to your user account, sold through eligible Cursor and SuperGrok plans. SpaceX acquired xAI and later closed the Cursor acquisition. That does not purchase Cognition and does not make Devin a Grok Bot SKU, a Grok Build CLI, or a grok-4.6 nickname. Sharing the word teammate in marketing copy does not merge vendors. Treat a roundup that lists Devin under Grok Bot as a filing error until the vendor pages agree.
Can Grok Bot merge a production fix the way a coding agent might?
Grok Bot does not merge PRs as the ops product you hired. Put never-merge in the charter. Keep git write off the shared computer. The Bot can drive a browser, so a GitHub session you signed in could still click merge unless the brief and approvals stop it. Approvals do not reverse a merge already clicked. For isolated repo work, confirm Devin on Cognition, or use a human with branch protection, or confirm Cursor Cloud Agents. Do not wait for Inbox Triage to land a patch. Click-path evidence belongs on the reproduction desk, which also never merges.
Does Grok Bot read SKILL.md because you also run Devin?
No. Claude Code compatibility, SKILL.md, CLAUDE.md, and related local files are documented for Grok Build, not for Grok Bot. The Bot docs do not mention those files. Buying Devin does not import a repo skill file onto the named teammate. A Cursor login does not either. If a tweet said Grok is compatible with Claude Code, that sentence belongs on the Build page. Paste a Bot charter in prose, with a boundary. Confirm Devin's own instruction format on Cognition. Leave skill files on Build.
Should you drop Devin if Inbox Triage already runs on Grok Bot?
Only if you do not want a software-engineering agent. Inbox Triage is mail. It never sends, and it is not a merge tool. Turning Devin off will not make the mail teammate open a pull request. Turning Grok Bot off will not move Gmail onto a Cognition workspace. If you have both jobs this afternoon, keep both, named, with two briefs, and confirm Devin on Cognition before you budget it. If you only wanted standing ops, skip Devin. If you only wanted a coding agent, skip Grok Bot and still do not treat Devin as a Grok Bot SKU.