fix: clear command should not clear corpus_client_state.json
Prevent Clear Command from Removing Login State File
Description
Currently, executing the clear command removes the login state file (corpus_client_state.json). This behavior forces users to log in again unnecessarily, even when they only intend to clear other application data.
This results in a poor user experience by introducing redundant authentication steps and interrupting workflow continuity.
Proposed Enhancement
- Modify the
clearcommand to exclude the login state file (corpus_client_state.json) from deletion. - Ensure that only non-authentication-related data is cleared.
Benefits
- Eliminates unnecessary re-authentication for users.
- Improves user experience and workflow efficiency.
- Provides clearer separation between clearing application data and authentication state.
Acceptance Criteria
- Executing the
clearcommand does not deletecorpus_client_state.json. - Users remain logged in after running the
clearcommand. - Documentation is updated to reflect the revised behavior of the
clearcommand.
Edited by Bhaskar Battula