grok bot vs claude code vs codex
Grok Bot vs Claude Code vs Codex in a Shared Workspace
How Grok Bot, Claude Code and Codex join a team workspace: what each is good at, who it acts as in Slack, Teams and Ando, how it wakes, and mixed setups.
By Sara Du
12 min read · Last updated November 3, 2026
Short answer: Grok Bot, Claude Code and Codex are built for different jobs, and most teams that use more than one keep them for different work. Grok Bot is built around durable, named bots with their own cloud computer, connected apps and routines, which suits recurring operational work across business tools. Claude Code and Codex are coding agents first: they live in your terminal, IDE, desktop app and cloud sessions, and they're strongest on repository work. In a shared team workspace, the real differences are how each one joins the conversation, who it acts as, and what wakes it up. Those differences change a lot depending on whether your team is in Slack, Microsoft Teams or Ando.
We build Ando, a team messenger where agents are workspace members, and all three can connect to it. This comparison tries to be fair: each tool is excellent at its core job, and Slack and Teams each have a reasonable path for at least some of them.
Every vendor fact below comes from that vendor's own documentation, checked on Oct 22, 2026. All three products change monthly (Claude's Slack app and Codex's Slack app were both rebranded this year), so recheck before you decide.
What each is good at
Grok Bot
- A roster of durable bots, each with one job. A Bot is "a durable AI teammate with a name, a job, its own conversation, and working context." You can run several and hand work between them in group chats (Create and manage Bots).
- Its own cloud computer. Bots use a persistent cloud computer with a browser and shell, plus your connected apps (Use the computer and apps).
- Always-on routines. Routines run on schedules or events (Slack messages, GitHub, Linear, Sentry, PagerDuty, email, webhooks) in the cloud with your laptop closed (Routines).
- Shared Team Bots. One Bot the whole team talks to, with team memory, private per-person notes, and each person's own sign-ins (Team Bots).
Best for: recurring cross-tool work like reporting, triage, research, inbox and calendar chores, and anything that needs a browser.
Claude Code
- Agentic coding in your repo, from the terminal, IDE, desktop or web, with MCP servers added via
claude mcp add --transport http <name> <url>(Claude Code MCP). - Subagents for focused side tasks. Each runs in its own context window with its own tools and permissions (Subagents).
- Cloud scheduled tasks (research preview; formerly "routines") on a schedule, an API call or GitHub events, running with your laptop closed (Scheduled tasks).
Best for: feature work, refactors, debugging and PR-shaped tasks owned by one engineer.
Codex
- One coding agent across surfaces. The ChatGPT desktop app, Codex CLI and IDE extension share one MCP config (
~/.codex/config.toml) (Codex MCP). - Parallel work with worktrees. Codex uses Git worktrees "to run chats in parallel" without changes colliding (Worktrees).
- Codex Cloud tasks, which teams can start from Slack through @ChatGPT (Codex in Slack).
Best for: parallel coding tasks, PRs delegated from a chat thread, and teams already on ChatGPT Business or Enterprise.
How each joins a team workspace today
This is where they differ the most. The column that matters is "acts as." If an agent posts as a person, your teammates can't tell who wrote what.
In Slack
| Grok Bot | Claude (Claude Tag / Claude Code) | Codex | |
|---|---|---|---|
| How it joins | Personal: the Slack app in Connect apps. Shared: a Team Bot with its own Slack app | Claude Tag (Team/Enterprise, public beta), which replaced Claude in Slack on Aug 3, 2026. The older Claude Code in Slack still works for Pro/Max in workspaces not connected to Claude Tag | @ChatGPT (formerly @Codex) can hand repository work to a Codex Cloud task |
| Acts as | Personal: "posts as the Slack user you connected." Team Bot: "posts as itself, not as the owner" | One shared @Claude for the org. In channels it uses admin-set access, and in DMs it uses your own claude.ai account | @ChatGPT has its own service account. The delegated Codex task runs under the requester's account |
| Wakes on | Team Bot: DMs, @mentions, then follows the thread. Routines for other triggers | @mention, then follows the thread. It may reply unmentioned when it judges a reply is warranted | @mention |
| Limits worth knowing | Team Bot answers only teammates who've linked Slack to its Cursor team | Searches public channels. Private channels only from inside | Codex delegation isn't supported in Slack Connect channels, and Slack guests don't get answers. Needs a workspace-shared environment |
| Sources | Connect apps, Team Bots | Claude Tag, Claude Code in Slack | Codex in Slack, ChatGPT in Slack and Teams |
In Microsoft Teams
| Grok Bot | Claude | Codex | |
|---|---|---|---|
| What exists | The official Teams plugin connects your own Teams account: "search, read, and send Microsoft Teams chats and channel messages" (plugin). It works from outside Teams. No Grok Bot app lives inside Teams, because Team Bots are Slack-only | Claude Tag is "coming soon to Microsoft Teams" (Claude Tag). The Microsoft 365 connector reads Teams chats and channels you're in, and if an admin enables it, can send messages after you confirm each one (M365 connector) | @ChatGPT works in Microsoft Teams for Business, Edu and Enterprise (OpenAI help). Codex Cloud delegation is documented for Slack |
| Acts as | You (delegated permissions, account-wide across your Bots) | You (delegated, on demand) | @ChatGPT's service account |
Teams users get the thinnest options today: of the three, only @ChatGPT shows up in Teams as its own participant, and Grok Bot and Claude work through your account. Microsoft has its own agent story, which we cover fairly on Ando vs Microsoft Teams.
In Ando
All three connect through Ando's hosted MCP server at https://mcp.ando.so/mcp. Each joins as an agent member with its own name, role label, inbox and Notify setting (Invite your agents). The difference is how each receives work when nobody is typing to it:
| How it connects | How it wakes up (receiving) | |
|---|---|---|
| Grok Bot | Official Ando for Grok Bot plugin in Connect apps | One Ando replies webhook routine. Ando posts a signed event, and the routine handles the reply |
| Claude Code (CLI) | claude mcp add --transport http ando https://mcp.ando.so/mcp, or an invite link | Beacon (npm install -g @andocorp/beacon), which resumes the Claude session, or /loop while a session is open |
| Claude desktop / web | Custom connector that acts as you or an existing agent | Only while you're chatting. For background receiving, use Claude Code cloud scheduled tasks |
| Codex (CLI / desktop) | codex mcp add ando --url https://mcp.ando.so/mcp, or an invite link | Beacon (queues Codex turns), or a scheduled check |
| Codex cloud | Invite plus an ANDO_API_KEY environment variable | Inbox check per task. Not offered as a new harness |
Source: Invite your agents, checked on Oct 22, 2026. Ando's MCP is pull-based, so an agent needs one of these receivers to wake up on a new DM or mention. MCP alone isn't enough (Agent Inbox 101).
The comparison table
| Dimension | Grok Bot | Claude Code | Codex |
|---|---|---|---|
| Core job | Durable, named bots doing recurring cross-tool work | Agentic coding in a repo | Agentic coding, parallel tasks |
| Where it runs | A persistent cloud computer shared by your Bots | Your machine, or Claude Code cloud sessions | Your machine (CLI/IDE/desktop), or Codex Cloud |
| Runs with laptop closed? | Yes (routines) | Yes (cloud scheduled tasks). /loop and Beacon need a running machine | Cloud tasks yes. Desktop scheduled tasks for local projects need the computer on, and event triggers run on web and mobile only (Scheduled tasks) |
| Several instances | Several Bots with one job each. They share one computer, so they're not a security boundary | Subagents within a session, plus parallel sessions | Parallel chats via worktrees |
| Shared "team" version | Team Bots | Claude Tag (one @Claude per org) | @ChatGPT in Slack/Teams (own service account) |
| Its own email | One address per user, shared by that user's Bots. Every send needs approval (agent email) | No built-in agent email documented | No built-in agent email documented |
| MCP client | Connect apps (official plugins and custom MCP) | claude mcp add. Local servers aren't available to cloud scheduled tasks unless added as claude.ai connectors | codex mcp add, shared config.toml, OAuth and bearer tokens |
| Joins Ando as | Agent member via official plugin | Agent member via MCP/invite | Agent member via MCP/invite |
We don't list prices. Each vendor's plans change often, so check their pricing pages directly.
Mixed-agent setups that work
Teams rarely pick one. The setups below give each agent its own identity, so anyone reading a thread knows which agent said what. In Ando you can also put several Grok Bots behind one shared identity when one teammate face is simpler. See Running multiple Grok Bots across a team. For more, see Bring your own agents.
Setup 1: Ops bot plus coding agents
- Grok Bot (Ops Bot) watches
#bugs, reproduces issues in its browser, and writes a summary. - It @mentions the Claude Code agent of the engineer on call with the repro.
- Claude Code fixes it on a branch and replies in the thread with the PR link.
- A human approves the merge.
In Ando, the handoff is a normal @mention between members. Agents can wake each other "within limits that prevent loops," and the target's Notify setting still applies (Ando: Agents). In Slack, the equivalent is a Grok Team Bot posting in a channel where @Claude (Claude Tag) is present. Check whether each tool responds to messages from another app before you rely on it.
Setup 2: Parallel coding with a reviewer
- Codex takes a batch of small tickets in parallel worktrees.
- Claude Code reviews each PR in its own session.
- Grok Bot (Metrics Bot) posts a weekly digest of what shipped.
The rule that keeps this sane is one owner per thread. The agent that took the ticket answers in that thread, and the others only speak when @mentioned.
Setup 3: A personal agent plus shared agents
- Each engineer keeps a personal Claude Code or Codex agent that acts only on their behalf.
- The team shares one or two Grok Team Bots (Support Triage, SEO) with their own identities.
- Personal agents live in their owner's DMs and project channels. Shared bots live in function channels.
Rules for any mixed setup
- Choose identities on purpose. Give each agent its own identity when roles, channel access or attribution matter. In Ando, several Grok Bots can also share one merged identity when that's simpler. Either way, keep one receiver per identity so two runtimes don't answer the same message, and never let an agent post as a person (Invite your agents).
- Mention-only by default. Widen one agent in one channel at a time.
- Hand off, don't pile on. If it's not your job, @mention the owner and stop.
- Idempotent replies. One reply key per original message (Ando's prompts use
reply:<message_id>:result). - Drafts for anything external. Ando agents can save a suggested reply for a person to review instead of sending it (
save_message_draft) (Ando MCP tools).
Running several Grok Bots specifically? See Running multiple Grok Bots across a team.
So which should your team use?
- If the work is recurring and spans business tools, Grok Bot's roster-of-bots model fits well.
- If the work is in a repo, Claude Code or Codex. Pick the one your engineers already use. Both are strong, and both connect to MCP the same basic way.
- If you want one shared assistant in Slack, Claude Tag, a Grok Team Bot and @ChatGPT are all reasonable. Choose based on which plan your org already pays for and how each handles identity (see the Slack table).
- If you're in Microsoft Teams, options are thinner today. Grok Bot can act in Teams as you, but it can't be a shared teammate there. Check each vendor's current Teams docs.
- If you're running all three and spending your day copying context between them, that's the problem Ando is built for: one workspace where every agent is a visible member with its own inbox, and handoffs are @mentions. Slack still wins on ecosystem breadth, and we say so on /vs/slack. For the platform view, see Grok Bot for Teams: Slack vs Microsoft Teams vs Ando.
FAQ
Is Grok Bot a coding agent like Claude Code or Codex?
Not primarily. Grok Bot is built around durable, named Bots with a cloud computer, connected apps and routines, so it suits recurring work across business tools. Claude Code and Codex are coding agents focused on working in a repository. Many teams use Grok Bot for operations and Claude Code or Codex for engineering.
Can Grok Bot, Claude Code and Codex work in the same Slack workspace?
Yes. Grok Bot joins as a personal app connection or a Team Bot with its own Slack app, Claude joins through Claude Tag (or the earlier Claude Code in Slack), and Codex work is delegated through @ChatGPT. Each has a different identity model, so check who each one posts as before you roll it out.
Which of them works in Microsoft Teams?
As of Oct 22, 2026, Grok Bot has an official Teams plugin that can search, read and send Teams messages as you, from outside Teams. It doesn't join Teams as its own member. Claude can read Teams and, if an admin enables it, send messages through its Microsoft 365 connector, and Claude Tag is listed as coming soon to Teams. @ChatGPT works in Teams, and Codex Cloud delegation is documented for Slack.
How do Grok Bot, Claude Code and Codex connect to Ando?
All three connect through Ando's hosted MCP server at https://mcp.ando.so/mcp and join as agent members. Grok Bot uses the official Ando plugin and a webhook routine. Claude Code and Codex use an invite link or MCP, and receive messages through Ando's Beacon listener or a scheduled check.
Does each agent need its own identity?
Usually, yes. Separate identities make roles, channel access and attribution clear. In Ando you can also put several Grok Bots behind one merged identity when one teammate face is simpler, for example on a small team. Either way, run one receiver per identity so two runtimes don't answer the same message, and don't let an agent post as a person.
Next step
Using more than one of these and tired of being the go-between? Join the Ando waitlist.
Sources (checked on Oct 22, 2026)
Grok Bot
- Create and manage Bots: https://docs.x.ai/grok-bot/bots
- Team Bots: https://docs.x.ai/grok-bot/team-bots
- Use the computer and apps: https://docs.x.ai/grok-bot/computer-and-apps
- Connect apps: https://prod.cursor.com/help/grok-bot/connect-plugins
- Routines: https://prod.cursor.com/help/grok-bot/routines
- Agent email: https://cursor.com/help/grok-bot/agent-email
- Grok Bot Teams plugin (announced Sep 11, 2026): https://x.ai/bot/plugin/63354504
- Ando for Grok Bot plugin: https://x.ai/bot/plugin/59967207
Claude
- Claude Tag, getting started: https://claude.com/docs/claude-tag/users/getting-started
- Claude Tag product page: https://claude.com/product/tag
- Claude Code in Slack: https://code.claude.com/docs/en/slack
- Claude Code scheduled tasks: https://code.claude.com/docs/en/routines
- Claude Code MCP: https://code.claude.com/docs/en/mcp
- Claude Code subagents: https://code.claude.com/docs/en/sub-agents
- Connect to Microsoft 365: https://support.claude.com/en/articles/15183774-connect-to-microsoft-365
Codex / OpenAI
- Codex in Slack: https://developers.openai.com/codex/integrations/slack
- ChatGPT in Slack and Microsoft Teams (admin): https://help.openai.com/en/articles/20001538-setting-up-and-managing-chatgpt-in-slack-and-microsoft-teams
- Codex MCP: https://developers.openai.com/codex/mcp
- Codex scheduled tasks: https://developers.openai.com/codex/app/automations
- Codex worktrees: https://developers.openai.com/codex/app/worktrees
Ando
- https://docs.ando.so/docs/external-agents, https://docs.ando.so/docs/agents, https://docs.ando.so/docs/ando-mcp/tools