Backchannel v0.6.5
Long audio work no longer makes Backchannel look frozen. Audio imports and
Re-transcribe now run as observable background jobs, End Call reliably reaches
the completed review, and the live screen says whether recording is continuing
before explaining a connection or processing problem.
Highlights
- Audio import and Re-transcribe stay visible. Both operations run in the
background with model, progress, segment, and transcript-entry counts. They
can be canceled, and failure or cancellation keeps the transcript that was
there before the job began. - End Call finishes with transcript refinement enabled. A malformed
progress update could crash the final refinement stage and strand the
session as active. The complete post-call path now finishes and opens the
review normally. - Safe Ask requests get one local repair. If the final PII tripwire finds a
session value that should already have been tokenized, Backchannel tokenizes
the prompt again locally and reruns the tripwire. Nothing is sent if the
second check still finds the value. - Connection and processing notices use plain language. Connecting is no
longer presented as a lost connection. A real interruption leads with
"Recording paused," while slower processing leads with whether recording
continues and explains only the likely transcript impact. - The updater explains the handoff. Download update stays above the
optional release notes, and the ready state says the current window will
close, the update will install, and Backchannel will reopen automatically. - Unknown speakers stay unknown. Reaching the configured speaker-profile
limit no longer forces an unmatched voice onto the closest known speaker.
Longer unmatched turns survive as unknown instead of being mislabeled or
dropped.
Smaller improvements
- Insight cards do not claim bookkeeping-only changes were AI refinements.
- The synthesizer uses its one live event path and no longer carries dead
fallback triggers that could make its behavior and cost harder to reason
about. - The release toolchain is pinned to Node 24.x, and platform publication now
preserves useful metadata-validation errors without exposing credentials.
Upgrading
An install on v0.5.3 or later updates itself in place and verifies the new
build before applying it. An install on v0.5.2 or earlier needs one manual
download from the release page.
Nothing to migrate. Existing sessions, transcripts, recordings, and provider
settings remain in place.