Get set up

The desktop app

Install the desktop app on macOS, Windows or Linux, sign in, keep it updated, and open a build marked Unsigned.

Last updated November 15, 2026View as Markdown

The desktop app is where your sessions run. It drives your harnesses on your machine, on your own logins, and signs you in to your org. Use it to start and pick up sessions, scan repos for your org and test in the built-in browser.

Download the app

Open Download EasyCode: in the web app, click Get the desktop app at the bottom of the left rail. The page offers the build for your system first and lists the others under Other builds. Each build shows its version and size, and its SHA-512 hash in a disclosure, so you can check the file by hand.

On a Mac, the page may not know which chip you have. It then offers the other build too: On an Intel Mac? or On a Mac with Apple silicon?

Install it

Download the .dmg, open it and drag EasyCode to Applications. Then open EasyCode from Applications.

There are builds for Apple silicon and for Intel Macs.

Open a build marked Unsigned

Some builds are not yet signed by the OS vendor. The download page marks them Unsigned, Unsigned preview, Unsigned beta or Unsigned alpha. Your system warns the first time you open one.

macOS blocks the app the first time. Open System Settings → Privacy & Security and click Open Anyway.

Sign in

The app asks you to sign in before it shows your org's pages. Your machine's pages and your Personal space work without signing in.

Start in the app

Click Sign in with your browser. The app shows a code and waits.

Approve in your browser

Your browser opens on Sign in a device?. Check that it shows the same code as the app. Approve only if the code is on your screen right now. Type its last four characters in the field, then click Approve.

Return to the app

The app finishes signing in on its own and opens your org.

The app keeps your sign-in in your system's keychain or keyring. Settings → Desktop shows this machine's version, device name and data folder, and has Sign out.

What runs on your machine

The app starts two parts on your machine, each on its own port on your computer's loopback address:

  • The runner runs your harnesses, terminals and sessions. It is what reads your repos and your harness's own logs.
  • The app's pages, which the app's window shows.

Your harness logins and your working tree stay on your machine. What an org session shares is listed in Security and privacy.

The app also lives in your menu bar or system tray. Its menu has Open EasyCode, New session, your recent sessions, Settings…, Check for updates, Start at login and Quit.

Keep it updated

The app checks for updates when it starts and every four hours. It downloads a new build in the background.

  • A signed update installs when no session is running, or when you quit. Settings → Desktop shows Restart to update once it is ready.
  • A build the app can't install by itself, such as an unsigned one, shows a banner with Download and install. The app checks the download before it hands it to your system. On a Mac, drag EasyCode to Applications to replace it, then reopen it.
  • Check for updates in Settings → Desktop or the tray menu checks right away.

When your org needs a newer version, the banner says EasyCode version is required, sometimes from a date. After that date, org pages, sync and org tools pause until you update. Sessions on your machine keep running. Finish your org sessions before then.

Turn updates off for a fleet

An IT team can turn update checks off with a policy file. Put {"autoUpdate": false} in:

/Library/Application Support/EasyCode/policy.json

Settings → Desktop then says Turned off by your organization. A policy file the app can't read also turns updates off.

Next

Something wrong or missing? Suggest a change

On this page