Logo

VS Code windows on Mac

Open and switch between VS Code project windows on Mac.

Choose File → New Window in VS Code, then open a project folder in that window. Repeat for a second project. You can keep projects in separate windows, use the Window menu to choose one, or use InfyniDock previews when several projects look alike.

By the InfyniDock team · Updated

Work with two projects in separate VS Code windows

Separate windows are useful when each project needs its own editor context. A multi-root workspace is another option if you want several folders in one window.

  1. STEP 1

    Open your first project

    Open a project folder in VS Code. Keep an identifiable file open so that the project is easy to recognize in its title and preview.

  2. STEP 2

    Create a second project window

    Choose File → New Window, then File → Open Folder in that new window. Select your second project. This keeps its editor context separate from the first project.

  3. STEP 3

    Optionally open a window from Terminal

    On macOS, first run “Shell Command: Install code command in PATH” from VS Code’s Command Palette. Then replace the example folder below with your actual project path. The --new-window option opens it in a new window.

    code --new-window ~/projects/my-project
  4. STEP 4

    Switch to a specific project

    Use VS Code’s Window menu to select a window by its title. With InfyniDock, reveal the VS Code previews and select the project you recognize, or use the configured FloatDock shortcut. A preview selects a window; editor tabs stay inside it.

InfyniDock product screenshot with separate Terminal and VS Code windows visible in the window selector
A product screenshot showing individual app windows in the selector. Appearance and available controls vary by app version and settings.

A VS Code multi-root workspace combines folders inside one editor window. An InfyniDock workspace organizes desktop windows. Neither creates a Git branch or changes a repository automatically.

The problem

Command-Tab switches VS Code, not the project you meant.

When several VS Code windows are open, app-level switching still leaves you searching for the exact repository or branch.

The InfyniDock workflow

Make each VS Code project a visible window target.

InfyniDock helps preview and activate the exact VS Code window, then keep it together with Terminal, Chrome, docs, and AI assistant windows in a broader workflow.

Developer workflow benefits

Project recognition

Preview windows before switching to avoid opening the wrong codebase.

AI coding context

Keep VS Code near ChatGPT, Claude, Codex, Terminal, and docs.

Workspaces

Group project windows into recurring coding contexts.

Best for

  • Developers with multiple VS Code windows
  • AI coding workflows with docs and terminal windows
  • Users who switch between several repositories

Not the best fit for

  • Developers who only use one editor window
  • Users who prefer keyboard overlays only

Common questions

Can InfyniDock switch between VS Code windows?

Yes. InfyniDock focuses on exact window switching, which is useful when VS Code has multiple project windows open.

Can it replace Command-Tab for coding workflows?

It can complement Command-Tab by adding window previews, exact activation, FloatDock, and workspace context.

Is this useful with AI coding tools?

Yes. AI coding often adds assistant, browser, terminal, and preview windows, making exact window switching more important.