Skip to content

Persist names for paginated threads - #34229

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/5ac4dfa2a83682b43d59ecc87e0f515580164dca
Jul 19, 2026
Merged

Persist names for paginated threads#34229
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/5ac4dfa2a83682b43d59ecc87e0f515580164dca

Conversation

@copyberry

@copyberry copyberry Bot commented Jul 19, 2026

Copy link
Copy Markdown

Persist names for paginated threads

Why

Paginated threads need explicit user-facing names to remain distinct from
derived titles and previews without requiring rollout metadata writes.

What changed

  • Add a nullable name column to persisted thread metadata and use it as the
    canonical name for paginated threads.
  • Route paginated name updates through the state database while retaining the
    name index as best-effort compatibility data and preserving legacy thread
    behavior.
  • Return persisted names when reading, listing, searching, and resuming
    paginated threads, and include them in state-database search matching.

Testing

  • Cover paginated name updates, reads, list/search results, and metadata-only
    resume behavior, including stale or unavailable compatibility data.

## Why

Paginated threads need explicit user-facing names to remain distinct from
derived titles and previews without requiring rollout metadata writes.

## What changed

- Add a nullable `name` column to persisted thread metadata and use it as the
  canonical name for paginated threads.
- Route paginated name updates through the state database while retaining the
  name index as best-effort compatibility data and preserving legacy thread
  behavior.
- Return persisted names when reading, listing, searching, and resuming
  paginated threads, and include them in state-database search matching.

## Testing

- Cover paginated name updates, reads, list/search results, and metadata-only
  resume behavior, including stale or unavailable compatibility data.

GitOrigin-RevId: 5ac4dfa2a83682b43d59ecc87e0f515580164dca
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/5ac4dfa2a83682b43d59ecc87e0f515580164dca branch from 7c9dce4 to 5a208c1 Compare July 19, 2026 21:14
@copyberry
copyberry Bot merged commit 5a208c1 into main Jul 19, 2026
32 checks passed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/5ac4dfa2a83682b43d59ecc87e0f515580164dca branch July 19, 2026 21:15
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants