| Term | Definition |
|---|---|
| Access level | Who can use an AI coworker or an app. Coworkers: Anyone can talk to name, Specific people or You only, shown on the coworker’s Sharing tab as Everyone at organization, Only people invited or Private. Apps: Anyone in the organization, Specific people or You only. See Coworker sharing and App access. |
| Activity | The run history of a coworker, in Usage & Activity → Activity. Each run shows its input, response and the steps taken. |
| AGENTS.md | A coworker’s standing instructions: its role, personality and rules. It’s included in every conversation. See Instructions. |
| AI coworker | An AI teammate with a name, avatar, role, instructions, knowledge and connections. It works in Slack, email, meetings and the Vybe web app. |
| App | An internal web application with its own database, built with AI in the app editor and published to a private URL. See Apps overview. |
| Archive | Takes a coworker or app out of active use without deleting it. Archived coworkers stop their automations; archived apps go offline. Both can be restored. |
| Artifact | A self-contained interactive page a coworker publishes: a report, dashboard, diagram or calculator. See Artifacts. |
| Auto | The default model setting. Vybe picks a suitable model for the task. See AI models. |
| Capability | A family of tools a coworker can use, such as Web Search or Image Generation. Each one can be set to Full access, Read only, Custom or Off. See Capabilities. |
| Chats | The section of a coworker’s page where you talk to it in the web app, organized into channels and threads. |
| Checkpoint | A saved version of an app’s code, created after each AI change. You can restore it from the app chat. See Version history. |
| Connection | An integration, MCP server, custom API or database connected to your organization. See Connections overview. |
| Credit | The unit of AI usage. One credit is worth $0.01. See Plans and credits. |
| Custom API | A REST API you add yourself, with credentials Vybe stores and injects on each call. See Custom APIs. |
| Data query | A saved SQL query against an external database that apps and coworkers can run. See Data queries. |
| Effort | How long a model thinks before answering: Low, Medium, High, Extra high or Max. Higher effort is slower and uses more credits. |
| External database | Your own PostgreSQL, MySQL or Redshift database connected to Vybe. Read-only by default. See Databases. |
| Gallery | A collection of ready-made coworkers you can start from, at vybe.build/gallery. |
| Guest | A role for people outside your core team. Guests only get the apps and coworkers shared with them, and talk to coworkers in Slack rather than in the Vybe web app. |
| Ingestion log | The record of what a coworker learned from Slack and what it did with each thread. See Knowledge and memory. |
| Integration | A connection to a third-party app such as HubSpot, Salesforce or Google Drive. See Integrations. |
| Knowledge | A coworker’s notes, skills and files. The Knowledge page in the sidebar shows organization memory in one place. |
| MCP server | A server that exposes tools through the Model Context Protocol. Coworkers can use its tools once granted access. See MCP servers. |
| Models Gateway | An organization setting that routes AI usage through your own AI gateway key instead of Vybe credits. See Models and gateway. |
| Monthly usage limit | A per-coworker spending cap. When it’s reached, the coworker pauses until the next month or until someone raises the limit. See Usage and activity. |
| Note | A piece of memory. Notes belong to one coworker, to a person, or to the whole organization. |
| Organization | Your team’s workspace. Coworkers, connections, apps, members and billing belong to it. |
| Organization database | A managed PostgreSQL database shared by coworkers and apps in your organization. See Databases. |
| Pin | Keeps a coworker or app at the top of your lists. Pinned coworkers also appear in the sidebar’s Pinned section. Pins are personal. |
| Preview | The live version of an app running in its sandbox while you build it. |
| Publish | Makes the latest version of an app available at its URL. See Publishing. |
| Run | One piece of work by a coworker, started by a message, a scheduled task or a trigger. |
| Sandbox | An isolated cloud environment. Each coworker has one for running commands and keeping files, and each app has one for its preview. |
| Scheduled task | Work a coworker does on a schedule. See Scheduled tasks. |
| Skill | A note that teaches a coworker how to do a specific job. Skills can belong to one coworker, a person or the organization. |
| Slack memory | Coworkers learning facts from public Slack channels they belong to. See Knowledge and memory. |
| Thread | A conversation inside a channel, in Slack or in a coworker’s Chats. |
| Trigger | A rule that makes a coworker act when an event happens, such as a new Slack message or a new record in a connected tool. See Triggers. |
| Viewer | A role that can use coworkers and apps shared with them, but can’t create or edit them. |
Reference
Glossary
Definitions of the terms used throughout Vybe