eDebug

eDebug is a browser-based debugging tool for Bash scripts. It brings the kind of debugging experience you expect from a proper IDE to shell scripting, which has traditionally relied on echo statements and careful reading. You can set breakpoints, watch variables, and step through your script line by line, all through a web interface.

The setup is minimal. You run a single curl command that pipes to bash with your script name as an argument. That launches a debugging session accessible through the browser. No account needed, no installation beyond the one-liner, no dependencies to manage. The script runs on your machine while the debugging interface renders in your browser.

For anyone who has spent time debugging a complex Bash script, the value is obvious. Shell scripts don't have built-in debuggers the way Python or JavaScript do. When something breaks, you're usually adding print statements, running the script, checking output, and repeating until you find the bug. eDebug shortcuts that by letting you pause execution, inspect what's in each variable, and step forward one line at a time.

It's built for system administrators, DevOps engineers, and developers who write or maintain nontrivial shell scripts. If your scripts are short one-liners, you probably don't need a debugger. But if you're maintaining deployment scripts, build pipelines, or automation that spans hundreds of lines, the ability to trace execution properly saves time.

The web-based approach means you're not locked to a specific editor or terminal emulator. You can run the debugger on a remote server and access it from your laptop browser. That's useful when debugging scripts that need to run in production environments or on machines where you can't install additional tooling.

From what's visible, the tool appears to be free with no account required. There's no pricing page or subscription tiers mentioned, which suggests it's either a free utility, an open source project, or early enough that monetization hasn't been implemented yet.

The tradeoffs are worth noting. Because it's remote and web-based, you're sending your script execution through an external service. For sensitive scripts with secrets or proprietary logic, that might be a concern. The tool also requires a live internet connection to the eDebug service, so fully offline debugging isn't possible. For most development and testing scenarios, those limitations are acceptable, but they're worth considering before piping your production deployment script through it.