# Versioning and Backups and AI use **URL:** \ **Category:** Feature Request\ **Created:** [May 20, 2026, 2:13pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142 "2026-05-20T14:13:57Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mlw](https://avatars.discourse-cdn.com/v4/letter/m/8edcca/32.png) [@mlw](https://community.bear.app/u/mlw)\ **Post date:** [May 20, 2026, 2:13pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142/1 "2026-05-20T14:13:57Z")
With the release of the MCP and cli tools, I really think these two features gain much more importance. Bulk edit to notes with AI for example is practically impossible to revert without backups and makes me very afraid to use it. The problem is that the backups are manual AND that restoring them changes all notes UIDs, rendering links to notes broken. Version control is very useful to know what changes the AI agent makes. Would also love some way to diff the different versions so I can see easily what the agent changed in particular note. is the team working on them, and if not are there any plans to do so? ---
**Author:** ![bolive](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/bolive/32/3160_2.png) [@bolive](https://community.bear.app/u/bolive)\ **Post date:** [May 20, 2026, 2:57pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142/2 "2026-05-20T14:57:05Z")
Asked the same question. [Note versioning - Bear feedback / Feature Request - Bear Community](https://community.bear.app/t/note-versioning/19015) ---
**Author:** ![daneb1](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/daneb1/32/5808_2.png) [@daneb1](https://community.bear.app/u/daneb1)\ **Post date:** [May 22, 2026, 7:35pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142/3 "2026-05-22T19:35:08Z")
I agree that versioning would be good. However I am not sure your claim “restoring them changes all notes UIDs, rendering links to notes broken.” is valid. I believe UID is changed only if you try to restore older note and newer (with the same UID) still exist in Bear as your actual note. If you restore to empty database, UID are restored to originals. ---
**Author:** ![mlw](https://avatars.discourse-cdn.com/v4/letter/m/8edcca/32.png) [@mlw](https://community.bear.app/u/mlw)\ **Post date:** [May 24, 2026, 3:14pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142/4 "2026-05-24T15:14:17Z")
They aren’t IIRC. The devs have confirmed it elsewhere. The UUID is apparently used for sync functionality and are assigned anew in a restore: > [@Bug report: different note ids after restoring from backup](https://community.bear.app/t/bug-report-different-note-ids-after-restoring-from-backup/12362/3): > > Hello, this is intended because the same UUIDs are used for the sync. Backup restoration is supposed to reset the online status, but using the same UUID may lead to issues because of how CloudKit and our sync are conceived. The UUID in the backup’s single files is used to change the internal note-linking when a backup is restored. Unfortunately, this applies only to the note links in Bear and not to external apps. Theoretically, we can overcome this limitation but means heavily changing the sy… ---
**Author:** ![CrazyFurBall](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/crazyfurball/32/7914_2.png) [@CrazyFurBall](https://community.bear.app/u/CrazyFurBall)\ **Post date:** [May 30, 2026, 8:03pm UTC](https://community.bear.app/t/versioning-and-backups-and-ai-use/19142/5 "2026-05-30T20:03:12Z")
I’ve started using the Bear CLI to accomplish versioning. It runs hourly to check if any new notes, and then extracts the .md files and attachments. This is then copied to my cloud backup service. The cloud service maintains versions of all the .md files. I made some changes to a script I found on the bear Reddit forum. It’s working well for me. I wish this was built in however. Even if in Bear I could tell it to make a copy of an .md file automatically after any changes and save it to a specific folder.