I open VS Code and have to decide which repository to open first. I know which ones I've been working on. What I can't always remember is where I left changes, whether I pushed my last commit, or whether I need to pull before I start.
I switch between repos more often now. A small task in one project can interrupt a longer one somewhere else. If a coding agent works in a separate Git worktree, there's another checkout to remember too. File → Open Recent can get me back into a folder. I still have to open that folder to find out what's waiting for me.
I wanted to make that decision before opening the repo. So I built Repo Board, a VS Code extension that puts the Git state of my local repositories in one tab. The way I work with AI is part of why I wanted it. The extension itself reads Git and runs without AI.
The first thing I want to see in VS Code
I wanted to set this up once by pointing it at the folders where I keep my clones. That's why the setup guide asks for a folder to scan. Give it a parent folder such as C:\code or ~/src and it looks for Git repositories underneath it, three levels deep by default. If you want to add a single repo, open it and run Repo Board: Add Current Folder from the Command Palette.
The second thing I wanted was a way to keep a few repos in the same place. A repo can matter for the whole week even if I opened it only once today. Pin it and it stays in the Pinned section at the top of the board. The project switcher gives pinned repos priority too.
The Repo Board demo uses sample repositories. The two pinned repos stay at the top while the rest are grouped below.
To make it the first tab you see, choose Use Repo Board as Start Page in the setup guide or the board's ⋯ menu. This applies to new VS Code windows that start without a folder. You can restore your previous startup setting with Repo Board: Stop Using Repo Board as Start Page. Repo Board setup and startup behavior
“Do I need to pull?” takes more than one number
Look at checkout-web in the demo. Its branch, feature/apple-pay, has seven file changes, one local commit ahead of its upstream, and two commits behind. Those numbers describe three different things. The file changes are in the working tree or index. The ahead count tells me I have a commit the upstream branch doesn't have. The behind count tells me there are upstream commits I haven't incorporated. For that tile, I'd open the repo and inspect the diff and history before deciding how to update it.
The board lets me shorten that list of decisions. With changes brings up repos that have uncommitted work, and Most changes puts the largest counts first. I can switch to Behind when I want to see which branches need an update. The status filters help me decide which folder to open, and the board can open a terminal there directly.
The sample board filtered to repositories with uncommitted changes.
Under the hood, git status --porcelain=v2 --branch supplies the branch, upstream, ahead and behind counts, and file status. Ahead and behind are relative to what Git knows about the upstream locally. If somebody pushed five minutes ago, a status check alone won't see that push. Repo Board can fetch in the background when the dashboard opens. It shows cached information while it refreshes, so I treat the counts as a snapshot. Turn off repoBoard.fetchOnOpen if you'd prefer to fetch manually. Repo Board Git client · Git fetch documentation
Fetching updates Git's view of the remote. Pulling can move the checked-out branch and update files, so it's an action I choose. Repo Board's pull uses --ff-only. If both sides have new commits, Git stops and leaves the decision about how to reconcile them to me. That's what I want for the checkout-web example. Git pull documentation
For a pass across the board, Repo Board: Fetch All Repos refreshes repos with an upstream. Repo Board: Pull All Repos That Are Behind fetches first, then tries a fast-forward on the ones that are behind. It skips repos with conflicts already present in the working tree. Bulk fetch and pull implementation
Finding the worktree where I left the changes
A clean main checkout can sit next to a linked worktree with unfinished edits. Opening the main folder is only half the answer when the work happened in the linked one. This is easy to run into when an agent uses a separate checkout for a task. It can happen just as easily if you use git worktree yourself.
Repo Board groups linked worktrees under the main repo by default. Click the worktree badge and you can see the branches, open the right checkout, or start a terminal there. The demo shows six changes on agent/fix-checkout-total and flags review/pr-412 because its folder is gone. Both entries belong to storefront. If you want each worktree to appear as its own project, set repoBoard.worktrees to separate. Worktree behavior in Repo Board
Linked worktrees under the storefront tile in the sample board.
When I already know what I want to open, the board can stay in the background. Press Ctrl+Alt+P on Windows or Linux, or Cmd+Alt+P on macOS, and type part of a repo name, path, branch, or tag. If the shortcut is taken, look for Repo Board: Switch Project… in the Command Palette.
Try it with the repos you're using this week
Install Repo Board from the VS Code Marketplace, or run this if you have the code CLI on your PATH.
code --install-extension emanuelebartolesi.vscode-repoboard Start with one folder you already work in and pin two repos you return to often. Give the start page a try the next time you open an empty VS Code window. See if you can tell where you left off before you open a project. That's the bit of my day I wanted to make easier.
If you try it, I'd like to know what you check first when you come back to a project. And if Repo Board gets something wrong about your folder layout, upstream, or worktrees, please open an issue on GitHub. The extension is open source under the MIT license.



