User guide

1. Click Download for your platform on the home page (or visit /download directly). The site detects your OS and hands you the right file.
2. Save cue_0.1.0_x64_en-US.msi to your Downloads folder.
3. Double-click the MSI. Windows SmartScreen says “Windows protected your PC” — click More info → Run anyway. The binary is unsigned in this alpha; a code-signing cert is on the v0.2 roadmap.
4. Follow the installer. cue lands in your Start menu.

cue ships with placeholder build-time keys, so you provide your own. Keys are stored locally in %APPDATA%\cue\config.toml and never leave your machine.

1. Open cue. Click the ⚙ gear icon in the header.
2. Paste your Deepgram API key. Required for speech-to-text. Get one free at deepgram.com — they grant ~$200 in credit on signup.

   Deepgram API key:  <your-40-char-deepgram-key>

3. Paste your Override Anthropic key. Required (the placeholder built-in key is empty). Create one at console.anthropic.com.

   Override Anthropic key:  sk-ant-api03-<your-anthropic-key>

4. Click Save.

1. Click Context in the header.
2. Fill in three fields:
   • Job description — paste the full posting.
   • Resume — paste your resume in plain text (no file upload yet).
   • Role / company — short note like Staff PM, Acme Corp, Series C.
3. Click Save.

These three strings get pinned in the Anthropic prompt cache, so every answer you generate stays grounded in them without paying full token cost each turn.

Three modes. Pick the one that fits the situation.

1. Join your call (Zoom, Google Meet, Microsoft Teams, Webex, Slack Huddle, Discord, Loom — any of them).
2. Position the cue overlay where you want it. Drag the header bar to move; click the ▢ button to collapse to a small pill.
3. Click Start. The two voice-activity dots appear:
   • you — flashes green when your mic hears voiced speech.
   • them — flashes green when system audio (the other person) is talking.
4. Use cue as you would expect for the mode you picked.

Press Ctrl + \ from any application — including the call window — to hide cue. Press it again to show cue and refocus it. The hotkey is registered globally with the OS, so it fires even when cue itself isn't focused.

Three things to know:

• Position and mode are preserved across hide/show. cue picks up where you left off.
• Capture keeps running while hidden. If you toggle away mid-question in Auto mode, the answer will be waiting when you toggle back.
• On any keyboard layout where \ isn't conveniently placed, the chord can be rebound in apps/desktop/src-tauri/src/overlay/hotkeys.rs (developer-only for now; UI setting on the v0.2 roadmap).

When you're done — interview over, meeting wrapped, study session finished — click the End button in the header. A confirmation panel appears.

• Quick reset (checkbox unchecked): stops capture and wipes the transcript + answer cards. Keeps your pasted JD / Resume / Role-Company. Use between back-to-back interviews against the same prep.
• Full wipe (checkbox checked): same as above, plus blanks the Context fields. Use when you're done with a job-hunt cycle or handing the laptop to someone else.

Either way, your API keys stay safe in config.toml. The End Session flow never touches them — clear those manually via the gear if you need to.

• Your audio never leaves your machine except as streams to Deepgram (for transcription) and Anthropic (for answers). cue does not log audio, transcripts, or answers anywhere else.
• Your API keys live in config.toml only. They're not sync'd, telemetry-ed, or transmitted to any third party besides Deepgram and Anthropic when you make calls.
• Personal use only. See the license. You are responsible for compliance with local recording laws, two-party-consent statutes, and the terms of service of any platform you use cue with.
• Not invisible to webcams or remote proctoring. cue is hidden from standard OS screen-capture APIs only. Software that bypasses those APIs (some proctoring tools) and any camera pointed at your monitor will see it.