Skip to main content
POST
Preview Agent Branch Rebase

Overview

Dry-runs a three-way merge of the branch onto dev’s current head and reports what a rebase would bring in from dev (changes) and where dev and the branch changed the same value differently (conflicts). This is a POST but it writes nothing and takes no body. Call it after Merge Agent Branch returns 409 BRANCH_BEHIND, then pass the returned dev_head_version_id and a resolution for every conflict to Rebase Agent Branch. Requires an admin, owner, operator, or prompter role.

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
The agent’s unique identifier.
string
required
The branch’s unique identifier. Must be an open branch on this agent.

Response

string | null
The dev version the preview ran against. Pass this unchanged to Rebase Agent Branch. null when the agent has no dev versions.
boolean
true when the branch’s base is already dev’s head (or the agent has no dev versions), so there is nothing to rebase and a merge would fast-forward. changes and conflicts are empty in that case.
integer
Number of entries in changes.
array
Dev-side edits the branch did not touch. They merge in automatically on rebase; nothing is required from you.
array
Values changed differently on both sides. Each needs a resolution before the rebase succeeds; key your resolutions map by the conflict’s id.
null | array
null on success, or a list of error objects if the request failed.

Docs for agents: llms.txt