Codex Users Are Sealing Unfinished Projects in Evidence Bags

The first bags appeared after a Codex session stopped halfway through a project and left its users with no reliable way to resume the exact conversation. Subscribers began printing the last accepted change, the unaccepted request and a note identifying which part of the code was not yet safe to touch, then sealing the packet beside the laptop.

A project now needs a chain of custody

The workaround is to divide one long assignment into numbered handoffs. Each fresh session receives a compact history of what happened before, what failed and what the previous session was about to do. The method has made continuity possible, although it has also turned a two-hour coding task into a relay race staffed by one engineer and several increasingly suspicious summaries.

I used to pay for the tool so the project could continue while I slept. Now I pay so I can explain to it what happened while it was asleep.

A paid Codex subscriber

At one small software studio, the handoff has become a job in everything but name. A senior engineer now opens each morning by checking the bags, rejecting two stale versions of the same instruction and confirming that the newest session has not mistaken a workaround for a requirement.

By the end of the week, one project had accumulated eleven bags, three duplicate introductions and a single working build. The team moved the build to a separate machine and stopped opening it, deciding that the safest way to preserve its context was to leave it undisturbed. The only part of the project to survive every reset was the monthly charge.