Skip to main content
This page explains the main ideas you’ll meet in Vybe and links to the details for each.

​
Organization

An organization is your team’s workspace. AI coworkers, connections, apps, members and billing all belong to it. You can belong to several organizations and switch between them from the user menu at the bottom of the sidebar. Each organization connects to one Slack workspace. Members have one of five roles: Owner, Admin, Editor, Viewer or Guest. Owners, Admins and Editors can create coworkers and apps; Viewers use what’s shared with them; Guests only get the apps and coworkers shared with them directly. See Members and roles.

​
AI coworker

An AI coworker is an AI teammate with a name, an avatar and a role, such as “Recruiting coordinator” or “Sales ops”. Each coworker has:
  • Instructions in a note called AGENTS.md that describe its role, personality and rules. See Instructions.
  • Knowledge: notes, skills and files it builds up over time. See Knowledge and memory.
  • Capabilities that control which tools it may use, and how much. See Capabilities.
  • Connections to the integrations, MCP servers, APIs and databases it has been given access to.
  • Automations that make it act without being asked.
  • Its own Slack app, email address and calendar.
You decide who can talk to each coworker and who can manage it. See Sharing and access.

​
Channels: where coworkers work

Coworkers meet your team where the work happens:

​
Chats and threads

In the web app, each coworker has channels, like Slack, starting with #general. Each message you post starts a thread, and replies stay in that thread. A coworker’s channels and threads are visible to everyone who can access that coworker.

​
Knowledge and memory

Coworkers remember things in notes. A note can belong to one coworker, to a person (every coworker sees it when talking to that person) or to the whole organization. Skills are notes that describe how to do a specific job, step by step. Coworkers can also learn from the public Slack channels they’re in. The Knowledge page in the sidebar shows everything in one place.

​
Connections

Connections give coworkers and apps access to your tools and data:
  • Integrations: thousands of apps, such as HubSpot, Salesforce, Notion, Google Workspace and Jira.
  • MCP servers: tools exposed through the Model Context Protocol.
  • Custom APIs: any REST API you add yourself.
  • Databases: your own PostgreSQL, MySQL or Redshift databases, and shared organization databases.
A coworker can’t use a connection until someone gives it access, and you choose whether that access is read-only or full. See Connections overview.

​
Automations

Automations let a coworker work without anyone messaging it:
  • Scheduled tasks run on a schedule, for example “every weekday at 8am”.
  • Triggers run when something happens, for example a new message in a Slack channel or a new record in a connected tool.
See Automations overview.

​
Artifacts

An artifact is an interactive page a coworker publishes for you: a report, a dashboard, a diagram or a calculator. It can show live data from your connections. See Artifacts.

​
Apps

An app is a full internal web application with its own database. Coworkers can build apps when you ask them to, and builders can work on apps directly in the app editor. When an app is ready, you publish it to a private URL that only your organization can open. See Apps overview.

​
Credits

Credits measure AI usage. Each coworker run uses credits according to the model and the amount of work. Every plan includes a monthly credit allowance, and you can set a monthly limit for each coworker. See Plans and credits.

​
How it fits together