Topic archive
70 essays tagged Claude Code. Practical notes on what happens after the demo: prompts, tools, review packets, evals, rollback, and production ownership.
Claude Code permissions matter before the run, but teams also need permission receipts after the run: what the agent used, what was blocked, what still needs approval, and how to undo it.
The safer question for Claude Code and enterprise agents is not how much autonomy the model can handle. It is which privilege the work deserves, how long it lasts, and what evidence the human gets back.
AI agent teams often ask whether the demo worked. Buyers, auditors, and production owners ask a harder question: can we trust the run when authority, evidence, and rollback are visible?
A Claude Code diff shows the changed lines. A review packet shows the delegated intent, scope, checks, risks, and rollback path a human needs before merge.
Claude Code review packets and enterprise agent security are often treated as separate problems. They are two parts of the same operating stack: evidence for the work, boundaries for the authority.
Teams keep asking whether an AI agent is ready for more autonomy. A better question is whether the review path is clear enough before the next permission is added.
A good prompt can shape agent behavior, but production teams need a control plane around identity, tool scope, approval, logs, revocation, and review.
Production AI agents need a fast way to stop action and a plain receipt after every meaningful run. Without both, autonomy becomes trust without evidence.
A clean Claude Code diff is a weak production signal. Ask for a review packet with scope, tests, gaps, rollback, and human inspection notes before merge.
Agent permissions that helped a pilot can become hidden production authority. Put expiry, renewal evidence, and removal paths around AI agents before access drifts.