Treating Agent Runs as Review Packets: A Practical Pattern for Claude Code & Codex

A Reddit user experimenting with Codex/Claude-style agent workflows shares a pattern that improved their results: instead of treating agent runs as chat transcripts, they now produce a durable folder with multiple artifacts that another human or agent can inspect.

Key artifacts per run

• research.md — sources and assumptions used by the agent
• drafts.md — candidate outputs, including rejected ones
• evals.md — scoring rubric and reasoning for the chosen option
• approval-packet.md — checkpoint before the irreversible step
• metrics.json — numeric outcomes of the run
• memory.md — reusable workflow lessons only

Two big lessons

Memory should be about how to work, not an unreviewed fact database. If a claim matters, it belongs in a reviewed artifact with a source.

“Fully autonomous” is less useful than “autonomous until the irreversible step.” For code that means commit/deploy. For content that means publish. For local workflows it means anything touching credentials or third-party accounts.

Why this helps

Failures become visible at specific stages: Was the research wrong? Was the draft bad? Was the eval rubric too vague? Did the approval packet miss a risk? Did memory store a lesson that actually helped next time? This makes iteration faster and more targeted than relying on chat transcripts.

The post is a discussion starter — the author is curious if others are using durable artifacts or trusting chat transcripts for Claude Code/Codex workflows.