Guide contents

versioning_project_history

Purpose and availability

Read paged recorded project history across branches, with names, heads and named versions. No editor switch or engineering approval.

Before invocation

Inspect the current definition and exact version/project binding before invoking. Required fields, enums, bounds and consent fields below are authoritative. Omit no required input and do not invent unavailable values.

Exact input schema

{
  "additionalProperties": false,
  "properties": {
    "cursor": {
      "type": [
        "string",
        "null"
      ]
    },
    "include_archived": {
      "type": "boolean"
    },
    "include_checkpoints": {
      "type": "boolean"
    },
    "limit": {
      "maximum": 100,
      "minimum": 1,
      "type": "integer"
    },
    "query": {
      "maxLength": 120,
      "type": "string"
    }
  },
  "required": [],
  "type": "object"
}

Results, errors and safety

Inspect the structured result and retained IDs/artifacts. Errors, unsupported profiles, missing data and cancellation remain explicit. A successful call grants no human engineering approval. Do not retry inference automatically. See Workflows, History and Project tools.