// Add or modify noise-reduction providers in assistant-api with denoiser factory wiring, packet safety, and UI option compatibility.
| name | noise-reduction-integration |
| description | Add or modify noise-reduction providers in assistant-api with denoiser factory wiring, packet safety, and UI option compatibility. |
Integrate denoisers that suppress background noise while preserving speech quality, low latency, and packet ordering.
If user does not answer:
In scope:
api/assistant-api/internal/denoiser/internal/<provider>/...api/assistant-api/internal/denoiser/denoiser.goapi/assistant-api/internal/type/packet.goui/src/providers/<provider>/noise.jsonOut of scope:
Input:
DenoiseAudioPacketRequired outputs:
DenoisedAudioPacket with stable context and chunk orderingNoiseReduced=falseOptional diagnostics:
ConversationEventPacket{Name:"denoise"} for provider/debug contextrn_noise, krisp).internal/<provider>/.denoiser.go factory switch.Close, context cancellation, cleanup).noise.json where needed.microphone.denoising.provider.go test ./api/assistant-api/internal/denoiser/...go test -run TestGetDenoiser ./api/assistant-api/internal/denoiser/...cd ui && yarn test providers./.claude/skills/noise-reduction-integration/scripts/validate.sh --check-diff --provider <provider>Add or modify microphone noise-reduction providers in assistant-api with denoiser factory wiring, packet safety, and option/UI compatibility.
Add or modify end-of-speech integrations in assistant-api with strict separation from VAD internals. Use for transcript/audio/history-aware turn-finalization logic, provider wiring, and EOS UI config.
Add or modify LLM/integration providers in integration-api with caller factory wiring, unified provider routing, streaming behavior, and metric/audit compatibility.
Explain and validate local setup paths for this repo with Docker and without Docker. Use when developers need exact prerequisites, startup commands, health checks, and troubleshooting steps.
Add or modify speech-to-text providers in assistant-api with transport-aware ingestion (WS/SDK/HTTP), transcript packet correctness, and UI/provider wiring.
Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level change scope for a requested integration.