Pick up waiting AI work without digging through finished sessions

Description and use

<p><code>claude --resume</code> lets you go back to an earlier Claude Code conversation started in the same folder, by picking it from a list. The catch is that list: sessions still waiting for an answer sit beside sessions that already finished, and nothing marks which ones are still waiting. So I stopped closing waiting sessions at all.</p> <p>The problem is not specific to Claude Code. Anyone who hands work to an AI coding agent, Claude Code, Codex or another, ends up with sessions that are only waiting: for a review, for another repository, for a person. Codex has a similar <code>codex res

Problem

<p><code>claude --resume</code> lets you go back to an earlier Claude Code conversation started in the same folder, by picking it from a list. The catch is that list: sessions still waiting for an answer sit beside sessions that already finished, and nothing marks which ones are still waiting. So I stopped closing waiting sessions at all.</p> <p>The problem is not specific to Claude Code. Anyone who hands work to an AI coding agent, Claude Code, Codex or another, ends up with sessions that are only waiting: for a review, for another repository, for a person. Codex has a similar <code>codex res

Outcome

<p><code>claude --resume</code> lets you go back to an earlier Claude Code conversation started in the same folder, by picking it from a list. The catch is that list: sessions still waiting for an answer sit beside sessions that already finished, and nothing marks which ones are still waiting. So I stopped closing waiting sessions at all.</p> <p>The problem is not specific to Claude Code. Anyone who hands work to an AI coding agent, Claude Code, Codex or another, ends up with sessions that are only waiting: for a review, for another repository, for a person. Codex has a similar <code>codex res

Evidence

Pick up waiting AI work without digging through finished sessions

Source