Skip to content

Downloads

Where to find the installer, CLI binaries, and the VS Code extension.

On /downloads you will find all current distributions for your subscription. The page shows the latest Stable release plus a list of older releases; each older release has its own page at /downloads/v{version}.

What is available

Artifact Purpose
Windows Installer (.exe) Devs on Windows, everything in one setup
CLI Windows x64 (ZIP) CI runners on Windows
CLI Linux x64 (tar.gz) CI runners on Linux, Docker
CLI macOS x64 (tar.gz) Devs on older Macs (Intel)
CLI macOS arm64 (tar.gz) Devs on Apple Silicon
VS Code Extension (VSIX) Editor integration

All artifacts are released together, so you always get one consistent version number across all platforms per release.

Via the UI vs. via the API

In the portal you click the artifact and it downloads. The session cookie handles auth. For each CLI archive and the installer you can choose between two variants: with license (your codecharter.license file is embedded in the archive) and without license (the plain archive). The VSIX is always delivered plain. You can also download your license on its own as a codecharter.license file via the button at the top of the page; this requires an active subscription.

Note for the with license variant: the licensed archive is built once per user and asset and may then be served from a per-user cache for up to 30 days, so the embedded license can be one that was issued up to 30 days earlier. If you need a freshly issued license — for example right after a subscription renewal — use the standalone codecharter.license download, which always mints a new license.

Via the API for automated pulls (CI):

curl -L -H "Authorization: Bearer $CODECHARTER_API_KEY" \
    -o codecharter-cli.tar.gz \
    https://codecharter.tools/api/v1/cli/linux-x64/latest

API downloads always deliver the plain archive without an embedded license. CI fetches a short-lived license separately via GET /api/v1/cli/license, authenticated with the same API key.

Every download response carries an X-CodeCharter-Sha256 header so you can verify the checksum of the file you received.

More details at Managing API keys.

Latest vs. a specific version

In the URL you can use latest, a full version number, or a version prefix — 1, 1.4, and 1.4.2 all work, with or without a leading v. The newest release matching the prefix wins:

https://codecharter.tools/api/v1/cli/linux-x64/latest
https://codecharter.tools/api/v1/cli/linux-x64/1.0.12

Recommendation for CI: always pin. latest is fine for local tests or devs who always want the newest version.

See Versioning.

Channels

All downloads come from the Stable channel; every release published there has been vetted.

More at Channels.

When a download fails

  • 400 Bad Request: unknown platform slug. Valid values are win-x64, linux-x64, osx-x64, and osx-arm64.
  • 401 Unauthorized: API key is missing or incorrect.
  • 402 Payment Required: your subscription has expired (API downloads). Renew it in the portal.
  • 403 Forbidden: returned by portal (cookie-based) downloads when your subscription is not active.
  • 404 Not Found: no release matches the requested version. Compare with the release channel log.
  • Timeouts: should not occur given current file sizes. If they do, drop us a note and we will investigate on our end.