Plugins
Plugins, built by the herd
A Bentomux plugin is a folder of JavaScript that adds buttons, panels, tabs, modals and background services to the app. Every repository carrying the GitHub topic below is listed here, most-starred first.
Listings are not reviewed. A plugin runs in the app's own context, so permissions are a declared contract rather than a sandbox — review what you install the way you would review a shell alias. How plugins and permissions work.
Browse the catalog
the full index — search it, then install from the app
topic:bentomux-plugin · most-starred first, repo name breaking ties
- petdex-pluginsv1.6.0
Plugins for Bentomux — discovered by the bentomux-plugin topic
farasjibran/petdex-plugins
Read from GitHub when this page was built. The app re-reads it on every open, and its copy is at most six hours old.
Install from the app
Open Plugin Studio
The catalog lives in the app, not on this page. This site lists what is published; the app is what downloads, verifies and installs it.
Bentomux → Plugin Studio → Browse marketplace…
Install from the row
Each row shows the repo, its star count, the release tag and the asset download count. Installing downloads the release asset and checks it against the sha256 GitHub published at upload.
owner/your-plugin ★ 314 ↓ 1.2k → Install
Read the review screen
The real plugin.json is read out of the downloaded archive and shown before anything runs: its id, its name, the permissions it asks for and the hosts it may reach. Nothing runs until you confirm.
Updates keep one rollback
A row offers an update only when the release tag is strictly newer than the installed manifest version. The previous version is kept on disk, and Roll back appears in Settings → Plugins.
Publish
Get your plugin listed
GitHub is the catalog: the topic makes a repository discoverable and the release is what makes it installable. Both are required, and there is no submission form, account or review queue.
Push a public repo
A folder holding plugin.json and an ES module entry. Start from one of the seven templates that ship with the app.
cp -r resources/plugin-templates/basic ~/acme-habit-tracker
Add the topic
Add bentomux-plugin to the repo's topics. That is the entire registration step — there is nothing to submit and nobody to approve. Topics take a few minutes to index.
gh repo edit --add-topic bentomux-plugin
Validate before you ship
The validator checks the manifest, the id namespace, the entry file, the contribution ids, the permissions and the network origins without running any of your code.
bentomux --plugin-validate ~/acme-habit-tracker --json
Publish a release with one .zip
The plugin files must sit at the root of the zip — not inside a wrapper directory, which is why the auto-generated source tarball will not do. Exactly one .zip asset; zero is not installable and two is ambiguous.
gh release create v1.0.0 ../acme-habit-tracker-1.0.0.zip
Tag = manifest version
The tag is stripped of one leading `v` and parsed as semver, then compared against the installed manifest version. A repo tagged `v1.1.0` whose manifest still says `1.0.0` keeps offering the same update forever.
The full publishing reference — digests, the archive layout, troubleshooting — lives in the application repository's PLUGIN_MARKETPLACE.md (opens in a new tab). The plugin platform itself — manifest, permissions, contribution points — is documented on this site's plugins page.
What the numbers are, and are not
- ★ stars
- GitHub's star count for the repository, surfaced as-is. Not an endorsement by Bentomux.
- ↓ downloads
- Downloads of that one release asset — including downloads that were never installed by Bentomux.
- version
- The release tag. The manifest version inside the archive is what the app actually compares, and it is read after download.
- order
- One order, and it is the only one offered: most stars first, with the repository name breaking a tie. The app implements no other sort, so none is described here.