# How To Manage Multiple Flutter Versions With Git Worktrees And Z

> Manage multiple Flutter versions efficiently using Git worktrees, eliminating the need for external version managers like FVM.

- Skill: `rodydavis/how-to-manage-multiple-flutter-versions-with-git-worktrees-a` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rodydavis/how-to-manage-multiple-flutter-versions-with-git-worktrees-a`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rodydavis/how-to-manage-multiple-flutter-versions-with-git-worktrees-a/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: rodydavis (https://skillmd.com/u/rodydavis)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rodydavis/how-to-manage-multiple-flutter-versions-with-git-worktrees-a

---


# How to Manage Multiple Flutter Versions with Git Worktrees and ZSH


If you have been using [Flutter](https://flutter.dev/) for any length of time then you probably have needed to use multiple flutter versions across multiple projects.

In the past I used to use [FVM](https://fvm.app/) (Flutter Version Management) which is similar to [NVM](https://github.com/nvm-sh/nvm) (Node Version Manager) in the JS world.

I wanted a solution that only relied on [Git](https://git-scm.com/), and started using [worktrees](https://git-scm.com/docs/git-worktree) to manage the Flutter channels.

## Download the SDK 

Check out the flutter repo in a known directory, in this case I will download it to `~/Developer/`:

```
git clone https://github.com/flutter/flutter ~/Developer/flutter
```

## Add Flutter Channels 

Now we can add the branches we want to track:

```
cd ~/Developer/flutter
git checkout origin/dev
git worktree add ../flutter-stable stable
git worktree add ../flutter-beta beta
git worktree add ../flutter-master master
```

We need to checkout the dev channel to allow us to create the worktree for the master branch. This will keep the `flutter` directory separate so we can work on PRs and apply local changes.

After this runs we should have 4 directories: `flutter`, `flutter-master`, `flutter-beta` and `flutter-stable`.

## Add ZSH Alias for each Channel 

Now we need a way to reference each SDK on the fly with an [alias in ZSH](https://github.com/rothgar/mastering-zsh/blob/master/docs/helpers/aliases.md). Add the following to `~/.zshrc`:

```
alias flutter-master='~/Developer/flutter-master/bin/flutter'
alias dart-master='~/Developer/flutter-master/bin/dart'

alias flutter-beta='~/Developer/flutter-beta/bin/flutter'
alias dart-beta='~/Developer/flutter-beta/bin/dart'

alias flutter-stable='~/Developer/flutter-stable/bin/flutter'
alias dart-stable='~/Developer/flutter-stable/bin/dart'
```

## Conclusion 

After reopening the terminal, you can verify it is working by running (or add any channel we added above):

```
flutter-master doctor
dart-master --version

flutter-stable doctor
dart-stable --version
```

You can update any of the channels by navigating to the directory of the worktree for the given channel and pulling changes like any other Git repo.

```
cd ~/Developer/flutter-master
git checkout origin/master
```

Git worktrees are just a way to checkout multiple branches as separate folders instead of needing to stash changes.