Repository navigation
feat(speakers): let an owner turn voice recognition off for a namespace - #644
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QFUNzy1QZy5HhKAyJxTAYJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: every namespace kept a voiceprint for each person and matched them across recordings; there was no way to keep voices to each recording only.
After: on People, an owner can turn off "Recognise voices across recordings". Voices are still told apart inside each recording, but no voiceprint is kept and nobody is matched across recordings or namespaces. Turning it off deletes the namespace's voiceprints and the matches waiting for review (names, transcripts and who spoke when stay), so it asks once first; turning it back on recognises people in recordings diarized after that. Recognition stays on by default. Agents use
PUT /api/v1/namespaces/<ns>/voices/modeand readvoicesfromGET /speakers.How:
speakers.set_voice_modestores the mode on the namespace and deletes the voiceprints; diarization skips matching when the mode isseparate. The change is audited asvoices.mode.Motivation and Context
Item from the personal feature plan sheet (voiceprints are biometric data; let a household opt out).
Screenshots (if appropriate):
n/a
Steps to reproduce (if appropriate):
People › Recognise voices across recordings › off › Delete voiceprints.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).tests/api/test_voice_mode.py).docs/accordingly (docs/processing.md, People and namespaces).## UnreleasedinCHANGELOG.md. Written aschangelog.d/voices-off.md, per build(release): changelog fragments in changelog.d/ instead of one Unreleased section #581.Done questions (AGENTS.md)
PUT /api/v1/namespaces/<ns>/voices/mode..envedit or manual step.manage), audited; it removes biometric data rather than adding surface.recognize, so no upgrade step is needed.make openapi).Local CI (
ci/local-ci.sh): FastAPI (embedded and server), Next.js (1246 tests), pre-commit and PR title passed.Generated by Claude Code