Use this page when Coder Studio does not start, cannot reach a provider, or cannot be opened from another device.
If the first trial does not work, check in this order:
node --versionconfirms Node.js >= 24.0.0.coder-studio versionconfirms the CLI is installed.coder-studio statusconfirms the service is running.coder-studio logsshows recent errors.which <provider-command>confirms the Provider CLI is in PATH.<provider-command> --versionconfirms the Provider CLI can run.- If the browser does not open, manually visit the URL from
coder-studio status. - If mobile cannot connect, confirm the service listens on
0.0.0.0and your firewall allows the port.
Use desktop for the first full trial. Do not start by debugging public tunnels and phone access at the same time.
Check status and logs:
coder-studio status
coder-studio logsTry foreground mode for a direct error:
coder-studio serve --foregroundRun:
coder-studio statusOpen the displayed URL manually.
Change the port and restart:
coder-studio config --port 8080
coder-studio serve --restartCoder Studio can open files and terminals without an AI CLI, but agent sessions require their matching provider CLIs.
Install the provider CLI, confirm it works in a normal terminal, then start a new session in Coder Studio.
Common causes:
- Phone and computer are not on the same network.
- Wi-Fi guest isolation blocks device-to-device access.
- The computer firewall blocks the port.
- Coder Studio is listening only on
localhost. - VPN, company network, or campus network blocks local device discovery.
For LAN access:
coder-studio config --host 0.0.0.0
coder-studio serve --restart
coder-studio statusThen open:
http://<computer-lan-ip>:<port>
Reset the password:
coder-studio config --password <new-strong-password>
coder-studio serve --restartIf an IP is blocked after repeated failed attempts:
coder-studio auth ban-list
coder-studio auth unblock --ip <ip-address>Try:
- Refreshing the browser.
- Checking
coder-studio status. - Checking
coder-studio logs. - Confirming the tunnel or network route is still active.
- Restarting the service with
coder-studio serve --restart.
Collect:
coder-studio status- Relevant
coder-studio logs - Browser URL used
- Operating system
- Node.js version
- Whether the issue happens locally, on LAN, or through a tunnel