[Bug]: Imported Codex conversation stays stale after continuing it in Codex

[nojeans]

What happened

I'm trying to use T3 and Codex for the same ongoing conversation. I don't want to copy the chat or start over every time I switch apps.

After importing a Codex conversation into T3, I continued it in Codex. When I came back to T3, that part of the conversation was missing. I also ran into this after the conversation had already been continued from T3.

I found #27581, which mentions stale imported history, but it is marked completed. I'm reporting the narrower continuation case here, with a local workaround we tested.

Steps to reproduce

1. Import an existing Codex conversation into T3.
2. Continue the same native conversation in Codex and wait for the answer to finish.
3. Return to the imported conversation in T3 and compare the messages.
4. Also check this after the conversation has had turns from both apps.

Expected behavior

The existing conversation should pick up the new completed messages, without creating another chat or repeating old messages. If imported history is intentionally a snapshot, that limitation needs to be clear before I continue it.

Actual behavior

T3 showed an older version of the conversation. Waiting did not bring the missing part into view.

Environment

Windows; T3 Code Beta 0.1.6; Codex app-server/CLI 0.166.0.
Area: apps/server. Impact: missing context when switching apps.

What helped locally

With Codex's help, I tried a local patch that appends completed native turns through T3's event sink and refreshes before sending another message. It handles conversations with existing T3 runs as well as untouched imports. Native IDs prevent repeated imports, and a transaction checks that the active conversation hasn't changed or started running meanwhile.

In an isolated T3 → Codex → T3 test, the external turn appeared in T3, the native conversation ID stayed the same, and repeated refreshes didn't duplicate messages.

This is still a workaround, not a finished upstream patch: it only syncs completed message text, not all tools or attachments. Older divergent history and failed pre-start runs need more careful reconciliation. But it made this workflow usable for me, so I wanted to share the approach.

The investigation and patch were done with Codex; I checked the resulting workflow myself. No private conversation or raw database files are attached.