oc-update

To update ClawedBack without losing data, you need a process that fetches upstream code changes while explicitly preserving local configurations, auth tokens, and user-installed skills. This ensures your running deployment retains custom runtime data directories during the upgrade.

When applying upstream updates to a live deployment, your auth tokens and runtime data directories are preserved. The update process safely sequences code, docs, and core component upgrades without overwriting the local setup.

To resolve conflicts between upstream changes and local customizations, you use guided prompts that help you safely merge the updates. This ensures the upstream code changes are applied without breaking your specific running environment.

Yes, you can install updated dependencies while upgrading code and docs in a running installation. The update process verifies post-update health and can automatically install new dependencies required by the upstream changes.

The best way to safely apply upstream updates to a customized deployment is to use safe update sequencing that fetches upstream changes while preserving data directories. This approach verifies post-update health and guides conflict resolution.

Updating core components may overwrite user-installed skills if the update process does not explicitly preserve local configurations. Using a safe update method ensures user data and installed skills are protected during the upgrade.