You said “later.” The summary didn’t.
Long sessions get compacted. The summary keeps the big picture and drops the side notes. Your “later” was a side note.
The “let’s do that later” from two hours ago. The step that got skipped. The plan that one /clear wiped out. Kanbanbar catches every open task in your chat and pins it right above your prompt, where neither you nor Claude can lose it.
Nobody decides to forget. It just happens, somewhere between message 12 and message 94. You have been there.
Long sessions get compacted. The summary keeps the big picture and drops the side notes. Your “later” was a side note.
You cleared to get a fresh start. The plan you spent an hour on went with it.
Claude says done with full confidence. Two of three things happened. Nobody kept count of the third.
The longer the session, the less weight early instructions carry. The rule you set this morning fades by the afternoon.
A restart, a new day, a second terminal. Every session starts fresh, and the open ends live only in your head.
And you get angry. At the AI, at yourself, at the hour you now spend digging through old chats.
Kanbanbar listens to every turn, writes down what is still open, and keeps it on a rail above the prompt. It survives compaction, /clear, restarts and new sessions. Claude reads the list before every answer. You only confirm what is really done.
Click “show all” and the rail opens into a full board. Backlog for later, Up next for now, Done for what you confirmed.
After every answer a small model reads the turn and files what is still open. No duplicates, and nothing you deleted comes back.
One click on ▶ start moves a task to Up next and hands it to Claude as the next prompt.
Claude checks a task off when it is finished. It stays struck through until you say yes. Only you close tasks.
Kanbanbar works without a single command. These habits get the most out of it.
“We still need to…”, “don’t forget…”, “after this…”. Kanbanbar files it. No syntax, no commands.
Check the rail, run /clear, keep going. The list stays, and Claude picks it up on the next prompt.
No retyping. Start hands Claude the task as its next prompt, with its number, so the check-off lands on the right card.
Claude marks a task done. You press ✓ Yes, done only after you saw it. ↺ Not done yet puts it back.
“show all” before the first prompt of the day: what is up next, what waits, what Claude says is done.
▶ Summary reads the last answer aloud while you look at the diff. The 📂 links open what Claude made.
Every answer as a short spoken summary or in full, with Markdown turned into plain speech. Play and stop sit right in the rail. Or let every answer read itself.
/clear, /resume, restarts and compaction.Every open task, right above your prompt. In every session, after every /clear.