storybook-manager

You can manage multiple Storybook dev servers across git worktrees using an automated instance manager that handles instance creation, tracks them in a registry, and assigns unique ports starting from 6006.

Automatic port assignment for Storybook instances sequentially allocates unique ports starting from 6006 for each new instance, preventing network conflicts when running multiple dev servers simultaneously.

Yes, this Storybook instance management approach is fully cross-platform compatible, meaning the scripts to start, stop, and check dev server status function natively on Windows, Mac, and Linux.

Yes, you must install Storybook directly in each git worktree before running the instance manager, because the automation handles the dev servers and port routing but does not provision the Storybook framework itself.

The best way to check the status of running Storybook instances is to use a registry-based manager that tracks all active dev servers, allowing you to query their operational state and stop them as needed.

Storybook instances conflict because multiple worktrees attempt to bind to the default port 6006, an issue resolved by using an instance manager that automatically assigns a unique port to each worktree.