Summary
history.md is valuable for context recovery, but it records complete code, stdout, stderr, and tracebacks. It survives both stop and clean.
On the reviewed macOS installation, the session directory was mode 0755 and history.md was 0644, making contents readable to other local users on a shared host.
Expected
Make retention and cleanup explicit, while preserving the useful default workflow.
Possible scope
- Add
pyreplab clean --history or a dedicated history purge command.
- Document persistence and the risk of printing secrets.
- Create and validate a per-user session directory with restrictive permissions such as
0700 (for example under $XDG_RUNTIME_DIR).
- Reject unexpected ownership or symlinked IPC/history paths.
Priority context
This is low priority on a private single-user machine, but is important privacy hygiene for shared machines or agent workflows that may print credentials.
Summary
history.mdis valuable for context recovery, but it records complete code, stdout, stderr, and tracebacks. It survives bothstopandclean.On the reviewed macOS installation, the session directory was mode
0755andhistory.mdwas0644, making contents readable to other local users on a shared host.Expected
Make retention and cleanup explicit, while preserving the useful default workflow.
Possible scope
pyreplab clean --historyor a dedicated history purge command.0700(for example under$XDG_RUNTIME_DIR).Priority context
This is low priority on a private single-user machine, but is important privacy hygiene for shared machines or agent workflows that may print credentials.