Branch sessions with git worktrees

In short

Branch sessions let you try work in an isolated copy of your project using git worktrees, so experiments never disturb your main copy until you choose to merge.

Updated 2026-06-29

What is a branch session?

A branch session is a safe, isolated copy of your project where work happens on its own track. Under the hood it uses a git worktree, but you don't need to know git — Granular handles the branching, committing, and merging for you through plain-English actions.

Why work in a branch?

Branches let you try things without risk. The main copy stays untouched until you decide to merge the branch's work in. If an experiment doesn't pan out, you discard it and nothing is lost. This is also how worker agents stay isolated from each other.

Git, without the jargon

Granular surfaces a per-session git status and offers commit, push, merge, and sync as guarded, one-click actions — so you get version control's safety net without learning its commands.

Frequently asked questions

Do I need to understand git?
No. Granular runs git for you behind plain-English actions; you get the safety of version control without the commands.
What happens if a merge conflicts?
Granular leaves your main copy untouched and tells you about the conflict in plain English so you can decide how to proceed.

Related