From afcf138c298b1fcbf6999fb5967bbb1412398a82 Mon Sep 17 00:00:00 2001 From: clawbot <35+clawbot@noreply.example.org> Date: Mon, 16 Nov 2026 23:38:12 +0000 Subject: [PATCH] Correct snapshot remove --help on remote keys The help said a remote key is accepted only on a host with no local index; a remote-only snapshot's key is accepted on any host. Model: opus-5-5 --- internal/cli/snapshot.go | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/internal/cli/snapshot.go b/internal/cli/snapshot.go index 04214cd..86ac329 100644 --- a/internal/cli/snapshot.go +++ b/internal/cli/snapshot.go @@ -331,10 +331,10 @@ know about), which is what 'vaultik prune' does. The command prints the 'vaultik prune' invocation to run as a follow-up only when it removed the snapshot's metadata from the destination store, and never under --json. -The snapshot may be named by its ID or, on a host with no local index, -by the remote key that 'snapshot list' prints for a remote-only snapshot -(an unambiguous leading part is enough). An identifier that names no -snapshot in the local index or on the destination store is an error. +The snapshot may be named by its ID or by its remote key, which +'snapshot list' prints for a remote-only snapshot. An unambiguous +leading part of the key is enough. An identifier that names no snapshot +in the local index or on the destination store is an error. Use --local-only to skip the remote half (e.g. when you want to forget a snapshot locally without touching the destination store); the snapshot