← Series

Agent Operating Notes
Short operating notes from redacted Claude and Codex sessions: boundaries, prompts, failure modes, and team practices for AI-assisted engineering.
Part 14 minPart 24 minPart 34 minPart 44 minPart 54 minPart 64 minPart 74 minPart 84 minPart 94 minPart 104 min
Restart AI Coding Sessions When Context Stops Being Verifiable
Restart an AI coding session when context stops being verifiable. Use a checkpoint that preserves facts, uncertainty, and the next safe probe.
Before an AI Agent Asks a Question, Make It Search
Use AI agent context gathering to reduce avoidable team interruptions. Separate cheap lookups from decisions that genuinely need a human.
Make Agent Integration Failures Explicit Before Asking Humans
Classify AI agent integration errors before asking humans for context. Preserve missing input, unavailable capability, denied access, and stale sources.
Define AI Agent Work as Verifiable Execution Slices
Use AI agent task decomposition built around one outcome, changed surface, proof path, rollback, and stop condition instead of arbitrary small tasks.
Turn Painful Agent Runs Into Evaluated Skills
Build AI agent skills from hard-won runs by extracting invariants, bounding authority, and testing new cases instead of saving an unverified prompt.
Give AI Agents Permissions by Intent, Not Identity
Scope AI agent permissions to inspect, plan, patch, deploy, or verify. Review authority transitions instead of granting broad access by assistant identity.
Build a Provenance Ledger for AI Agent Research
Use an AI agent provenance ledger to separate observed, inferred, contested, and unsupported claims before research drives engineering decisions.
Use Reversible Rollouts for AI Agents in Production
Run an AI agent production rollout through observe, prepare, shadow, limited, and general stages with evidence, thresholds, and executable rollback.
Monitor Long-Running AI Agent Work Without State Drift
Design AI agent monitoring as a read-only delta heartbeat with stable evidence, idempotent checkpoints, anomaly thresholds, and terminal conditions.
What a Genuinely Blocked AI Agent Should Report
Use an AI agent blocker report to stop equivalent retries, preserve completed evidence, identify the failed dependency, and name the smallest unblock.