Vault Branching
Цей контент ще не доступний вашою мовою.
Sometimes you want to try something without committing to it. Vault branching lets you create an isolated copy of your knowledge where you can add, modify, or remove entries — then merge when you’re satisfied, or delete the branch if the experiment didn’t work out.
Creating a branch
Section titled “Creating a branch”When you want to experiment — reorganize entries, test a new tagging scheme, or stage changes before a team review:
You: “Create a vault branch called ‘security-reorg’”
Agent: Created branch: security-reorg
The branch starts empty. It doesn’t copy your entire vault — it only tracks the changes you make on it.
Adding changes to a branch
Section titled “Adding changes to a branch”Once you have a branch, you can stage operations on it. Each operation targets a specific entry:
You: “On the security-reorg branch, add a new entry about input sanitization”
Agent: Added operation to security-reorg: add entry ‘Input Sanitization Standards’
You can also modify existing entries or mark them for removal:
You: “On the security-reorg branch, modify the JWT pattern to include token rotation”
Agent: Added operation to security-reorg: modify entry ‘JWT Best Practices’
You: “On the security-reorg branch, remove the outdated CORS entry”
Agent: Added operation to security-reorg: remove entry ‘CORS Permissive Config’
Three operation types are available:
| Action | What it does |
|---|---|
| add | Stage a new entry to be created on merge |
| modify | Stage changes to an existing entry |
| remove | Mark an existing entry for deletion on merge |
Listing branches
Section titled “Listing branches”See all your active branches and how many operations each one has:
You: “List vault branches”
Agent: 2 branches:
- security-reorg — 3 operations, not merged
- q4-cleanup — 7 operations, not merged
Merging a branch
Section titled “Merging a branch”When you’re happy with the changes, merge them into the main vault:
You: “Merge the security-reorg branch”
Agent: Merged security-reorg into main vault. 1 entry added, 1 modified, 1 removed.
On conflict — when a branch modifies an entry that was also changed in the main vault — the branch version wins. This keeps the merge predictable: what you staged is what you get.
Merging requires admin-level access. If your agent has access controls configured, only admins can merge.
Deleting a branch
Section titled “Deleting a branch”If you decide to discard the experiment:
You: “Delete the q4-cleanup branch”
Agent: Deleted branch: q4-cleanup (7 operations discarded)
Deleting a branch removes all staged operations. It does not affect the main vault.
When to use branching
Section titled “When to use branching”- Knowledge reorganization — restructure domains or tags without risking your live vault
- Team collaboration — one person stages changes, another reviews before merge
- Bulk imports — stage a large batch of entries on a branch, review them, then merge
- Rollback safety — if something goes wrong during a complex edit, the main vault is untouched
Branching is lightweight. Create branches freely — they cost almost nothing until merged.
Related guides
Section titled “Related guides”- Building a Knowledge Base — learn what to capture before you branch
- Entry Linking & Knowledge Graph — connect entries with typed links (links are preserved across branches)
- Knowledge Review Workflow — combine branching with review for team quality control
- Capabilities — full list of vault branching operations
- API Reference — parameter details for
vault_branch,vault_branch_list,vault_merge_branch
Previous: Cross-Project Knowledge — share patterns across projects. Next: Entry Linking & Knowledge Graph — connect your entries into a Zettelkasten.