Deleting

Plans are kept forever by default. Nothing expires, nothing is pruned automatically, and there is no background GC. They are a few kilobytes each.

Deleting is something you do by hand, in the picker, on the row in front of you.

d, in the picker

Open bare planx, put the cursor on what you want gone, and press d.

• On a plan row, that is the whole plan and every version of it.
• On a version row — press → on a plan to open its versions — that is that one version.

Bare planx with no arguments. Type to filter, → opens a plan's versions, d deletes the row you are pointing at.

00000000000000000000

╭─ planx v0.3.0 ───────────────────────────────────────────────────────────────╮

│ │

│ planx │

│ every plan in ~/.planx, newest first 3/3 │

│ │

│ ❯ guard-clock-a3f9 Guard the clock regression · 3 … │

│ rate-limit-uploads-77c2 Rate limit the upload endpoint … │

│ retry-webhooks-1b40 Retry failed webhooks with back… │

│ │

│ │

│ │

│ │

│ │

│ │

│ → versions · ↑↓ choose · d delete · enter open · esc cancel │

╰─────────────────────────────────────────────── ★ github.com/thisisnsh/planx ─╯

click to use your keyboard, or tap the keys below

Typing — enter saves, esc discards. On a phone, tap here for the keyboard.

A red line at the foot names the target in full before anything happens:

delete guard-clock-a3f9 v3? this cannot be undone

enter confirms, esc backs out. d is only offered when the highlighted row can actually be deleted, so a key that is going to refuse is a key you never see.

It is permanent

There is no trash. Deleted is gone.

planx used to soft-delete to ~/.planx/.trash/ with a planx restore to bring things back, and nobody ever emptied it — a soft delete you never empty is a directory full of plans you have already decided you do not want. The red confirmation is what stands in its place, which is why it names the target rather than asking about "this".

What cannot be deleted

Two version rows refuse, and say so by not offering d:

• The latest version. A plan with no current text is not a plan, and every read path assumes one exists.
• A version a lock was cut from. --splice re-reads a locked block's source text out of the version it was recorded in, so deleting that version would break the marker path. See Locking.

Deleting the plan itself is always allowed. If you want it gone, the locks go with it.

Repairing the index

index.json is a derived cache — planx list and the picker read it instead of opening every plan directory — so an interrupted write can leave it stale.

planx doctor

It walks every plan, reports anything it cannot make sense of, and rebuilds the index from the directories on disk. It is the only repair path in the tool.