Cloud agents fail instantly - pod not found in backgroundComposerPod kv

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Since about 5:47 PM CT (22:47 UTC) on Oct 29, 2026, every cloud agent launch or follow-up on my account errors immediately with “Agent encountered an error. The agent stopped because of an unexpected error.” The transcript is empty, so the agent fails before setup. This happens on new agents and existing ones, including a trivial read-only test. Clicking “Set Up Cloud Agents” started a setup agent that failed the same way, and saving the environment showed “pod not found in backgroundComposerPod kv”. The status page shows Cloud Agents operational. My usage is at 70% on a unified account, so it isn’t a limit.

Steps to Reproduce

Launch any cloud agent (or send a follow-up to one) on repo wendfold/wendfold from cursor.com/agents.

Expected Behavior

Expected: The agent starts and runs. Agents on this same repo worked normally from 5:00 to 5:34 PM CT (22:00–22:34 UTC) on Oct 29, 2026.

Actual: Since about 5:47 PM CT (22:47 UTC), every launch and follow-up stops at once with “Agent encountered an error. The agent stopped because of an unexpected error,” and the transcript is empty. This includes a trivial read-only test agent. Clicking “Set Up Cloud Agents” started a setup agent that failed the same way, and saving the environment showed “pod not found in backgroundComposerPod kv”.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Grok Bot Version 0.78.1

For AI issues: which model did you use?

Grok 4.7 High Fast (the default shown on the agent page)

For AI issues: add Request ID with privacy disabled

Agent IDs: bc-c8d61e2c-5e06-5045-ba50-fe40021d579b, bc-7e200f24-ee96-5344-8cdf-2369d0da6dc2, bc-8799fdac-0485-5408-9c53-4f617acc6a26, bc-542fc333-30e6-4c89-9e4f-c0c3c76e47a4

Additional Information

The same repo’s agents ran normally from 5:00 to 5:34 PM CT that day, and GitHub status is operational.

Does this stop you from using Cursor

Yes - Cursor is unusable

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

Happens both on iOS and macOS. “Cursor encountered an error.” Retry doesn’t work. Pinging cursor from GitHub PRs wakes it and then causes it to error too.

Steps to Reproduce

Try to message an agent or create a new agent.

Screenshots / Screen Recordings

Operating System

MacOS
iOS

Version Information

iOS cursor 1.10.0
macOS cursor 3.27.23

Does this stop you from using Cursor

Yes - Cursor is unusable

Getting similar, empty repo and existing repo i had an agent midway working on

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud Agents on the web agents page and in the macOS Agents window start, reply once, then stop.

Banner: “Agent encountered an error. The agent stopped because of an unexpected error. Retry or send a follow-up below.”

The transcript shows one or two “Continue executing.” lines, sometimes “Planning next moves”, then the banner. Retry does not finish the run.

Same result on every project tried tonight (IOS APP, Profittevole, MX Shorts start 30 Oct) and on a chat that still shows “Create repo”. Models tried: Grok 4.7 High Fast, Grok 4.7 Low, Grok 4.6 High Fast.

A local editor chat in the same Cursor app still answers.

Time: 30 Oct 2026, about 00:05–00:20 Europe/Rome.
OS: macOS. Also reproduced in Chrome.
Account: Paride Di Lazzaro.
Agent id: bc-19d5b3ba-5dc0-4430-92f8-f32c18be5c4d

At 23:13 UTC the status page still listed Cloud Agents as operational. The only open incident was IDE / VS Code extensions.

Steps to Reproduce

  1. Open the web agents page or the Agents window in Cursor on Mac.
  2. Send “sei operativo?” in a project chat.
  3. The agent replies once, shows “Continue executing.”, then stops with “The agent stopped because of an unexpected error.”

Operating System

MacOS

Version Information

Cursor 3.27.22 on macOS

Does this stop you from using Cursor

Yes - Cursor is unusable

me too

Same things happen for me as well.
It asked to set up the Cloud Environment again. Went to set up but error occurred. Tried to save but error “pod not found in backgroundComposerPod kv” show again.
I’ve been working over phone and browser - Microsoft Edge.
Tried to change the agent model, it it a continuous loop.

I observe the same issue, any cloud agent fails on the environment setup step.
Tried to kick of a new environment setup - that fails too.

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Investigate the cloud agent environment build bld-20261029-4ad2fda5-e40b-40e6-9832-df735ae8cf90. Fetch its build logs with the cursor-cloud environment-build-logs tool (buildId: bld-20261029-4ad2fda5-e40b-40e6-9832-df735ae8cf90), then explain what the build did. If it failed, explain why and recommend fixes to the code or the environment configuration that would address the failure.

Steps to Reproduce

agents stuck with this error

Expected Behavior

it should not error out

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 0.78.1
Built: 2026-10-28T02:34:00.517Z
Release Track: stable
OS: darwin

Does this stop you from using Cursor

Yes - Cursor is unusable

Me too! I need to get some work done, any workarounds?

me too!!

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

e1e0cae1-0b94-4b7f-940b-4fa9258cd780
This run hit an unexpected error. Retry or send a follow-up below.

Steps to Reproduce

I don’t know how. Just let cursor think one question and a few time later, all project couldn’t work.

Operating System

Windows 10/11

Version Information

Version: 3.27.22 (user setup)
VS Code Extension API: 1.128.0
Commit: b1aa50cb6db84fd3e8c808259cb172ea73425c10
Date: 2026-10-27T00:33:02.045Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

compose grok

For AI issues: add Request ID with privacy disabled

e1e0cae1-0b94-4b7f-940b-4fa9258cd780

Does this stop you from using Cursor

Yes - Cursor is unusable

me to…

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

While using the Agent feature in the Cursor IDE (using the Grok 4.7 High Fast model), the run suddenly failed. It was processing a request and showing file changes (9 files changed), and then a red error box appeared at the bottom saying: “Agent encountered an error. This run hit an unexpected error. Retry or send a follow-up below.” Clicking “Retry” does not seem to fix the issue permanently.

Steps to Reproduce

Open Cursor IDE and navigate to the Agent/Chat panel.

Set the model to Grok 4.7 High Fast.

Send a prompt that requires the Agent to modify multiple files (like the 9 files shown in the screenshot).

Wait for the Agent to process and apply the changes.

The Agent abruptly stops and throws the “unexpected error” message.

Expected Behavior

The Agent should complete the run successfully, apply the code changes, and provide a summary response without throwing an internal system error.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Cursor IDE 0.45.0 (Windows x64)

For AI issues: which model did you use?

Grok 4.7 High Fast

Additional Information

I am working on a project and asked the Agent to modify several files (as shown in the screenshot, 9 files changed). After it finished generating the code, the red error box appeared. Clicking ‘Retry’ sometimes works, but the error keeps happening randomly.

Does this stop you from using Cursor

Yes - Cursor is unusable

Version: 3.27.22 (user setup)
VS Code Extension API: 1.128.0
Commit: b1aa50cb6db84fd3e8c808259cb172ea73425c10
Date: 2026-10-27T00:33:02.045Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26300

same issue

same

same issue

the same

my issue is on windows not IOS

same