Support
Help with setup, recording, and troubleshooting the Eyekit beta.
Before you record
- Create an Eyekit account, open the extension settings, and choose “Sign in and connect.” Approve the device in the browser handoff; no token or Groq API key is required.
- Grant microphone permission when Chrome asks. Eyekit works on ordinary HTTPS pages; browser-internal pages and some restricted pages cannot be recorded.
- Use the shortcut saved in Eyekit settings. If an old action shortcut opens the popup unexpectedly, clear it in
chrome://extensions/shortcuts.
If a session is empty
Check that the correct microphone is selected and your account is connected in extension settings. If the free allowance is exhausted, upgrade from the account page. Stop the recording after speech finishes so the last audio chunk can be sent.
If screenshots are unexpected
Screenshot capture is part of every session and records visible content in the recorded browser tab. Avoid recording pages that show information you do not want in the session files. Screenshots are stored with each saved session. Session downloads contain session.json and frames/*.jpg in one ZIP. Deleting a downloaded ZIP does not remove the copy in the extension. This version keeps session files browser-local; earlier hosted copies require a separate support request and approved cleanup.