How it works
Why Claude Code forgets your “later”
You said it clearly: “we still need to update the README.” Two hours later nobody remembers. Not you, not Claude. It is not carelessness. It is how a chat works.
1. Compaction keeps the big picture
When a Claude Code session gets long, the conversation is compacted: the history is replaced by a summary so there is room to keep working. A summary keeps the main thread. A side remark like “later we should…” is exactly the kind of detail a summary leaves out.
2. /clear starts from zero
/clear gives you a fresh context, which is often the right move. But everything that lived only in the chat goes with it, including the plan you just agreed on.
3. Early instructions fade
A rule you set in message 12 has to compete with everything that came after it. By message 94, the newest messages carry the most weight, and the early “don’t ship before X” is easy to lose.
4. Every session is its own island
A second terminal, a restart, a new morning: each session begins without the open ends of the last one. The only place they still exist is your head.
The fix is simple: open tasks must not live only inside the chat.
What Kanbanbar does about it
- Catch. After every answer, Kanbanbar reads the turn and files what is still open, without duplicates.
- Keep. The list lives outside the conversation, per project, mirrored to a Markdown file. It survives compaction,
/clear,/resumeand restarts. - Remind. The open list rides along with every prompt you send, so Claude has it in mind before it answers.
- Confirm. Claude can mark a task done, but it stays struck through until you press ✓ Yes, done.
Every open task, right above your prompt.
Get Kanbanbar →