One picker, zero ceremony
There is no add or remove subcommand to remember. Run cl, type, press Enter. Adding is ctrl+a from inside the same list — where the command you just thought of already belongs.
SPLTEK · COMMAND LAUNCHER
COMMAND LAUNCHER
Every alias, one-liner and three-week-old incantation in one drawer.
cl keeps a name → shell command dictionary in a JSON file and
hands you a single interactive picker to search it — while the command itself
stays hidden.
No add/remove subcommands to memorise. No editor, no temp files, no shell config. One Go binary, three platforms, persisted to disk the instant you hit Enter.
▸ Not a video. A real picker replica — try ctrl+s or run ssh server. Or watch the 4-minute film ↓
▶ / THE FILM
The real binary, captured end to end: filtering, placeholders,
Ctrl+A/E/R/D and the pink
cl-exec line. No cuts, no voiceover.
01 / WHY CL
Personal command launchers usually punish you with config files and subcommands. cl is the opposite: one picker, one JSON file, and your fingers never leave the keys.
There is no add or remove subcommand to remember. Run cl, type, press Enter. Adding is ctrl+a from inside the same list — where the command you just thought of already belongs.
Names only, by default — so you can run something private in a shared screen without its value on display. ctrl+s peeks at commands; Enter always runs the real thing.
{{name}} and {{name:default}} are detected the moment you pick a command. cl asks for each value in sequence, then announces the resolved name before running it.
Every add, edit, rename and delete lands in the JSON file immediately — not when you quit. Kill the terminal, lose the SSH session, crash the machine: your commands are already on disk.
Editing happens inline, pre-filled and editable. Enter asks save? — y writes, n/esc leaves the stored command untouched. Duplicate or empty names are rejected in place.
macOS, Linux and Windows from one static build. No runtime, no daemon, no background service, no telemetry — the picker exits the moment your command starts, and your shell takes over.
02 / THE PICKER
Filtering is a case-insensitive substring match — the whole typed text has to appear together, not its letters scattered anywhere. Arrows move, Enter runs, esc cancels.
03 / PLACEHOLDERS
Put {{name}} where a value goes and {{name:default}} where you usually
reuse one. cl prompts for each in order, pre-fills the defaults, then announces the
run in pink with the values in grey.
{{name}} cannot be skipped; the run waits for a value.{{name:default}} arrives pre-filled; Enter accepts it.(user, host) or (remote[default:origin]) as a hint.04 / STORAGE
Commands live in your user config directory — never in a project, never in a dotfile you hand-edit. Writes happen as each add, edit, rename or delete is confirmed.
~/Library/Application Support/cl
Written on first launch. Installed to ~/.local/bin by the release installer.
{
"build": "npm run build -- --watch",
"ssh server": "ssh {{user}}@{{host:prod.example.com}}",
"git push": "git push {{remote:origin}} {{branch:main}}",
"psql main": "psql -h {{host:localhost}} -p {{port:5432}} -U {{user}} -d {{db:postgres}}",
"go to project": "cd ~/projects/target-folder && exec $SHELL",
"deploy": "kubectl apply -f production/overlays/us-east-1/kustomization.yaml --prune --selector app=api"
}
05 / SHELL STATE
cl runs your command in a subshell. Builtins that mutate the shell — cd,
source, export — evaporate with it. Append && exec $SHELL
and the launcher replaces the subshell with a fresh interactive shell instead.
cd ~/projects/target-folder && exec $SHELL
Pick go to project and the current terminal is replaced by a new shell in the target directory — the cd actually persists.
git, npm, docker, ssh — need nothing extra.
&& exec $SHELL
cdChanges directory only in the subshell, then it's lost.sourceSources a file in a subshell, leaving your env unchanged..Same as source — the dot builtin.exportSets env vars that disappear when the subshell ends.aliasDefines aliases that are lost when the subshell exits.unsetUnsets variables only in the subshell.06 / INSTALL
Every installer writes into your own home directory and edits your own shell rc files — plain per-user operations. Pick the one that matches your machine.
brew install spltek/tap/cl
The fastest path on macOS and Linux. Updates arrive through brew upgrade.
brew uninstall clcurl -fsSL https://raw.githubusercontent.com/spltek/cl/main/uninstall.sh | shiwr https://raw.githubusercontent.com/spltek/cl/main/uninstall.ps1 -UseBasicParsing | iexDownloads the right binary for your OS and arch from the latest release. Override the destination with CL_INSTALL_DIR.
Go 1.25+. make install-local compiles and installs to ~/.local/bin, then prints the one command to activate it in your current shell.
If your execution policy is Restricted or AllSigned, run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned first.
END OF LINE
“All those moments will be lost in time…
like uncommitted changes before a force push.”
Time to launch.