Find the right module surface before you build.

Re:T-UI modules are small launcher panels for status, controls, scripts, and guided input. The market page separates discoverable module paths from the deeper implementation guides.

browse lua modules browse termux modules browse built-ins open module guide

mako@retui:~/docs$ module -ls --built-ins

Built-in module shelf

Use shipped panels before adding custom code.

Built-in modules are the safest market entries because they ship with the launcher and use native Android surfaces where needed.

music

Playback controls and track info for the selected music source.

notifications

Page through selected notifications, open them, or reply when Android exposes a reply action.

timer

Dock a countdown surface and control it from terminal commands.

calendar

Keep a compact date surface available in the module dock.

reminder

Create reminders through a launcher-owned prompt session.

notes

Keep small persistent notes and task fragments in the launcher.

rss

Scan configured feeds without turning the terminal into a full feed reader.

weather

Dock the existing weather status instead of adding another service.

open built-in guide

mako@retui:~/docs$ module -new lua counter

Lua module shelf

Use Lua when the module needs launcher-native controls.

Lua modules are local scripts that render into the module dock, expose optional config forms, store prefs/files, and can publish native action buttons or suggestion chips.

Starter counter

Create a small stateful panel with one visible action and one persisted preference.

open starter recipe

Config form module

Let Lua declare text, number, toggle, select, and textarea fields while Re:T-UI owns the UI.

open config guide

Native controls

Render module buttons for always-visible controls and suggestion chips for keyboard-first actions.

open controls guide

Module-local storage

Use prefs for flags and files for notes, logs, cached JSON, or user-generated text.

open persistence guide

mako@retui:~/docs$ module -add server termux:/path/script.sh

Termux module shelf

Use Termux when the module needs shell tools.

Termux modules should print output, then exit. They are best for health checks, local scripts, curl checks, summaries, and shell automation that does not need an interactive REPL.

Server health

Print status lines, optional monospace blocks, and refresh suggestions from a shell script.

open script module guide

Callback module

Update a module from Termux, Tasker, or another automation app through a token-protected callback.

open callback docs

mako@retui:~/docs$ cat market/publish-notes.md

Publish and install boundary

Module market entries are recipes first.

Unlike visual presets, module entries can execute logic. Treat shared Lua and Termux modules as inspectable recipes: read the source, check requested permissions, then approve or install intentionally inside Re:T-UI.

Lua modules: create with module -new lua <name>, edit locally, then approve permissions when requested.
Termux modules: register a known local script with module -add <id> termux:/path/script.sh.
Suggestion scripts: use Lua when the workflow should publish command chips without occupying the module dock.

open Lua module guide open module maker notes