DRUDGE
DRUDGE runs your backlog through coding agents, each in its own sandbox, on your own machine.
You make the decisions and review what comes back. The agents do the grunt work in between.
They’re not coworkers. They’re not digital employees. They’re tools.
Features
- Projects that link a local directory and its git repositories
- Tasks stored as plain markdown files
- Task dependencies, ensuring work starts only once its blockers are done
- Tasks grouped by ticket (external ID) and by parent task
- A pool of reusable drudgers, each with its own git worktree per repository
- Several drudgers working in parallel, you configure how many
- Claude Code as the agent (others TBD) vendor
- A full record of every run: the prompt, the event stream, the logs, the cost and the time it took to work on a task
- Tasks go back to the queue when the vendor turns an agent away, whether by rate limit, outage or expired login
- Commands to reclaim a stuck sandbox or nuke a broken one
- A bundled skill that lets a planning agent write DRUDGE tasks for you
- Color themes and a config file with a JSON schema
Install
DRUDGE runs on Linux and macOS. On Windows, use WSL.
Single command
curl -fsSL https://drgtools.dev/install.sh | sh
The script puts drg in ~/.local/bin, or in /usr/local/bin when run as root. Set DRG_VERSION=v0.1.0 to install a specific release, or DRG_INSTALL_DIR to pick another directory.
Go
go install github.com/IgorBolotnikov/DRUDGE/cmd/drg@latest
Then run drg setup.
Update
drg update
It replaces the binary with the latest release and checks it against the release checksums. A binary built from source is updated by building it again.
Future improvements
- TUI
- Extensibility with plugins
- More agent vendors