Debug Voice
Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture...
Install
npx skills add cursor/plugins --skill debug-voice -g -a claude-code -y- Repository
- cursor/plugins15k
- Category
- Testing
- Updated
- 4d ago
- License
- See repository
- Context cost
- Mediumabout 2,997 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture what happened in a Grok realtime voice session, or a voice integration has no debug logging yet. Proposes a plan, then installs a dev-only log pipeline (client logger → local NDJSON) in the app's own language and conventions, then runs the fix loop: match the user's report to log signatures, fix one thing, re-test.
Debug Voice
Make a voice session readable after the fact, then fix from evidence. The agent cannot hear the app; the log is its ears, the user is its judge. No audio, no tokens, never in prod.
Works for any stack. The pipeline is a small contract (below); implement it in whatever the app already uses.
Workflow
- Map the app (read only).
- Plan: write the change list, show it, stop. Nothing is edited until the user aligns.
- Install the agreed pieces in the app's language, framework, and conventions.
- Verify the sink, hand the app to the user.
- Fix loop from the log.
1. Map
Find, and note the paths:
- Voice client: where realtime events are received and sent, mic capture, audio playback, token fetch.
- Server: framework, how routes are declared, where shared server code lives, how env is read, what "production" means here.
- Conventions: language(s), module system, formatter, where scripts or tasks live (
package.json,Makefile,pyproject,justfile),.gitignore. - Client kind: browser, mobile, desktop, CLI. A non-browser client still POSTs the same JSON; a single-process app can skip HTTP and append to the file directly.
- Where audio deltas are handled. They must be counted, never logged.
2. Plan, then stop
Fill this in with real paths and the app's language, post it, and wait for a yes or a trimmed list. Do not edit files before that.
## Debug voice: plan
Add
- <path>: client logger (batch, redact, flush) in <language>
- <path>: dev-only sink `POST /api/voice/log` → `.voice-logs/<sessionId>.ndjson`
- <path> (optional): summary command `<cmd>`; otherwise read the NDJSON with jq
