Skip to main content

Approvals and change sets

When Copilot proposes writes, the chat shows a change set with tool names and arguments. Nothing applies until you approve.

Lifecycle​

  1. Copilot returns explanation text plus optional tool proposals.
  2. You review the proposal (arguments are shown in the card).
  3. Approve runs validated tools through editor sagas / APIs.
  4. Reject discards the proposal with no writes.

Execute and destructive tools may require an extra per-action approval.

Tips​

  • Prefer @Entity mentions so Copilot receives source context instead of asking you to paste code.
  • For query fixes, expect update_action proposals rather than code-only replies.
  • Greenfield “build an app” flows propose create_application first; approve to create and open the editor.