Vybe vs Superblocks vs Claude Tag vs Grok Team Bots

Specialized coworkers with their own responsibilities and tools.

Earlier record: Builds only. Clark AI builds apps but doesn't operate autonomously. Not reverified.

Claude takes on tasks from a channel or DM.

Shared Team Bots built around a role, each with context, plugins, credentials, and memories; public beta on Teams and Enterprise plans.

Shared conversations and Slack threads with people and AI.

Not verified in this review

Teammates can review and refine work in the same thread.

Everyone works with the same Bot and its expertise, while each person's conversations and memories stay private.

In-app chat, Slack, and email; other channels require setup.

Earlier record: Not supported. No multi-channel messaging. Not reverified.

Slack channels and DMs with different access scopes.

Slack with a dedicated handle per Team Bot, alongside the Grok Bot app.

Delegate work to other AI coworkers.

Not verified in this review

Not offered: one Claude works each thread; no delegation between specialized agents documented.

Bots pass context between each other, hand off tasks, and can pass ownership so you are not the router between tools.

Persistent memory, company knowledge, and reusable skills.

Earlier record: Enterprise. Clark Memory — Enterprise plan only. Not reverified.

Persistent channel context, memory, and standing instructions.

Team Bots keep separate context and memories per person while drawing on skills shared across the team.

Schedules, events, and follow-ups with run history.

Earlier record: Enterprise. Enterprise plan only. Not reverified.

Routines on a schedule, channel watch, or repository event.

Routines run on a schedule or, where supported, after an event; background routines run while the laptop is closed.

Hosted browser with persistent sessions; browser service required.

Earlier record: Not supported. No browser automation. Not reverified.

Not offered: work runs in an ephemeral cloud sandbox through channel-scoped tool connections; no browser-control tool documented.

Every Bot runs on a persistent cloud computer with a browser, filesystem, and terminal, and can log in to services in that browser.

Supported meeting recording, transcripts, and follow-up; meeting service required.

Earlier record: Not supported. No meeting capabilities. Not reverified.

Not offered: no meeting recording or transcription documented.

Not offered: connectors cover Gmail and Outlook calendars, but no meeting recording or transcription is documented.

Prebuilt connectors and custom integrations.

Earlier record: 50+. Growing but limited compared to Vybe. Not reverified.

Admin-configured connections scoped to organizations, workspaces, or channels.

Built-in connectors, a preconfigured connector catalog, and custom MCP servers.

Build apps with AI, inspect code, and iterate in a live preview.

Not verified in this review

Interactive pages, charts, and code changes from the thread.

Bots steer Cursor Projects and launch Cloud Agents for code work; no interactive app-building surface documented.

Private, individual, and organization-wide app sharing.

Earlier record: Supported. Not reverified.

Hosted artifacts accessible to people in the channel.

Not offered: Bot share links are public previews on x.ai; no internal publishing surface documented.

Role-based access for owners, admins, editors, and members, with apps kept private, shared, or organization-wide.

Earlier record: Enterprise RBAC. RBAC on Enterprise plan. Not reverified.

Not offered: access is scoped per channel and by organization roles; no per-row data permissions documented.

Not offered: access follows connector permissions such as permission-aware Google Drive; no per-row data permissions documented.

SSH tunnels and custom connections for private resources.

Earlier record: Not supported. VPC deployment available on Enterprise. Not reverified.

Not offered: the ephemeral cloud sandbox reaches tools through configured connections; no private-network or SSH access documented.

Custom MCP servers must be reachable over the public internet; local servers require a tunneling service.

29 models across 11 providers.

Not verified in this review

Choose from permitted Claude models, including Opus and Sonnet.

Runs Grok models; no cross-provider model catalog documented for Bots.

Auto routes tasks to Cheap, Balanced, or Smart tiers.

Not verified in this review

Choose a model for a thread, channel, or DM; automatic task routing not verified.

Not offered: no automatic task-to-model routing documented.

Choose tier models, map task categories, or pin a model.

Not verified in this review

Admins set workspace and channel defaults; individual threads can switch models.

Not offered: no task-category-to-model routing rules documented.

Separate conversation and coding routing policies.

Not verified in this review

Not offered: admins choose permitted Claude models per scope; no separate coding policy documented.

Not offered: Cursor team rules and privacy settings apply to Bots; no separate coding model policy documented.

Bring your own provider keys as part of an enterprise setup.

Not verified in this review

Not offered: Claude uses admin-provided tool accounts with credentials kept out of the sandbox; no customer model keys documented.

Credentials connect third-party tool APIs; no customer AI provider keys documented.

OpenRouter and Vercel AI Gateway.

Not verified in this review

Not offered: no bring-your-own model gateway documented.

Not offered: no bring-your-own AI gateway documented.

SAML single sign-on for enterprise.

Earlier record: Enterprise. Enterprise plan only (SSO/SAML/OIDC). Not reverified.

Claude Team and Enterprise organizations support SAML SSO and JIT provisioning via WorkOS.

Members sign in with their Cursor account, so existing Cursor SSO and team membership apply.

Access, agent activity, and tool usage for enterprise review.

Earlier record: Enterprise. Enterprise plan only. Not reverified.

Documented activity trails; review your required audit scope.

Advanced audit controls ship on Enterprise plans; Grok Bot-specific audit coverage not documented.

Action-specific permissions and contact controls on every channel; explicit approval gates not documented.

Not verified in this review

Every action passes a permission checker; admins pre-approve action types per scope with auto-mode allow rules.

Require Approval rules and Auto Review evaluate tool calls and computer actions; passwords and 2FA use human takeover.

Usage visibility and per-agent credit budgets.

Not verified in this review

Monthly organization usage limit; DMs use personal accounts separately.

Pooled billing with weekly usage allowances on premium seats; per-Bot budget controls not documented.

Free plan with $10 in credits every month; paid plans from $20/month. $1 = 100 credits; top-ups available.

Not verified in this review

Channel work draws from the organization’s usage balance.

Individual access via SuperGrok Heavy or Cursor Ultra; self-serve teams use premium seats with usage allowances; Enterprise is rolling out.

Unlimited builders and viewers in your organization.

Earlier record: $49-80/seat. $49-80 per AI builder/month. Not reverified.

Channel usage is not charged against individual seats; account eligibility still applies.

Team seat management and consolidated billing on paid plans.