Get set up

Network and firewall

The public hosts EasyCode, the desktop app and your harnesses reach, so they work behind a firewall or proxy.

Last updated November 16, 2026View as Markdown

EasyCode itself only makes outbound connections on port 443: HTTPS, and secure WebSockets (wss://) for live co-editing. Nothing on your machine has to accept connections from outside. Allow the hosts below on your firewall or proxy.

EasyCode

HostWhat uses itWhy
app.easycode.studioBrowser, desktop appThe web app, sign-in, the API the desktop app and its runner talk to, and the desktop update feed
downloads.easycode.studioDesktop appInstallers and update files
relay.easycode.studioBrowser, desktop appLive co-editing of documents, library drafts and studio boards, over a secure WebSocket
*.easycode.runBrowser, desktop appStudio artifacts and shared pages. Code you didn't write runs here, never on easycode.studio
easycode.studioBrowserThe public site and the changelog
docs.easycode.studioBrowserThese docs

A host on easycode.run looks like a-… or m-… followed by an ID, so allow the whole *.easycode.run wildcard.

Your proxy must let secure WebSockets through to relay.easycode.studio: allow the upgrade from HTTPS and keep the connection open. If it doesn't, live editors can't connect.

Signing in

You sign in to EasyCode with one of these. Allow the ones your team uses:

HostFor
accounts.google.comSign in with Google
login.microsoftonline.comSign in with Microsoft
github.comSign in with GitHub

Email sign-in needs no extra host: the link arrives in your inbox.

GitHub

Your sessions clone, push and open pull requests with your own git and gh, and admins install the EasyCode GitHub App on GitHub. Allow:

  • github.com for git, sign-in and the App's install pages
  • api.github.com for gh and pull requests

If your git remotes use SSH, git also needs port 22 to github.com.

Your harnesses

Each harness talks to its own vendor on your own login. EasyCode adds no host of its own to that traffic. Allow what your vendor documents for the harnesses your team uses; each harness page links to its documentation.

Installing and updating a harness also needs its installer's host:

claude.ai (the install script)

Optional hosts

These make the app better, and it still works without them:

HostWhat it doesIf you block it
raw.githubusercontent.comThe runner refreshes model prices for usage costsCosts use the prices built into the app
api-eu.mixpanel.comProduct analytics, only if you agreed to themNo analytics are sent
*.de.sentry.ioError reports, in Sentry's EU regionErrors aren't reported to EasyCode
mcp.linear.app, mcp.atlassian.comThe Linear and Atlassian MCP servers, if you connect themYour harness can't read tickets

The desktop app's built-in browser opens whatever sites you test, and searches from its address bar with duckduckgo.com.

On your own machine

The runner listens on 127.0.0.1 only and checks every request's host and origin. It is never reachable from another machine, so you don't open any inbound port. If a local firewall asks whether EasyCode may accept incoming connections, you can deny it.

Behind a TLS-inspecting proxy

If your proxy re-signs HTTPS traffic, your harnesses and git need its certificate too. Set it up as each vendor's documentation describes.

Next

Something wrong or missing? Suggest a change

On this page