dlm
A service-backed download manager with CLI, TUI, and adaptive segmented downloads.
Read the build from several angles.
Authentic screens, terminal output, and architecture plates are kept together so the page shows the shape of the work without inflating the claim.
This record uses a procedural architecture view because no authentic public screenshot has been approved.
TOOLING
What exists.
dlm runs a local daemon over a Unix socket, accepts URLs, curl commands, fetch snippets, and HAR files, then manages downloads with pause, resume, cancel, retry, and queue restoration.
Where it resisted.
Download management needs reliability across restarts, adaptive streaming for different server capabilities, and a usable interface without a full desktop app.
What I changed.
Built a service-backed architecture with SQLite persistence, adaptive single-stream and segmented range downloads, and both CLI and OpenTUI surfaces.
The obvious implementation was not the product.
Separate the daemon from the interface so downloads survive terminal disconnects and the UI can be swapped.
Current proof
04- Unix domain socket daemon with SQLite persistence.
- CLI and full-screen OpenTUI dashboard.
- Adaptive downloading with segmented range support.
- Post-download verification, extraction, and notification hooks.
What this build changed.
A download manager is really a reliability problem: the interface is secondary to getting the bytes across cleanly.