2026-08-27 · Comparison
Grok Bot vs Lindy vs Cowork: Three Ways to Hand Off Work
The labelled invoice in Gmail, the 07:15 inbox pack, and the CSV pile in Downloads are not one job with three steps. They are three handoffs, and stuffing all three into one Gmail workflow is how an ops person either double-sends a vendor reply or leaves Friday's close sitting next to the company mailbox cookies.
This is a three-way picker with Lindy as the third pole, not a remake of Grok Bot vs Claude Cowork vs ChatGPT Work. That page asks where the work lives, with ChatGPT Work in the third column. This page asks how you hand the work off: a workflow and agent product, a named cloud teammate, or a desktop-ish operator. Pairwise: Grok Bot vs Claude Cowork and Grok Bot vs Lindy. Start with What Is a Grok Bot? if you need the object.
Lindy and Cowork move. This page will not print their prices or freeze their feature lists as fact. Confirm Lindy on lindy.ai and Lindy pricing the morning you buy. Confirm Cowork on Anthropic's Cowork page. Grok Bot facts were checked on 2026-08-25, with plans rechecked on 2026-09-23, against the Grok Bot FAQ and computer and apps. Grok Bot: named bots on one persistent cloud computer. Screens are not vaults. Lindy, as currently presented: a workflow and agent product. Cowork, as Anthropic currently describes it: closer to a local and desktop operator. Confirm both. Then pick by the handoff.
Name the three handoff objects before you pick a vendor
Ask what object you are operating after you click buy.
Grok Bot is a roster of named bots on one managed Linux VM assigned to the user account, not to a bot. Cookies, sessions, files, and CLI credentials are shared. Deleting a bot does not remove them. See one computer, many screens.
Lindy is the column you re-read on the vendor. lindy.ai currently presents an AI teammate and a workflow and agent product: triggers, steps, connected apps, Gmail listed as a surface. Current docs describe a flow editor with a trigger, then actions, conditions, and agent steps. Recap, not a contract. Confirm the live object and the pricing page the morning you buy. Do not copy a connector count or a Lindy price from a roundup.
Cowork is the other hedged column. Anthropic currently presents it as the place you hand Claude real work. The product page still leans desktop for folders and apps on your own computer, and it also describes web, mobile, and cloud continuation. Confirm those on the live page. For this tree, treat Cowork as more local and more this disk unless the page in front of you says otherwise today.
| Handoff object | What you actually operate | Confirm before you buy |
|---|---|---|
| Named cloud teammate | A named Grok Bot on one persistent account computer | Grok Bot FAQ |
| Workflow and agent product | Triggers, steps, and connected apps as Lindy currently presents them | lindy.ai and Lindy pricing |
| Desktop-ish operator | A Cowork session that may reach this disk | Anthropic Cowork |
If two rows fight, the handoff wins. A qualifying Grok Bot plan does not turn Lindy into a named bot.
Treat Lindy as a workflow and agent product until the live page says otherwise
The search phrase dumps Lindy into the same bucket as a cloud teammate. That is the error this page exists to stop.
A workflow product, as Lindy currently describes itself, is a canvas you point at an event and then steps: extract, branch, draft, post, stop. Confirm that on Lindy's docs and the homepage. If the live product has moved toward a persistent cloud desktop per agent, write that down from the page.
Gmail is why ops people land here. Lindy currently lists Gmail as a place it drafts, schedules, and replies. Verify the live connection, the approval rule, and whether send is gated. Then read Grok Bot and Gmail for the other mailbox: grant, draft-only stop line, shared computer.
Do not freeze Slack as Lindy's only home. The homepage currently also mentions iMessage and the browser. The pairwise article is the two-column fight. This page only needs Lindy as the workflow-shaped pole until you confirm a different object on lindy.ai.
Staff a named Grok Bot on one shared cloud computer
Standing cloud work still has a name in October, still has last week's file, and still has to run when nobody's laptop is open. That is a role, not a canvas.
Grok Bot is that desk. Name the bot, write the charter, connect the minimum login. One persistent cloud machine for the whole account. Each bot gets a screen. Docs: do not use separate bots as a security boundary. An inbox triage bot and a research bot on the same account share the cookie jar. Routines attach to one bot (max 50, 20 recent run records) and die with it. Nothing is team-level. See how to schedule a Grok Bot routine.
Launched beta 11 August 2026. Eligibility widened 21 August 2026. Cheapest paid path: Cursor Pro at $20 a month. Every paid Cursor plan includes Grok Bot, from Cursor Pro at $20; Cursor Hobby, the free plan, does not, and an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead. Also eligible: Cursor Pro+, Cursor Ultra, Cursor Teams, plus a one-time trial. No Grok Bot-specific spend cap, no published allowance figure, no model picker. Weekly allowance, then on-demand. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer. An audit view of bot actions does not exist outside Enterprise.
Clients: macOS (Apple silicon and Intel), Windows (x64 and Arm64) and Linux (x64 and Arm64) desktop apps, plus iPhone (iOS 18 or later), Android (9 or later) and iPad companion apps that can pause routines, approve steps, read run history and delete a routine, but not edit or test one. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). The computer is a managed Linux VM, not a Linux desktop client.
Treat Cowork as a desktop-ish operator until Anthropic's page says otherwise
Local work already sits on a specific disk. Copying Friday's close folder to a cloud computer so you can peek from a phone is a residency decision.
Cowork is the column to check. Anthropic currently presents it as handing Claude real work, running on desktop, with web and mobile described as beta. The line that matters is the desktop app reaching folders and applications on your own computer. If that is still true today, Jordan's Mac is a Cowork home for local CSVs. If Anthropic has moved the default to a cloud session, re-run the tree. Cloud continuation is not Grok Bot's named roster.
This page will not print Cowork prices. Open claude.com/product/cowork and copy from there. Check the desktop grant, and whether a closed lid stops local computer use. A desktop operator that needs the machine awake is the wrong home for overnight mail.
Keep Grok Bot off that CSV folder unless a human writes that the exports may live on the account computer. Keep Lindy off that folder unless you have confirmed that the current product reaches this disk without copying the files into a connected-app store.
Walk an ops person through a Gmail builder, a named bot, and a local session
You are Jordan in ops at a twelve-person company. Three jobs landed in the same week. They all look like email and files if you squint.
Job one: a vendor invoice hits a Gmail label, you extract fields, then post a draft Slack note. Never send, never pay. Trigger-shaped. Try a workflow builder first. Confirm Gmail and send-off on lindy.ai.
Job two: a draft-only morning pack by 07:15 after both laptops close, with last week's exceptions file still there. Standing named role. That is Grok Bot. Use inbox triage. The client is a remote control. An From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it.
Job three: CSV exports in Downloads that must not leave this Mac. Cowork-shaped if Anthropic's current desktop grant can see one subfolder. Grant one folder, not the whole home directory.
| Jordan's job this week | Shape of the handoff | Pole to try first |
|---|---|---|
| Invoice hits a Gmail label, extract fields, draft a Slack note, never send | Connector and trigger | Lindy-shaped workflow, confirm Gmail on lindy.ai |
| Overnight inbox pack by 07:15, lids closed, last week's exceptions file | Standing named role | Grok Bot, inbox triage, drafts only |
| CSV exports in Downloads that must not leave this Mac | Local folder on this disk | Cowork session, confirm the desktop grant on Anthropic |
If two rows fight, residency still wins. A Lindy Gmail workflow does not move Friday's CSVs off this Mac. A Cowork session does not keep 07:15 alive if this Mac is in a bag.
Put connector-shaped Gmail work on a workflow product you confirm
Trigger-shaped mail is mail that should fire because an event happened, not because a named worker woke up and went looking.
An invoice label is that shape. So is a bounce. So is a calendar invite that should draft a conflict note and stop. The honest product for that shape, as Lindy currently presents itself, is a workflow you can toggle. Confirm the Gmail trigger, the Slack action, and the approval gate on the live pages. If the current Gmail surface will send unless you opt out, do not opt in until the stop is real.
Grok Bot can also read Gmail. That is a different object: a named bot on a shared computer, watching a mailbox that will share cookies with every other bot on the account. Right call for standing triage. Wrong call for a narrow invoice extractor if you hoped the invoice login would stay away from the overnight inbox. It will not. See Grok Bot and Gmail before you widen the grant.
Cowork can also open Gmail if the current desktop operator can see a browser on this Mac. Confirm Anthropic. Then ask whether you want 07:15 and invoice intake to depend on this laptop staying awake. Usually you do not. Never send. Never pay. Never archive.
Put standing overnight mail on a named bot with a written stop line
Overnight mail is not a trigger you forgot to draw. It is a role that has to exist while both lids are closed, with last week's exceptions file still on the desk.
That desk is Grok Bot's account computer. Name the bot. Charter it as drafts only. Connect the minimum mailbox scope. Do not add the accounting portal while you are in there. Do not add Friday's CSV folder. Do not invite a second human onto this login so they can just check the pack.
A chief of staff briefing that diffs last Monday is the same shape: standing, named, lids may close. A churn watch bot is also that shape if you accept the shared computer. Do not collapse them into Jordan's invoice workflow because they all touch email.
If you try Lindy for overnight mail, confirm what remains when both laptops are shut, and whether the exceptions file is last week's file or a fresh prompt. If you try Cowork, confirm whether a closed lid stops local computer use. Then admit you still have not created a named Grok bot with a routine attached to one bot. Sessions are not desks.
Keep laptop-local exports on a Cowork session you confirm
Friday's CSVs are already on this Mac. The failure mode is copying them so a cloud product can help.
Cowork is the pole to try first if Anthropic's current desktop grant can see one Downloads subfolder and nothing else. Confirm the grant. Confirm delete is gated. Sleep the Mac and write down whether the job continues.
Grok Bot is the wrong first home. Uploading the CSVs puts payroll-adjacent exports next to the mailbox session. A bot named local-close is still on the same VM as inbox triage. Deleting it does not remove the files or the sessions.
Lindy is the wrong first home unless you have confirmed that the current product works in this folder without ingesting the CSVs into a connected store you cannot point at. Do not paste the folder into a Gmail workflow because the invoice job already lives there.
If the CSVs must be processed after Jordan's train ride, you have changed the job. Either the files are allowed on a cloud computer, or the job waits for the Mac. Write the exception.
Score trigger shape against persistence against disk residency
Feature grids go stale. Score trigger shape, persistence, and residency, then read the live vendor pages for the two hedged columns. Invoice label is a trigger. Overnight pack is persistence. Friday CSVs are residency. If two scores fight, residency still wins.
| Score this first | Grok Bot | Lindy (confirm live) | Cowork (confirm live) |
|---|---|---|---|
| Persistence | Named bot and last week's path on the account computer | Confirm what remains after you close the tab | Confirm what remains after the session and a closed lid |
| Trigger shape | Routines on one bot, max 50, 20 recent records | Confirm current email and schedule triggers on Lindy docs | Confirm scheduled tasks and folder grants on Anthropic |
| Disk residency | Bytes live on xAI's managed Linux VM | Bytes live wherever Lindy currently stores connected-app data | Bytes may stay on this disk if the desktop grant still holds |
A cheaper canvas does not move a file off Jordan's Mac.
Count one Grok Bot computer even when two ops people share a login
The three-way trap the pairwise pages do not have to solve is people, not bots.
If Jordan's teammate logs into Jordan's Grok Bot account to just check the invoice bot, you added a second pair of hands on the same computer. They can reach whatever Jordan signed in. Deleting the invoice bot does not sign anyone out. Hosted MCP tokens stay with Cursor's backend. The Gmail cookie on the computer does not.
Screens will not save you. Invoice Desk and Inbox Desk are two windows, not two offices. Two humans are not isolated because they typed two names.
If the teammate needs a standing cloud role, use a separate eligible account. Eligible does not mean Cursor Hobby. If they only need local files, keep them on their own disk (Cowork, confirm Anthropic). If they only need a Gmail invoice extractor, use their own Lindy login and confirm whether Lindy's current connection model actually isolates it.
Paste an ops routing charter that classifies the three poles
You need a classifier before you need another bot. Paste this into a note you actually read when a new ops job appears. Replace the bracketed lines. This is not a bot that sends mail. It is a routing brief so you stop stuffing three poles into one Gmail workflow.
IDENTITY
You are Handoff Router for [OPS PERSON]. You do not run the jobs. You
classify each incoming request into one pole and stop. You are not a
Grok bot with a private computer. If a job later runs on Grok Bot, it
will sit on the one persistent cloud computer assigned to the user
account. Screens are not vaults.
THREE POLES
1. WORKFLOW PRODUCT (Lindy, confirm lindy.ai the morning you use it):
trigger-shaped work in connected apps, such as a Gmail label that
should draft a Slack note and never send.
2. NAMED CLOUD TEAMMATE (Grok Bot): standing role, lids may close,
last week's file may live on the account computer. One computer
per account. Never a second human on this login.
3. LOCAL SESSION (Claude Cowork, confirm Anthropic the morning you
use it): the file already sits on this laptop and must not be
copied to a vendor VM until a human writes that exception.
WHOSE COMPUTER
Ops Mac: client only, unless the job is local files on this Mac.
Overnight inbox: NAMED CLOUD TEAMMATE only. Drafts. Never send.
Invoice Gmail: WORKFLOW PRODUCT first, confirm Gmail on Lindy.
Friday CSVs: LOCAL SESSION only.
WHERE YOU STOP
Never send, archive, or delete mail.
Never treat a second bot name as a second computer.
Never copy Downloads CSVs onto the cloud computer.
Never create a named Grok bot for a job that should be a Gmail
trigger you can toggle.
If the pole is unclear, ask. Waiting is correct. Copying is not.
OUTPUT
One line: POLE=WORKFLOW|NAMED TEAMMATE|LOCAL SESSION
One line: WHOSE COMPUTER=[account VM|this Mac disk]
One line: STOP VERB=[the action a human must still do]
The overnight inbox is safe to leave running only if it drafts and never sends. The CSVs are safe only if they never leave this disk. The invoice flow is safe only if send stays off on the live Gmail connection you confirmed.
Watch week one and week four diverge when you force one pole onto all three jobs
Week one, matching poles. Invoice Gmail workflow on Lindy, confirmed, draft Slack only. Overnight inbox bot on Grok Bot, drafts only. Cowork (confirmed) granted one Downloads subfolder. Pack appears while both lids are closed. CSVs never left the Mac.
Week four, forced Grok Bot because you already pay for Cursor Pro+ at $60 a month. Jordan creates an invoice-bot next to the inbox bot. The Gmail session is now on the shared computer. Friday CSVs got uploaded so the bot can help from the train. You deleted a throwaway close bot. The vendor portal is still signed in. No audit view outside Enterprise.
Week four, forced Lindy. Overnight mail now depends on whatever schedule and storage Lindy currently offers, not on last week's exceptions file on an account computer. If the Mac slept, Cowork never ran Friday's close. If someone toggled send on, a vendor got a reply nobody reviewed.
Week four, forced Cowork as a desktop-ish operator is often described. Mac off. 07:15 pack missing. Invoice labels waited in Gmail. You are on a train with a phone that can pause a Grok bot you never staffed.
| Job | Week one on the matching pole | Week four if you force one product onto all three |
|---|---|---|
| Invoice Gmail workflow | Draft Slack note, no send, after you confirm Lindy | Gmail session now sits next to overnight mail, or Cowork missed invoices because the Mac slept |
| Overnight pack | Draft pack exists after both lids close | Missing on a sleeping desktop; leftover sessions if you used a disposable Grok bot for invoices |
| Friday CSV folder | Files stay on this Mac under a grant you can name | Files sit next to mailbox cookies if you copied them to the account computer |
Diagnose the wrong-pole failure before you rewrite the Gmail filter
When the week breaks, name the pole before you touch the label taxonomy. Filter surgery does not wake a laptop, and it does not unspread a Gmail cookie across every bot on an account.
| Symptom | You put it on the wrong pole | Move it |
|---|---|---|
| Invoice Slack note never fires because nobody started a Cowork session | Desktop operator used as a Gmail trigger | Workflow product, confirm Lindy Gmail |
| 07:15 pack missing because both laptops slept | Desktop operator, or a workflow that may not run after lids close | Grok Bot cloud computer, draft-only |
| Friday CSVs visible to the overnight bot | Shared Grok Bot account, one computer | Keep the folder on this disk (Cowork, confirm) |
| You restaffed the invoice flow as a named bot, then deleted it | Grok Bot used as a throwaway workflow | Confirm Lindy for the trigger-shaped job |
| Roundup said each bot is a private VM so two ops people are safe | You believed names isolate people | Count computers by account |
Approvals on Grok Bot control a proposed action. They do not reverse completed work. Design overnight mail so send is never proposed. On Lindy and Cowork, confirm the live permission model. If Jordan needed a CSV on a plane, either the file is allowed on a cloud computer, or it waits.
Answer the objection that a workflow builder should replace the bot and the desktop
The strongest case against this three-way is simplicity. Lindy already lists Gmail. If a canvas can watch a label, why pay for a named cloud teammate, and why install a desktop operator.
That case wins when all three jobs actually are trigger-shaped connected-app work. No overnight pack after both lids close. No folder that must stay on this disk. Confirm Lindy. Use Grok Bot vs Lindy if the only fight left is teammate versus workflow.
It loses the moment Friday's CSVs and the overnight inbox are both real. Using Lindy for the pack makes 07:15 depend on whatever Lindy currently is, which you have not verified as a persistent account computer. Using Lindy for the CSVs copies residency into a connected-app store unless the live page says otherwise. Using Grok Bot for the invoice label puts a trigger-shaped job on a shared VM next to the mailbox. Using Cowork for the inbox makes 07:15 depend on a Mac that is off.
A Gmail workflow builder is a pole, not a union of all three. Confirm it the morning you buy. Do not invent a Lindy price here. Do not freeze a three-column grid from a roundup.
None of these products is a wall between two humans who should not see each other's logins, not if they share a Grok Bot account, and not if you paste Friday's folder into a Lindy workflow on Jordan's login. Isolation is an account choice, a disk choice, or a decision not to copy the file. Do not let any of the three send, pay, post, merge, or delete without a human. Do not run a job that needs an immutable action log on Grok Bot. Claude Code, SKILL.md, and CLAUDE.md belong to Grok Build, never Grok Bot.
You can keep all three products. Stop using one object for the other object's job. Inbox triage never sends. Mail cleanup assistant only proposes. If the job fails that filter, keep it.
Keep reading: Grok Bot vs Claude Cowork: Cloud Teammate or Desktop Operator, What Is a Grok Bot? The Plain Explanation for Non-Engineers, Grok Bot and Gmail: Permissions and What to Automate.
Frequently Asked Questions
How is this three-way different from Grok Bot vs Claude Cowork vs ChatGPT Work?
This page puts Lindy in the third column, not ChatGPT Work. The other article asks where the work has to live, including a ChatGPT task surface that should end when the file lands. This one asks how you hand the work off: a workflow and agent product you confirm on lindy.ai, a named Grok Bot on one shared cloud computer, or a Cowork session you confirm on Anthropic. If your third pole is ChatGPT Work, use that page. If your third pole is a Gmail workflow builder, stay here.
Does a Lindy Gmail workflow give me a named Grok Bot on a shared computer?
No. Lindy currently presents a workflow and agent product. Confirm the live object on lindy.ai. Grok Bot is a roster of named bots on one persistent cloud computer assigned to the user account. Screens are not vaults. Cookies, sessions, files, and CLI credentials are shared. Deleting a bot does not remove them. A Gmail trigger in a workflow builder is not that computer. Do not copy Grok Bot's shared-computer model onto Lindy, and do not copy Lindy's trigger canvas onto Grok Bot.
Can I treat Lindy or Cowork prices in this article as current?
No. This page does not print Lindy prices or Cowork prices, and it does not freeze either product's feature list as fact. Confirm Lindy on lindy.ai and the current pricing page the morning you buy. Confirm Cowork on Anthropic's current Cowork page, including whether the desktop grant still reaches this disk. Grok Bot's cheapest published paid path is Cursor Pro at $20 a month, with other eligible subscriptions listed in xAI's FAQ as of 23 September 2026. Do not copy a three-column bargain grid from a roundup.
What if I run the overnight inbox as a local Cowork session instead of a named Grok Bot?
Then 07:15 depends on that laptop staying awake, signed in, and at a desk, unless Anthropic's current page says the job continues in the cloud. Confirm that. Even cloud continuation is not a named Grok bot on an account computer with last week's exceptions file and a routine attached to one bot. Put standing overnight mail on Grok Bot, drafts only. Keep Friday CSVs on this disk. Put the invoice Gmail trigger on a workflow product you have confirmed. Do not move the company mailbox onto a laptop that goes home in a bag.