Skip to content

[Docs] Explain task history recovery safeguards #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
zoomote wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[Docs] Explain task history recovery safeguards #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/features/settings-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,10 @@ Opens a dialog to set a custom storage directory for Zoo Code data. By default,

**Note:** This setting can also be configured in VS Code settings as `roo-cline.customStoragePath`. See the [VS Code Settings Reference](#vs-code-settings-reference) section below for details.

#### Task History Reliability

Zoo Code preserves the last saved task history if the storage file is temporarily unavailable or cannot be parsed while reopening a task. Reopening also keeps finalized task messages intact instead of treating hydration cleanup as a reason to rewrite the stored conversation. If a task cannot load from a custom, network, or cloud-synced storage location, restore access or recover a valid copy of the history file from backup before reopening the task; Zoo Code does not replace the existing history with an empty conversation.

### Import Settings from File

**Command:** `roo-cline.importSettings`
Expand Down
Loading