Yes, an AI interview assistant can run without clicking. In CoPilot Interview, auto-answer can trigger on its own after the interviewer pauses, a new question is detected automatically after a 20-second pause in speech, and every main action has a global hotkey that works while your cursor stays in another window. In practice you can keep your hands on the meeting app or the coding editor for the whole call and only glance at the answer window.
This page lists the hotkeys exactly as they exist in version 1.3.16, explains the two automatic behaviors, and covers click-safe mode, which is the setting that makes hands-free use work in a live coding round. It also covers the one situation where hands-free is a bad idea.
Why hotkeys matter more in an interview than in normal software
In most apps, a hotkey saves you half a second. In an interview, it saves you something more visible: the moment where you stop talking, move the mouse to a second window, click, and look back. Interviewers notice that pause even if they do not know what caused it. If your cursor is in a shared coding editor, clicking another window also moves focus away from the editor, and in some meeting apps that briefly changes what the interviewer sees on the shared screen.
A desktop AI interview assistant solves this with global hotkeys: key combinations that the app registers with the operating system, so they fire no matter which window is active. You can be typing in the editor, press Ctrl+Shift+A, and the answer appears in the assistant window without the editor losing focus.
The full hotkey list
These are all of the hotkeys in CoPilot Interview. On Windows they use Ctrl; on macOS, ⌘ replaces Ctrl in every combination. There are no others, so if you memorize this table you know the whole keyboard surface of the app.
| Hotkey (Windows) | Action | When you reach for it |
|---|---|---|
| Ctrl+Shift+L | Listen / pause | Start captions at the beginning of the call; pause during small talk or a break. |
| Ctrl+Shift+A | ⚡ Answer | Ask for the structured answer now instead of waiting for auto-answer. |
| Ctrl+Shift+R | Redo | The answer missed the point of the question; regenerate. |
| Ctrl+Shift+Q | New question | The interviewer moved on and you do not want to wait for the 20-second pause. |
| Ctrl+Shift+S | Read screen | Answer what is shown in the shared coding editor or on a slide. |
| Ctrl+Shift+C | Coding on / off | Switch between code answers and spoken-style answers. |
| Ctrl+Shift+D | Debug on / off | Find bugs in code captured from the screen. |
| Ctrl+Shift+E | 🗣 Talk answer | Answer the next conceptual question in words while Coding stays on. |
| Ctrl+Shift+F | Click-safe | The window never takes focus from the app you are working in. |
| Ctrl+Shift+/ | Scroll the answer | Move down a long answer without touching the mouse. |
| Ctrl+Shift+H | Show / hide the app window | Clear the screen for a moment, bring it back when needed. |
A note on the slash key: Ctrl+Shift+/ is the one hotkey people forget, and it is the one that matters most for long answers. A system design answer can run past the visible area of a narrow window. Scrolling with the hotkey keeps your cursor where it was.
The two automatic behaviors
Auto-answer
With auto-answer on, the app waits for the interviewer to stop speaking and then produces the structured answer in about 2 seconds, key points first and then detail. You never press anything. The trade-off is that auto-answer fires on every pause, including rhetorical ones, so during a chatty interviewer's long preamble you may get an answer to a question that was not really asked. Many people leave auto-answer on for behavioral rounds, where questions arrive one at a time, and turn it off for coding rounds, where they want to choose the moment with Ctrl+Shift+A.
Automatic new question after a 20-second pause
Captions accumulate into the current question until there is a 20-second pause in speech. After that, the next thing the interviewer says starts a new question. This matches how interviews actually flow: you answer, there is a beat, the interviewer asks the next thing. If the interviewer asks a follow-up quickly, before 20 seconds have passed, the follow-up is added to the same question, which is usually what you want for a two-part question. If it is not, press Ctrl+Shift+Q and the app starts clean.
Click-safe mode: the setting that makes hands-free work
Click-safe (Ctrl+Shift+F) tells the window never to take focus from the app you are working in. Without it, interacting with the assistant window would make it the active window, which means your next keystroke goes to the assistant instead of the editor. With it on, the assistant window stays visible but keystrokes keep going to the editor you were in.
This matters most in pair-programming and live coding rounds. Picture the sequence without click-safe: you glance at the suggested code, click back into the editor to continue typing, and the editor's cursor position or the meeting app's shared window flickers. With click-safe on and hotkeys for everything else, there is no clicking at all. You type in the editor, press Ctrl+Shift+S to read what is on screen, press Ctrl+Shift+E when the interviewer asks why you chose a hash map, and never leave the editor.
A hands-free sequence for a typical technical screen
Here is how a full session can run with no mouse (example we wrote, based on how the modes work):
- Before the call, open the app, pick your language and model, turn click-safe on with Ctrl+Shift+F, and press Ctrl+Shift+L to start listening.
- During introductions, press Ctrl+Shift+L again to pause so small talk does not generate answers. Press it once more when the first real question starts.
- For behavioral questions, let auto-answer run. Read the key points, then speak. If an answer misses, Ctrl+Shift+R.
- When the interviewer shares a coding problem, press Ctrl+Shift+C to turn Coding on, then Ctrl+Shift+S to read the problem from the shared editor.
- When they ask a conceptual follow-up such as the time complexity, press Ctrl+Shift+E so the next answer comes in words, not code.
- If the answer is long, Ctrl+Shift+/ to scroll. If you want the screen clear while you think, Ctrl+Shift+H, and again to bring it back.
Once the session ends, the 📊 Summary report lists every question with category and difficulty, a scorecard, and likely next-round questions, with no further input from you.
Where hands-free use is the wrong choice
Hands-free is about removing clicks, not removing judgment. The honest limitation is that auto-answer and automatic question detection are built around pauses in speech, and some interviewers do not pause cleanly. A panel interview where three people talk over each other, or an interviewer who thinks aloud for a minute before landing on the question, will produce captions that run together and answers to the wrong thing. In those rounds, turn auto-answer off, read the caption, and press Ctrl+Shift+Q and Ctrl+Shift+A yourself when the actual question is on screen. You lose about two keystrokes of convenience and gain a lot of accuracy.
The other limit is you. A real-time interview assistant gets you a structured answer in about 2 seconds, but reading it and saying it in your own words still takes your attention. Hotkeys cannot shorten that part. The people who use the tool well treat the answer as an outline, not a script, which is why practicing with the AI mock interview first pays off: you learn how much of an answer you can absorb in a glance.
Getting the hotkeys into muscle memory
Run two or three mock interviews with the real hotkeys before an interview that matters. The mock interviewer reads each question aloud, you answer out loud, and each answer is scored out of 10 with a model answer, so you practice the keyboard and the content at the same time. Writing the eleven combinations on a sticky note next to your monitor for the first week is not a bad idea either. If you are still choosing a tool, you can compare AI interview assistants on exactly this point: whether the hotkeys are global and whether there is a click-safe option, because those two features decide whether hands-free is possible at all. For positioning the window so a glance is enough, see where to position the assistant window.
Follow the rules of the employer or assessment you're in — many people use it only to practice, which works on the free plan.
Try the hotkeys in a mock interview
Run a free AI mock interview, use the real hotkeys, and see how a hands-free session feels before an interview that counts.
Start a free mock interviewFAQ
Do the hotkeys work when the assistant window is not the active window?
Yes. They are global hotkeys registered with the operating system, so they fire while your cursor is in Zoom, Teams, Meet, a browser or a coding editor. That is the whole point: you do not have to click the assistant to use it.
What is the hotkey to get an answer in CoPilot Interview?
Ctrl+Shift+A on Windows, or ⌘+Shift+A on macOS. It asks for the structured answer right away instead of waiting for auto-answer to trigger after the interviewer pauses.
How does the app know a new question has started?
After a 20-second pause in speech, the next thing the interviewer says is treated as a new question. If you do not want to wait, press Ctrl+Shift+Q to start a new question immediately.
What does click-safe mode do?
Click-safe (Ctrl+Shift+F) means the assistant window never takes focus from the app you are working in. Your keystrokes keep going to the editor or meeting app, and the assistant stays visible beside it. It is the setting that makes a hands-free coding round possible.
Can I change the hotkeys to different key combinations?
The hotkeys listed on this page are the ones available in version 1.3.16. On macOS, ⌘ replaces Ctrl in every combination. If a combination conflicts with another app on your machine, close or adjust that app before the interview.
Is hands-free use available on the free plan?
Yes. The free plan includes all modes and the full hotkey set, with 15 minutes a day in sessions of up to 15 minutes and no signup or credit card. That is enough to rehearse the hotkeys in a mock interview before a real call.