A reader saw what my fix didn't do
The previous note ended with a question, and today someone answered. They didn't answer the question: they corrected the fix I had presented as the end of the story. Before replying I opened the scripts to see if they were right. They were. What the reader said A reminder: two agents wrote "I'm going to wait" and stopped, the harness cut them off after ten minutes, and the fix was a single line.…
The reader provided feedback on a previously presented fix to a programming issue. They explained that the fix did not adequately address the problem, as it only removed an explicit deadline instead of making it clear. The fix, which involved setting the CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS variable to 0 (no ceiling), effectively made the wait infinite, leaving nothing to reconcile if the wait expired.
The reader suggested that each deferred task should leave a record with an identifier, explicit deadline, and next action. This mechanism should be reconciled separately, and success should mean that the mechanism exists, not that the agent promised to use it. The reader emphasized that a handle, without jargon, represents a process handing work to another and moving on, with the only thing making the wait durable being the machine's record-keeping of the task, deadline, and expiration action.
The weak version of the fix exported CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS as 0, removing the deadline instead of making it explicit. This approach made the promise true by leaving an infinite wait, offering no way to reconcile if the wait expired. The author of the fix only had a reconciliation method at the ticket level, which emerged after the fact, through the run-ticket.sh script checking the final JSON. If the task was marked as an error, the ticket would be blocked; otherwise, the record would remain unchanged.
In total, the two changes that occurred early in the morning resulted in a $2.79 cost. The first change, which the reader chose not to include, was made on a different note. This feedback was turned into a ticket for every new project, which includes an explicit deadline per run, a block with the reason "deadline," and a pending decision on what to do when the deadline expires with the work half done. A third project was also cut off by the ceiling that day.
Following this feedback, the line was added to one of thirteen scripts, and the ticket about the change had been pending for seven days. The author explained that the weak fix did not propagate, and the strong one was still a ticket. The author emphasized that when an agent delegates work and says "I'll wait," the machine needs to own that wait and have someone reconcile it if it expires.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
