Remove a plugin or disconnect it [write]
Changed onA bare name removes that installed plugin bundle exactly as before (deprecated: the answer carries a Deprecation header; use bundle:<name>): its skills are deleted, and a skill a session still holds is switched off (no longer attached to new sessions) instead. A Plugin id runs the source's own removal, and never deletes a connection a plugin uses: app:<slug> disconnects your connection of that app only with disconnect=true (connection_id when you have several, else 409 connection_required naming them; a workspace key is 403 person_required), chat:<platform> disconnects your chat-app connection, tool:<id> switches it off in the workspace's default environment, bundle:<name> uninstalls it (the apps it used stay connected), skill:<id> deletes it (409 skill_in_use while attached), mcp:<id> deletes the vault secrets that hold that server's address (404 when none; a server an agent declares is removed from the agent). Mac features and browser logins are 422 not_switchable. A merged product's first id (app:slack_v2) also disconnects its chat-app connections and switches its tool off, answering result: {removed, kept}; the person's app connection is kept unless disconnect=true. Each alias (chat:slack) removes only itself, as before. To stop one agent or chat using a plugin, use PUT /plugins/{id}/off.
Request
- Base URLhttps://api.agentsky.dev/v1
- URLhttps://api.agentsky.dev/v1/plugins/{name}
- AuthHTTP bearer
Path parameters
Query parameters
Which of your connections, for an app or a chat app
app:<slug> only: disconnect that account at the provider. Without it, 409 disconnect_required: the person may use it elsewhere
Response
Removed
Changes
- info
endpoint added
- info