Multitasking doesnt work with AWS bedrock models

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

All day im getting error messages that say:

Error resuming chat
Failed to resume after background task completed: Al Model Not Found Model name is not valid:
“eu.anthropic.claude-opus-4-6-v1” Request ID: 36a4ca44-cf71-4880-a628-0775b7dc2a30

it makes it really hard to work

Steps to Reproduce

Enable AWS bedrock and spawn any background agent → it fails once it finishes

Expected Behavior

It should automatically resume

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z (1 day ago)
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

eu.anthropic.claude-opus-4-6-v1

For AI issues: add Request ID with privacy disabled

36a4ca44-cf71-4880-a628-0775b7dc2a30

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report with the request ID and version. This is a known bug. When resuming a sub-agent after a background task on BYOK AWS Bedrock, Cursor sends the raw Bedrock model ID like eu.anthropic.claude-opus-4-6-v1, and the backend rejects it because validation only allows names from the Cursor catalog.

We’re already tracking this bug. I can’t share an exact ETA for a fix yet. Once we have an update, we’ll post it in this thread.

Unfortunately, there isn’t a clean workaround right now. The BYOK Bedrock model picker only shows Bedrock names, and the catalog names won’t work when BYOK is enabled. If you can temporarily work without sub-agents, the normal single-agent flow on the same Bedrock model should work fine, and that’s the fastest way to avoid this error for now.

If you hit any other symptoms, please share new request IDs here. It really helps with debugging.

it still makes it super hard :slight_smile: any ETA on this?

Hey, unfortunately I can’t share an exact ETA yet. The bug is being tracked and is a high priority, but I don’t have a specific fix date. As soon as I have an update, I’ll reply in this thread.

I get that the workaround with a single agent and no sub-agents isn’t a real replacement, but for now it’s the most reliable way to get around the issue on BYOK Bedrock.

Hi there!

This will be fixed in 3.3, which is right around the corner. :slight_smile: