Skip to content

Remove unnecessary OpenAI and AssemblyAI references#2

Open
R4ph-t wants to merge 1 commit intomainfrom
cleanup/remove-openai-assemblyai-refs
Open

Remove unnecessary OpenAI and AssemblyAI references#2
R4ph-t wants to merge 1 commit intomainfrom
cleanup/remove-openai-assemblyai-refs

Conversation

@R4ph-t
Copy link
Collaborator

@R4ph-t R4ph-t commented Feb 20, 2026

Summary

  • Remove misleading API key references: Removed OPENAI_API_KEY and ASSEMBLYAI_API_KEY from docker-compose.yml and all docs, since all LLM/STT calls go through LiveKit Inference and don't require separate provider keys.
  • Update branding: Replaced OpenAI/AssemblyAI brand names with "LiveKit Inference" in the UI (page.tsx, layout.tsx), README.md, QUICK_START.md, AGENT_README.md, and render.yaml.
  • Update Next.js: Bumped next and eslint-config-next from 16.0.1 to 16.1.6.

Why

Users only need LiveKit credentials + a Rime API key. The old references to OpenAI and AssemblyAI keys/branding created confusion about what's actually required to run the demo.

Test plan

  • Verify docker-compose up works without OPENAI_API_KEY or ASSEMBLYAI_API_KEY in .env
  • Confirm the web app loads and displays "LiveKit Inference" instead of "OpenAI" in the header and footer
  • Verify the agent connects and responds to voice input
  • Grep the repo for OpenAI and AssemblyAI — should return zero results outside package-lock.json

All LLM, STT, and TTS calls go through LiveKit Inference — users only
need LiveKit credentials and a Rime API key. This commit removes
misleading references to OpenAI and AssemblyAI API keys and branding
across the codebase so the demo setup is clear and friction-free.

Changes:
- Remove OPENAI_API_KEY and ASSEMBLYAI_API_KEY from docker-compose.yml
- Replace OpenAI/AssemblyAI branding with "LiveKit Inference" in UI,
  meta tags, README, QUICK_START, AGENT_README, and render.yaml
- Update agent.ts pipeline comment to reference LiveKit Inference
- Update Next.js to 16.1.6 and eslint-config-next to match
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant