Wrixton Recurrence: Roll-Forward vs. Spawn-on-Complete

Recurring items let you track obligations that come back on a schedule without having to re-enter them every time. Wrixton supports recurrence on all six item kinds, but the mechanics differ depending on whether the item is a chore or anything else. Understanding the two models helps you pick the right kind from the start.

The `--every` flag

Add recurrence to any item with --every. The flag accepts several named intervals as well as a freeform "<N> <unit>" syntax:

Value	Meaning
`daily`	Every 1 day
`weekly`	Every 1 week
`biweekly`	Every 2 weeks
`monthly`	Every 1 month
`quarterly`	Every 3 months
`yearly`	Every 1 year
`"3 months"`	Every 3 months (explicit)
`"2 weeks"`	Every 2 weeks (explicit)
`"90 days"`	Every 90 days

Units can be singular or plural: day or days, week or weeks, month or months, year or years.

Two recurrence models

Chore — roll forward
Everything else — spawn on complete

A chore is a task you never truly finish — you just do it again. Rather than ever being marked done in the traditional sense, a chore tracks when you last completed it. Its effective next-due date is computed as:

next due = last completion date + every

When you run track done <id> on a chore, Wrixton records today as the completion date and the chore stays open. No completion history is kept; no new item is spawned. The same c- prefixed ID persists for as long as the chore exists.

# Create a chore (--every is required)
track add chore "Replace HVAC filter" --every "3 months" --estimate 20m

# Mark it done today (records completion, stays open)
track done c-a4f1

# Record a past completion date
track done c-a4f1 --when 2026-05-15

# Push next due out by two weeks
track snooze c-a4f1 2w

Snoozing a chore adjusts the recorded completion date rather than setting a due date directly, so the next computed due date lands on the target you specify.

For all non-chore kinds (todo, task, gift, shopping, grocery), adding --every opts into spawn-on-complete recurrence. Each time you mark the item done, Wrixton:

Sets the current item’s status to done (landing it in the Completed tab).
Creates a brand-new copy of the item with status todo, due one interval after the original’s due date (or today if no due date was set).

Each occurrence is its own independent item, so your completion history is fully preserved. The spawned copy keeps the same title, priority, tags, notes, estimate, and --every interval, so it continues to recur without any extra work on your part.

# Add a recurring todo
track add todo "Pay rent" --every monthly --due 2026-06-01

# Marking it done creates the July occurrence automatically
track done t-1f3a
# → done: Pay rent
# → ↻ repeats monthly — next due 2026-07-01

# Recurring gift (spawns a new reminder after each giving)
track add gift "Birthday flowers" --for "Mom" --every yearly --due 2026-08-12

# Recurring shopping item
track add shopping "Printer ink" --every "3 months"

The CLI prints the next due date immediately after you run track done on a recurring non-chore item, so you can confirm the interval looks right before moving on.

Editing recurrence after creation

You can add, change, or clear the recurrence interval on any existing item:

# Change an existing interval
track edit t-1f3a --every weekly

# Clear recurrence entirely (pass an empty string)
track edit t-1f3a --every ""

For chores, you can correct a missed or mis-recorded completion by passing --when to track done:

track done c-a4f1 --when 2026-05-28

​The --every flag

​Two recurrence models

​Editing recurrence after creation

The `--every` flag

Two recurrence models

Editing recurrence after creation