The CLI keeps the model simple: each command does one job, and you decide how to connect them. Use it directly in a terminal, or wire it into scripts, schedules, and tests.
Use save to create history,diff to inspect changes,restore orextract to recover content, and verify,validate,gc, andrepair for maintenance.
v0.9.8 adds storage format v2, which keeps chunks in pack files for faster saves with many files. New repositories use it by default; existing repositories stay in format v1 until you runupgrade, and downgrade converts back when Rinne v0.9.7 must open the repository again. See upgradeand Layout.
Since v0.9.7, Rinne also has activity, a separate local history of CLI command execution. It records results, exit codes, timing, and bounded error details in.rinne/activity/activity.db when recording is enabled.
Activity history
Activity history is independent from snapshot history. Snapshot history describes saved workspace states; Activity describes CLI commands that were executed in the workspace.
- Recording is disabled by default and is controlled by
.rinne/activity/settings.json. - Entries use UUIDv7 identifiers and a BLAKE3 hash chain.
rinne activity listandshowreview entries;verifychecks chain consistency.pruneapplies retention limits;clear --forcestarts a new Activity epoch.- Activity write failures use best-effort handling and do not change the main command result.
See the activity command referencefor selectors, date filtering, settings, pruning, and verification behavior.
Command groups
Early Access note: flags and output formatting may evolve between versions. Use the unified exit codes for scripting.