fix(codex): load persisted threads only on explicit send after refusal
This commit is contained in:
@@ -66,3 +66,11 @@ It does not call `thread/resume` on open/model selection, so merely watching a
|
||||
chat cannot awaken a queued goal. Native turn IDs protect the queue/UI from stale
|
||||
completion events. A real, isolated tool-free turn passed after replacing the
|
||||
owning connection; no command, permission grant or global setting was involved.
|
||||
|
||||
An explicit Send can load a persisted thread if `turn/start` is refused with
|
||||
the exact application error `thread not found: <owned-thread-id>`. Only then
|
||||
does the adapter call `thread/resume` (metadata only, no policy/configuration
|
||||
override) and submit the original message/model/files. Transport failures and
|
||||
unrelated errors are never retried. This loading is not performed by browsing,
|
||||
history reads or model selection. As in Codex's native client, explicitly
|
||||
continuing a thread also resumes that thread's configured execution context.
|
||||
|
||||
Reference in New Issue
Block a user