# IDE 1.3.0: USB, Wi-Fi and network connections

The toolbar's link icon opens **Device connections**. USB and network connections use the same shared Device Core with EV-MUX v4. Firmware must explicitly support v4; v3 is incompatible.

1. Connect the device over USB. Prefer USB-OTG for preview and file transfers.
2. Open **Device connections**, enter the Wi-Fi name and password under **Device Wi-Fi**, then choose **Connect and save**. An empty password selects an open network. Wait for the operation result and device IP. Passwords are cleared from the form and are not saved by the IDE.
3. Disconnect USB in the panel. The device supports a single active owner; disconnect another Agent/IDE session before connecting over the network.
4. On a computer on the same LAN, install the IDE's Node dependencies and build the IDE. Start its local bridge:

   ```sh
   npm run network:bridge -- --device 192.168.1.107
   ```

5. Open `http://127.0.0.1:8766/`, click the toolbar link icon, and choose **Connect network**. The default bridge address is `ws://127.0.0.1:8766/device`. Files, Run/Stop, resets, terminal and preview use the shared DeviceSession through this binary byte transport.

The bridge fixes the device IP at startup and connects to TCP port 3232. It binds only to loopback, accepts one browser connection, and closes TCP when the browser disconnects. It does not acquire a device owner or implement another EV-MUX protocol stack. Wi-Fi operations are sent through Device Core with stable operation IDs, and their final status is read from firmware. Changing/disabling Wi-Fi can close a network connection; reconnect over USB to inspect the final status rather than resubmitting the operation.

To use an IDE served from another origin, explicitly allow its exact origin:

```sh
npm run network:bridge -- --device 192.168.1.107 --origin https://your-ide.example
```

Browser security policies may restrict a hosted HTTPS page from opening an insecure loopback WebSocket or require local-network permission. The IDE served by the local bridge is the supported default. A trusted TLS reverse proxy can expose `wss://` with the exact allowed origin where needed. No Wi-Fi password or device command belongs in the bridge URL.

Use `--port 8767` to change the bridge's listening port, or `--device-port 3232` to change the firmware endpoint port. Update the bridge address in the panel when changing the listening port. The legacy MicroPython WebREPL protocol is separate and cannot connect to this firmware TCP endpoint.