`NO_WORKSPACE_TO_CLAIM`

HTTP 409

Something about the request must change

A device-grant login poll presented no anonymous board and its approved account owns no workspace, so there is nothing to bind an account token to.

How to fix it (contract guidance)

Provision a board first (run 'pullboard init' to create an anonymous board, then 'pullboard login' to claim it), or claim a board in the browser before logging in.

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": "NO_WORKSPACE_TO_CLAIM",
  "httpStatus": 409,
  "meaning": "A device-grant login poll presented no anonymous board and its approved account owns no workspace, so there is nothing to bind an account token to.",
  "fix": "Provision a board first (run 'pullboard init' to create an anonymous board, then 'pullboard login' to claim it), or claim a board in the browser before logging in.",
  "example": null,
  "emittedBy": [],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "NO_WORKSPACE_TO_CLAIM",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 409 errors

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