Plugins can add central views, workspace sidebars, commands, keyboard shortcuts and controls in the application’s extension slots. A package can also supply themes.
The application installs local, prebuilt folders. There is no plugin marketplace or npm installation flow in the Plugins screen.
Where to start
Section titled “Where to start”| Goal | Shortest path |
|---|---|
| Install a built plugin | Follow the steps below; no Node.js or Rust required |
| Create a plugin | Your first plugin and template selection |
| Extend an existing project | Manifest, API, views and state |
| Add a command or button | Commands and interface contributions |
| Improve appearance | Styles and assets |
| Release or troubleshoot | Desktop qualification, CLI, packaging and recovery |
A package is a folder containing plugin.json, built code and assets. A manifest declaration describes a contribution; registration inside activate() supplies its implementation. A revision identifies the exact installed contents, independently of the author’s version number.
Install a plugin
Section titled “Install a plugin”- Obtain the built package from its author. Its root must contain
plugin.jsonand the compiled files referenced by that manifest. - Open Settings > Plugins > Import plugin and select the package folder.
- Find the imported plugin and turn on its enable switch.
- Read the package details and select Trust and enable if you approve this revision.
- Open a view or run one of its commands. A lazy plugin activates when first used; a startup plugin activates after the workbench is ready.
Importing does not run plugin JavaScript. Approval applies to the installed content hash, not to a verified publisher identity.
Extract ZIP downloads first. Select the directory directly containing plugin.json, not the archive or source project. For a theme-only package, skip enabling code and select it in Settings > Themes.
Access and trust
Section titled “Access and trust”Plugin code runs in the main application’s JavaScript environment. It is not sandboxed and can have application-level access, including to files and terminals. Only enable code you trust. The public SDK describes supported integration points; it is not a permissions boundary.
Settings reads plugin metadata without running the plugin module. Theme contributions become available in Settings > Themes after import, even if executable code remains disabled.
Disable, update or remove
Section titled “Disable, update or remove”Use the enable switch to disable a plugin. Choose Uninstall to remove it. If the plugin has registered unsaved views, resolve Save, Discard or Cancel in the main window first. Canceling or failing to save keeps the plugin available.
Open views from a disabled or missing plugin become placeholders. Their saved descriptors remain until you close them or restore a compatible plugin.
To update a plugin, disable it, import the new built folder and approve the new revision. When earlier code has already been loaded, use Restart Lomi before running the replacement. See packaging and recovery for the complete workflow.
Write your own
Section titled “Write your own”Start with Your first plugin. It builds a small panel that shows the active project and remembers whether its path is visible.
Source: plugin settings, native package management.