---
title: ".@openclaw workspace and memory files can be version-controlled!"
date: 2026-01-06
canonical: https://solmaz.io/x/2008538728180941238/
x_url: https://x.com/onusoz/status/2008538728180941238
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
---

.@openclaw workspace and memory files can be version-controlled!
In our pod, inotify triggers a watcher script every time there is a change to workspace folder, to sync these files to our monorepo. It then goes through the same steps:
- Create zeno-workspace branch if doesn't exist, otherwise, skip
- Sync changes to the branch, then commit
- Create PR on github if doesn't exist
- PRs can then be merged every once in a while, after accumulating enough changes. Merge triggers re-deploy, and clawd restarts with the same state
Simple foolproof automatic persistence for remote CI/CD handled clawd (except for when you are running multiple clawds at the same time, but we are not there yet)
cc @steipete