Allow parallel browser development ports

README.md

@@ -22,7 +22,9 @@ builds still require the [Tauri prerequisites](https://v2.tauri.app/start/prereq
 See [contributing](docs/contributing.md) for exact pins, registry settings,
 and the pinned pnpm package's Intel Mac limitation.
 
-Run **one** of `just web` or `just desktop` at a time; both use port 1430.
+Browser servers prefer port 1430 and automatically use the next open port, so
+`just web` can run from multiple worktrees. `just desktop` requires port 1430
+because its native window uses that fixed development URL.
 Without live opt-in they run the shell without relay identity access.
 `just iterate` applies formatting and runs fast checks plus the frontend build.
 `just scan` adds tests and native checks. [PR CI](.github/workflows/ci.yml) runs
@@ -53,13 +55,16 @@ in the non-live shell/fixture state.
    are public configuration, not secrets. With both relay settings unset, there is
    no default relay or alias map; Personal space and communities saved by canonical
    URL remain usable. Configuration does not automatically join a community.
-3. Start **one** development target:
+3. Start a development target:
    ```sh
    just web
    # Or, instead of web:
    just desktop
    ```
 
+   Open the Local URL printed by `just web`; parallel worktrees may use a port
+   above 1430. Stop the process using 1430 before starting `just desktop`.
+
 The broker reads the existing Keychain credential only after validating the
 public pin, refuses mismatches and never falls back to another credential. If it
 reports a mismatch, check which account your existing Buzz installation uses;

docs/agents.md

@@ -212,7 +212,7 @@ There is no agent-global sequence gate: producer sequences reset, skip and inter
 ### Try with an existing owner account
 
 Use the [README's public-pin/Keychain setup](../README.md#relay-channels) and run
-`bin/just web` (or `bin/just desktop`, not both). Open http://localhost:1430, choose
+`bin/just web` (or `bin/just desktop`). Open the printed Local URL, choose
 the agent's community and click **Agent Activity**. Keep the existing Buzz runner
 active, with telemetry publication enabled on the agent, then give it work. This
 app does not start agents or turn publishing on. No records may mean publishing

docs/communities.md

@@ -10,7 +10,7 @@ each community's queries, live subscriptions, projections and durable outbox.
 
 Configure `BUZZ_DEV_VIEWER` with your existing Buzz public key in `.env.local`
 ([setup and safety notes](../README.md#relay-channels)), then run
-`just web` and open http://localhost:1430, or use `just desktop` instead. The
+`just web` and open the Local URL it prints, or use `just desktop` instead. The
 development broker requires macOS and refuses a Keychain identity that does not
 match your explicit public pin.
 Click the avatar → **Settings → Profile** to edit and save a local default

docs/contributing.md

@@ -44,7 +44,8 @@ The pinned pnpm Hermit package supports Apple Silicon macOS but marks Intel macO
 on an unsupported platform; resolve that tooling gap first. Other platforms still
 need their own validation.
 
-- `just web`: install locked dependencies and start Vite.
+- `just web`: install locked dependencies and start Vite on port 1430 or the
+  next available port, allowing parallel browser development across worktrees.
 - `just desktop`: install locked dependencies and start Tauri, which starts Vite.
 - `just fullstack`: reserved, exits unsuccessfully with an explanation. It will
   eventually start local Docker services including the Buzz relay backend.
@@ -65,8 +66,9 @@ isolated test buses, never use the desktop session bus or display real banners.
 Installs run on every invocation to account for branch and lockfile changes.
 pnpm reuses its shared package cache; no node_modules directory needs to be copied
 into a new worktree. Native dependencies are fetched by Cargo as needed. Initial
-downloads and native compilation can take time. Web and desktop dev use the same
-port; run them separately or open the browser at the desktop dev server URL.
+downloads and native compilation can take time. Desktop dev requires port 1430
+for its fixed native development URL. Browser dev prints its selected URL and can
+use a later port when 1430 is occupied.
 Both run the development broker with your identity when the public
 `BUZZ_DEV_VIEWER` pin is configured in `.env.local`, and start without live
 identity otherwise; see [the setup and Keychain requirements](../README.md#relay-channels).

package.json

@@ -9,6 +9,7 @@
   },
   "scripts": {
     "dev": "vite",
+    "dev:desktop": "vite --strictPort",
     "build": "pnpm typecheck && vite build",
     "preview": "vite preview",
     "author:build": "node scripts/build-author.mjs",

src-tauri/tauri.conf.json

@@ -4,7 +4,7 @@
   "version": "0.0.0",
   "identifier": "dev.local.buzz.foundation",
   "build": {
-    "beforeDevCommand": "pnpm dev",
+    "beforeDevCommand": "pnpm dev:desktop",
     "devUrl": "http://localhost:1430",
     "beforeBuildCommand": "pnpm build",
     "frontendDist": "../dist"

vite.config.ts

@@ -34,7 +34,7 @@ export default defineConfig(async ({ command, mode }) => {
     clearScreen: false,
     server: {
       port: 1430,
-      strictPort: true,
+      strictPort: false,
       watch: { ignored: ["**/src-tauri/**", "**/target/**"] },
     },
   };