Feature guide · history

Find the exact operation without digging.

Search, date ranges, and action counts compose locally so command history remains reviewable and exportable.

Behavior

History uses plain text by default, with an optional bounded regex builder, date-from/date-to controls, and action checkboxes derived from the actual records. Counts show what each action contributes.

Configuration

Use any combination of the text query, date range, and action filters. Export Markdown exports the filtered view and includes its result count.

Failure modes

Invalid patterns stay visibly invalid; reversed dates report an inline error; no-match states name the active filter result.

Security

Filtering is local. Export uses the existing user-selected file destination and does not send history to a service.

Verification

Electron contract checks cover the derived filters and composition, while the real off-screen History capture shows the controls.

Suggested articles

Electron manual client · Memory checkpoints · Tab groups and bulk close