Grok Bot vs Devin is not two tools fighting over one job: Grok Bot runs errands across your apps and the web, while Devin writes, runs and tests code inside your repositories.
So the real setup question is which lane each agent gets, and which switches you flip before either one acts.
xAI's Grok Bot overview describes a proactive AI teammate with a real computer in the cloud.
Cognition's Devin introduction describes an autonomous AI software engineer.
Neither vendor publishes a comparison of the two, so everything below is my own reading of each tool's docs, checked on 7 November 2026.
If you want my team to sort the tasks in your business into the right lane, get your Backlink Gameplan, or try Polar Rank free for 3 days.
The split to settle before you install anything
Give Devin anything that should end as a pull request.
Give Grok Bot anything that ends as a sent email, a filled form, an updated sheet or a drafted post.
Grok Bot can still get code written, but it does that by handing the job to Cursor Cloud Agents, as How Grok Bot Works explains.
Devin can still browse the web, but its browser sits inside an engineering workspace built around your repos.
Hold that line and both setups stay simple.
Grok Bot vs Devin side by side
| Area | Grok Bot | Devin |
|---|---|---|
| Built for | Business tasks across apps, websites and files | Engineering work: tickets, bugs, features, pull requests |
| Where work runs | One persistent cloud computer per user in Cursor's cloud, with a screen for each Bot | A Linux VM per session, booted fresh from your saved snapshot |
| Sign-in | Your Cursor account | A Devin account, with repos connected through your Git provider |
| Where you talk to it | Desktop app on macOS, Windows and Linux, iOS, Android, X Chat, @bot on X, shared Bots in Slack | Web app, Slack, Microsoft Teams, Linear, Jira, GitHub comments, Devin CLI, Devin Desktop |
| Repeat work | Routines on a schedule or on Slack, GitHub, Linear, Sentry, PagerDuty, email or webhook events | Automations on Slack, GitHub, GitLab, Linear, Jira, Pylon, PagerDuty, schedule or webhook triggers |
| Reusable know-how | Saved skills in one private library for all your Bots | SKILL.md files in repos or on the Customize page |
| Guard rails | Auto Review, approval cards, Ask first rules | Repo access scope, PR review, per-call approval for Local Hands |
| Code | Delegated to Cursor Cloud Agents | Written, run and tested by Devin itself |
Every row traces to the vendors' docs; the grouping is mine.
Step 1: Sign in to Grok Bot and learn how the shared computer works
Install the Grok Bot desktop app and sign in with your Cursor account, as the Grok Bot FAQ describes.
On The X Subscription, Premium, Super and Ultra include it, per the same FAQ.
Now learn the machine.
Every Bot on your account works on one persistent cloud computer, and each Bot gets its own screen on it.
The Bots share that computer's files, browser sessions and logins, which is how they pass work along.
The FAQ says the computer is assigned per user, not per Bot, so separate Bots are no security boundary.
Plan around that from day one: if one Bot is signed in to a supplier portal, assume every Bot can reach it.
Step 2: Set Grok Bot's approval rules before the first job
Open Settings → General, find the Bot section, then open Custom Rules.
Describe actions in plain words, like "send an email" or "publish a post", and set each one to Ask first.
A matching Ask first rule always stops the action and shows an approval card, per Approvals, security, and privacy.
Auto Review is on by default and checks each action before a Bot runs a command, uses an app or acts on its computer.
Instructions hidden in an email or web page don't count as your request.
xAI adds that these checks lower the risk without removing it, so put Ask first on anything you can't undo.
One more switch matters: a card saved in the Vault fills in at checkout without asking.
Want to approve every payment? Leave the card out of the Vault.
🔥 Want the two-lane agent setup without the trial and error? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members wiring agents like these into real businesses. → Join the AI Profit Boardroom
Step 3: Connect Devin to GitHub and build its snapshot
Devin's setup starts with code access, not chat.
Under Settings → Connections, connect GitHub, GitLab, Bitbucket or Azure DevOps, as the environment setup docs describe.
On GitHub, pick Select repositories instead of All repositories unless you want Devin everywhere.
The GitHub integration page notes you must be an admin of the GitHub organization to create the connection.
Then configure the environment.
Devin works in a Linux virtual machine with your repos cloned, tools installed and dependencies resolved.
That configuration is saved as a snapshot, and each session boots a fresh copy.
Whatever changes during a session stays out of the snapshot, so every run starts from the same clean state.
Cognition calls environment setup the single highest-leverage step, so give it real time.
Windows and macOS snapshots are available if your app needs them.
Step 4: Switch on Computer Use and Slack for Devin
An organization admin turns on Computer Use in Settings → Devin, inside the Sessions section.
With it on, Devin gets a full desktop where it can click through your app, take screenshots and record its testing, per the Computer Use docs.
The docs list support for Linux, Windows and macOS sessions.
Next, open Settings → Connections → Slack and install the Devin app in your workspace.
Each person who wants to tag @Devin must click Link user profile once, the Slack integration guide says.
If linking fails, check that the Slack email matches the email on the Devin account.
Step 5: Write skills for both agents
Both tools say "skill", and both mean a reusable procedure.
On Devin, a skill is a SKILL.md file at .agents/skills/<name>/SKILL.md in a repo, or one written on the Customize page.
The Devin Skills guide says these follow the open Agent Skills standard.
Skills replace Knowledge and Playbooks, which Devin is phasing out, so write every new procedure as a skill.
After a session, Devin can propose a skill and offer a Create PR button to commit it.
On Grok Bot, get one task working first, then ask the Bot to save that method as a skill.
xAI's guidance says a useful skill covers when to use it, inputs and access, the sequence, how to validate, what to return and what needs approval.
Private skills live in a single library that every one of your Bots can use.
Step 6: Wire triggers, routines on one side and Automations on the other
A Grok Bot routine tells one Bot when to run a workflow.
It fires on a schedule, or on a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email or a webhook call, per Skills and routines.
A new routine waits for its next scheduled slot, so press Test to run it straight away.
A Devin Automation pairs a trigger with an action, plus optional conditions and a Preflight check.
That action can start a session, message a running session, run a Triage Devin on a Slack channel or send an email notification, per the Automations guide.
Both agents can listen to Slack, GitHub, Linear and PagerDuty, so give each event source to exactly one of them.
Two agents answering the same Slack message is the mess you're setting up to avoid.
Step 7: Decide who is allowed to touch code
Grok Bot's route into code is the Cloud Agents switch on the Grok Bot page of the Cursor dashboard.
It's on by default for the whole team, and delegated work runs on separate computers under your Cloud Agent controls, per Grok Bot for teams and enterprises.
When a Cloud Agent run finishes, the Bot attaches its files, and View PR opens the pull request if the run created one.
If Devin is your engineer, switch delegation off so code has a single owner.
If you skip Devin and only need the odd fix, leave it on and let Cursor carry the code.
I covered that Cursor lane on its own in Grok Bot vs Cursor.
📞 Not sure which agent should own which event? Get your Backlink Gameplan and my team will map your tasks, triggers and approvals with you, or try Polar Rank free for 3 days. Backlink Gameplan or try Polar Rank free for 3 days
Three small-business setups, step by step
A five-person web agency
- A client posts "contact form broken" in a shared Slack channel.
- A Devin Automation with a Slack trigger on that channel starts a session with the message attached as context.
- Devin reproduces the fault in its browser, fixes the code and opens a pull request on GitHub.
- A developer reviews the change and merges it.
- A Grok Bot drafts the client update email, and an Ask first rule holds it until you approve.
A plumbing firm with a booking website
- Grok Bot sorts the overnight inbox and drafts replies to new job requests.
- It reads the calendar and flags any double bookings.
- When the booking page throws an error, the office opens a Linear ticket and assigns it to Devin.
- Devin starts from the ticket and returns a pull request for the firm's contractor to review.
A small accounting practice
- A team of Bots runs the month-end close: one matches invoices to purchase orders, one reconciles expenses against receipts, one lists every mismatch.
- The partner signs off the exceptions list.
- Devin only enters the picture if the practice runs its own client portal that needs code changes.
The month-end team comes from xAI's use cases page; the agency and plumber setups are my own examples built from documented features.
Gotchas I'd plan around
- Grok Bot sign-ins spread: when one Bot signs in to a site, your other Bots are signed in too.
- Sign out of services a Bot no longer needs, and delete sensitive files once the job is done.
- Devin sessions started by Automations neither read nor write your personal memory, per the Memory docs.
- Devin's Secrets page recommends a dedicated login for Devin on each service, while a Grok Bot has no account of its own and acts as you.
- Devin's Local Hands lets a cloud session run commands on your own computer, with your approval for each tool call.
- Windsurf is now Devin Desktop, so older guides that mention Windsurf mean the same IDE.
- Skip broad Grok Bot listeners such as "every new message"; xAI warns they create noise and use up usage.
Which one to set up first
Set up Devin first if your backlog lives in Linear or Jira and someone on the team reviews pull requests.
Set up Grok Bot first if your day is inbox, calendar, documents, spreadsheets and websites with no API.
Run both if you carry a code backlog and an admin backlog, and hand each event source to one agent.
Neither one replaces the person who approves the send, the payment or the merge.
FAQ: Grok Bot vs Devin
Does Grok Bot write code itself?
It hands coding work to Cursor Cloud Agents, which run on separate computers, and attaches the results to its reply. Team admins can switch that delegation off.
Does each Grok Bot get its own computer?
No. All of your Bots share one persistent cloud computer, and each Bot gets its own screen on it.
What replaced Devin Knowledge and Playbooks?
Skills. Knowledge is deprecated and Playbooks are becoming Skills, and new Devin accounts have started with Skills and no Playbooks since 24 October 2026.
Can both agents run on a schedule?
Yes. Grok Bot uses routines with a schedule, and Devin uses Automations with a Schedule trigger.
What is Devin Desktop?
It is the new name for Windsurf from 2 June 2026: the same IDE, now with the Agent Command Center as the main view.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Install one agent, write its first approval rule today, and join the AI Profit Boardroom for the setups we run on both sides of grok bot vs devin.











