-
Notifications
You must be signed in to change notification settings - Fork 2
Add OAI Realtime API blog post #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on January 9
Details
You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| --- | ||
| title: Building Voice Agents with OpenAI's Realtime API | ||
| description: A production-focused guide to speech-to-speech AI — architecture, typed events, and the patterns that actually matter | ||
| --- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Blog post missing required metadata export object
The new blog post uses YAML frontmatter (--- delimiters) for metadata, but the codebase expects an export const metadata JavaScript object. The getPostMetadata and getPost functions in src/lib/utils/posts.ts destructure metadata from imported MDX modules. Without a proper export const metadata object (including required fields like date, author, category, and bannerImageUrl), the post will fail to load or display correctly in the blog listing.
| 3. Control happens through JSON events on a data channel | ||
| 4. The server manages conversation state for you | ||
|
|
||
|  |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Image path resolves to non-existent location
The image path ./assets/realtime-architecture.svg is a relative path referencing a non-existent assets directory in src/lib/posts/. The SVG file was added to public/images/realtime-architecture.svg, so the path needs to be /images/realtime-architecture.svg (absolute from public) to match the pattern used by all other blog posts in the codebase.
Summary
Testing
bun run format(fails: existing lint issues unrelated to this change)Codex Task
Note
Adds a comprehensive Realtime API blog post with an architecture SVG, improves video overlay accessibility using semantic buttons, and adds a title to the app icon SVG.
src/lib/posts/working-with-oai-realtime-api.mdxdetailing architecture, WebRTC/WebSocket setup, typed events, session config, function calling, interruptions, and costs with code samples.public/images/realtime-architecture.svg.src/ui/video/video.tsx: replace overlay divs with semantic buttons for play/pause and play-with-sound; preserves behavior and improves accessibility.src/app/icon.tsx: add SVG title for accessibility.Written by Cursor Bugbot for commit 1a97f0d. This will update automatically on new commits. Configure here.