Remember what actually happened

Execution Journal

Shell history should record executions as structured events, not merely save the command strings.

A journal entry can know more

Command text, working directory, host, shell, explicit context, start/end time, duration, exit code, tags, privacy state, and optional notes can all be stored as queryable metadata.

Context turns history into useful memory

The F7 key should answer “what is relevant to what I’m doing now?” rather than only “what did I type most recently?” Exact folder, repository, host, client, project, and recency can all influence ranking.

Capture first. Curate later.

Start a context before an unfamiliar operational task, work normally, then review the session. Keep the commands that worked, annotate the important failures, and export a reusable runbook.