Vybe vs Claude Tag vs Gumloop vs Viktor

Specialized coworkers with their own responsibilities and tools.

Claude takes on tasks from a channel or DM.

Reusable agents with skills and tool access.

An AI coworker that works across business tools.

Shared conversations and Slack threads with people and AI.

Teammates can review and refine work in the same thread.

Shared agents with owner, editor, viewer, and use-only access.

Workspace members can work with Viktor in channels and DMs.

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

Slack channels and DMs with different access scopes.

Web chat, Slack, and API access to shared agents.

Slack and Microsoft Teams.

Delegate work to other AI coworkers.

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

Agents can hand tasks to other agents.

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.

Persistent channel context, memory, and standing instructions.

Reusable skills and playbooks that evolve with use.

Workspace-scoped skills and memory.

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

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

Recurring or one-time scheduled runs plus event triggers from Gmail, Slack, Teams, and more.

Recurring tasks and proactive automations.

Hosted browser with persistent sessions; browser service required.

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

Interactive browser automation via the Website Scraper's Web Agent mode, an AI browsing node, and the Chrome extension.

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: no meeting recording or transcription documented.

No native recording or transcription; meeting work centers on Gumball pre-meeting briefs from a connected calendar.

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.

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

Connectors, shared credentials, and MCP support.

3,200+ business-tool integrations advertised.

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

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

Not offered as a business-app builder: the platform ships agents, workflows, and hosted agent pages.

Build and deploy internal apps connected to business tools.

Private, individual, and organization-wide app sharing.

Hosted artifacts accessible to people in the channel.

Hosted agent pages on gumloopagents.com with sign-in and role-based access.

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 is scoped per channel and by organization roles; no per-row data permissions documented.

Not offered: access control uses organization and team roles plus custom feature roles, not per-row data permissions.

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

SSH tunnels and custom connections for private resources.

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

Not offered: tools connect through cloud connectors, MCP, and webhooks; 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.

Choose from permitted Claude models, including Opus and Sonnet.

35+ models advertised.

Choice across OpenAI, Anthropic, and Google.

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

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

Auto picks the model for each agent message, with mid-run escalation and fallbacks.

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

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

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

Admins restrict models, pin per-agent presets, and set fallbacks; task-category mapping not offered.

Workspace defaults and individual scheduled-task settings.

Separate conversation and coding routing policies.

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

Not offered: AI model governance restricts and pins models platform-wide; 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.

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

BYOK on Pro and above; organization-wide keys on Enterprise.

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 model gateway documented.

Provider proxy URL, custom headers, and model name mapping per provider on Enterprise.

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

SAML single sign-on for enterprise.

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

SAML SSO and SCIM for enterprise identity.

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

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

Documented activity trails; review your required audit scope.

Agent activity, tool-call tracking, and analytics.

Enterprise audit logging; confirm required event coverage.

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

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

App guardrails, spending approvals, and scoped policies.

Sensitive actions can wait for explicit approval in chat.

Usage visibility and per-agent credit budgets.

Monthly organization usage limit; DMs use personal accounts separately.

Spend caps by agent, team, or organization.

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.

Channel work draws from the organization’s usage balance.

Pro starts at $37/month; credits and an orchestration fee apply.

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

Unlimited builders and viewers in your organization.

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

Unlimited seats listed on Pro and Enterprise.

No per-seat licenses; credits reflect model usage.