01 Prompt Kanban for Claude Code

Claude forgot it.
Kanbanbar didn’t.

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.

~/projects/shop · claude
Ship the checkout fix. We still need to write the login tests later.
Checkout fix is merged. The login tests are on your backlog as #3.
Backlog 2Up next 1 · 1 to confirmDone 6▼ collapseshow all
Claude says done:#6 Fix the checkout rounding bug✓ Yes, done↺ Not done yet
#3 Write the login tests▶ start✓ done← backlog
📂 Results:📂 checkout-fix/📂 release-notes.md
🔊 Read aloud:▶ Summary▶ Read all■ Stop
Next, the pricing page
The rail
BacklogUp nextDoneRead aloud
02 Sound familiar?

Six ways a task dies in a chat.

Nobody decides to forget. It just happens, somewhere between message 12 and message 94. You have been there.

Tuesday · 10:1401 / 06
Fix the login bug. And later we still need to update the README.
Login bug fixed.
✻ Compacting conversation…
Summary: login bug fixed. README

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.

Tuesday · 11:3002 / 06
Here is the 9-step migration plan…
Great. Context is full, let me clear first.
/clear
Hi! What would you like to work on?

One /clear and the plan is gone.

You cleared to get a fresh start. The plan you spent an hour on went with it.

Tuesday · 14:0203 / 06
Add the tests, the docs and the error messages.
All done! ✓
Where are the docs?
You’re right, I missed those.

“All done.” It wasn’t.

Claude says done with full confidence. Two of three things happened. Nobody kept count of the third.

Tuesday · 16:4004 / 06
msg 12 · Don’t ship until the rate limit is in.
Noted.
· · · 81 messages later · · ·
msg 94 · Shipped to production 🚀

Message 94 forgot message 12.

The longer the session, the less weight early instructions carry. The rule you set this morning fades by the afternoon.

Wednesday · 09:0505 / 06
api ⏺ Where were we?
web ⏺ Where were we?
docs ⏺ Where were we?
…no idea.

Three sessions. Nobody kept the list.

A restart, a new day, a second terminal. Every session starts fresh, and the open ends live only in your head.

Friday · 09:1206 / 06
✉ Client: Quick question, did you update the README?
…
You scroll back. 400 messages. Nothing.

Then you find out. From the client.

And you get angry. At the AI, at yourself, at the hour you now spend digging through old chats.

03 The fix

Stop being your AI’s memory.

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.

04 The board

One rail. Three columns.

Click “show all” and the rail opens into a full board. Backlog for later, Up next for now, Done for what you confirmed.

Backlog LATER

#7found in chat
Update the README
▶ start✓ done
#8added by you
Add dark mode to settings
▶ start✓ done
#9found in chat
Rename the export command
▶ start✓ done

Up next NOW

#3started
Write the login tests
▶ start✓ done← backlog
#6Claude says done
Fix the checkout rounding bug
✓ Yes, done↺ Not done yet

Done CONFIRMED

#1today
Set up the staging deploy
#2today
Migrate the users table
#4yesterday
Fix the flaky upload test
05 How it works

Catch. Start. Confirm. That is all.

01

Catch

After every answer a small model reads the turn and files what is still open. No duplicates, and nothing you deleted comes back.

+ new #9 Rename the export command
02

Start

One click on ▶ start moves a task to Up next and hands it to Claude as the next prompt.

#3 Write the login tests   ▶ start
03

Confirm

Claude checks a task off when it is finished. It stays struck through until you say yes. Only you close tasks.

Claude says done: #6   ✓ Yes, done
06 Use it like a pro

Six habits for calmer Claude Code sessions.

Kanbanbar works without a single command. These habits get the most out of it.

01 · JUST TALK

Say “later” out loud.

“We still need to…”, “don’t forget…”, “after this…”. Kanbanbar files it. No syntax, no commands.

02 · CLEAR WITHOUT FEAR

Glance, then /clear.

Check the rail, run /clear, keep going. The list stays, and Claude picks it up on the next prompt.

03 · ONE CLICK

▶ start the next one.

No retyping. Start hands Claude the task as its next prompt, with its number, so the check-off lands on the right card.

04 · TRUST, THEN VERIFY

Confirm after you looked.

Claude marks a task done. You press ✓ Yes, done only after you saw it. ↺ Not done yet puts it back.

05 · MORNING REVIEW

Open the board first.

“show all” before the first prompt of the day: what is up next, what waits, what Claude says is done.

06 · EARS FREE, EYES ON CODE

Listen to the summary.

▶ Summary reads the last answer aloud while you look at the diff. The 📂 links open what Claude made.

07 Read aloud

Listen instead of scrolling.

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.

▶ Summary▶ Read all■ Stop
“The checkout fix is merged. The login tests are on the backlog as number three.”
08 Built to remember
Survives everythingTasks stay through /clear, /resume, restarts and compaction.
Claude keeps it in mindThe open list rides along with every prompt you send.
Per projectEach repository has its own board, mirrored to a Markdown file.
Terminal and desktopWorks in the Claude Code terminal and in the desktop app.
Kanbanbar

Never be the one who forgot.

Every open task, right above your prompt. In every session, after every /clear.

We send you the install link and a two-minute setup.
Free · MIT license · for Claude Code