Skills, connectors, and plugins
Find integrations in Marketplace, install them, and grant Chat or Code only the access each surface needs.
Skills, connectors, and plugins
A skill gives the assistant instructions for a particular kind of task. A connector gives it callable access to an external service. A plugin groups related skills or connections. Instruction-only skills may require software or a connected service before the requested work can run.
| Surface | What applies |
|---|---|
| Chat on PC, web, and mobile | Account-backed library, Chat-enabled entries, and compatible connection flows |
| Desktop Code | Code-enabled local installation and connections, subject to the selected runtime |
| Mobile Remote | The paired desktop's installed capabilities and permissions |
| Files | No separate tool execution surface; use Chat or Code to work with documents |
See Skills and plugins in Code for local setup and runtime differences.
Find an integration
Users open Skills & Plugins from the Chat left rail or visit Skills & Plugins. The page has Marketplace and Installed tabs. Marketplace is the discovery surface: it searches the library, filters entries by All, Chat, or Code, groups entries by category or type, opens a preview, and adds an entry. Marketplace discovery does not grant an installed connector access by itself.
Install and scope
Installed is the control surface. Each connector can be enabled for Chat, Code, or both when its catalog entry supports those surfaces. A plugin detail view lists its bundled skills; child skills can be enabled or disabled from that installed detail. The setting follows the canonical skill across collections, so a child toggle applies wherever that skill is offered.
View diagram text
flowchart TD accTitle: When an installed capability can be used accDescr: An installed entry must support the surface, be enabled with its child skill, have any required connection, and fit agent and task permissions. A[Install from Marketplace] --> B[Enable Chat or Code in Installed] B --> C[Enable the required child skill] C --> D[Complete required connection] D --> E[Check agent and task permissions] E --> F[Use with a compatible model or runtime]
Sign-in and keys
Authentication depends on the connector. Some entries are keyless or platform-provided. Others use OAuth or a user-supplied key. Chat sign-in is account-backed and shared across supported Chat surfaces. Code connections belong to the local desktop and remain separate from Chat tokens. The web and iPhone surfaces cannot complete a connector flow that requires a desktop loopback callback; the affected entry identifies the desktop sign-in step before Chat can use the saved connection.
Review and remove access
Connector cards show whether an entry is installed, enabled, signed in, or waiting for a key. Sign in, Add Key, Disconnect, Clear Key, and Remove act on the selected connector and surface. Integrations with external effects can display a confirmation dialog before enablement, identifying account or repository access, possible vendor charges, and write or trading capability. A catalog label does not grant broad authority. See Chat, Code, Agents, and Privacy.