External tools, ordinary repositories

Plugins

Add Project tools and automated integrations without modifying swe-mux. Every listing resolves to inspectable source at an exact Git commit, and no plugin runs until you approve its current bytes.

Plugins run as your user. Manifest permissions limit cooperative swe-mux callbacks. They do not sandbox filesystem, process, credential, or network access.

Catalog

loading

Official plugins are maintained with swe-mux. Community listings have a valid manifest and indexed revision but are not security-reviewed or endorsed.

Publish a plugin

  1. Put swe-mux-plugin.toml, runnable source, tests, README, and a license in one standalone public repository.
  2. Run swemux plugin validate . and test installation from a clean checkout.
  3. Publish a release whose tag matches the manifest version.
  4. Add the swe-mux-plugin GitHub topic. The catalog validates the repository before listing it.

The complete manifest, permission, testing, and lifecycle contract is in the plugin authoring guide.

Local authors can use the configurable development folder for inert direct-child discovery, while existing repositories remain explicitly linkable from any location.