samiandClaude Sonnet 5 60363a7142 proto: land B4 and B2a — buffer bounds, budget knobs, effective readback (1.1.0)
Minor bump on 1.0.0, per core/docs/buffer-sizing.md.

B4 — bufferBytes bounds corrected in all four locations (DownloadSpec,
TaskDetail, download.update's patch, Settings.connection.bufferBytes): was
4 KiB-8 MiB with no stated default, now 64 KiB-16 MiB with a 1 MiB default.
64 KiB because 4 KiB is smaller than one libcurl HTTP/2 write-callback delivery;
16 MiB because throughput from write size is flat past ~1-4 MiB and past 16 MiB
there is stall-cover left to buy but no memory left to spend it on; 1 MiB
default because it is the only candidate for which docs/04's 60 MB RSS target
actually holds once buffers are counted per segment, not per download.

Two new settings keys: connection.maxTotalBufferBytes (128 MiB default) and
connection.maxActiveSegments (32 default). Without them CORE's clamp — reduce
every live segment's buffer to fit the global cap — has no wire configuration
surface, and "20 active downloads" has no meaning distinct from 160 live TLS
connections.

B2a — TaskDetail.effectiveBufferBytes: what a segment is actually using right
now, after the clamp. Placed on TaskDetail next to bufferBytes, following the
requested/effective pattern ADR 0010 already established for segments. The
download.get fixture now demonstrates a real clamp (16 MiB requested, 4 MiB
effective) rather than a case where the cap happens not to bind.

docs/04-engine-design.md §4 and §8 updated in the same change per CORE's
request and CLAUDE.md rule 5: the RSS target is now stated as conditional on
maxActiveSegments = 32, and the old 4 MiB/64 MiB/256 MiB numbers are corrected
to match the schema. ADR 0012 records the reasoning and explicitly keeps the
60 MB target over CORE's offered 120 MB alternative, with the arithmetic that
makes 60 MB achievable with margin.

Numbered 0012 rather than 0011: DAEMON is independently drafting ADR 0011
(admission control / segment budget split) in a peer session at time of
writing, so 0011 was reserved to avoid a collision.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_012fgjnqFCS5h5L7gZTZo3rV
2026-09-09 23:20:58 +04:00
2026-09-09 20:14:11 +04:00

Velox Download Manager (VDM)

An IDM-class download manager for Ubuntu 26.04 LTS: multi-segment accelerated HTTP(S) downloading, resume, categories and automatic file distribution, queues and scheduler, speed limiter, a Firefox extension that captures downloads automatically, and clipboard link capture.

Name is a placeholder. Binaries are veloxd, velox-gui, velox, velox-nmhost. Rename before first release if you want something else — do it in M0, never later.


Status

Phase M0 — scaffolding. No implementation code exists yet. This repository currently contains the architecture, the wire contract, the roadmap, and one brief per build lane so that several agents can work in parallel without colliding.

Start here:

Document What it answers
docs/01-architecture.md Process model, why four binaries, framework choices and why
docs/02-roadmap.md Milestones M0M7, what runs in parallel, exit gates
docs/03-gui-spec.md IDM-parity UI: every window, dialog, column, menu
docs/04-engine-design.md Segmentation, resume, buffers, rate limiting, disk I/O
docs/05-extension-spec.md Firefox capture, transports, pairing, media grabber
docs/06-risks-and-spikes.md Snap Firefox, Wayland clipboard, and the other landmines
docs/07-packaging.md .deb/PPA, Flatpak, AMO signing, install layout
contracts/README.md The interface. Both sides build against this
CLAUDE.md Rules of engagement for agents working in this repo

Per-lane briefs live in docs/agents/ — one per agent, each with an owned directory list, a definition of done, and the files it must never touch. To dispatch the agents, use docs/agents/PROMPTS.md — six copy-paste prompts plus the worktree commands and the wave order.


Architecture in one picture

  ┌────────────────────┐   native messaging (stdio JSON)   ┌──────────────┐
  │  Firefox extension │◄─────────────  or  ──────────────►│ velox-nmhost │
  │       (MV3, TS)    │   loopback WS 127.0.0.1 + token   └──────┬───────┘
  └────────────────────┘                                          │
                                                                  │
  ┌────────────────────┐                                          ▼
  │  velox-gui (Qt 6)  │◄──── JSON-RPC 2.0 over Unix socket ──► ┌─────────────┐
  └────────────────────┘      $XDG_RUNTIME_DIR/velox/velox.sock │   veloxd    │
                                                                │  (daemon)   │
  ┌────────────────────┐                                        │             │
  │   velox (CLI)      │◄───────────────────────────────────────┤ libveloxcore│
  └────────────────────┘                                        └──────┬──────┘
                                                                       │
                                                              SQLite + sparse files

The daemon owns all state and all sockets. The GUI is a view — closing it does not stop a download. The extension never touches the disk; it hands URL + headers + cookies to the daemon and gets a task id back.


Repository layout

vdm/
├── contracts/          ⭐ Wire contract: JSON Schema, fixtures, codegen. Frozen per version.
├── core/               C++23  libveloxcore — engine. No UI, no RPC, no SQL.
├── daemon/             C++23  veloxd — RPC server, scheduler, queues, SQLite store.
├── gui/                C++23  velox-gui — Qt 6 Widgets, IDM-parity UI.
├── cli/                C++23  velox — scriptable client.
├── nmhost/             C++23  velox-nmhost — Firefox native-messaging bridge (thin pipe).
├── extension/          TS     Firefox MV3 WebExtension.
├── tools/
│   ├── mockd/          TS mock daemon — lets GUI + extension work before veloxd exists.
│   ├── testserver/     Deliberately hostile HTTP server (no Range, flaky, redirects, auth).
│   ├── bench/          Throughput and CPU benchmarks.
│   └── fuzz/           libFuzzer targets for parsers.
├── tests/
│   ├── conformance/    Protocol suite. Every lane must pass it. Gate for merging.
│   ├── integration/    veloxd + testserver.
│   └── e2e/            Playwright: real Firefox + real daemon + real file on disk.
├── packaging/          debian/, flatpak/, appimage/, native-host manifests.
└── docs/               Everything above, plus adr/ and agents/.

Toolchain bootstrap

Surveyed on this machine 2026-09-09 — most of it is already installed:

Present Version
git · cmake · ninja · g++ · gdb 2.53.0 · 4.2.3 · — · 15.2.0 (C++23 ready)
qt6-base-dev · qt6-tools-dev · qt6-tools-dev-tools
libcurl4-openssl-dev · libsqlite3-dev · nlohmann-json3-dev · libssl-dev
libavformat-dev · libavcodec-dev · ffmpeg
clang-format · clang-tidy · python3 · pkg-config

Only these four are missing:

sudo apt update && sudo apt install -y \
  libqt6svg6-dev \    # GUI: SVG icon rendering
  libsecret-1-dev \   # DAEMON: Secret Service for site logins
  nodejs npm \        # EXT + PROTO: extension build, mockd, conformance runner
  clang               # optional: libFuzzer targets in M7

Node in the 26.04 archive may lag; if the extension toolchain needs 22+, use nvm.

Verify with cmake --preset dev && cmake --build --preset dev once lane CORE lands its first target. Note CMake 4.2.3 is installed — newer than the 3.28 floor in CMakeLists.txt, and it hard-errors on cmake_minimum_required below 3.5, so no dependency may ship a pre-3.5 CMake file.

S
Description
a download manager for ubuntu
Readme
1.4 MiB
Languages
C++ 69.9%
TypeScript 20.5%
Python 6.1%
CMake 1.9%
Shell 1.1%
Other 0.4%