For when you don't know how you dunnit.

Your team wants you shipping at AI speed. Then comes “quick question”, and suddenly you’re expected to remember every implementation detail.

Howdunnit reads all relevant context to help you answer during meetings. Answers appear in your private floating overlay.

Free & open source Windows alpha coming soon

In the meeting
“Why did we move token refresh out of the frontend?”
howdunnit Your private overlay

“Multiple tabs were refreshing the same session at once and causing intermittent logouts. Refresh now runs in the backend so those requests can be coordinated.”

Code session refresh handler Commit move refresh to backend Claude Code debugging multi-tab logouts

The code tells you what changed.
The conversation tells you why.

There was the first approach. Then the fix. Then the fix for the fix. Howdunnit brings your code and available coding conversations together, so you can explain how you got here without digging through old chats mid-meeting.

Claude Code conversation

“Two tabs can refresh the same session at once. That race is what’s causing the intermittent logouts.”

debugging multi-tab logouts

What the evidence explains

“Refresh moved to the backend so simultaneous requests can be coordinated.”
Implementation + change + reason

How it works

Connect your project

Choose a local project folder. Howdunnit indexes its code, Git history and available Claude Code conversations.

Your project. Your machine. Your call.

Pick your AI provider. Bring your own keys. No Howdunnit account required.

Free, open-source software. Your AI and transcription providers may charge for usage.

Your PC
Project code + available history
Local index
Your AI provider Selected redacted excerpts + your question
Your transcription provider Meeting audio, while listening Get participants’ consent before transcribing.