You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit eb8e447
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): Codex threads open in another client are no longer silently replaced
When Codex refuses to resume a thread because another client (the Codex
app, the CLI, or an IDE extension) still holds its writer lock, T3 treated
it like any other resume failure: it started a fresh native thread and
handed it a summary of the conversation. The user saw no sign of the
switch, the native history was abandoned, and the other client kept
working in the original thread.
The Codex adapter now reports that conflict as a typed
ProviderAdapterThreadInUseError, and turn start fails the run with a
message that says which client to close, instead of falling back. Once
the other client lets go, the next send resumes the same native thread.
Copy file name to clipboardExpand all lines: apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.ts
+28-8Lines changed: 28 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -338,6 +338,21 @@ function normalizeCodexCause(error: unknown): unknown {
338
338
returnerror;
339
339
}
340
340
341
+
constCODEX_THREAD_IN_USE_MESSAGE=
342
+
"This conversation is open in another Codex client, such as the Codex app, the Codex CLI, or an IDE extension. Codex lets one client write to a conversation at a time. Quit that client, then send your message again.";
0 commit comments