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?
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.
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.