Question: Purpose, naming, and future of command_history.txt

Summary

The file ~/.code_puppy/state/command_history.txt stores a timestamped log of all user prompts/messages sent to the agent. A few questions have come up about this feature:

Questions

1. Naming Confusion

The name command_history.txt suggests it might store shell commands or slash-commands (like /help, /model), but it actually stores user prompts/messages. Should this be renamed to something clearer like prompt_history.txt or message_history.txt?

2. Redundancy with Session Storage

With the autosave/session storage system already persisting conversation history, is this file redundant? What's the intended use case that session storage doesn't already cover?

3. Documentation

There doesn't appear to be documentation explaining what this file is for or how users might leverage it. Should we add docs?

4. Privacy Considerations

Users may not be aware their prompts are being logged to a plaintext file. Should there be:

• A note in the docs/README about this?
• A config option to disable it?
• A /clear-history command?

Context

• Introduced in commit e1b1d73 ("Updates") on 2025-08-24
• Originally part of the TUI feature set
• Currently lives at ~/.code_puppy/state/command_history.txt

Start by inspecting the implementation of ~/.code_puppy/state/command_history.txt introduced in commit e1b1d73, then compare it with the autosave/session storage system. Clarify the intended distinction, naming, privacy behavior, and documentation needs; done means the project has an agreed scope and actionable requirements.