session refresh handler
await refreshSession(session);
return updatedSession;
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
“Why did we move token refresh out of the frontend?”
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.
session refresh handler
await refreshSession(session);
return updatedSession;
Git commit
move refresh to backend
Frontend refresh removed; session handling moved server-side.
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
Choose a local project folder. Howdunnit indexes its code, Git history and available Claude Code conversations.
my-project /
src / workers / email-worker.ts
.git / dead-letter queue change
Claude Code / retry-limit discussion
Howdunnit traces the worker’s retry logic through its Git changes and available Claude Code conversations, then links the explanation to each source.
Someone asks a technical question. Howdunnit picks it up from meeting audio and brings the answer into your private floating overlay, with sources you can check. Screen-capture Privacy Mode is controlled in the app.
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.
Leave your email and we’ll let you know when the free, open-source Windows alpha launches.
Launch notifications only. No newsletter and automated emails.