Skip to content
/ dumbcli Public

The "Dumb" Way to Manage Smart Commands. Stop asking AI for the same command twice. Store it. Trust it. Run it.

Notifications You must be signed in to change notification settings

S488U/dumbcli

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DumbCLI

██████╗ ██╗   ██╗███╗   ███╗███████╗╔██████╗██╗     ██╗
██╔══██╗██║   ██║████╗ ████║██╔══██║║██╔═══╝██║     ██║
██║  ██║██║   ██║██╔████╔██║███████║║██║    ██║     ██║
██║  ██║██║   ██║██║╚██╔╝██║██╔══██║║██║    ██║     ██║
██████╔╝╚██████╔╝██║ ╚═╝ ██║███████║╚██████╗███████╗██║
╚═════╝  ╚═════╝ ╚═╝     ╚═╝╚══════╝ ╚═════╝╚══════╝╚═╝
  

The "Dumb" Way to Manage Smart Commands.
Stop asking AI for the same command twice. Store it. Trust it. Run it.


Why DumbCLI?

Modern terminals are smart, but they have a fatal flaw: They remember your mistakes.

If you mistype a command, break a flag, or run a syntax error, your shell history (Ctrl+R or autosuggestions) saves it forever. When you try to find it later, you often get the broken version, leading to frustration and wasted time.

DumbCLI is your "Golden Record." It ignores the noise and only stores the verified, working commands that you explicitly choose to save.

The Workflow:

  1. Stop searching history for that one specific ffmpeg command buried under 50 failed attempts.
  2. Stop Googling the same Regex syntax every two weeks.
  3. Stop asking AI for critical operations and risking hallucinations.

DumbCLI lets you save complex shell commands with Short IDs or Aliases, and reuse them instantly with dynamic arguments.

Killer Features

  • Anti-Hallucination: Don't rely on AI for critical ops. Use your own trusted, verified commands.
  • Clean History: Your shell history is full of typos. DumbCLI is curated. It only runs what works.
  • Dynamic Placeholders: The killer feature. Use {} to insert arguments at runtime.
  • Team Onboarding: Export your project's build/test scripts to JSON. New team members just import and start working immediately.
  • Power User Syntax (Alpha): Add commands in seconds without leaving the prompt.
  • Smart Search: Find commands by ID, alias, or vague comment keywords.

Installation (Local Script, Safer)

We recommend downloading the installer and running it locally (no direct curl | bash).

Linux / macOS

# Download the installer
curl -fsSL https://plexaur.com/dumbcli/install.sh -o install.sh

# Review the script (recommended)
less install.sh

# Run it
chmod +x install.sh
./install.sh

Windows (PowerShell)

# Download the installer
iwr -UseBasicParsing https://plexaur.com/dumbcli/install.ps1 -OutFile install.ps1

# Review the script (recommended)
notepad .\install.ps1

# Run it
powershell -ExecutionPolicy Bypass -File .\install.ps1

Windows (CMD + curl)

curl -fsSL https://plexaur.com/dumbcli/install.ps1 -o install.ps1
powershell -ExecutionPolicy Bypass -File install.ps1

The installer will handle both first-time install and updates.

Quick Start

1. Save a Command

Interactive mode makes it easy to save complex one-liners.

$ dumb add

Follow the prompts to add command, alias, and comments.

2. Run it (The Standard Way)

Run by ID or Alias.

$ dumb run 1
# OR
$ dumb run build-app

3. The Killer Feature: Dynamic Arguments {}

Stop hardcoding paths or messages. Use {} as a placeholder when adding a command.

Saved Command (Alias: gcom):

git commit -m "{}"

Run it:

$ dumb run gcom "Fixing the login bug"

Result: Executed git commit -m "Fixing the login bug" instantly.


Power User Features (Alpha Stage)

Rapid Add

Don't want to go through the interactive menu? Use the generic syntax: d:a:<command>:<alias>:<comment>

# Quickly save an echo command
dumb d:a:"echo Hello World":hello:"My first command"

Team Workflow (Import/Export)

Ideal for dev teams. Don't write a long Wiki page about how to build the project. Just share a project-commands.json.

Team Lead:

# Export verified build scripts
dumb export ./onboarding/

New Developer:

# Import scripts into their local DumbCLI
dumb import -a ./onboarding/project-commands.json

Now the new dev has all the project scripts ready to go!


Command Reference

Command Description
dumb add Add a new command interactively
dumb ls List all saved commands (shows ID & Alias)
dumb find <query> Search commands, aliases, or comments
dumb run <id/alias> Execute a command. Add arguments for {} placeholders
dumb edit <id/alias> Update a command's logic or alias
dumb dl <id/alias> Delete a command
dumb import <file> Load commands from a JSON file (use -a to append)
dumb export [path] Backup your commands to JSON
dumb dump Print your JSON file

Installation Location

DumbCLI installs the project files in a permanent, OS-specific location:

  • Linux: ~/.local/share/dumbcli (or $XDG_DATA_HOME/dumbcli)
  • macOS: ~/Library/Application Support/DumbCLI
  • Windows: %LOCALAPPDATA%\DumbCLI

This is separate from your personal command data.

Configuration & Data

Your commands and settings are stored locally in ~/.dumbcli/:

  • Commands: ~/.dumbcli/dumbcli.json
  • Config: ~/.dumbcli/config.json

Back up or sync this folder if you want to move your commands across machines.


Contributing

Found a bug? Want to add a feature? Connect with me on GitHub: https://github.com/S488U

About

The "Dumb" Way to Manage Smart Commands. Stop asking AI for the same command twice. Store it. Trust it. Run it.

Topics

Resources

Stars

Watchers

Forks