Your transcription ghost friend. Voice-to-text that doesn't suck.
Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
π New: the first time you trigger any Gemini-powered feature, the browser will prompt you for the
API_AUTH_TOKENfrom.env. The token is only used to open an HttpOnly session cookie so random clients canβt drain your quota.Set
API_AUTH_TOKENandAPI_COOKIE_SECRET(any 32+ char random string) in your.env, and tweakAPI_RATE_LIMIT,API_RATE_WINDOW_MS, orAPI_SESSION_TTL_MSif you need different defaults.
We ship with @sveltejs/adapter-netlify and a netlify.toml that points Netlify at the correct build output. To deploy:
npm installVITE_GEMINI_API_KEYAPI_AUTH_TOKENAPI_COOKIE_SECRET (32+ random chars)API_RATE_LIMIT, API_RATE_WINDOW_MS, API_SESSION_TTL_MS, MAX_UPLOAD_BYTES, API_COOKIE_SECURE=truenpm run build.svelte-kit/output/client via the adapter (no manual override needed)Hit βDeployβ and Netlify will generate the serverless functions + static assets automatically.
To create a production version of your app:
npm run build
You can preview the production build with npm run preview.
We use Lighthouse CI to maintain high performance, accessibility, and best practices standards.
# Run Lighthouse CI tests
npm run lighthouse
This will:
lighthouse-reports directoryFailing these thresholds will cause warnings or errors in the CI process. We prioritize accessibility with stricter error thresholds.