- Block-based grouping of commands
- Easily run or kill a named group of tasks
- Track background or sustained processes (e.g. GUI apps, dev servers)
- Command-type prefix system for flexible control
npm install -g blocrunCreate a BLOCFILE in your project root. This file defines blocks of commands:
dev {
@ code .
% vite
$ echo "Development server launched"
}
build {
% npm run build
}| Symbol | Description | Tracked |
|---|---|---|
@ |
Sustained (servers, terminal commands, etc) | ✅ Yes |
% |
Tracked but auto-closing jobs (e.g. build) | ✅ Yes |
$ |
One-off commands (not tracked e.g. gui app) | ❌ No |
blocrun run <block-name>Example:
blocrun run devIf the block is already running, it will not run again.
blocrun kill <block-name>This command:
- Terminates all tracked processes for the block
- Cleans up the
.blocksPID tracking file
BLOCFILE— Your command block definitions.blocks— Internal file storing tracked PIDs
dev {
@ code .
% npm run dev
$ echo "Started successfully"
}
build {
% vite build
}@— GUI or server that should stay alive (cmd /k, VSCode, etc.)%— Script or tool that ends on its own (e.g.vite build)$— Logging or setup scripts you don’t need to track
- Simpler than shell scripts
- Safer than PM2 for dev use
- Works on Windows/macOS/Linux
- Better UX for managing grouped tasks