Vybe vs Claude Tag vs Claude Cowork vs Gumloop

Specialized coworkers with their own responsibilities and tools.

Claude takes on tasks from a channel or DM.

Claude handles tasks in a working session.

Reusable agents with skills and tool access.

Shared conversations and Slack threads with people and AI.

Teammates can review and refine work in the same thread.

Personal working sessions. Shared Slack-channel work is handled by the separate Claude Tag product.

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

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

Slack channels and DMs with different access scopes.

Desktop, web, and mobile; availability depends on plan and rollout.

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

Delegate work to other AI coworkers.

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

Task dispatch routes development work to Claude Code sessions; knowledge work runs in Cowork.

Agents can hand tasks to other agents.

Persistent memory, company knowledge, and reusable skills.

Persistent channel context, memory, and standing instructions.

Role-based plugins, skills, and connected tools.

Reusable skills and playbooks that evolve with use.

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

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

Cloud tasks can run while devices are offline; local sessions use your computer.

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

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.

Built-in browser or Claude in Chrome, subject to admin controls.

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

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

Not offered: no meeting recording or transcription documented.

Not offered: sessions work with files, the web, and connected tools; no meeting recording or transcription documented.

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

Prebuilt connectors and custom integrations.

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

Connectors for Slack, Google Workspace, Microsoft 365, and other tools.

Connectors, shared credentials, and MCP support.

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

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

Works with files in a chosen folder; evaluate your app deployment workflow separately.

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

Private, individual, and organization-wide app sharing.

Hosted artifacts accessible to people in the channel.

Not offered: outputs are documents, files, and deliverables in your Claude account; no internal app-publishing surface documented.

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

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 is account- and admin-scoped; no per-row data permissions documented.

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

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: cloud sessions reach tools through connectors and MCP; no private-network or SSH access documented.

Not offered: tools connect through cloud connectors, MCP, and webhooks; no private-network or SSH access documented.

29 models across 11 providers.

Choose from permitted Claude models, including Opus and Sonnet.

Claude product experience, rather than a cross-provider model catalog.

35+ models advertised.

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

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

Not offered: runs on Claude models with no automatic cross-model routing documented.

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

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

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

Not offered: admins control feature availability, not task-to-model routing rules.

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

Separate conversation and coding routing policies.

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

Not offered: one Claude experience spans chat and coding work; no separate coding model policy documented.

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

Not offered: runs on Anthropic-managed credentials; no customer provider keys documented.

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

OpenRouter and Vercel AI Gateway.

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

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

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

SAML single sign-on for enterprise.

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

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

SAML SSO and SCIM for enterprise identity.

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

Documented activity trails; review your required audit scope.

Admins can monitor Cowork activity via OpenTelemetry; Cowork activity is not yet in the Compliance API.

Agent activity, tool-call tracking, and analytics.

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.

Per-task permission approvals; admins control auto-approve mode and connector-tool always-allow.

App guardrails, spending approvals, and scoped policies.

Usage visibility and per-agent credit budgets.

Monthly organization usage limit; DMs use personal accounts separately.

Usage analytics for admins on Team and Enterprise plans.

Spend caps by agent, team, or organization.

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.

Available through paid Pro, Max, Team, or Enterprise plans.

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

Unlimited builders and viewers in your organization.

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

Per-seat pricing: Team standard seats $20/seat/mo billed annually ($25 monthly); Premium $100; Enterprise custom.

Unlimited seats listed on Pro and Enterprise.