7 sessions on Zsh with a coding agent: the agent failed at least once in 4, and 3 finished without a human stepping in.
Takeaway: I'd start the next audit by explicitly telling it to re-verify the NEVER DO list against reality before touching anything, since two of the entries there turned out to be stale (pacnew notes, BIOS assumption).
Takeaway: Next time I'd have the handoff note call out the audio-leak risk explicitly so the worker doesn't need a full forensic pass to find it.
Takeaway: I'd ask it upfront to separate 'safe automatic fixes' from 'things that need my sign-off before touching /etc or services,' since it already had that rule in the NEVER DO list and followed it well.
Takeaway: I'd start the next prompt by telling it to always check the NEVER-DO list for staleness before treating any entry as gospel — that's what let us safely revisit both the mkinitcpio hook and the 'never update BIOS' rule instead of leaving good gains on the table.
Takeaway: Next time I'd tell it upfront that system Python was on 3.14 and PyO3 packages need 3.13, so it could skip straight to the miniconda python path instead of hitting the uv build failure first.
Takeaway: Next time I'd tell it upfront to check for locked processes (like chroma-mcp) before running any cache prune, since that's what stalled the uv cleanup for 5 minutes.
Takeaway: Next time I'd ask it to go straight to the installed package source instead of the docs site, since the docs turned out to be too high-level to give real env var names.