Cluely

Build a local desktop AI overlay assistant called "Peek". Stack: Electron 30 with TypeScript, Vite for the renderer, no framework beyond plain TS and CSS. Target macOS first, keep Windows paths behind a small platform module. Everything runs locally except LLM calls. Behavior: 1. On launch, create a frameless, transparent, always-on-top BrowserWindow, 420x520, positioned top-right of the primary display. No dock icon, no menu bar item beyond a tray icon with Quit. 2. Set the window to ignore mouse events by default; hold a modifier hotkey to make it interactive. 3. Global hotkeys: Cmd+Shift+Space asks a question from the current context, Cmd+Shift+H toggles visibility, Cmd+Shift+Enter follows up in the same thread. 4. On ask: capture a PNG of the active display via Electron desktopCapturer at max 1600px wide, grab the last 30 seconds of rolling audio transcript, and send both to the model. 5. Audio: capture from a configurable input device using the renderer's MediaRecorder in 5 second chunks, transcribe each chunk with OpenAI whisper-1, keep a rolling 60 second transcript buffer in memory only. Never write audio to disk. 6. LLM: call the OpenAI chat completions endpoint with a multimodal message (screenshot plus transcript plus user intent), stream tokens into the overlay. System prompt: answer in under 60 words, lead with the answer, bullets only when listing, no preamble. 7. Attempt screen-share exclusion: call setContentProtection(true) on the window, and on Windows use the SetWindowDisplayAffinity equivalent flag. Print a startup warning in the console that exclusion is best effort and must be verified manually. 8. Settings: a small JSON config at userData/config.json for model name, input device id, hotkeys, and transcript window length. No settings UI beyond a tray menu item that opens the file. In scope: the overlay, hotkeys, screenshot capture, rolling transcription, streaming answers, tray quit, README with macOS permission steps and BlackHole routing instructions for capturing other-party audio. Out of scope: accounts, login, cloud sync, telemetry, analytics, auto-update, code signing, mobile, browser extension, meeting integrations, transcript persistence, any database. Secrets: OPENAI_API_KEY in .env, loaded in the main process only. Never expose the key to the renderer; proxy all API calls through IPC. Commit a .env.example. Deliver: working npm scripts dev and build, a README with a 60 second setup, and a HONESTY.md file listing what will break, starting with screen-share invisibility and audio device routing.