Vybe vs Grok Team Bots vs Claude Tag vs Viktor

Specialized coworkers with their own responsibilities and tools.

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

Claude takes on tasks from a channel or DM.

An AI coworker that works across business tools.

Shared conversations and Slack threads with people and AI.

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

Teammates can review and refine work in the same thread.

Workspace members can work with Viktor in channels and DMs.

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

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

Slack channels and DMs with different access scopes.

Slack and Microsoft Teams.

Delegate work to other AI coworkers.

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

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

External agents can delegate work to Viktor through its MCP server and public API; internal multi-agent handoffs not documented.

Persistent memory, company knowledge, and reusable skills.

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

Persistent channel context, memory, and standing instructions.

Workspace-scoped skills and memory.

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

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

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

Recurring tasks and proactive automations.

Hosted browser with persistent sessions; browser service required.

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

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

Works the web directly: logs in, clicks through pages, fills forms, and pulls data from real sites.

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

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

Not offered: no meeting recording or transcription documented.

Meeting follow-through runs through connected meeting tools like Symbl.ai, Fireflies, or Gong; native recording and transcription not documented.

Prebuilt connectors and custom integrations.

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

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

3,200+ business-tool integrations advertised.

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

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

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

Build and deploy internal apps connected to business tools.

Private, individual, and organization-wide app sharing.

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

Hosted artifacts accessible to people in the channel.

Viktor Pages share finished documents and dashboards at links; Viktor Spaces are internal tools your team signs into.

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

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

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

Not offered: enterprise access is role-based (RBAC); no per-row data permissions documented.

SSH tunnels and custom connections for private resources.

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

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

Not offered: tools connect through cloud integrations and per-user OAuth; no private-network or SSH access documented.

29 models across 11 providers.

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

Choose from permitted Claude models, including Opus and Sonnet.

Choice across OpenAI, Anthropic, and Google.

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

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

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

Workspace model and task-level cost presets; automatic category routing not verified.

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

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

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

Workspace defaults and individual scheduled-task settings.

Separate conversation and coding routing policies.

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

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

Not offered: model governance is workspace-wide with per-task presets; no separate coding policy documented.

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

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

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

Not offered: model providers run under Viktor-managed agreements; tool credentials are per-user OAuth handled by the Viktor gateway.

OpenRouter and Vercel AI Gateway.

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

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

Not offered: models run through the Viktor-managed stack; no bring-your-own gateway documented.

SAML single sign-on for enterprise.

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

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

SAML SSO via Okta, Entra ID, Google Workspace, OneLogin, or any SAML 2.0 IdP.

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

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

Documented activity trails; review your required audit scope.

Enterprise audit logging; confirm required event coverage.

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

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

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

Sensitive actions can wait for explicit approval in chat.

Usage visibility and per-agent credit budgets.

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

Monthly organization usage limit; DMs use personal accounts separately.

Auto-topups with monthly spend caps; per-user spend caps on Enterprise.

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

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

Channel work draws from the organization’s usage balance.

Credit-based plans from $50/month, with trial credits.

Unlimited builders and viewers in your organization.

Team seat management and consolidated billing on paid plans.

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

No per-seat licenses; credits reflect model usage.