Plugins, made by
the people who use it.
Effects for ryolune and kimchi, filters for nori, functions for folio, tools for zenith: plugins written in Rust by the people who use lsuite, often with their agent, and by lsuite itself. A plugin is native code that runs inside the app, so every version is reviewed before anyone can install it.
Installing comes with lsuite Pass · browsing and publishing are free · every version reviewed · SHA-256 checked
Approved, ready to install.
From the lsuite launcher's next release, install them from its Marketplace area or with lsuite-cli market.*: the file is checked against its SHA-256, unpacked into the app's plugin folder and loaded without a restart.
The first plugins are on their way — publish yours
No plugins yet. Build one with your app's agent and publish it: every version is reviewed before anyone can install it.
Publish a pluginThe plugins every lsuite app already loads.
Every lsuite app has plugins: bundles with a plugin.toml and a library built against the app's Rust SDK (the contract). The marketplace is where they travel from one person's computer to everyone's.
Rust, inside the app
A plugin runs where the app's own effects run: the audio thread, the compositor, the filter worker. Fast, and never blocking the window.
Made by anyone
Anyone with an lsuite account can publish. Plugins lsuite makes itself are marked by lsuite; their ids start xyz.lsuite.
One file per system
Each version comes for macOS (Apple silicon and Intel), Linux and Windows, as its author built it: the card says which.
Every paid plan installs from the marketplace.
Plus, Pro and Studio bring lsuite AI, lsuite Cloud and the lsuite Marketplace. On Free you can browse and publish; installing comes with a plan. The apps themselves stay free. A demo for now: no payment is taken.
Ask your agent for it. Then share it.
In any app's Plugins area, "Describe the plugin you want" starts the app's agent on the plugin recipe: it scaffolds a crate from the SDK, builds it until it's green and installs it. Then publish the bundle folder.
- Build it with your app's agent, or by hand:
plugin.new,plugin.build,plugin.publishLocal. - Publish it with
lsuite-cli market.publish path=<bundle folder>, or from the launcher's Marketplace area (in its next release). Sign in with your lsuite account first. - Wait for the review. Every version is read and tried before it is listed; its status and any note are in your account. An approved version never changes: fixes are a new version.
- The id is yours once published (reverse-DNS, like
com.yourname.tape-warmth): only you publish its next versions.
No payment for creators yet: a revenue share is for when payments are live. Bundles are up to 15 MB per platform in the demo.
# 1. build it (your agent runs the same commands) ryolune-cli plugin.new name=tape-warmth kind=effect ryolune-cli plugin.build name=tape-warmth ryolune-cli plugin.publishLocal name=tape-warmth # 2. publish the bundle folder for review lsuite-cli market.publish path=~/.lsuite/plugins/ryolune/com.example.tape-warmth
Native code, so nothing goes unread.
A plugin can do what the app can do. That is why the marketplace is reviewed, version by version, and why every file can be checked.
Every version, before it's listed
lsuite reads each submission's manifest and files and tries it before approving it. A version that was approved can't be replaced, and one found unsafe is taken down.
The file you were shown
Each file's size and SHA-256 are listed, and the launcher checks them before it unpacks anything into ~/.lsuite/plugins/<app>/.
Off in one click
Every app's Plugins area shows each plugin with an on/off switch, and a plugin that panics is switched off. Agents install plugins only when you allow it.
Before you install or publish.
Do I need the marketplace to have plugins?
No. Every app ships with its stock plugins, loads the plugin formats of its trade, and builds new ones with your agent, free. The marketplace is for plugins other people made.
Who can publish?
Anyone with an lsuite account, Free included. Each version waits for review; you'll find its status, and the reviewer's note if it was turned down, in your account.
What does the review look at?
That the bundle is what it says (its plugin.toml, id, version and app), what the library does, and that it behaves in the app. The server already refuses archives that don't match their submission.
Are creators paid?
Not yet. lsuite Pass is a demo and takes no payment; a revenue share for creators is for when payments are live.