Fetching from the wire…
Public story · 2026-08-24 · high
Hub drain finishes running work before an upgrade, and a durable event log replays whatever a reconnected client missed.
Why now: The release notes remain the only public account of how hub drain and replay behave, as of Aug. 24.
Cline added hub drain and hub upgrade to its CLI in version 3.0.57, letting a running hub restart without losing in-flight work, per Cline's release notes.
Anyone running Cline's hub unattended has had to choose between restarting mid-task and losing work, or holding every upgrade until the hub sits idle. Drain removes that trade-off.
The hub stops accepting new mutating work when a drain starts, finishes whatever's already running, then restarts on the current build. If the upgrade fails partway through, the drain lifts on its own. The hub doesn't get stuck refusing new work indefinitely.
A durable event log backs the restart. A client that drops its connection during an upgrade can reconnect and replay whatever it missed. Replay is deduplicated by event id, so the client doesn't reprocess results it already has.
The release notes don't say how long a drain typically takes to clear, or what counts as mutating work versus work that's safe to interrupt.
Drain and replay only earn their complexity if Cline's hub runs unattended long enough to hit them. The test is whether future release notes have to patch a drain that got stuck or an upgrade that dropped events anyway.
The release notes remain the only public account of how hub drain and replay behave, as of Aug. 24.
Each link below shares sources, entities, or timing with this story.
Cline benchmarked against Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover CLI, Cline; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover CLI, Cline; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover CLI, GitHub; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entity: GitHub / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover GitHub; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entity: GitHub / Same source domain / Earlier coverage
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover GitHub; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entity: CLI / Same source domain / Earlier coverage
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover CLI; reported by the same outlet (github.com).
Cline released Kanban / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Cline released Kanban); both cover CLI, GitHub; reported by the same outlet (github.com).