---
title: Voice History
---

# Voice History

## What it is

Viewable, persisted history of the user's voice conversations, in the Omniscio sidebar group. It keeps every hands-free and per-session voice exchange so you can revisit what was said.

## Where to find it

The **"Voice History"** entry sits in the Omniscio sidebar group and opens a recency-ordered list of past conversations. It appears when the `voiceHistorySidebarEnabled` setting is on, so if you do not see it, search Settings for "voice history" and turn it on.

## How it behaves

### Two kinds, one list

- **Omniscio Voice** — the general hands-free assistant (Voice Layer 2, Cmd+Shift+L). App-level: stored with no session link even if a session was on screen.
- **Session Voice** — conversations about a specific session (Layer 3 ask-about-a-thread, Layer 4 ask-the-live-agent). Linked to that session; the row is badged `Session Voice - <session name>`.

Both kinds appear in one "Voice History" list, distinguished by a badge. The voice layers themselves are documented on the Voice & TTS page.

### What you see and do

- **Sidebar entry "Voice History"** (Omniscio group) — a recency-ordered list of past conversations.
- **Filter** by type: All / Omniscio Voice / Session Voice.
- **Open** a conversation to see its individual turns; **Retry** re-loads it if a fetch hiccups.
- **Delete** a conversation — its spoken-transcript rows are **immediately and permanently erased** (F097/F145: a privacy delete of spoken content should not linger in a recoverable window), and it drops out of the list.
- The list **live-refreshes** as new voice turns are captured, so an in-progress voice chat shows up without a manual reload.

### How it is gated

Shipped feature, controlled by the `voiceHistorySidebarEnabled` setting (search Settings for "voice history"). The sidebar entry appears when it is on.

## For agents

### How it is stored

Two SQLite tables (`voice_conversations`, `voice_turns`). A user-initiated delete **immediately hard-erases** the rows (both the Voice History viewer and the CLI `DELETE /voice/history/:id` route go through `hardDeleteVoiceConversation`), so the verbatim spoken transcript does not survive in the `.db` or a backup after the user deletes it. Each completed voice turn is recorded best-effort at the source (the L2 orchestrator and the L3/L4 handlers) via `voice-history-recorder` — a DB hiccup never breaks a live conversation. The conversation title is derived from the first user utterance; the session name is resolved at read time so history survives a deleted session (falling back to the stored title).

## Related

The voice layers this history records, including the hands-free assistant and the ask-about-a-thread flows, are documented on [Voice and TTS](voice-and-tts.md). The per-session voice conversation this list keeps under a Session Voice badge is described on [Session voice](voice-l3-session-voice.md), and the command that speaks an answer back to you is on [Voice report back](voice-report-back.md).