of people don’t get enough uninterrupted focus time.
Meeting mein bola.Repo mein bana?
A voice teammate for engineering teams. It remembers what was decided, asks the lead when it isn’t sure, and opens the exact line of code. Every answer comes with its source.
- Team MemoryWhat the team decided←
- Leader DeskAsk the lead↑
- Code NavigatorFind it in the code→
“Code freeze kab hai, 3:30 ya 3:45?”
That was only proposed, not confirmed. I won't guess. Want me to ask Charan, the lead?
Meetings end. Doubt doesn’t.
A decision gets spoken, never written down properly, and an hour later three people remember three different versions. These are the numbers behind that feeling.
of the workday goes to meetings, chat and email.
say next steps are unclear when a meeting ends.
of developers spend 30+ minutes a day searching for answers.
Every team runs the doubt loop. Nobody owns it.
The decision was spoken, then never written down properly. The code changed, but nobody checked which commit. The one person who knows is busy. So people guess, and guesses ship.
- Meeting ends“Someone will own it.”
- Slack ping“Wait, who owns this?”
- WaitingThe lead is in 4 meetings
- A guess“I think it was merged.”
- ReworkWrong commit, old CI
Wispr hears it. The evidence decides it.
Half-sentences and Hinglish are fine. What you say is cleaned up, matched to a decision or a function, checked against fixed rules, and only then answered.
Where you look decides who answers.
Turn left, face front or turn right with AirPods, a webcam or the arrow keys. A turn only picks the agent. You still choose when to talk.
“Code freeze kab hai, 3:30 ya 3:45?”
That was only proposed, not confirmed. I won't guess. Want me to ask Charan, the lead?
One desk to check that the whole team got it.
Ask the Leader Desk once. It calls each teammate through Bolna to confirm they understood, and walks the code graph to show what actually changed in the repository since the meeting.
- Calls, not reminders. Each teammate hears the decision and confirms it in their own words.
- Follow-ups come back to you. Open questions land in your inbox, never as a guess.
- The code is the proof. The graph walk ends at the exact lines that changed, with the test that covers them.
export async function persistVerifiedUpdate(task: Task) { const ci = await checks.forCommit(task.sha) if (!ci.green) return { saved: false, reason: "CI not green" } const saved = await store.write(task) return store.readBack(saved)From “not sure” to a sourced answer.
Unknowns become a question for the lead instead of a guess. The answer comes back with its source, even if you hung up in the meantime.
Confident is easy. Correct is the product.
Six questions where a general chatbot sounds helpful and is wrong. Each refusal below is a rule in the code, with a test.
“Kahan hai?” gets a line number.
Code Navigator walks the repository graph to a file, a function and the nearest test, pinned to one commit.
Measured, not guessed.
Numbers from our own repository and our own calls. Read them as a regression guard, not a public benchmark.
Code search
Right function in the top 3 · 28 questionsHeld-out set of 12 questions never used for tuning: 33% vs 17%. Full eval
Tests on every push
GitHub Actions, 15 Nov · 0 failuresEvery call, evaluated
7 Bolna attempts · 45 s quality gateThe 94 s call ended with a voice-provider error. Each call has a written review. Open call evals
Sources in. Evidence out.
Wispr supplies reviewed passages from one approved meeting, GitHub supplies commit-pinned code. Fixed rules decide status; the language model only explains.
Works now
- Evidence engine, three agents, leader escalation with read-back
- Live GitHub reads: PRs, changed files, check runs
- Bolna runtime tools over HTTPS, tested with fixtures
- AirPods motion companion and webcam controls with calibration
Next
- Verify the voice path in a real call
- Three consented phone calls longer than 45 seconds
- Passkey checks on real devices
- Optional realtime sync once tests match
Stop guessing what the team meant.
Open the workspace, connect a repository and ask your first question.