Teal / Launcher

A launcher you can learn in layers.

RETUI has a lot of commands now. That is useful, but a giant alphabetical wall is a terrible way to introduce them. You do not need to memorize the launcher. Learn the few commands that match how you use your phone, then let `help` handle the rest.

Start here, not everywhere

If RETUI is new to you, these are enough to understand its shape. They cover discovery, settings, apps, companion files, and the occasional clean reload.

help

List available commands, or use `help <command>` when you need the exact arguments for one.

guide

Run the built-in walkthrough without leaving the terminal or blocking normal launcher use.

settings

Open the normal settings hub. Direct XML editing is optional, not an initiation ritual.

apps -ls

Open the app drawer when browsing is easier than remembering a name.

files

Hand file work to RETUI Files, the companion app built to own that permission and workflow.

restart

Reload the launcher and re-apply settings after direct edits or when you want a clean visual refresh.

Commands should describe intent

I like commands when they remove steps, not when they turn ordinary actions into puzzles. RETUI commands are grouped around jobs you already understand: open something, change the launcher, focus, automate, or inspect what went wrong.

weather
apps -ls
pomodoro 25m
module -show music
files -open Downloads

You can stop there. The deeper layers exist because some people want their phone to behave like a small workstation, but none of that should make launching an app harder.

Shape the launcher

These commands change what RETUI looks like, remembers, or places within reach. This is the part of the command model that turns a clean install into your launcher.

apps

Control app visibility, groups, details, Play Store links, Android settings, and default slots. The full walkthrough lives on the Apps page.

alias

Give a repeated command or chain a name that makes sense to you.

preset

Save, list, and apply stable theme snapshots.

wallpaper

Open static or live wallpaper pickers, or derive launcher colors with `wallpaper -auto`.

space

Save and switch larger launcher setups with their own settings, modules, and command-facing state.

username

Change the user and device names shown in the prompt.

config

Inspect, set, or reset individual configuration values when you want the direct path.

Use the phone without leaving the prompt

Not every command is about customization. A large part of RETUI is simply keeping common actions close to the terminal surface.

notifications / reply

Read, page through, open, filter, and reply where Android exposes a reply action.

music / podcast / rss

Control playback, follow ordered podcast feeds, or keep an RSS surface in the launcher.

timer / stopwatch / pomodoro

Handle ordinary timing and deliberate focus sessions.

lockdown / breach

Use RETUI's opt-in focus friction rather than pretending distraction can be solved with one permanent block switch.

notes / events

Keep short local information and calendar-facing work available from the terminal.

search / open / share

Move from a typed intention to a browser, Android intent, file, or share sheet.

Extend it when the built-ins stop being enough

This is the workstation layer. It is powerful, but it is not the place I would tell a new user to begin.

module

Show built-in panels and manage Termux-backed or launcher-native Lua modules.

lua

Create and open focused launcher-native Lua applications inside the sandboxed runtime.

termux / tmux

Run one-shot scripts or open persistent TUI sessions while Termux continues to own the actual shell.

tbridge

Set up and diagnose the Termux execution and callback bridge. It is not the file manager.

tasker

Run approved RETUI actions from Tasker or start an existing named Tasker task.

webhook / post

Trigger saved HTTPS requests or send a one-off POST when that really is the shortest tool.

read the automation post

The current command map

This is the current main command registry, grouped so it remains readable. Some entries are compatibility or specialist surfaces rather than things most people should learn. Device and Android-version restrictions still apply, and `help` inside your installed build remains authoritative.

Everyday launcher

helpguidesettingsappsfilessearchopenshareshortcutrefreshrestarttutorial

Identity and customization

aliasconfigpresetthemewallpaperusernameprofilespacetuituixtthemer

Modules, media, and focus

modulewidgetluamusicpodcastrssnotificationsreplynoteseventstimerstopwatchpomodorolockdownbreachstatus

Device and Android actions

airplanebluetoothbrightnesscallcontactscntctsdataflashintentlocationorientationlandscapeportraitshellvibratevolumewifi

Automation and integrations

taskertermuxtmuxtbridgeretui-tokenwebhookposthtmlextractregextermuxopen

Utilities, inspection, and compatibility

beepcalccdchangelogclearcreditsctrlcdebugdevutilsdonateduoexithackinstalllspwdratetimetuiweatheruninstallwallet

A command list should feel like a map, not homework. Learn the part of RETUI that solves a real problem for you. The rest can wait until curiosity pulls you deeper.