List installed plugins and their runtime state
GET/plugins
Returns every plugin known to the database, merged with the loader's live state so the UI can tell "enabled but failed" from "disabled". Open to any authenticated user, not just admins: the app shell calls this on every session to decide which plugin-contributed tabs and rail items to register, so gating it behind admin.plugins.manage would break the shell for non-admin users.
Non-admins get only what the shell needs. What a plugin is allowed to do, what has been granted to it and why it failed are operational details, so capabilities, grants, lastError and publicRoutes are included only for holders of admin.plugins.manage. publicRoutes lists the HTTP paths and socket paths a running plugin serves without core's login check.
The frontend fields drive the browser's plugin loader: frontend says there is a bundle at /plugin-assets/<id>/frontend.js, assetVersion is its cache key, css says a stylesheet sits beside it, and locales lists the languages it ships ("en" and xx_YY). dependencies and optionalDependencies let the loader activate frontends in the same order the server does. engine holds the manifest's api and termix ranges, so other clients (the mobile app) can tell whether they understand the plugin.
On a desktop linked to a server, runsOnServer marks plugins that only run on that server and stay off here on purpose, and, for admins, managedByServer marks plugins whose on/off state the server decides.
While TERMIX_SAFE_MODE is on, an enabled plugin that safe mode keeps off reports state: "safe-mode".
Responses
- 200
List of plugins.