VibeDesk/Guides

How to run several Claude Code sessions at once on Windows

Frontend in one terminal, API in another, a side project in a third. Here is how to set that up with what Windows already has – and how to always know which session is waiting for you.

Updated 20 October 2026 · 6 min read

Why more than one session?

Claude Code works best when it can focus on one task in one folder. As soon as you work on two things – a frontend and its API, or a bug fix next to a new feature – it is faster to give each its own session than to keep switching context in one. The catch: you now have to watch several terminals, and a session that is waiting for a yes just sits there until you notice.

1. Windows Terminal: one tab per project

Windows Terminal is installed on Windows 11 and free on Windows 10. Open a tab per project and start Claude there:

wt -d C:\Projects\shop-frontend cmd /k claude ; nt -d C:\Projects\api-server cmd /k claude

Run it from the Run dialog (Win + R) or cmd. In PowerShell, escape the separator as `;.

That opens two tabs, each already in its folder with Claude running. Two tips:

  • Name your tabs (right-click → Rename tab) so you can tell them apart at a glance.
  • Split panes with Alt + Shift + + if you want to see two sessions side by side.

2. Same repo? Use a git worktree per session

Two sessions editing the same folder will step on each other's changes. Git worktrees give each session its own copy of the repo on its own branch:

git worktree add ..\shop-login feature/login
git worktree add ..\shop-cart  feature/cart

Start one Claude session in each folder. When both are done, merge the branches as usual and remove the worktrees with git worktree remove ..\shop-login.

3. Know when a session waits for you

This is the part that costs the most time: a session asks for permission, you are looking at another tab, and nothing happens for fifteen minutes. Claude Code has hooks for exactly this. A Notification hook runs whenever Claude needs your attention. Add this to %USERPROFILE%\.claude\settings.json to hear a short beep:

{
  "hooks": {
    "Notification": [
      { "hooks": [ { "type": "command", "command": "powershell -NoProfile -Command \"[console]::beep(880,250)\"" } ] }
    ]
  }
}

A beep tells you that something waits, not which session. With tab names you can usually find it quickly; with four or more sessions it gets harder. For a real toast with the project name, see Windows notifications for Claude Code.

4. Keep an eye on your limits

Several sessions on a Pro or Max plan use up your five-hour window faster. Keep long, expensive tasks in one session and give the others smaller jobs. If you hit the limit, the message tells you when it resets – a good moment for a break rather than a reason to babysit the terminal.

5. Or let a desktop do the watching: VibeDesk

Full disclosure: this site belongs to VibeDesk, a free and open-source app built for exactly this setup. It runs the real Claude Code CLI and adds the overview around it:

  • One dot per session in the dock – green working, yellow waiting for you, blue done.
  • Permission requests as cards – Allow, Always or Deny in one click, also from your phone.
  • Merge Studio gives parallel sessions their own worktrees and predicts conflicts before you merge.
  • After a usage limit it reads the reset time and lets Claude continue on its own.

See it in the 5-minute tour or read more about sessions and approvals. Comparing setups? See Claude Code GUIs for Windows.

Checklist

  • One terminal tab (or pane) per project, named.
  • Same repo? One git worktree per session.
  • A Notification hook so a waiting session gets your attention.
  • Big tasks in one session, small ones in the others.

Let Claude work.Step in when it counts.

FreeOpen source (MIT)Windows 10/11Uses your own Claude plan