This effectively makes the CLI unusable and untrustworthy in a CI environment if it can stop working so abruptly (ie. for the same kind of things you would use claude code for to create automatons in transient environments in reaction to triggers/events)
We should be able to pin a version of the CLI for installation, and not rely on this method, which can shut down pipelines and automations overnight. IMHO this should be a hard requirement for any CLI.
curl -L Cursor · CLI | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
Cursor Agent Installer
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
✗ Download failed. Please check your internet connection and try again.
✗ If the problem persists, the package might not be available for linux/x64.
the cursor CLI installation for the latest version (2026.03.24-933d5a6) is failing as the download fails for the installation artifact.
I have tried downloading it for linux/arm64 and linux/x64 architectures.
please note: I was able to download and install the previous versions like 2026.02.27-e7d2ef6 (with the same Dockerfile).
Is cursor not supported for certain architectures now?
or Am I doing something wrong?
I would really appreciate any kind of support.
Thanks
here is my Dockerfile for the reference:
FROM python:3.11-slim as builder
WORKDIR /app
COPY pyproject.toml .
RUN pip install --no-cache-dir --upgrade pip &&
pip install --no-cache-dir build &&
pip install --no-cache-dir .
FROM python:3.11-slim
WORKDIR /app
RUN apt-get update && apt-get install -y
git
curl
vim
jq
&& rm -rf /var/lib/apt/lists/*
Hey there, this is a known issue – the CLI package for version 2026.03.24-933d5a6 isn’t available on our CDN right now, which is why the versions directory ends up empty. The installer unfortunately doesn’t surface the download failure properly on Mac (shows green checkmarks despite the download failing silently).
Our infrastructure team is working to publish the artifact. If you have a previously cached CLI version at ~/.local/share/cursor-agent/versions/, you can point your symlink there as a temporary workaround. Will follow up when the fix is deployed.