
Steel Panda
Local-first task executor for system operations, automation, and command workflows.
Free1 impressionslaunches Oct 281 comment
Steel Panda runs all shell scripts in a folder locally, logs each exit code and fails if any task fails.
- for
- Developers needing a simple local task runner for maintenance scripts.
- pricing
- open source
- license
- MIT
Key features
- Folder-wide script execution — Runs every *.sh file in a specified directory in lexical order.
- Exit code aggregation — Returns 0 if all tasks succeed, 1 if any fail, 2 on runner errors.
- Simple logging — Appends task results to steel.log with per-task exit codes.
- Configurable stop-on-error — Halts after first failure via env var or --stop-on-error flag.
- No network dependencies — Runs entirely locally without opening network connections.
- Cross-platform Bash support — Works on Linux, macOS and Termux (Bash 3.2+).
- One-command install — Installs the latest release via a single curl | bash command.
- Environment variable support — Customizable TASK_DIR, LOG_FILE, and other settings via env vars.
Use cases
- Run a set of recovery scripts when a service crashes
- Execute daily maintenance tasks from cron without a scheduler
- Validate a collection of CI scripts locally before committing
Steel Panda FAQ
How do I install Steel Panda?+
Run the one-command installer: curl -fsSL https://github.com/pandadad0214/Steel_Panda/releases/latest/download/install.sh | bash.
Where should I place my scripts?+
Save *.sh files in the Tasks/ directory (or set TASK_DIR to another folder).
How does Steel Panda indicate success or failure?+
It exits with code 0 if all tasks succeed, 1 if any task fails, and 2 if the runner cannot start.
Can I stop after the first failing task?+
Yes, set STEEL_STOP_ON_ERROR=1 or use the --stop-on-error flag.
Does Steel Panda require internet access?+
No, the runner opens no network connections and runs entirely locally.
Summarized by DevHunt from github.com · Nov 10, 2026. Details may change; check the official site.


