Inaccurate OpenAPI spec for Cloud Agent errors

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

The OpenAPI spec for Cloud Agents defines an error as:


    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            message:
              type: string
              description: Human-readable error message
            code:
              type: string
              description: Machine-readable error code

The actual returned response from a failed api call /v0/agents in my case is:

2026-02-10 08:34:46 [error]: {
  error: { error: 'Failed to determine repository default branch' },
  ....
}

The response and or spec should be updated to be consistent with one another.

Steps to Reproduce

Call POST /v0/agents with something to trigger a 400 error (e.g. invalid repo name) and observe the response’s structure.

Expected Behavior

The spec should match the real world behavior.

Operating System

MacOS

Version Information

Version: 2.4.28 (Universal)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. The error response schema in the OpenAPI spec really doesn’t match what the API actually returns. It returns error.error (a string) instead of the documented error.message / error.code structure.

I’ve passed this to the team to fix. We’ll either make the actual response match the spec, or update the spec to match reality.

Let me know if you run into any other API mismatches.

1 Like