Manage plugins and access
After installing a plugin, use this page to check its account, access, updates, and removal. Installation delivers capabilities; actual use also depends on tools, identities, provider permissions, and task authorization. See Plugins and app connections for installation and MCP servers for custom servers.
Review the workflow before choosing capabilities
Define the task, resources, read/write needs, and recipients. Record source, maintainer, version, update method, local dependencies, and charges. Review bundled instructions, MCP tools, and services separately; one package can contain several data and execution paths.
| Object | Review |
|---|---|
| Plugin and skills | Source, instructions, supporting files, changes, intended work |
| Local MCP | Launch command, dependencies, environment, process permissions |
| Remote MCP or service | Endpoint, authentication, identity, data destination |
| External account | Projects, files, messages, read/write permissions |
| Task authorization | Tools, change scope, confirmation requirements |
Installation does not establish connectivity; connectivity does not establish resource access; reading does not establish write authorization. Retain evidence for each layer.
Check that a plugin works
- Install or configure from a trusted source and identify actual version and dependencies.
- Authenticate the connection and confirm the intended service identity and scope.
- Inspect tools, read an approved test resource, and verify the result.
- Test permitted and denied requests against configured restrictions. Use a disposable approved target for writes.
- Verify output, recipient, and location in your own task. Keep the plugin source available for troubleshooting and help.
Verify publication and sending in the destination system. After a timeout, inspect the destination before retrying to avoid duplicate writes.
Re-review updates
Compare instructions, tools, dependencies, endpoints, and authorization scope. New write tools or changed destinations require another workflow review. Preserve the previous version or non-secret reconstruction details and validation evidence.
Manage plugin updates, skill-file updates, and provider permissions separately. Reinstallation cannot restore revoked account access. Repair failed authentication at its connection rather than reinstalling all extensions.
Disable, remove, and revoke
Identify dependent tasks and replacements first. Use the offered disable/removal controls and verify tasks no longer use that entry. Revoke remote authorization and keys with the provider; local removal does not delete remote data.
Address multiple paths separately. For example, the voice product bridge used by local external agents does not read the voice-plugin switch. Revoke the corresponding provider credential to stop that path. See plugin disablement.
If connection removal offers history handling, choose explicitly and verify its result. Successful removal and failed history cleanup are separate outcomes. After the change, check which plugins remain enabled, which accounts they use, and whether any task still depends on the old connection.