Skip to main content

Accept or reject a proposal

A Copilot proposal is a draft until you act on it. Accepting applies the change to a draft on the target surface; it does not publish. Rejecting discards it.

Step 1 — Review the diff

Open the proposal. Read the before/after state, the rationale, the warnings, and the expected cost. If anything looks wrong, do not accept.

Step 2 — Accept or reject

  • Accept — the change is applied to a draft on the target surface (for example, a new prompt draft). You still review and publish that draft through the normal workflow.
  • Reject — the proposal is discarded. The decision and rationale are recorded.
Acceptance re-checks your current authority. If you lost permission between the proposal being generated and you accepting it, the accept fails safely.

Step 3 — Finish the protected transition

Accepting a proposal does not publish. Go to the target surface, review the draft, and complete the normal review and publish steps there.

Common outcomes

Up next

When the change is ready, deploy an artifact.