On /downloads you will find all current distributions for your subscription.
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 (ZIP) | CI runners on Linux, Docker |
| CLI macOS x64 (ZIP) | Devs on older Macs (Intel) |
| CLI macOS arm64 (ZIP) | Devs on Apple Silicon |
| VS Code Extension (VSIX) | Editor integration |
All artifacts are released under the same release, so you always get a consistent version per day.
Via the UI vs. via the API
In the portal you click the artifact and it downloads. The session cookie handles auth.
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
More details at Managing API keys.
Latest vs. a specific version
In the URL you can use either latest or a specific version number:
https://codecharter.tools/api/v1/cli/linux-x64/latest
https://codecharter.tools/api/v1/cli/linux-x64/1.4.0
Recommendation for CI: always pin. latest is fine for local tests or
devs who always want the newest version.
See Versioning.
Channels
We publish two channels:
- Stable for vetted releases — what you get by default.
- Edge for early pre-release versions, intended for internal builds and early adopters.
More at Channels.
Download log
Every download is logged in the portal audit: date, artifact, version, and whether it came via UI or API. You can see your own log; admins see the log for all users in the organisation.
Personal data in the logs is removed when an account is deleted (see Privacy and GDPR).
When a download fails
- 401 Unauthorized: API key is missing or incorrect.
- 403 Forbidden: API key is fine, but your subscription has expired or
the variant (
win-x64, etc.) does not exist for that version. - 404 Not Found: wrong version number or wrong platform slug. 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.