‘Agent encountered an error' Issue

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud Agents failing since Jul 23 — empty Environment error, then ‘Agent encountered an error’ - can’t reach execution environment

Steps to Reproduce

Open cursor.com/agents (signed in).
Create a new Cloud Agent against:
Repo: Git
Branch: main
Use a minimal prompt, e.g.:
echo “test”
or Run node -v and paste stdout. Do not edit files.
Start the agent and watch the run timeline.

Operating System

Windows 10/11

Version Information

Cursor IDE: 3.12.30 (Windows)
Primary surface: Web — cursor agents (Cloud Agents)
Also affected: cursor automations
OS: Windows 10 (build 26200)

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @NehaSharma ,

This isn’t a Cursor-side outage. It traces back to the new custom environment your team set up on Jul 23. Cloud Agents clone your repository inside your environment’s image, and it looks like the new image doesn’t have git available on its PATH. So every run fails right at the clone step, before the agent even reaches your prompt (which is why even a minimal echo "test" / node -v run errors out). Right now that failure surfaces as the generic “Agent encountered an error” instead of telling you the clone failed - that’s not helpful, and making these clone failures show the real cause is on our radar.

Two ways to fix it:

  1. Unblock now: switch back to your previous environment (the one that was working through Jul 23). That should get the whole team running again immediately.
  2. Fix the new image: add git (and ca-certificates) to your custom Dockerfile, then rebuild/re-save the environment:

RUN apt-get update && apt-get install -y git ca-certificates

(If your base image is Alpine, use RUN apk add --no-cache git ca-certificates instead.)

Since your automations dispatch into the same environment, fixing the image clears those too.

Setup reference: Cloud Environment Setup.

If you rebuild with git in place and still hit the error, reply here with a fresh run link and I’ll dig into that specific run.

7

Thanks Mohit. It worked!