LEGACY SUB-CHATS

Open 💬 1 comment Opened Jun 11, 2026 by faction-hash

What version of the Codex App are you using (From “About Codex” dialog)?

26.608

What subscription do you have?

General access

What platform is your computer?

Microsoft Windows NT 10.0.22000.0 x64

What issue are you seeing?

After recent update, the main chat panel work perfectly fine, and creating new sub-chat works perfectly. However, opening any older older sub-chat thread results in a permanently blank or rather frozen right side bar.

What steps can reproduce the bug?

  • Update the codex desktop app to the June 9th build
  • Open any legacy project thread that contains past agent execution logs or sub-chats
  • Observe the right sidebar panel (Agent allocation explorer
  • The panel opens, the top snippet of the first chat string renders correctly, proving the app can access the basic thread entry. however, the component immediately crashes directly below that line when attempting to parse the legacy subagent chat, goal state, rendering nothing but an empty container for the rest of the panel.

What is the expected behavior?

The side bar should hydrate properly, reading the historical layout state and displaying the existing subagents logs, goals and thread history.

Additional information

It appears be a schema migration failure or a UI state hydration bug ('#26157' style layout lockup). The new update's layout engine fails to map legacy 'sidebar-project-thread-orders' keys in the local SQlite/JSON state, causing an unhandled null pointer that crashes the rendering of the sidebar component. Wiping local UI cache temporarily resets the layout but does not fix the underlying backward compatibility break for old threads.
New findings;Legacy sub-agent thread hydration crashes the Agent Allocation Explorer because the June 9 schema parser is not backward-compatible with older sub-agent execution/goal metadata. Resuming the legacy sub-agent partially migrates the chat into the new format, but the migration does not preserve or reattach the existing thread_goals record, causing the goal to disappear even though the chat becomes readable.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗