Submit Changeset
Instructions
Submit Changeset
Store a changeset as a proposal for human review instead of applying it.
POST
Submit Changeset
Stores a changeset as a
SUBMITTED proposal for review instead of applying it — the write path for agents without direct-write authority. The proposal is validated on submission; an invalid one returns 409 with structured conflicts and is not stored.
Requirements: instructions:propose + workspace EDITOR or OWNER access.
Request
The shared changeset body (see validate). Supports theIdempotency-Key header — the replay check runs before planning, so replays are cheap and exact.
Response
Returns201 when stored, 409 when validation failed.
object | null
The stored record:
{id, workspaceId, status: "SUBMITTED", description, authorKind, operationCount, createdAt, decidedAt, decisionNote, appliedManualRevisions}.object[]
Structured validation conflicts when rejected at submission.
string | null
In-app review link for human reviewers.