SYS.CL_CORE // ONLINE
DEVELOPED BY SPLTEK
CLICK THE TERMINAL · TYPE TO FILTER
--:--:-- LOCAL

SPLTEK · COMMAND LAUNCHER

CL

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.

binary
1
subcommands
0
platforms
3
license
MIT
cl — ~/projects/target-folder
LIVE
$ cl
cl>
    ↑↓ move enter run selected ctrl+a add ctrl+e edit ctrl+r rename ctrl+d delete ctrl+s show commands esc cancel
    picker ready click terminal to focus

    ▸ Not a video. A real picker replica — try ctrl+s or run ssh server. Or watch the 4-minute film ↓

    ▶ / THE FILM

    Four minutes,
    one picker.

    The real binary, captured end to end: filtering, placeholders, Ctrl+A/E/R/D and the pink cl-exec line. No cuts, no voiceover.

    cl // terminal session 04:04
    The cl picker running in a terminal, listing named commands.
    Recorded by spltek · MIT Nothing loads from YouTube until you press play · watch on YouTube

    01 / WHY CL

    Built for the command
    you keep retyping.

    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.

    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.

    UXno subcommands

    The command stays hidden

    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.

    privacydisplay-only toggle

    Placeholders, resolved live

    {{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.

    templatingdefaults

    Written the moment you confirm

    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.

    durabilityjson

    No editor, no temp files

    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.

    inlineguarded

    A single Go binary

    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.

    go 1.250 deps

    02 / THE PICKER

    Ten keys.
    Everything else is typing.

    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.

    ↑↓ MoveStep through the filtered list.
    enter Run selectedAlways runs the command — the toggle never changes that.
    ctrl+a AddPrompts for a name (spaces allowed), then the shell command.
    ctrl+e EditCurrent value pre-filled. Enter → save?
    ctrl+r RenameCurrent name pre-filled; duplicate names rejected in place.
    ctrl+d DeleteAsks first — y confirms, N is the default.
    ctrl+s Toggle commandsDisplay-only, persisted immediately, remembered next time.
    esc CancelBack out of any prompt. Nothing is written.
    list view / names only
    • >buildnpm run build -- --watch
    •  ssh server(user, host[default:prod.example.com])ssh {{user}}@{{host:prod.example.com}}
    •  deploykubectl apply -f production/overlays/us-east-1/kustomization.yaml --prune --selector app=api
    •  go to projectcd ~/projects/target-folder && exec $SHELL
    ◂ With show on, long commands wrap under their name — you always know what Enter is about to launch.
    ◂ Placeholder hints ride along with the name, whether commands are visible or hidden.

    03 / PLACEHOLDERS

    Templates that
    ask nicely.

    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.

    • Required — {{name}} cannot be skipped; the run waits for a value.
    • Optional — {{name:default}} arrives pre-filled; Enter accepts it.
    • Visible — the list shows (user, host) or (remote[default:origin]) as a hint.
    • Independent — placeholders resolve whether or not commands are shown.
    ssh server resolver
    resolved command
    > cl-exec: ssh server (admin, prod.example.com)
    Last login: Tue Nov 12 09:41:07 on ttys002 · running…

    04 / STORAGE

    A JSON file.
    That's the whole database.

    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.

    config dir ~/Library/Application Support/cl

    Written on first launch. Installed to ~/.local/bin by the release installer.

    • Portable — copy the JSON to another machine and your commands come with you.
    • Readable — plain text, no lock-in, no migrations, no schema.
    • Inspectable — cat it, diff it, version it. It is just your commands.
    commands.json written immediately
    {
      "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"
    }
    names are unique · empty values rejected in place

    05 / SHELL STATE

    Some commands need
    a shell to live in.

    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.

    the pattern
    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.

    Regular commands — git, npm, docker, ssh — need nothing extra.
    commandwhy it needs && 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

    Four ways in.
    No sudo, no admin.

    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.

    installs to ~/.local/bin/cl · %LOCALAPPDATA%\cl\bin
    requires Homebrew · or build with Go 1.25+
    shell rc PATH updated per-user, never machine-wide
    Uninstall
    Homebrewbrew uninstall cl
    macOS / Linuxcurl -fsSL https://raw.githubusercontent.com/spltek/cl/main/uninstall.sh | sh
    Windowsiwr https://raw.githubusercontent.com/spltek/cl/main/uninstall.ps1 -UseBasicParsing | iex
    01

    Release binary

    Downloads the right binary for your OS and arch from the latest release. Override the destination with CL_INSTALL_DIR.

    02

    Build it yourself

    Go 1.25+. make install-local compiles and installs to ~/.local/bin, then prints the one command to activate it in your current shell.

    03

    Windows quirks

    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.