optionOS optionOS
← All updates
Mac

Speech flow and the source of captured content are now visible

optionOS now shows conversation order, the current word during playback and the source of captured content directly. The terminal agent and voice turns remain separate targets, the played word advances through the tra…

optionOS

optionOS now shows conversation order, the current word during playback and the source of captured content directly. The terminal agent and voice turns remain separate targets, the played word advances through the transcript, and a captured agent or file appears with the app it came from.

The terminal agent and every voice turn have separate rows

The terminal agent keeps its own identity, while each conversation turn is separated as voice 1 or voice 2. Click the editing action beside a voice turn to open and edit that voice in the editor. The bar stays simpler, and the action you want no longer sits behind a combined intermediate layer.

The optionOS bar showing a Claude Code terminal agent, separate voice 1 and voice 2 rows, and the voice editing action Terminal agent — the detected agent identity has its own rowVoice turn — voice 1 and voice 2 are separate targetsEdit — opens the selected voice in the editor
·
Terminal agent

the detected agent identity has its own row

Terminal agent — the detected agent identity has its own row
The terminal agent, conversation order and editing action are now readable as separate targets in the same bar.

The transcript follows each word while a recording plays

When you play a voice recording, the word you are hearing is highlighted in the transcript. The highlight advances word by word with playback, so you do not lose your place in the text during a long conversation.

Blue highlight following the currently spoken word in the optionOS transcript player
As audio advances, the transcript highlight follows the word being heard.

A terminal agent appears with its source app

When optionOS captures an agent running in Ghostty, the agent identity and terminal source appear in the same row. You can read which terminal session the captured agent came from directly in the panel.

Agent session in Ghostty and an optionOS capture row showing Codex with its Ghostty source Agent session in the terminalAgent identity and Ghostty source
·

Agent session in the terminal
The captured agent appears with its identity and source terminal app.

A captured file appears with its name and editor

Content captured from VS Code appears in the same row as its filename and VS Code source. Markdown, Package.swift and JSON filenames carry the same source relation. For now this information is visible only in the interface; it is not sent to AI as additional file context.

The open 13-july.md file in VS Code and an optionOS capture row showing the filename with its VS Code source File open in VS CodeFilename and VS Code source
·

File open in VS Code
A captured file appears with its name and the editor it came from.