Plugins

The extension shelf: what is published, what runs code, and what an admin can disable.

Shared extensions — algorithm patches that inject with a job, data scripts that run on your machine, and declarative packs the platform only reads.

The extension shelf, with built-in and published packages.

What you see

Badge	What it means
Built-in	Ships with the platform. Cannot be disabled or deleted
Published	Uploaded by a user with sf plugin publish. An administrator can disable it
Runs code	Code in this package executes in your own training container or on your own machine

The Runs code badge is the one to read. It marks the difference between a package the platform parses and a package that executes — which is exactly the line that decides how strictly it was gated. See extension points.

What you can do

• Search by name, summary, author or keyword.
• Copy the install reference — the sf plugin install line for a plugin.
• Open the detail page for its manifest, version history, digest and README.

Administrators additionally get Manage: enable or disable a published extension across the whole deployment. Disabling blocks new submissions from referencing it; running and queued jobs are unaffected, and the history stays readable.

Where built-in methods are

Not here. Built-in methods are not extensions — they are the platform, and there is nothing to manage about them. They live on Methods. To turn one off, an administrator changes FORGE_ALLOWED_RECIPES, not a toggle on this page.