Vybe vs Claude Tag vs OpenAI Dots vs Grok Team Bots, 25 criteria
Vybe
Claude Tag
OpenAI Dots
Grok Team Bots
Agents & collaboration
AI coworkers
Supported:
Specialized coworkers with their own responsibilities and tools.
Supported:
Claude takes on tasks from a channel or DM.
Conditional:
One always-on primary dot per user, working 24/7 toward goals on its own cloud computer; role-based specialist dots are in enterprise preview and teams of dots are not yet available.
Supported:
Shared Team Bots built around a role, each with context, plugins, credentials, and memories; public beta on Teams and Enterprise plans.
Team collaboration
Supported:
Shared conversations and Slack threads with people and AI.
Supported:
Teammates can review and refine work in the same thread.
Conditional:
ChatGPT Space shared workspaces with agent-editable Pages; available on Pro, Business, and Enterprise plans.
Supported:
Everyone works with the same Bot and its expertise, while each person's conversations and memories stay private.
Communication channels
Conditional:
In-app chat, Slack, and email; other channels require setup.
Supported:
Slack channels and DMs with different access scopes.
Supported:
ChatGPT, Slack, Teams, SMS, and voice calls.
Supported:
Slack with a dedicated handle per Team Bot, alongside the Grok Bot app.
Agent handoffs
Supported:
Delegate work to other AI coworkers.
Limited:
Not offered: one Claude works each thread; no delegation between specialized agents documented.
Conditional:
Specialist dots with defined org roles are in enterprise preview; general delegation between dots is not yet available.
Supported:
Bots pass context between each other, hand off tasks, and can pass ownership so you are not the router between tools.
Persistent memory & skills
Supported:
Persistent memory, company knowledge, and reusable skills.
Supported:
Persistent channel context, memory, and standing instructions.
Supported:
Dots learn your preferences, how you think, and your standards from ongoing feedback.
Supported:
Team Bots keep separate context and memories per person while drawing on skills shared across the team.
Automation & tools
Schedules & triggers
Supported:
Schedules, events, and follow-ups with run history.
Supported:
Routines on a schedule, channel watch, or repository event.
Supported:
Team tasks act on a schedule or in response to events like a new email or Slack message; MCP events trigger automations from connected apps.
Supported:
Routines run on a schedule or, where supported, after an event; background routines run while the laptop is closed.
Browser automation
Conditional:
Hosted browser with persistent sessions; browser service required.
Limited:
Not offered: work runs in an ephemeral cloud sandbox through channel-scoped tool connections; no browser-control tool documented.
Supported:
Each dot has its own cloud computer and browser; you can open your dot's computer to inspect its work, and dots can connect to your laptop with permission.
Supported:
Every Bot runs on a persistent cloud computer with a browser, filesystem, and terminal, and can log in to services in that browser.
Meeting intelligence
Conditional:
Supported meeting recording, transcripts, and follow-up; meeting service required.
Limited:
Not offered: no meeting recording or transcription documented.
Conditional:
Meeting note-taking via the ChatGPT Meetings plugin (beta, macOS desktop); no recording or transcription.
Limited:
Not offered: connectors cover Gmail and Outlook calendars, but no meeting recording or transcription is documented.
Integrations
Supported:
Prebuilt connectors and custom integrations.
Supported:
Admin-configured connections scoped to organizations, workspaces, or channels.
Supported:
Connects to 4,000+ apps through plugins.
Supported:
Built-in connectors, a preconfigured connector catalog, and custom MCP servers.
Apps & infrastructure
Custom app building
Supported:
Build apps with AI, inspect code, and iterate in a live preview.
Supported:
Interactive pages, charts, and code changes from the thread.
Conditional:
Dots can build working apps and complete PRs as part of their work; evaluate your app deployment workflow separately.
Limited:
Bots steer Cursor Projects and launch Cloud Agents for code work; no interactive app-building surface documented.
Internal publishing
Supported:
Private, individual, and organization-wide app sharing.
Supported:
Hosted artifacts accessible to people in the channel.
Limited:
Not offered: outputs live in ChatGPT and connected surfaces; no internal app-publishing surface documented.
Limited:
Not offered: Bot share links are public previews on x.ai; no internal publishing surface documented.
Row-level permissions
Conditional:
Role-based access for owners, admins, editors, and members, with apps kept private, shared, or organization-wide.
Limited:
Not offered: access is scoped per channel and by organization roles; no per-row data permissions documented.
Limited:
Not offered: access is governed by ChatGPT plan permission rules; no per-row data permissions documented.
Limited:
Not offered: access follows connector permissions such as permission-aware Google Drive; no per-row data permissions documented.
Private resources & SSH
Conditional:
SSH tunnels and custom connections for private resources.
Limited:
Not offered: the ephemeral cloud sandbox reaches tools through configured connections; no private-network or SSH access documented.
Limited:
Not offered: dots run on their own cloud computer and connect through plugins; no private-network or SSH access documented.
Limited:
Custom MCP servers must be reachable over the public internet; local servers require a tunneling service.
Models & cost control
Model choice
Supported:
29 models across 11 providers.
Supported:
Choose from permitted Claude models, including Opus and Sonnet.
Limited:
Runs on OpenAI's GPT-6 Astra; no other providers or bring-your-own-model options documented.
Conditional:
Runs Grok models; no cross-provider model catalog documented for Bots.
Automatic model routing
Supported:
Auto routes tasks to Cheap, Balanced, or Smart tiers.
Conditional:
Choose a model for a thread, channel, or DM; automatic task routing not verified.
Limited:
Not offered: dots run on GPT-6 Astra with no automatic cross-model routing documented.
Limited:
Not offered: no automatic task-to-model routing documented.
Custom routing rules
Supported:
Choose tier models, map task categories, or pin a model.
Conditional:
Admins set workspace and channel defaults; individual threads can switch models.
Limited:
Not offered: no task-category-to-model routing rules documented.
Limited:
Not offered: no task-category-to-model routing rules documented.
Separate coding policies
Supported:
Separate conversation and coding routing policies.
Limited:
Not offered: admins choose permitted Claude models per scope; no separate coding policy documented.
Limited:
Not offered: one OpenAI model experience; no separate coding policy documented.
Limited:
Not offered: Cursor team rules and privacy settings apply to Bots; no separate coding model policy documented.
Bring your own keys
Conditional:
Bring your own provider keys as part of an enterprise setup.
Limited:
Not offered: Claude uses admin-provided tool accounts with credentials kept out of the sandbox; no customer model keys documented.
Limited:
Not offered: dots run on OpenAI-managed credentials; no customer provider keys documented.
Limited:
Credentials connect third-party tool APIs; no customer AI provider keys documented.
Bring your own gateway
Supported:
OpenRouter and Vercel AI Gateway.
Limited:
Not offered: no bring-your-own model gateway documented.
Limited:
Not offered: no bring-your-own AI gateway documented.
Limited:
Not offered: no bring-your-own AI gateway documented.
Security & governance
Single sign-on
Conditional:
SAML single sign-on for enterprise.
Conditional:
Claude Team and Enterprise organizations support SAML SSO and JIT provisioning via WorkOS.
Conditional:
SAML SSO for Business, Enterprise, and Edu workspaces, configured workspace-wide via the Global Admin Console.
Conditional:
Members sign in with their Cursor account, so existing Cursor SSO and team membership apply.
Audit & activity visibility
Conditional:
Access, agent activity, and tool usage for enterprise review.
Conditional:
Documented activity trails; review your required audit scope.
Conditional:
Compliance Logs Platform exports audit events for Enterprise and Edu workspaces; dot-specific audit coverage not documented.
Conditional:
Advanced audit controls ship on Enterprise plans; Grok Bot-specific audit coverage not documented.
Human approvals
Conditional:
Action-specific permissions and contact controls on every channel; explicit approval gates not documented.
Conditional:
Every action passes a permission checker; admins pre-approve action types per scope with auto-mode allow rules.
Supported:
Custom permission rules; dots request approval before sensitive actions like sending an invoice or making a purchase.
Supported:
Require Approval rules and Auto Review evaluate tool calls and computer actions; passwords and 2FA use human takeover.
Usage visibility & budgets
Supported:
Usage visibility and per-agent credit budgets.
Supported:
Monthly organization usage limit; DMs use personal accounts separately.
Limited:
Not offered: no usage-tracking or per-agent budget controls documented; usage follows ChatGPT plan allowances.
Conditional:
Pooled billing with weekly usage allowances on premium seats; per-Bot budget controls not documented.
Pricing & rollout
Billing model
Supported:
Free plan with $10 in credits every month; paid plans from $20/month. $1 = 100 credits; top-ups available.
Conditional:
Channel work draws from the organization’s usage balance.
Supported:
Included with Pro and Business Premium in eligible markets; the Enterprise, Edu, and Healthcare beta is admin-enabled and off by default.
Conditional:
Individual access via SuperGrok Heavy or Cursor Ultra; self-serve teams use premium seats with usage allowances; Enterprise is rolling out.
Seat pricing
Supported:
Unlimited builders and viewers in your organization.
Conditional:
Channel usage is not charged against individual seats; account eligibility still applies.
Conditional:
Teammates can work with @ChatGPT in Slack or Teams without their own license; dot access follows ChatGPT plans.
Conditional:
Team seat management and consolidated billing on paid plans.
Published by Vybe from public product documentation, reviewed October 5, 2026. “Not verified” means our sources didn’t confirm it, not that the feature is missing. Confirm what matters with each provider.