Preview · agent deploys
Approve an agent's deploy once. It runs again only while the ticket holds.
A person approves a supported agent deploy against the company's change ticket. FieldHash reuses that approval while the deploy matches its reviewed inputs and the ticket conditions it relies on remain valid.
The company's records and authorized reviewers set what the agent may do. FieldHash checks that authority at the connected action as the work changes. Cancel a ticket or change a condition the approval relied on, and the affected approval returns to review, with a signed record of why.
PDF · 120 KB
A live run of Claude Code with the FieldHash plugin against a local FieldHash server, replayed from its transcript with the messages shortened and the timing compressed. kubectl is a stand-in, so nothing reached a cluster. The results at the end come from the scripted side-by-side tests below, which are separate from this run.
What happens in the video
- Two change tickets are approved: CHG-412 for the web deploy, CHG-418 for the worker.
- The agent runs both deploys. Each goes to a person first, and neither runs.
- A reviewer approves each one, naming the ticket it relies on.
- The agent runs the same deploys again. Both approvals are reused.
- CHG-412 moves to in progress. Nothing the approval relies on changed, so the next re-apply runs.
- The agent edits the web manifest. That is a different deploy, so it goes to a person.
- The agent puts the manifest back exactly as approved. The original approval applies again.
- The change manager cancels CHG-412. The web deploy goes back to a person; the worker deploy keeps running.
- Every decision has a signed receipt that verifies offline.
- The side-by-side results: right answers out of 190 for each approach, and the custom check code each one needed.
What this preview covers
This page demonstrates supported kubectl apply calls through the FieldHash hook. Approval reuse binds selected deploy inputs, not the complete cluster effect. Enforcement depends on the agent tool running the hook for every covered call. Change-bound approvals are built and tested, off by default, and not yet released.