Files
orca/docs/reference
Brennan Benson 4827f1b456 fix(native-chat): name structured Codex chat tabs from their own session
Structured app-server chat tabs kept the generic "Codex Chat" label while an
equivalent terminal-backed Codex tab picked up the name Codex writes for the
thread, so several open chats were indistinguishable.

Routes structured chats into the existing AI Vault tab-title pipeline rather
than adding a second title source: the host publishes the session's Codex
thread id (`RuntimeMobileSessionAgentTab.providerSessionId`, the head of the
record's provider-handle chain) as identity only, and the renderer's existing
title sync resolves the name against the host that owns the session and writes
it to the same `aiVaultTitle` slot terminal Codex tabs use. Precedence,
refresh cadence, remote host routing and persistence therefore come from the
pipeline unchanged — a manual rename still outranks the provider name, and a
generated title still does not.

Absence stays unknown: the thread id is omitted until the provider proves one,
a late-proven thread reaches clients through a republished snapshot, and the
mirror now preserves the client-owned `customLabel` and `aiVaultTitle` it was
overwriting on every snapshot, which is what made a rename vanish and would
have blinked a named tab back to the generic label.
2026-08-29 18:57:58 -07:00
..