Extension type
different distribution/scopeGlobal plugin
Personal or workspace distribution can make the plugin available beyond one project or machine.
Execution staysclient/orb side | ordinary plugin runtime model
Semantic visualization prototype | Section 9
Similar names, different systems.
Extension type, distribution or scope, and execution side are separate questions. A name that answers one does not silently answer the others.
Mental-model boundary
Global does not mean server-side. Ordinary and global plugins remain grouped by client/orb execution, while the declarative server-only system keeps different geometry.
Three dimensions, compared directly
| Extension type | Distribution or scope | Execution side | Runtime model boundary |
|---|---|---|---|
| Ordinary plugin | Project or machine-local source in this comparison | Client/orb side | Separate ordinary plugin child process |
| Global plugin | Personal or workspace; available beyond one project or machine | Client/orb side | Ordinary plugin runtime model; distribution differs |
| Declarative server-only agent/tool | Separate declaration system, not a plugin scope | Server side | Do not inherit the ordinary child-process diagram |
Ask each question separately.
First identify the extension type. Then ask how broadly it is distributed. Finally ask where it executes.
This is not a product taxonomy.
The comparison protects the article's runtime model. It does not catalogue every Amp extension or internal server behavior.
The official Global Plugins and Skills guide defines global in terms of availability and scope. The official Plugin API reference documents declarative server-only agents and server-side tool execution. This scene keeps those dimensions separate.