Built for the call you cannot pause
ChampAI started as a way to survive technical interviews and turned into a general assistant for any conversation where the hard question arrives out loud.
Four things we decided early
Each one came out of something that did not work.
The call is the input, not you
Early versions listened to the microphone, which fell apart the moment anyone put headphones on - the interviewer's voice never reached it. Capturing the audio the computer is already playing fixed the problem properly rather than working around it.
A late answer is a wrong answer
Anything that arrives after the silence gets awkward is useless. Reasoning is off by default, the provider connection is warmed before the question lands, and answers stream a word at a time instead of appearing all at once.
Your data stays on your machine
Your resume, knowledge base and conversations are saved only on your computer. Answers and listening run through our server on your plan's credits, so anyone can start in a minute with no API keys to manage.
Say what it cannot do
It is hidden from screen capture, not from a person standing behind you, and it is not permission to use it where assistance is not allowed. Overstating either would be the easiest way to get someone into trouble.
A web version, and signed builds
The desktop app is the product today. Signed and notarised installers come next, so the operating system stops warning about an unknown developer, followed by a browser version for machines where installing anything is not an option.