Problem
The CLI allows changing the selected app's proxy listen port while the local proxy is running, as long as that app does not currently have an active proxy worker.
However, the TUI blocks editing the listen port whenever the local proxy is running. This makes the TUI stricter than the CLI and prevents a valid workflow: updating an inactive app's preferred proxy port while other app routes are still running.
Current Behavior
In the TUI proxy settings:
Listen Address is blocked while the local proxy is runningListen Port is also blocked while the local proxy is running- The user must stop the whole proxy before editing the port, even when the current app has no active worker
In the CLI:
- changing
listen-address requires stopping the proxy
- changing
listen-port is only blocked when the selected app has an active proxy worker
Expected Behavior
The TUI should match the CLI behavior:
- keep
Listen Address blocked while the local proxy is running
- allow editing
Listen Port when the proxy is running but the current app has no active worker
- block editing
Listen Port only when the current app's proxy route is active
- show different guidance for address vs port:
- address: stop the local proxy
- port: stop this app's proxy route
Why
The listen address is global runtime state, so blocking it while the proxy is running makes sense.
The listen port is app-specific preferred worker configuration, so it should be editable when the current app is not actively routed through the proxy. This keeps the TUI consistent with the CLI and avoids requiring users to stop unrelated running proxy routes.
Problem
The CLI allows changing the selected app's proxy listen port while the local proxy is running, as long as that app does not currently have an active proxy worker.
However, the TUI blocks editing the listen port whenever the local proxy is running. This makes the TUI stricter than the CLI and prevents a valid workflow: updating an inactive app's preferred proxy port while other app routes are still running.
Current Behavior
In the TUI proxy settings:
Listen Addressis blocked while the local proxy is runningListen Portis also blocked while the local proxy is runningIn the CLI:
listen-addressrequires stopping the proxylisten-portis only blocked when the selected app has an active proxy workerExpected Behavior
The TUI should match the CLI behavior:
Listen Addressblocked while the local proxy is runningListen Portwhen the proxy is running but the current app has no active workerListen Portonly when the current app's proxy route is activeWhy
The listen address is global runtime state, so blocking it while the proxy is running makes sense.
The listen port is app-specific preferred worker configuration, so it should be editable when the current app is not actively routed through the proxy. This keeps the TUI consistent with the CLI and avoids requiring users to stop unrelated running proxy routes.