A module is a plain GitHub repo with a manifest and some commands. Bash, Python, Lua, Rust, Node, anything your machine can run. No SDK, no plugin runtime, no registry to sign up for.
Hollywood called. They want their terminal back. Sci-fi terminal widgets that show only real data — latency, deployments, tailnet peers, GitHub, agents and clocks. Fifteen single-binary Rust widgets, nothing to install alongside them.
Three complete modules ship in the repo, one per language, each covering a different part of the surface. Copy one, change its id, and you have a module.
Build, flash and monitor ESP32 boards. Flashing stops the serial monitor and brings it back in the same pane, so the log from before the flash is still there.
Present a Markdown file as slides in a pane. Split on a rule, arrow keys to move, r to reload.
Python5 files821 lines
panessettings
luvus module link ./examples/modules/deck
Publishing
Getting listed takes one click
There is no submission, no review queue, and no account. Push a public repo with aluvus-module.toml at its root, then add theluvus-module topic to it on GitHub. This page andluvus module search both pick it up on their next run.
Put luvus-module.toml in the repo root (or a subdirectory).
On GitHub: About → ⚙︎ → Topics, add luvus-module.
Tell people to run luvus module install you/your-module.
What makes a good listing
A one-line repo description: it is the card text here.
A README showing what it adds, with a screenshot.
Any tools it needs (jq, node, …) stated up front.
A min_luvus_version you have actually tested.
A note on trust
A module is ordinary code that runs on your machine as you, with your environment and your full luvus CLI. That openness is the point, and a little judgment keeps it safe. Install from people you trust, and skim the manifest first:luvus module install shows you every command a module declares and asks before running anything. Builds run with a scrubbed environment, and a manifest cannot change between the preview and the install. luvus validates and isolates, but it does not sandbox: third-party modules come from their authors, not from luvus.