cpak 2.11.1 / September 1, 2026
Change networks without restarting your cpak apps
Switch Wi-Fi or enter a VPN and keep the same application container. cpak 2.11.1 refreshes its private network in place while host localhost stays closed.
Before 2.11.1, changing networks could leave a running cpak app without DNS. The window stayed open, but browsers stopped loading pages and connected apps appeared offline until you restarted them.
Keep your app running when the network changes
cpak now renews the app's private connection when your computer receives new DNS settings. The container stays open, so your session and anything running in the background remain where you left them.
Update cpak to 2.11.1 and keep using your apps normally. The change is automatic when you switch networks or connect to a VPN.
The connection stays private
An app with the ordinary network permission can reach the
internet and services on your local network. It still cannot reach
services bound only to your computer's localhost. A network change does
not weaken that boundary.
| Manifest | Network boundary | Host localhost |
|---|---|---|
network: false | Private, with no external route | Blocked |
network: true | Private, with internet and LAN access | Blocked |
network: true + hostNetwork: true | Shared with the host | Available |
Most apps should keep network: true. If an app needs a local
development server, bind the server to the machine's LAN address. Add hostNetwork: true only when the app must connect to a service
available exclusively on 127.0.0.1.
Existing packages need no changes
If a package already requests network, it receives the new
behavior as soon as cpak is updated. Package authors do not need to add a
permission or change their manifest.
Packages without network remain offline. The permissions reference explains when to use private networking and when explicit host access
is required.
