port-allocator

To prevent development port conflicts between multiple Claude Code instances, use a port allocator to assign dedicated 10-port ranges starting at 3000 to each project, persisting allocations in a registry file across sessions.

Automatically allocate ports for Node.js projects by scanning a code root to detect package.json files, which triggers the assignment of a dedicated 10-port range starting at 3000 for each discovered project.

Project port allocations are stored in ~/.claude/port-registry.json, using an append-only workflow to persist assignments across sessions and maintain a reliable port registry.

Yes, the port allocator excludes build artifacts during project scanning by enforcing skip rules, ensuring only valid package.json-containing projects are registered and assigned a port range.

Yes, you can restart a dev server safely because the port allocator ensures only the current project's ports are touched during restarts, preventing interference with other registered projects.

The best way to manage dev server ports for multiple projects is using an automated port registry that assigns 10-port ranges starting at 3000, scans for package.json files, and persists allocations to avoid conflicts.