Skip to content

[Windows][Voice] Empty voice placeholder cannot be archived after no rollout found #37058

Open
Open
[Windows][Voice] Empty voice placeholder cannot be archived after no rollout found#37058
Labels
appIssues related to the Codex desktop appbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

Description

@wlhjkl
wlhjkl
opened on Aug 5, 2026

Summary

On Codex Desktop for Windows, an empty voice-chat placeholder remains visible but cannot be archived or cleaned up. Opening/resuming it reports:

恢复对话失败
no rollout found for thread id 019fd0da-db57-75d1-a135-f1a1bfacdff6

Environment

  • Codex Desktop version: 26.730.8199.0
  • Platform: Windows x64
  • Session source: Voice Chat

Evidence

The affected ID is not a normal materialized conversation. The thread read operation reports:

thread 019fd0da-db57-75d1-a135-f1a1bfacdff6 is not materialized yet; includeTurns is unavailable before first user message

Attempting to archive it returns:

Inactive thread archive did not persist

The empty placeholder therefore remains stuck in the conversation list and repeatedly produces the resume error.

Expected behavior

If a voice session has no first user message or no rollout, Codex should automatically discard/retire the placeholder, or provide a reliable cleanup action. Archive/delete should not fail because the rollout is missing.

Related

This appears related to #33120, which reports archive failures for unmaterialized Codex tasks.

No transcript, local logs, project files, or account data are attached.

Activity

  1. github-actions
    added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Aug 5, 2026

  2. github-actions commented on Aug 5, 2026

    @github-actions
    github-actionsbot
    on Aug 5, 2026 – with GitHub Actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. linear commented on Aug 7, 2026

    @linear
    linearbot
    on Aug 7, 2026 – with Linear

    from yos:

    FYI: it's still occurring SE-8706 and looks not the dup/fixed yet.

  4. shield-9 commented on Aug 28, 2026

    @shield-9
    shield-9
    on Aug 28, 2026

    Still reproducible on Windows x64 with Codex Desktop 26.825.3734.0 and app-server 0.150.0-alpha.12.2.

    An empty voice session created a local voice_chat catalog entry but no materialized thread or rollout. The initial cleanup logged:

    Failed to discard provisional realtime voice thread: database is locked

    Attempting to archive the placeholder later logged:

    no rollout found for thread id <redacted>
Archive skipped because thread has no active rollout
Failed to persist inactive thread archive: database is locked

    The placeholder persisted across app restarts and was also observed with Codex Desktop 26.820.9563.0. No user transcript existed.

    As a local workaround, only the orphaned catalog/timeline metadata was removed after creating a backup; the local catalog database passed PRAGMA quick_check.

    ChatGPT (the Codex agent in the desktop app) assisted with inspecting the local app logs/state, diagnosing the failure chain, and drafting this update. The user reviewed the findings and explicitly authorized this public comment. No task ID, local path, account data, transcript, or unredacted logs are included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions