ADCode installs from one command. This page is the whole of it: what the command does, where things land, and how to look after the editor afterwards.

The command

Linux

curl -fsSL https://adcode.bluethenics.com/install.sh | sh

Windows, in PowerShell

irm https://adcode.bluethenics.com/install.ps1 | iex

macOS is not published yet. Signing and notarising a macOS build needs a paid Apple Developer membership, and an un-notarised app is not merely warned about - macOS refuses to open it. Rather than hand you a file your machine will reject, the installer says so and stops.

Why the terminal is the better route today

ADCode's installers are not code-signed yet, and on Windows that would normally mean the "Windows protected your PC" dialog, which hides the Run button behind More info.

That dialog fires on the Mark of the Web - a zone tag Windows attaches to files a *browser* downloaded. A file fetched by Invoke-WebRequest does not carry it, and ADCode installs per-user, so it asks for no administrator prompt either. The terminal install is not a way around a warning; it is the route that does not produce one.

What the script actually does

Worth knowing, because you are piping it into a shell:

Asks GitHub for the latest release.
Picks the artifact for your platform - a .deb where dpkg exists, an AppImage otherwise.
Downloads it into a private temporary directory.
Verifies it against the checksum published with the release. A tampered mirror or a truncated download is caught before anything runs.
Installs it, and prints what to do next.

If the checksum does not match, nothing is installed and the file is deleted.

Where it lands

Debian and Ubuntu - an ordinary package, with adcode on your PATH.
Other Linux - the AppImage goes to ~/.local/bin/adcode. If that is not on your PATH the script says so, and how to add it.
Windows - a per-user install, in the Start menu and on your PATH as adcode.

Using it

adcode opens the editor.
adcode open . opens it on the current folder.
adcode help lists every command.

The editor's Help menu has a Feature Guide listing every feature with what it is for and how to reach it. That is the fastest way to find something you suspect exists.

Updating

ADCode updates itself. New versions download quietly and apply the next time you start it - it will not restart itself and will not interrupt you to ask.

To update by hand, run the install command again. To stop automatic updates, turn them off in Settings, Updates.

Removing it

Debian and Ubuntu - sudo apt remove adcode
AppImage - rm ~/.local/bin/adcode
Windows - Settings, Apps, Installed apps, ADCode

Options the scripts honour

Set these before running if you need to point the installer elsewhere:

ADCODE_SITE - the site the script names in its messages.
ADCODE_GH_OWNER and ADCODE_GH_REPO - the repository releases are fetched from.

If something goes wrong

"is not on your PATH" - the AppImage installed correctly and your shell cannot find it. Add ~/.local/bin to your PATH, or run it by full path.

dpkg reports missing dependencies - the script already runs apt-get install -f to resolve them. If it still fails, use the AppImage from the downloads page instead.

The checksum did not match - nothing was installed, and this is worth telling us about at support. It means the file you received was not the file that was published.

No release for your platform - check what is published. Linux arm64 has no build yet.

One thing to know about ads

ADCode shows an occasional sponsored card while you work, and credits you half of what it pays. That is how a complete IDE is free.

You can turn ads off entirely in Settings, Ads and Earnings, and the editor stays complete - nothing is withheld behind them.