Agents

Request Agent Approval Changes

Send the agent back to replan, with a reason. THIS REJECTS THE PROPOSAL.

Not a "hold" and not a comment: the current proposal is rejected ATOMICALLY, and the feedback is stored alongside so the next plan is informed rather than identical. If you want the plan to proceed, use POST /agent/approvals/{approval_id}/decide.

It FAILS CLOSED on both halves. A deployment that does not have this route 404s rather than doing something approximate, and a worker that does not understand the stored feedback still reads the row as a rejection. There is no version of "older software saw this as approval".

Once decided, an approval cannot be decided again - the winner is settled server-side, so a second call gets 409 rather than overwriting.

post/agent/approvals/{approval_id}/request-changes

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/approvals/{approval_id}/request-changes
  • Auth: HTTP bearer

Path parameters

approval_idstring required

Approval id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

feedbackstring required

Why the proposal is wrong, and what to do instead. REQUIRED and not decoration: it is stored on the rejection and is what the next plan is built from, so an empty-handed rejection produces the same plan again.

Response

Successful Response

dataAgentBenchPayload required

An open envelope for one approval answer.

Open because an approval carries the plan digest it is bound to, its expiry and its provenance receipts, and that set has grown twice already. On a human-in-the-loop surface a dropped field is a guarantee the caller does not know they lost.

Changes

No recorded changes to this operation across all 2 revisions of this API.