conductor-remote 1.80.0 → 1.81.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -233,12 +233,15 @@ RELAY_TOKEN=$(openssl rand -hex 16) yarn start
233
233
  - ✅ Diff vs the workspace's target branch (file list + colorized patch,
234
234
  including untracked files).
235
235
  - ✅ **Launch and forward dev servers** — the workspace header's Play button
236
- presses Conductor's selected Run task, waits for its allocated
237
- `CONDUCTOR_PORT`, and exposes it at a tailnet-only HTTPS URL. Open and Stop
238
- controls appear once it is running; Stop uses Conductor's own button and
239
- removes only this relay's Serve mapping. Forwarding a server that is already up
240
- presses nothing in Conductor, so it takes about a second and opens the tab from
241
- that same tap. This requires a Run task configured
236
+ presses Conductor's selected Run task, expands the repository's named
237
+ `[[preview_urls]]` entries (including `$CONDUCTOR_PORT`), and exposes every local
238
+ HTTP preview at its own tailnet-only HTTPS URL. The primary preview opens
239
+ directly; additional previews appear in its dropdown. Repositories without
240
+ `preview_urls` retain detected-port fallback behavior. Open and Stop controls
241
+ appear once it is running; Stop uses Conductor's own button and removes only
242
+ this relay's Serve mappings. Forwarding a server that is already up presses
243
+ nothing in Conductor, so it takes about a second and opens the tab from that
244
+ same tap. This requires a Run task configured
242
245
  in Conductor and Tailscale on the viewing device, even when the relay itself
243
246
  uses public Funnel.
244
247
  - ✅ **Send prompt** — two strategies: