Skip to content

Add random ports guidance for detached mode #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Copilot wants to merge 2 commits into from
Closed

Add random ports guidance for detached mode #114

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ff3592
Initial plan
Copilot Mar 4, 2026
6331bad
Add random ports guidance for detached mode with --as-system-proxy false
Copilot Mar 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions assets/best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,9 @@

- Dev Proxy can run in detached (background) mode (v2.2.0+). This is useful for CI/CD pipelines, automated testing, and agent-driven workflows where Dev Proxy needs to run without an interactive terminal.
- When running in detached mode, use `--output json` to get structured, machine-readable output that can be parsed by scripts and agents.
- For detached mode and CI/CD scenarios, use `--port 0` (or set `port` to `0` in the configuration file) to let the OS assign a random available port. This avoids port conflicts when running multiple Dev Proxy instances in parallel. Similarly, use `--api-port 0` for the Dev Proxy API port.
- Combine random ports with `--as-system-proxy false` to prevent Dev Proxy from modifying system proxy settings. This way, each instance runs in isolation and only intercepts requests from applications explicitly configured to use its address and port.
- When using random ports, use `devproxy status` to find the actual assigned port, API URL, PID, and other details of the running instance.

## Output format

Expand Down