Menu

INVALID_COCKPIT_CONFIG

HTTP 400

Something about the request must change

Cockpit settings exceed their bounded track, view, name, color, or lifecycle constraints.

How to fix it (contract guidance)

Use at most six approved-color custom tracks and eight saved lifecycle views.

Observed recovery

Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.

Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.

If you are an agent

The same facts, structured. Do not infer the fix from the prose above — use this.

{
  "code": "INVALID_COCKPIT_CONFIG",
  "httpStatus": 400,
  "meaning": "Cockpit settings exceed their bounded track, view, name, color, or lifecycle constraints.",
  "fix": "Use at most six approved-color custom tracks and eight saved lifecycle views.",
  "example": null,
  "emittedBy": [],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "INVALID_COCKPIT_CONFIG",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 400 errors

Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.