osFoundry / Platform
Versions
Branch any note, KB or repo. Compare versions side-by-side. Merge or roll back.
What it is
Versions brings branch-compare-merge history to everything you keep in osFoundry, not just code. Fork a single note, an entire knowledge base, or a code repository into a separate line of work, make changes without touching the original, and decide later whether to merge them back or discard them. Every branch keeps its own history, so nothing you write over is truly gone until you choose to drop it.
Inside osFoundry, this works the same way across content types because they live in one local-first workspace. When an AI agent rewrites a KB article, drafts a new version of a note, or edits files in a repo, you branch first and review the result against the original before it becomes canonical. The side-by-side compare view shows exactly what changed line by line, so you approve a merge on evidence rather than trust. If a change turns out wrong after the fact, roll back to any earlier version.
Because osFoundry is a bring-your-own-key desktop app, your version history lives with your data on your device rather than in a vendor's cloud, and there are no per-seat fees for the people reviewing or branching alongside you. Versions is the safety net that makes it reasonable to let agents and teammates edit real knowledge: you can always see what changed, keep the good, and undo the rest.
Key capabilities
- Branch a note, knowledge base, or code repo into an independent line of work without altering the original
- Compare any two versions side-by-side with a line-by-line diff before you commit to a change
- Merge a reviewed branch back into the canonical version, or discard it if the change was wrong
- Roll back to any earlier version at any time, so an agent's or teammate's edit is never destructive
- Version history stays local on your device with no per-seat fees, part of the same BYOK workspace as your chat, apps, and data
Use cases
- Knowledge manager: branch the KB before an AI agent rewrites a batch of articles, diff each one, and merge only the improvements
- Researcher: fork a long note to try a different structure, compare both versions, and keep whichever reads better
- Developer: review an agent's changes to a repo on a separate branch, then merge or roll back once you've seen the diff
Frequently asked questions
Does versioning work for notes and knowledge bases, or only for code?
It works for all three. You can branch, compare, merge, and roll back a single note, an entire knowledge base, or a code repository — they share the same version model because they live in one osFoundry workspace.
Where is my version history stored?
osFoundry is a local-first desktop app, so your branches and history live with your data on your device rather than on a vendor's server. You bring your own keys and keep control of the data.
Can I undo a change an AI agent made to my content?
Yes. Branch before an agent edits, review the diff side-by-side, and merge only if it's right. If a change slips through and turns out wrong, roll back to any earlier version — edits are never permanently destructive.