plan_rebase
Preview a rebase of a task's branch onto its base branch without moving anything: what would be replayed, dropped and flattened, and which paths may conflict.
writesidempotentMCP toolAgent
Calling it#
curl -X POST http://127.0.0.1:8787/komrad.agent.v1.AgentService/PlanRebase \
-H 'Content-Type: application/json' \
-d '{
"task_id": "<task_id>"
}'komrad rpc plan-rebase \
--task-id '<uuid>'{
"name": "plan_rebase",
"arguments": {
"task_id": "<task_id>"
}
}Offered by the komrad MCP server to orchestrator agents.
Request#
PlanRebaseRequest#
PlanRebaseRequest asks what a rebase of a task's branch would do, without doing it.
Response#
PlanRebaseResponse#
| Field | Type | Description |
|---|---|---|
base_ref | string | The ref the branch would move onto. |
base_sha | string | The commit |
commits | int32 | How many commits the branch has that the base branch does not. |
branch | string | The branch that would move. |
landed_commits | int32 | How many of the branch's commits have landed. The rebase would drop them. |
replay_commits | int32 | How many of the branch's commits the rebase would replay. |
merges | int32 | How many merge commits the rebase would flatten. |
conflict_paths | string[] | The paths a merge of the base branch would conflict on. A rebase can conflict where a merge does not, so this is a warning only. |